W3C home > Mailing lists > Public > public-tracking@w3.org > August 2014

Re: tracking-ISSUE-252: IRI/non-ASCII not permitted [TPE Last Call]

From: Roy T. Fielding <fielding@gbiv.com>
Date: Tue, 26 Aug 2014 18:31:43 -0700
Message-Id: <A9449A61-C0A3-4367-ABF6-70D6426DABE0@gbiv.com>
To: Tracking Protection Working Group <public-tracking@w3.org>
On Jul 12, 2014, at 6:45 PM, Tracking Protection Working Group Issue Tracker wrote:

> tracking-ISSUE-252: IRI/non-ASCII not permitted [TPE Last Call]
> 
> http://www.w3.org/2011/tracking-protection/track/issues/252
> 
> Raised by: Nick Doty
> On product: TPE Last Call
> 
> 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.

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:32:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:40:12 UTC