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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: XSet, an XML Property Set, was: re: Why the Infoset?

[ Lists Home | Date Index | Thread Index ]
  • From: Jonathan Borden <jborden@mediaone.net>
  • To: "Bullard, Claude L (Len)" <clbullar@ingr.com>,Sean McGrath <sean@digitome.com>, "Simon St.Laurent" <simonstl@simonstl.com>,xml-dev@lists.xml.org
  • Date: Wed, 02 Aug 2000 11:07:14 -0400

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





 

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

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