W3C home > Mailing lists > Public > xml-editor@w3.org > April to June 2009

Erratum in XML 1.0 Fifth Edition (editorial)

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 15 Jun 2009 12:07:04 +1000
Message-Id: <53002D45-16F8-431E-A621-36D6632691B7@mnot.net>
To: xml-editor@w3.org
Section 4.2.2 says:

> Unless otherwise provided by information outside the scope of this  
> specification (e.g. a special XML element type defined by a  
> particular DTD, or a processing instruction defined by a particular  
> application specification), relative URIs are relative to the  
> location of the resource within which the entity declaration occurs.  
> This is defined to be the external entity containing the '<' which  
> starts the declaration, at the point when it is parsed as a  
> declaration. A URI might thus be relative to the document entity, to  
> the entity containing the external DTD subset, or to some other  
> external parameter entity. Attempts to retrieve the resource  
> identified by a URI may be redirected at the parser level (for  
> example, in an entity resolver) or below (at the protocol level, for  
> example, via an HTTP Location:header). In the absence of additional  
> information outside the scope of this specification within the  
> resource, the base URI of a resource is always the URI of the actual  
> resource returned. In other words, it is the URI of the resource  
> retrieved after all redirection has occurred.
>
> System identifiers (and other XML strings meant to be used as URI  
> references) may contain characters that, according to [IETF RFC  
> 3986], must be escaped before a URI can be used to retrieve the  
> referenced resource.
>

In this text, the term "resource" is sometimes misused. Proposed text:

> Unless otherwise provided by information outside the scope of this  
> specification (e.g. a special XML element type defined by a  
> particular DTD, or a processing instruction defined by a particular  
> application specification), relative URIs are relative to the  
> location of the resource within which the entity declaration occurs.  
> This is defined to be the external entity containing the '<' which  
> starts the declaration, at the point when it is parsed as a  
> declaration. A URI might thus be relative to the document entity, to  
> the entity containing the external DTD subset, or to some other  
> external parameter entity. Attempts to dereference the resource  
> identified by a URI may be redirected at the parser level (for  
> example, in an entity resolver) or below (at the protocol level, for  
> example, via an HTTP Location:header). In the absence of additional  
> information outside the scope of this specification, the base URI of  
> an entity is always the URI of the actual resource used. In other  
> words, it is the URI of the resource dereferenced after all  
> redirection has occurred.
>
> System identifiers (and other XML strings meant to be used as URIs)  
> may contain characters that, according to [IETF RFC 3986], must be  
> escaped before a URI can be used to dereference the resource.
>

Kind regards,

--
Mark Nottingham     http://www.mnot.net/
Received on Monday, 15 June 2009 02:07:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:41 GMT