W3C home > Mailing lists > Public > www-html-editor@w3.org > April to June 2001

URI and fragment identifiers

From: Karl Dubost <karl@w3.org>
Date: Fri, 20 Apr 2001 16:04:07 +0200
Message-Id: <p05010400b705f07cc8e1@[]>
To: www-html-editor@w3.org
In the HTML 4.01 specification, we can read at [1] 

href = uri [CT]
This attribute specifies the location of a Web resource, thus 
defining a link between the current element (the source anchor) and 
the destination anchor defined by this attribute.

but in the URI specification - RFC 2396 at [2]

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

So we have a kind of Conformance issue here.

	The HTML 4.01 specification says that for example, you must 
have something like that for an anchor.

	<a href="http://www.w3.org/TR/html4/struct/links.html">Links 
in HTML 4.01</a>

http://www.w3.org/TR/html4/struct/links.html is an URI
but http://www.w3.org/TR/html4/struct/links.html#adef-href is an URI 
plus a fragment identifier


The problem is still there in HTML 4.01, XHTML 1.1, XHTML 2.0 and XHTML Basic.

The content of the href attribute is not only an URI, but also an URI 
plus an URI reference.

Please consider to do modifications.


Karl Dubost / W3C - Conformance Manager

      --- Be Strict To Be Cool! ---
Received on Friday, 20 April 2001 10:05:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:08:26 UTC