- From: Elliotte Rusty Harold <elharo@metalab.unc.edu>
- Date: Tue, 20 May 2003 13:30:02 -0400
- To: www-xml-xinclude-comments@w3.org
Besides the previously reported problem with the lack of a namespace declaration for the xi prefix in example C5, I believe there is also a problem with the white space. There isn't enough of it in the result. The white space inside the various fallback elements should propagate into the result. This is the expected behavior when <?xml version='1.0'?> <div> <xi:include href="example.txt" parse="text"> <xi:fallback> <xi:include href="fallback-example.txt" parse="text"> <xi:fallback><a href="mailto:bob@example.org">Report error</a></xi:fallback> </xi:include> </xi:fallback> </xi:include> </div> Given that "If the [children] of the xi:include element information item in the source infoset contain exactly one xi:fallback element, the top-level included items consists of the information items corresponding to the result of performing XInclude processing on the [children] of the xi:fallback element." I think the correct result should be <?xml version="1.0" encoding="UTF-8"?> <div> <a href="mailto:bob@example.org">Report error</a> </div> (I hope that comes through the e-mail intact. There should be an extra blank line after <div> and another one before </div>. Also the <a> start-tag should be indented exactly four spaces by my count.) I don't see any justification for throwing away the extra white space around the xi:include elements, any more than we would throw away non-whitepsace text or other markup. XInclude processing replaces the xi:include elements. It does not replace anything else. -- Elliotte Rusty Harold
Received on Tuesday, 20 May 2003 13:26:46 UTC