Cart
[Home] [By Thread] [By Date] [Recent Entries]
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@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
