- From: Mirsad Todorovac <tm@rasips1.rasip.etf.hr>
- Date: Wed, 29 Nov 1995 11:12:36 +0100 (MET)
- To: fielding@avron.ics.uci.edu (Roy T. Fielding)
- Cc: jim@eies.njit.edu, uri@bunyip.com, www-talk@w3.org
R. Fielding wrote: > > > 1. The use of ## for special anchors seems reasonable. > > Use of more than one "#" character is illegal and not desirable > in the current URI syntax. It's an interresting point here. Let's see this quote from RFC 1808 (by R. Fielding): |2.4.1. Parsing the Fragment Identifier | | If the parse string contains a crosshatch "#" character, then the | substring after the first (left-most) crosshatch "#" and up to the | end of the parse string is the <fragment> identifier. If the | crosshatch is the last character, or no crosshatch is present, then | the fragment identifier is empty. The matched substring, including | the crosshatch character, is removed from the parse string before | continuing. | | Note that the fragment identifier is not considered part of the URL. | However, since it is often attached to the URL, parsers must be able | to recognize and set aside fragment identifiers as part of the | process. | It states clearly 'the first (left-most) crosshatch "#" and up to the end of the parse string is the <fragment> identifier'. This _does_ imply that there are more '#' characters than one ... Why say ``leftmost "#" character'' if there is only one allowed ? -- Mirsad > ...Roy T. Fielding > Department of Information & Computer Science (fielding@ics.uci.edu) > University of California, Irvine, CA 92717-3425 fax:+1(714)824-4056 > http://www.ics.uci.edu/~fielding/ > > -- Mirsad Todorovac at Electrical Engineering Faculty, University Zagreb, Croatia mirsad.todorovac@etf.hr, tm@rasip.etf.hr
Received on Wednesday, 29 November 1995 05:19:50 UTC