Altova Mailing List Archives
>xml-dev Archive Home
>Thread Prev - RE: XSet, an XML Property Set, was: re: Why the Infoset?
RE: XSet, an XML Property Set, was: re: Why the Infoset?
To: "Bullard, Claude L (Len)" <clbullar@----.--->,Sean McGrath <sean@--------.--->, "Simon St.Laurent" <simonstl@--------.--->,xml-dev@-----.---.---
Date: 8/2/2000 7:24:00 AM
Bullard, Claude L (Len) wrote: > > Why? Precisely why? > > Before we add one more stack of paper to the > already too dense stack of markup technical > specifications, we really need a defense for > it. 1) Because there is a real need to be able to precisely define a subsetting mechanism for XML. 2) Because we need a full fidelity logical description of XML documents. 3) Because the XML Infoset is already 90+% if the way there. 4) Because although groves and property sets are great in concept, the implementation has been zippo, mostly because few people understand what they are intended to accomplish. 5) Because the ISO specifications are just too dense. No offense. AFAIK, we can adopt property sets and grove plans largely unchanged if that is the *easiest* way to get the job done. Please remind me, why did XLink get written, rather than adopting HyTime? Jonathan Borden The Open Healthcare Group http://www.openhealth.org