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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: Conformance in XML processors

[ Lists Home | Date Index | Thread Index ]
  • From: James Clark <jjc@jclark.com>
  • To: xml-dev@ic.ac.uk
  • Date: Sun, 18 Jan 1998 15:47:47 +0700

Tim Bray wrote:

> No.  The spec is clear; a non-validating processor is required to
> do internal entities and default attribute values.  Nobody should
> expect one to do anything with notations or unparsed entities or
> anything else.  You want that, get a validating processor.

I think I would expect a non-validating processor to inform the
application about any unparsed entities that have been declared in the
internal subset. A non-validating processor has to keep track of this, 
because it has to report an error if any of them are referenced. I don't
see that passing this information on to the application has anything to
do with validation.

The only things I expect of a validating processor that I don't expect
of a non-validating processor are:

- processing the external DTD subset

- processing parameter entity references

- reporting violations of validity constraints

- reporting that character data is ignorable white space

James


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/
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