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

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

• From: Jonathan Borden <jborden@m...>
• To: "Bullard, Claude L (Len)" <clbullar@i...>,Sean McGrath <sean@d...>, "Simon St.Laurent" <simonstl@s...>,xml-dev@l...
• 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

• References:
  • RE: XSet, an XML Property Set, was: re: Why the Infoset?
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: RE: DTDs aren't going away even when schemas arrive (was Re: Aretherestill a lot of people using DTD rather than schema?)
• Next by Date: RE: XSet, an XML Property Set, was: re: Why the Infoset?
• Previous by thread: RE: XSet, an XML Property Set, was: re: Why the Infoset?
• Next by thread: RE: XSet, an XML Property Set, was: re: Why the Infoset?
• Index(es):
  • Date
  • Thread