OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: XInclude [was: XLink transformations]

[ Lists Home | Date Index | Thread Index ]
  • From: Didier PH Martin <martind@netfolder.com>
  • To: "Bullard, Claude L (Len)" <clbullar@ingr.com>,Paul Grosso <pgrosso@arbortext.com>, xml-dev@xml.org
  • Date: Tue, 25 Jul 2000 16:35:46 -0400

Hi Claude,

It is my understanding that the merge is occuring in a transient (or could
be permanent) infoset. It could be nearly impossible to undo the operation
if the xinclude processor does not keep track of the inclusion operations.
However, an xinclude may keep the necessary information to undo the

Is there any case you have in mind where this could be necessary?


-----Original Message-----
From: Bullard, Claude L (Len) [mailto:clbullar@ingr.com]
Sent: Tuesday, July 25, 2000 3:36 PM
To: Paul Grosso; xml-dev@xml.org
Subject: RE: XInclude [was: XLink transformations]

Is the sense of a merge operation that information
merged into another document loses its original
identity such that reversing the operation is
not guaranteed?

Len Bullard
Intergraph Public Safety

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h

-----Original Message-----
From: Paul Grosso [mailto:pgrosso@arbortext.com]

XInclude is more like knitting together parse trees
(or infosets) at (or immediately after) parse time
well before any application gets a chance at the document.
XInclusion in the original source document would occur
even before any XSLT transformation occurred and well
before any XLinking or styling occurred.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS