W3C home > Mailing lists > Public > uri@w3.org > August 2003

feedback on draft-fielding-uri-rfc2396bis-03.txt

From: by way of Martin Duerst <Daniel.Barclay@fgm.com>
Date: Thu, 28 Aug 2003 08:55:42 -0400
Message-Id: <4.2.0.58.J.20030828085537.02c37858@localhost>
To: uri@w3.org




Regarding the document at
http://www.ietf.org/internet-drafts/draft-fielding-uri-rfc2396bis-03.txt:


* "The URI syntax is organized hierarchically, with components listed in
    decreasing order from left to right."

   Should "in decreasing order" be "in order of decreasing significance"?


* "If data for a URI component would conflict with the reserved purpose,
   then the conflicting data must be escaped (Section 2.4) before forming the
   URI."

   Shouldn't "escaped" be "encoded"?

   Doesn't "escaping" refer to the characters that actually appear, and
   doesn't "encoding" refer to what is represented, especialy if it doesn't
   actually appear?

   (An escape character "escapes" from the normal meaning of a following
   character.  The special meaning of the escaped character may be to
   _encode_ some third character.

   - In the Unix shell input "echo \$PATH", the dollar sign is escaped
     by the backslash.  (The backslash escapes from the normal meaning
     of the dollar sign (encoding a "command" to subsitite a variable)
     to a special meaning (encoding an actual dollar sign character).)

   - In C, in the escape sequence "\7", the backslash changes the
     meaning of the character "7" in the source from representing the
     character "7" (in the compiled code) to representing (encoding) a
     BEL character.

   - Similarly, in URIs, the escape sequence "%20" _encodes_ a space.
     The space isn't _escaped_.  (It's not like the escaped spaces in
     "ls file\ with\ space".)

   )

- "...extends...to the first question-mark ("?"), number-sign ("#"), or
    the end of the URI string."

   probably should be:

    "...extends...to the first question-mark ("?") or number-sign ("#")
    or the end of the URI string."

   (Also, there are several similar non-parallel sentences.)


-  This:

      ...the URI <mailto:fred@example.com> has...

    would be less ambiguous if it were written with standard English
    quoting, as:

      ...the URI "mailto:fred@example.com" has...


- "URI generating applications"

    should be

   "URI-generating applications"




Daniel
Received on Thursday, 28 August 2003 16:12:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:32 GMT