ISSUE-348: Non-ASCII not permitted in extensions

Non-ASCII not permitted in extensions

State:
OPEN
Product:
tracking-dnt
Raised by:
Addison Phillips
Opened on:
2014-05-29
Description:
Non-ASCII not permitted?? Later 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, but don't have to be).
Related Actions Items:
No related actions
Related emails:
  1. Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2017-10-20)
  2. Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2017-10-18)
  3. I18N-ISSUE-348: Non-ASCII not permitted in extensions (from addison@lab126.com on 2014-06-20)
  4. [minutes] Internationalization telecon 2014-06-05 (from ishida@w3.org on 2014-06-05)
  5. I18N-ISSUE-348: Non-ASCII not permitted in extensions [.prep-tracking-dnt] (from sysbot+tracker@w3.org on 2014-05-29)

Related notes:

No additional notes.

Display change log ATOM feed


Addison Phillips <addisonI18N@gmail.com>, Chair, Richard Ishida <ishida@w3.org>, Bert Bos <bert@w3.org>, Fuqiao Xue <xfq@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 348.html,v 1.1 2023/07/19 12:02:03 carcone Exp $