-
Notifications
You must be signed in to change notification settings - Fork 4
IRI Terminology #17
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
IRI Terminology #17
Conversation
Do not suggest in any way that the WG may change core terminology to URL without the WG having agreed to that being said. |
There is no mention of "adopt the pertinent core of RFC3987". |
In re-creating the PR, this seems to have lost the more neutral text change you previously requested, I'll update. |
Closing in light of Martin's comment #15 (comment). |
Co-authored-by: Andy Seaborne <[email protected]>
@rdfguy, @ktk: in spite of the procedural issues about appropriate work items, I think this PR should be merged, as the existing text is now inappropriate. Note that this PR simply updates the issue marker to clarify that the open work item is on erratum 29 Terminology about IRIs not on the suitability of using RFC3987. |
It's worse to leave this PR unmerged than to keep the status quo, so merging. |
For #15.
Preview | Diff