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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Between raw and cooked II: Are? DTDs are just for validation

[ Lists Home | Date Index | Thread Index ]
  • From: "Jonathan Borden" <jborden@mediaone.net>
  • To: "David Brownell" <db@eng.sun.com>, "XML-Dev Mailing list" <xml-dev@ic.ac.uk>
  • Date: Fri, 2 Apr 1999 18:31:53 -0500

David Brownell wrote:

>> Jonathan Borden writes:
>>  > Beyond requiring that external entities and default attributes be
>>  > expanded, is there a way to allow non- and validating parsers to
>>  > process the same XML documents in a functionally similar fashion,
>>  > that is, the same SAX events be fired or the same DOM tree be
>>  > constructed whether or not validation is employed?
>Absolutely:  when a nonvalidating parser reads all external entities,
>it behaves almost exactly like a validating parser that's configured
>to ignore validity errors.
    You misunderstand me. I understand that it is possible for validating
and non-validating parsers to generate the same parse tree, what I am
looking for is a specification that parsers need meet to *ensure* that this
occurs. It is this specification that needs to be given an official standing
for use by XML applications.

    Unless I am otherwise missing something (which was the question), the
only way to ensure that identical parse events and trees are generated by
validating and non-validating parsers is to specify that external entities
and default attributes etc. be expanded. Aelfred, the sun,ibm, and microsoft
parsers provide identical parse trees *because* entities are expanded and
attributes are defaulted.

    Everyone agrees that non-validating parsers *may* expand external
entities and default attributes. The probem with XML is that this behavior
is *optional* for non-validating parsers.

    This behavior is also the default behavior of IE5's parser. The problem
is that this behavior, common to aelfred, ibm, sun and microsoft' parsers
has no official standing, nor name, which is why I suggested that this be
termed "well-behaved" (ok pick something less contentious but just pick
something!!) and be given a specific standing in the XML spec. That way, as
an XML application writer I can specify the needed features of the parser in
terms of a spec.

Jonathan Borden

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


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

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