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:
  1. Resolving Last Call issues to TPE (from jbrookman@cdt.org on 2014-09-08)
  2. Re: tracking-ISSUE-253: Section 6.4.2: restriction to "URI-safe characters" [TPE Last Call] (from fielding@gbiv.com on 2014-08-26)
  3. 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:48

Display change log ATOM feed


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $