-
Notifications
You must be signed in to change notification settings - Fork 40
Publish a Candidate Recommendation Draft #488
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
Comments
It would be good to fix the cross references that are currently broken because the terms no longer exist (and notably the notion of "allowed to show a popup"). It seems ok for now to continue to reference terms from other specs that do not yet have an export flag, while we discuss a proper resolution with other groups. I'll update the PR so that it may be merged. |
@tidoust, I believe the spec is now ready for CRD publication sans metadata tuning. CfC to publish is recorded in the 20 Oct minutes and 10 working days have passed. Feel free to proceed with the CRD publication. |
And one last one around use of inclusive terminology (#493). That should be all we need. |
The spec has now been published as a Candidate Recommendation Draft at: That new version is returned when one retrieves: |
via https://www.w3.org/2020/10/20-webscreens-minutes.html#r02
Per @tidoust's post-meeting note we can publish a Candidate Recommendation Draft right away under the new process.
@mfoltzgoogle, nice to have prior to the CRD publication would be an update to the change log. Alternatively, we could link to the commit log. The former is probably a bit friendlier for readers who are not following the spec development closely.
The text was updated successfully, but these errors were encountered: