RE: missing href, parse="text", xpointer="something"

We agree, and will clarify both that xpointer must only be present when
href is absent and parse="xml", and that xpointer must not be present
when parse="text".  (Expressing all these co-constraints in prose is
getting a little complicated but seems to ensure meaningful include
elements).

> -----Original Message-----
> From: www-xml-xinclude-comments-request@w3.org
[mailto:www-xml-xinclude-
> comments-request@w3.org] On Behalf Of Elliotte Harold
> Sent: Friday, December 05, 2003 7:06 PM
> To: www-xml-xinclude-comments@w3.org
> Subject: missing href, parse="text", xpointer="something"
> 
> 
> Consider the following include element:
> 
> <xi:include parse="text" xpointer="xpointer(/)"/>
> 
> What, if anything, does this include? Is it an error? If so what sort
of
> error and why?
> 
> I think the current draft spec is at best unclear on this point.
> According to section 3.1, "The |href| attribute is optional; the
absence
> of this attribute is the same as specifying |href=""|, that is, the
> reference is to the same document. If the |href| attribute is absent,
> the |xpointer| attribute must <http://www.w3.org/TR/xinclude/#dt-must>
> be present." However, in the same section, "The |xpointer| attribute
has
> no effect when |parse="text"|."
> 
> I suspect this should probably be a fatal error (just like omitting
both
> parse and href). However, my best current reading of the spec is that
> this does include the current document as text. I think this needs to
be
> discussed and, whatever the resolution, should be called out for more
> explicit treatment in the spec.
> 
> --
> Elliotte Rusty Harold
>

Received on Tuesday, 17 February 2004 18:48:09 UTC