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: "Bullard, Claude L (Len)" <clbullar@ingr.com>
  • To: Paul Grosso <pgrosso@arbortext.com>, xml-dev@xml.org
  • Date: Wed, 26 Jul 2000 08:18:51 -0500

Thanks Paul, good explanation. 

Yes, I remember puzzling over the 
ESIS as Neill Kipp spent a few hours explaining to 
me how addressing was affected by misteps in 
not having a true abstract model.  Like too 
many people then, I assumed the DTD was the
model, the things in the file were the things 
being counted and so forth.  That's what 
happens when English majors do computer 
science: we take too much at face value.  :-)

Ok, then, as I said to Didier, it appears 
that this is similar to the append in the 
relational system plus the notion of order 
per the point of inclusion.  Am I mistaken 
that the order of the information is preserved, 
that is

BCB includes in  AA(include)AA to produce 


Len Bullard
Intergraph Public Safety

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

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

For XInclude, yes, reversing the operation is not
necessarily guaranteed, and that was not a goal of
XInclude (or the Infoset on which XInclude is built,
though a fair amount of information in the original 
can be captured by the infoset, and one could build
an application based on XInclude that did what was
necessary to allow most include operations to be


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

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