-
Notifications
You must be signed in to change notification settings - Fork 16
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
Coalesce references to URI syntax into a new <uri> value expression (… #488
Conversation
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.
Looks good to me as far as it goes, and is editorial.
However it does not include the fix to the URI reference, as proposed at #474 (comment) (or an equivalent).
@skynavga please could you merge from |
Also, the pull request shouldn't include |
@nigelmegitt regarding the request to change the normative reference for [URI] from RFC2396 to RFC3986, I am not comfortable making this change in the context of this issue, as it may have wider ramifications; can you accept this PR as is and file another issue if you want to upgrade the [URI] reference? The references in this PR are synchronized with 2396 section numbering, and not 3986. |
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.
Yes, happy to move the change of URI reference to another issue. Approving.
…#474).
Closes #474.