- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Fri, 5 Nov 2004 10:59:03 -0800
- To: uri <uri@w3.org>
> I tend to agree that this paragraph that you mentioned is not > especially helpful: > [[ > URI producing applications should percent-encode data octets that > correspond to characters in the reserved set. However, if a reserved > character is found in a URI component and no delimiting role is known > for that character, then it should be interpreted as representing the > data octet corresponding to that character's encoding in US-ASCII. > ]] > > If late editorial changes are being considered, I would suggest > deleting this paragraph completely, since the first sentence can be > read as contradicting the content of section 2.4, and as far as I can > tell the second sentence repeats material already given at the > beginning of section 2. First, that is not an editorial change. Second, it does not contradict anything if you read the entire section. Third, it was added in response to specific comments. Fourth, the specification has already been approved as a replacement for RFC 2396 and won't be changed except as required by the IESG. Finally, if anyone thinks the mailto specification does not clearly specify what characters are reserved in the mailto URI, then fix the mailto specification -- all of the standards-track scheme specifications will have to be revised soon. ....Roy
Received on Friday, 5 November 2004 18:59:39 UTC