-
Notifications
You must be signed in to change notification settings - Fork 9
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
FPWD #74
Conversation
@@ -1052,13 +1052,13 @@ <h2>Example Mapping</h2> | |||
If <code>nbf</code> is present, set the value of <code>validFrom</code> to the | |||
<code>dateTime</code> obtained by converting the value of <code>nbf</code> from | |||
the <code>NumericDate</code> described in [[!RFC7519]] to a <code>dateTime</code> as | |||
described in [[!XMLSCHEMA11-2]]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was causing a respec warning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per my mail on the list the publication date of the 20th does not work. The date should be changed to the 25th or the 27th, depending on the WG resolution
I have updated the publication date to the 27th per the request on the list. @iherman I have also attached screenshots: Link Check Tool
Pub Rules
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @OR13. B.t.w., there is no bug in the link checker: the three links are, indeed, missing at this moment, but they will fall in place as part of the publication process. Actually, the FPWD has already been published, so the second error is already moot.
The official request for publication has gone out: w3c/transitions#500 and, as far as I am concerned, this PR can be merged for historical purposes.
@brentzundel @Sakurann can I merge this PR? |
I support merging based on Ivan's comment above. |
Please merge |
I am merging at the direction of our chairs and our staff contact. |
Prepare FPWD
Preview | Diff