Assymettry bewteen xi:include and xi:fallback

Section 3.1 of the CR states:

The /children/ property of the |xi:include| element may 
<http://www.w3.org/TR/2003/WD-xinclude-20031110/#dt-must> include a 
single |xi:fallback| element; the appearance of more than one 
|xi:fallback| element, an |xi:include| element, or any other element 
from the XInclude namespace is a fatal error 
<http://www.w3.org/TR/2003/WD-xinclude-20031110/#dt-error>. Other 
content (text, processing instructions, comments, elements not in the 
XInclude namespace, descendants of child elements) is not constrained by 
this specification and is ignored by the XInclude processor, that is, it 
has no effect on include processing, and does not appear in the 
/children/ properties of the result infoset. Such content might be used 
by applications analyzing a pre-inclusion infoset, or be made available 
to an application post-inclusion through means other than the normal 
infoset properties.


This is fine. it addresses one of my comments on the previous draft, and 
brings the spec in line with the test suite.

However, there is no equivalent statement in section 3.2 on 
xi:fallbacks. because, "It is a fatal error 
<http://www.w3.org/TR/2003/WD-xinclude-20031110/#dt-error> for an 
|xi:fallback| element to appear in a document anywhere other than as the 
direct child of the |xi:include" we can infer that it is illegal for a 
fallback to contain a fallback child. However, it sems to be legal for a 
fallback ton contain an xi:something element in the XInclude namespace 
where something is anything other than fallback. It's not clear why this 
shold be true for fallback but not include. |

--
Elliotte Rusty Harold

Received on Thursday, 15 January 2004 19:46:32 UTC