- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Tue, 26 Aug 2014 18:37:39 -0700
- To: Tracking Protection Working Group <public-tracking@w3.org>
On Jul 12, 2014, at 6:46 PM, Tracking Protection Working Group Issue Tracker wrote: > tracking-ISSUE-253: Section 6.4.2: restriction to "URI-safe characters" [TPE Last Call] > > http://www.w3.org/2011/tracking-protection/track/issues/253 > > Raised by: Nick Doty > On product: TPE Last Call > > 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. 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
Received on Wednesday, 27 August 2014 01:38:00 UTC