-
Notifications
You must be signed in to change notification settings - Fork 0
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
2141bis: Section 3.3.2 q-component clarification #2
Comments
2015-01-21: I think this one is settled unless someone complains on-list. However, since there are two (or maybe three) substantive issues hidden in this, I have put a placeholder into the text (as of -09c) rather than changing it. Those issues are: (0) Does 3986 disallow "?" from appearing in (without %-encoding) and should we say something about that? Given that the very clear text in 3986 managed to confuse Andy and has confused a lot of others, the answers are pretty clearly "it doesn't" and "yes, we should say something". A note to that effect is now in -09c. (1) Should we disallow "?" from appearing within a even though 2141 does not require that? I think the answer is "no reason to do that", but it may be worth further confirming that with the WG.. (2) Should we say something about embedded question marks as delimiters for name-value pairs? In my personal capacity, I feel quite strongly that the answer should be "yes", but haven seen nearly enough clear support for that view to starting changing the text. See http://www.ietf.org/mail-archive/web/urn/current/msg02725.html, several notes from probably a year or more ago, and some pieces of I-Ds that I can locate and drag out if needed. |
Text has been clarified to make it clear that "?" is allowed, without encoding, within q-components (after the question mark that introduces those components) and f-components. There have been no substantive comments about any of the other issues identified above. |
Above clarifications are present in 2141bis-11. The text may need further work if q-component is subdivided, e.g., along the lines of Keith's "??" proposal, but I'm starting a separate tracker entry for that, so this one can probably be closed. |
See tracker item #13, '"Component" Information associated with URN processing versus to be passed to objects, URLs, etc.', for the "??" proposal and it context. |
From John:
The text was updated successfully, but these errors were encountered: