W3C home > Mailing lists > Public > xml-uri@w3.org > May 2000

Re: inclusion

From: Paul Grosso <pgrosso@arbortext.com>
Date: Thu, 25 May 2000 11:15:45 -0500
Message-Id: <3.0.32.20000525103911.01f21f5c@pophost.arbortext.com>
To: xml-uri@w3.org
XML Base is setting the "Base URI within Document Content"
(see section 5.1.1 of RFC 2396).  See the diagram in section
5.1 "Establishing a Base URI" and note that the base URI
within the document content would take precedence over the
other levels (e.g., 5.1.2 Base URI from the Encapsulating Entity).

The XML Base spec [2] says "Note that the scope of xml:base 
does not extend into external entities."  The next draft will
make this even clearer.  Note also that the relationship of
XML document referencing an external entity and the referenced
external entity is not one that qualifies as an "Encapsulating 
Entity", so the base URI for the external entity (until an
xml:base is found) will be determined by "5.1.3. Base URI from 
the Retrieval URI" which is the same as it would be if you 
considered the entity standalone.

At 22:45 2000 05 24 -0400, Simon St.Laurent wrote:
>Inclusion, whether via external entities or via XInclude, raises some
>painful questions regarding how/if absolutization of namespace URIs should
>take place. 

[example elided]

>... It's not clear how the rules for determining
>base URI from 5.1 of RFC 2396 [1] apply to these cases, at least on my
>reading.  
>
>5.1.2 - Base URI from the Encapsulating Entity - seems most likely, but I'd
>still like a strong clarification that such behavior is in fact appropriate
>to namespace handling.  It seems more appropriate to determining where to
>retrieve an image from than describing a vocabulary or even a 'language'.
>For such cases, 5.1.3 seems more appropriate, or even fallback to the
>non-answer of 5.1.4.
>
>[1] http://www.ietf.org/rfc/rfc2396.txt
[2] http://www.w3.org/TR/xmlbase
Received on Thursday, 25 May 2000 12:15:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:42 UTC