-
Notifications
You must be signed in to change notification settings - Fork 48
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
Editorial: prepare for REC with Candidate Amendments #430
Conversation
Note: the only exit criteria of a REC with Candidate Amendments is a group decision (a CFC), with no requirement on the duration. |
new date format for the time stamps seems an unfortunate choice for people to read, and especially to hear. could these not at least have punctuation like periods or dashes to separate the year month and day? If it "has" to be this way, then we can go ahead and merge. |
@deniak is it possible to ask the pub-rule checker to ignore the date in the content of SoTD? I agree with Scott the current date format with punctuation is more friendly to the users. |
https://www.w3.org/pubrules/doc/rules/?profile=WD#datesFormat so the pub rules suggested we can use the format 01 July 2022 in the documents (but not 01 Jul 2022), I'll modify my pull request. |
thanks @siusin. This LGTM to merge then. |
Thx! |
A new version of the REC was published today:
https://www.w3.org/TR/2022/REC-html-aria-20220927/
See w3c/echidna#1048 (comment)
The group can publish a REC with Candidate Amendments (or multiple ones) anytime before the group decides to move to REC with Proposed Amendments.
Preview | Diff