ISSUE-252: IRI/non-ASCII not permitted
IRI/non-ASCII not permitted
- State:
- PENDING REVIEW
- Product:
- TPE Last Call
- Raised by:
- Nick Doty
- Opened on:
- 2014-07-13
- Description:
- http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0026.html
I18N-ISSUE-350
Section 6.3.2: The grammar doesn't allow %, so the path to the DNT value cannot include non-ASCII characters that are percent encoded. Neither can the path be an IRI or non-ASCII string value. A tracking resource might be named for some actual resource that uses non-ASCII characters in its name. Not permitting non-ASCII directly or via URI percent escapes limits what can be represented and this appears to represent a problem later for features such as requesting the status for a specific resource. - Related Actions Items:
- No related actions
- Related emails:
- Resolving Last Call issues to TPE (from jbrookman@cdt.org on 2014-09-08)
- Re: tracking-ISSUE-253: Section 6.4.2: restriction to "URI-safe characters" [TPE Last Call] (from fielding@gbiv.com on 2014-08-26)
- Re: tracking-ISSUE-252: IRI/non-ASCII not permitted [TPE Last Call] (from fielding@gbiv.com on 2014-08-26)
- tracking-ISSUE-253: Section 6.4.2: restriction to "URI-safe characters" [TPE Last Call] (from sysbot+tracker@w3.org on 2014-07-13)
- tracking-ISSUE-252: IRI/non-ASCII not permitted [TPE Last Call] (from sysbot+tracker@w3.org on 2014-07-13)
Related notes:
WONTFIX. The grammar for status-id is restricted in order to encourage a minimal token, not a human-readable name. There is no name connection (aside from the origin server root) between the status-id token and any of its corresponding designated resources.
Display change log
