ISSUE-253: Section 6.4.2: restriction to "URI-safe characters"
Section 6.4.2: restriction to "URI-safe characters"
- 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/0027.html
I18N-ISSUE-351
Section 6.4.2: Use of "URI-safe characters" (non-ASCII support). Since a site may wish to associate the tracking status with specific resources and since these resources might be named using non-ASCII characters, this appears to limit usage in a non-helpful way? This is similar to our comment 350.
See also ISSUE-252. - 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)
- tracking-ISSUE-253: Section 6.4.2: restriction to "URI-safe characters" [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.
Roy Fielding, 27 Aug 2014, 01:38:48Display change log
