[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XInclude [was: XLink transformations]

• From: Didier PH Martin <martind@n...>
• To: "Bullard, Claude L (Len)" <clbullar@i...>,Paul Grosso <pgrosso@a...>, xml-dev@x...
• 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
operation.

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

cheers
Didier

-----Original Message-----
From: Bullard, Claude L (Len) [mailto:clbullar@i...]
Sent: Tuesday, July 25, 2000 3:36 PM
To: Paul Grosso; xml-dev@x...
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
clbullar@i...
http://fly.hiwaay.net/~cbullard/lensongs.ram

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


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

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.

• References:
  • RE: XInclude [was: XLink transformations]
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: RE: XInclude [was: XLink transformations]
• Next by Date: RE: SOAP serialization
• Previous by thread: RE: XInclude [was: XLink transformations]
• Next by thread: RE: XInclude [was: XLink transformations]
• Index(es):
  • Date
  • Thread