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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: Arbitrary Infoset boundaries (was Re: Common XML -FinalReviewDraft)

[ Lists Home | Date Index | Thread Index ]
  • From: Aaron Skonnard <aarons@develop.com>
  • To: Rick JELLIFFE <ricko@geotempo.com>
  • Date: Wed, 02 Aug 2000 20:00:25 -0600

Rick Jelliffe wrote:

> XInclude is no replacement for entity referneces in attribute values or
> in text-only data content.  Neither does it adequately substitute for
> the ISO public entity sets for special characters:  HTML advocates have
> made it quite clear during the  XHTML discussions that the idea that
> entity references will not go away quickly.  (XInclude is a bad idea, if
> considered alone, because it will fragment XML into XML+XInclude and
> XML: it would be better to bundle it as part of namespaces and XBase.)

What we really need is the next version of XML ( Infoset + XML 1.0 - DTDs +
Namespaces + XBase/XInclude + XML Schemas ).

> A DTD is carted around with a document when the document is considered
> by its originater to have some life. The DTD represents constraints on
> the future of the document not just its present.


> XML Schemas may even lead to a resurgence of the use of DTDs: this is
> because once schema software is in place as a layer, the particular
> syntax becomes less important. (Of course, where there are features that
> cannot be supported, that is different. No magic.)

What? How? You lost me...



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

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