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

I18N-ISSUE-348: Non-ASCII not permitted in extensions

From: Phillips, Addison <addison@lab126.com>
Date: Fri, 20 Jun 2014 19:12:52 +0000
To: "public-tracking-comments@w3.org" <public-tracking-comments@w3.org>
CC: "www-international@w3.org" <www-international@w3.org>
Message-ID: <7C0AF84C6D560544A17DDDEB68A9DFB524701DA2@ex10-mbx-36009.ant.amazon.com>
http://www.w3.org/International/track/issues/348


Document: http://www.w3.org/TR/tracking-dnt


This is a WG comment.

Non-ASCII characters are not permitted in extensions. There is a note:

--
    The extension syntax is restricted to visible ASCII characters that can be parsed as a single word in HTTP and safely embedded in a JSON string without further encoding (section 6.5 Tracking Status Representation). At most one DNT header field can be present in a valid request [HTTP].
--

It's unclear why this restriction exists? Non-ASCII characters are useful in many contexts and they work in a JSON string (they can be encoded further using \u escape, but don't have to be). The limitation to ASCII-only may be helpful for other reasons, of course, but these are no spelled out. Can you clarify why extension names have a limited character set?

Addison Phillips
Globalization Architect (Amazon Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.


Received on Friday, 20 June 2014 19:13:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:37:44 UTC