W3C home > Mailing lists > Public > uri@w3.org > April 2004

Re: octets <=> ASCII conversion (important)

From: Roy T. Fielding <fielding@gbiv.com>
Date: Wed, 21 Apr 2004 01:06:33 -0700
Cc: uri@w3.org
To: Martin Duerst <duerst@w3.org>
Message-Id: <CD81749A-936A-11D8-B3EA-000393753936@gbiv.com>

> However, the comment in my mail at
> http://lists.w3.org/Archives/Public/uri/2004Mar/0012.html,
> cited below, and including actual proposed text, does not
> seem to have been addressed, nor did I find any reply saying
> that or explaining why it would not need to be addressed, or
> that (and how) it has been addressed.
> So in case you think that this has been addressed, please
> tell me where/how.

Section 2.5 was added to address this confusion.  It is the same
issue that Mike Brown was discussing.  While I understand folks
desire to have a standard give answers to common implementation
questions, it is inappropriate for the standard to define what
is the right implementation when no such definition is needed
for interoperability.


> In case you decided that it does not
> need addressing, please tell me why you think so.

The specific text that you supplied is not always true.
While %31 is equivalent to "1", there is no requirement that
data octets be represented in the URI syntax using the characters
corresponding to their US-ASCII value -- they could just as easily
be encoded in HEX first.  That is up to the URI producer.

>> So please, at the appropriate place, add a sentence saying
>> something like:
>> "Data octets which in the US-ASCII character encoding represent
>> unreserved characters can be represented by the corresponding
>> character. For example, the data octet 0x41 can be represented
>> by "%41" or by "A"; for readability and comparability, the later
>> is strongly preferred."

Received on Wednesday, 21 April 2004 04:19:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:07 UTC