W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 1999

Fragment Identifier and Application/MIME type behaviour

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Thu, 19 Aug 1999 18:23:48 -0400
Message-Id: <3.0.5.32.19990819182348.00afe100@localhost>
To: pnorman@factpoint.com
Cc: "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>
Peter,

RFC 2396, URI Generic Syntax, Berners-Lee, et. al.
http://www.ietf.org/rfc/rfc2396.txt

4.1. Fragment Identifier

   When a URI reference is used to perform a retrieval action on the
   identified resource, the optional fragment identifier, separated from
   the URI by a crosshatch ("#") character, consists of additional
   reference information to be interpreted by the user agent after the
   retrieval action has been successfully completed.  As such, it is not
   part of a URI, but is often used in conjunction with a URI.

      fragment      = *uric

   The semantics of a fragment identifier is a property of the data
   resulting from a retrieval action, regardless of the type of URI used
   in the reference.  Therefore, the format and interpretation of
   fragment identifiers is dependent on the media type [RFC2046] of the
   retrieval result.  The character restrictions described in Section 2
   for URI also apply to the fragment in a URI-reference.  Individual
   media types may define additional restrictions or structure within
   the fragment for specifying different types of "partial views" that
   can be identified within that media type.

   A fragment identifier is only meaningful when a URI reference is
   intended for retrieval and the result of that retrieval is 


_________________________________________________________
Joseph Reagle Jr.   
Policy Analyst           mailto:reagle@w3.org
XML-Signature Co-Chair   http://w3.org/People/Reagle/
Received on Thursday, 19 August 1999 18:23:48 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:07 GMT