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.
>

OK, that's weird but at least it's consistent. I'm not sure if I like 
it or not. For now I'm neutral. This should probably be called out 
explicitly in the spec; i.e. say that this is OK. Otherwise people 
will get this wrong.
-- 

+-----------------------+------------------------+-------------------+
| 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 Tuesday, 14 January 2003 10:40:52 UTC