Altova Mailing List Archives

Re: Microsot parser is OK (Was: Re: Copyright symbol in FOP)

From: David Carlisle <davidc@--------->
Date: 4/27/2000 10:43:00 PM
> Definitely so. This kind of expression is blamed as non-well-formed n the XML
> Spec, and parsers (even non-validating ones) are obliged to report deviations
> from well-formedness in the whole document including the DTD.

replacement texts of entities are only required to be well formed if
they are referenced, strange but true. (xml spec section 2.1, point 3)

It is arguable that the declaration of lt as "<" in the xmlspec does not
break this rule as the predefined entity takes precedence. That's what
happens with a web sgml system, where lt declared in the sgml
declaration for xml acts as if at the beginning of the local subset.
The xml spec is rather vague on whetehr predefined entities count
for the `first definition wins' rule that applies to normal entity

The declaration of lt as "<" contravenes the prose constraint that lt must 
be declared to be a reference to the < character, but that is not,
as such, a well formedness constraint.


 XSL-List info and archive:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.