- From: Daniel Veillard <Daniel.Veillard@w3.org>
- Date: Wed, 8 Nov 2000 12:02:30 +0100
- To: Jonathan Marsh <jmarsh@microsoft.com>
- Cc: www-xml-xinclude-comments@w3.org
On Tue, Nov 07, 2000 at 01:54:13PM -0800, Jonathan Marsh wrote: > 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. Ahhhh, okay now I understand, and it makes sense. A wording like "top level element" or "root element" while less precise from an Infoset point of view would probably have avoided the misunderstanding. thanks, Daniel -- Daniel.Veillard@w3.org | W3C, INRIA Rhone-Alpes | libxml Gnome XML toolkit Tel : +33 476 615 257 | 655, avenue de l'Europe | http://xmlsoft.org/ Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Rpmfind search site http://www.w3.org/People/all#veillard%40w3.org | http://rpmfind.net/
Received on Wednesday, 8 November 2000 06:02:37 UTC