RE: Non-defined elements in XInclude namespace

That would not be an error.  XInclude does not define the semantics for
<p>, neither should it prejudge the semantics of <p>'s children, nor
restrict them in any fashion.

> -----Original Message-----
> From: Elliotte Rusty Harold [mailto:elharo@metalab.unc.edu]
> Sent: Friday, January 10, 2003 5:23 PM
> To: Jonathan Marsh
> Cc: www-xml-xinclude-comments@w3.org
> Subject: RE: Non-defined elements in XInclude namespace
> 
> At 4:19 PM -0800 1/10/03, Jonathan Marsh wrote:
> >The [children] property of the xi:include element information item
may
> >include a single xi:fallback element; the appearance of more than one
> >xi:fallback elemenr, an xi:include element, or any other element from
> >the XInclude namespace is a fatal error.  ..."
> >
> 
> OK, so what if there's an XInclude element that's a grandchild or
> deeper of an xi:include element in a non fallback element? e.g.
> 
> <xi:include ...>
>    <p>
>      <xi:include .../>
>    </p>
> </xi:include>
> --
> 
> +-----------------------+------------------------+-------------------+
> | Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer |
> +-----------------------+------------------------+-------------------+
> |           Processing XML with Java (Addison-Wesley, 2002)          |
> |              http://www.cafeconleche.org/books/xmljava             |
> | http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA  |
> +----------------------------------+---------------------------------+
> |  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
> |  Read Cafe con Leche for XML News: http://www.cafeconleche.org/    |
> +----------------------------------+---------------------------------+

Received on Monday, 13 January 2003 12:53:14 UTC