W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > November 2000

RE: Couple of errors/questions on XInclude WD 26 October 2000

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Tue, 7 Nov 2000 13:54:13 -0800
Message-ID: <330564469BFEC046B84E591EB3D4D59C1641B3@red-msg-08.redmond.corp.microsoft.com>
To: "'Daniel.Veillard@w3.org'" <Daniel.Veillard@w3.org>, www-xml-xinclude-comments@w3.org
Thanks for the comments, I'll add the issues to the draft.

> -----Original Message-----
> From: Daniel Veillard [mailto:Daniel.Veillard@w3.org]
> 4) 3.2.2. Multiple Nodes
>     I may not have understood it but the second paragraph 
> sounds really
> strange to me:
> --------------------
> If the document element in the source infoset is an include element,
> it is an error to attempt to replace it with more than a 
> single element.
> --------------------
>    - when parse="xml" it sounds clear that multiple nodes can result
>      for the infoset insertion
>    - all document element in the source infoset should be XInclude
>      element now.
>   Is this a remain of the attribute syntax which should be removed ?
> Or did I simply missed the point of this sentence ?

The intent is to prevent

  <?xml version="1.0"?>
  <xinclude:include href="foo.xml#xpointer(//p)"/>

from generating multiple top-level elements in the resulting infoset, and
thus would be incapable of reserialization.  The above example would be an
error if there was more than one <p> in foo.xml.

The text certainly could be clearer.
Received on Tuesday, 7 November 2000 16:55:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:09:29 UTC