• From: emberson@f... (Richard Emberson)
• To: xml-dev@i...
• Date: Wed, 14 Oct 1998 15:00:33 -0700

In section 4.4, the spec states when a parsed general entity
"occurs as Attribute value", it is forbidden which means that a
fatal error has occurred.

In section 3.3.1, part: "Validity Constraint: Entity Name",
it is a validity constraint violation if the value is not a Name
of an unparsed entity.

It seems that there are two different actions for the same condition.

Which take priority, the fatal error that is detected by all XML
processors or the validity constraint violation that is only
detected by validating processors?


Richard Emberson
emberson@f...

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...)

• Follow-Ups:
  • Re: REC-xml-19980210 unparsed entity
    • From: John Cowan <cowan@l...>
  • Re: REC-xml-19980210 unparsed entity
    • From: Paul Prescod <papresco@t...>

• Prev by Date: Re: A call for open source DTDs
• Next by Date: REC-xml-19980210: whitespace
• Previous by thread: MSIE5 Beta 2 + XML
• Next by thread: Re: REC-xml-19980210 unparsed entity
• Index(es):
  • Date
  • Thread