Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The link to the track could be more specific #1713

Open
deniak opened this issue Mar 6, 2023 · 2 comments
Open

The link to the track could be more specific #1713

deniak opened this issue Mar 6, 2023 · 2 comments

Comments

@deniak
Copy link
Member

deniak commented Mar 6, 2023

As of today, the SOTD must mention the track the document is on and it must link to https://www.w3.org/2021/Process-20211102/#recs-and-notes whathever the track is.
As discussed in w3c/webcodecs#644, that link could be more specific, e.g.:

Such change would need to be implemented in respec, bikeshed and specberus.

@plehegar, WDYT?

/cc @tidoust

@tidoust
Copy link
Member

tidoust commented Mar 6, 2023

I note that, for registries, this is not so much about being more specific than about fulfilling the requirements imposed by the Process document, and in particular:

"The registry report [...] must [...] clearly label the registry report [...] as such, including a link to § 6.5 The Registry Track in this Process".
https://www.w3.org/2021/Process-20211102/#reg-pub

The SOTD sentence seems like a good enough place to me to "clearly label the registry report as such", but the Process document currently requires a more specific link to §6.5.

@plehegar
Copy link
Member

I'm supportive of having more specific links

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants