Lists Home |
Date Index |
- From: "Richard L. Goerwitz" <firstname.lastname@example.org>
- To: email@example.com
- Date: Wed, 07 Apr 1999 09:37:38 -0400
Chris Olds wrote:
> I'm not so sure that IE5 is wrong in reporting an error (when unreferenced
> General Entities are DTD chunks). The XML REC says (in 4.3.2 "Well-Formed
> Parsed Entities")
>> "An external general parsed entity is well-formed if it matches the
>> production labeled extParsedEnt", which is an optional TextDecl 
>> followed by 'content' . Non-validating processors are not required to
>> read external entities, but they are not forbidden to read them if they are
>> not referenced.
> While I don't think this is necessarily the best choice, I think it is just
> that - an implementation choice.
I don't see anything in the spec that says "don't read and validate
external parsed entities if they're not used." And in fact, the spec
seems to say that, in order to be valid, they must (whether used or not)
match certain productions in the grammar.
Someone please correct me if there is explicit language to the contrary.
My feeling is that this is another one of those cases where the XML spec
is typically interpreted in terms of SGML practice, but where nothing in
the XML spec itself actually mandates such interpretation.
And in fact, one can make a good case for reading in and checking exter-
nal entities even if they're not "used." If you fail to do this, you can
end up with a DTD that itself triggers errors when used with some docu-
ments, but not others. Worse yet, you can end up with a DTD that was
thought to be valid, but which fails unexpectedly when used with a new
PGP key fingerprint: C1 3E F4 23 7C 33 51 8D 3B 88 53 57 56 0D 38 A0
For more info (mail, phone, fax no.): finger firstname.lastname@example.org
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)