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

RE: Arbitrary Infoset boundaries (was Re: Common XML - Final ReviewDraft

• From: Aaron Skonnard <aarons@d...>
• To: Xml-Dev <xml-dev@l...>
• Date: Wed, 02 Aug 2000 16:27:55 -0600

> -----Original Message-----
> From: Simon St.Laurent [mailto:simonstl@s...]
> Sent: Wednesday, August 02, 2000 3:15 PM
> To: xml-dev@x...
> Subject: Arbitrary Infoset boundaries (was Re: Common XML - Final Review
> Draft)
>
> >One sticking point seems to be DTDs.  If we did DTDs, we'd have to do
> >Schemas too, and that seemed like too big a job (plus the Schema WG is
> >changing things all the time as well).  So we arbitrarily ruled
> >metainformation (except for base URIs) out of scope.
>
> You arbitrarily ruled it out of scope, the DOM folks arbitrarily ruled it
> out of scope, and now we have a lot of XML features that applications just
> plain can't get at easily.

Once XSD and XInclude are done, DTDs are dead weight for the Infoset. It's
really about the fundamental abstractions that we can infer from XML 1.0 +
Namespaces in light of our current direction.

-aaron

• Follow-Ups:
  • Re: Arbitrary Infoset boundaries (was Re: Common XML - FinalReviewDraft)
    • From: Rick JELLIFFE <ricko@g...>
  • RE: Arbitrary Infoset boundaries (was Re: Common XML - Final ReviewDraft)
    • From: "Simon St.Laurent" <simonstl@s...>

• References:
  • Arbitrary Infoset boundaries (was Re: Common XML - Final Review Draft)
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: RE: problem with enumerated lists
• Next by Date: RE: Why the Infoset?
• Previous by thread: Re: Arbitrary Infoset boundaries (was Re: Common XML - Final ReviewDraft)
• Next by thread: RE: Arbitrary Infoset boundaries (was Re: Common XML - Final ReviewDraft)
• Index(es):
  • Date
  • Thread