[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Undeclared elements error

• From: James Clark <jjc@j...>
• To: xml-dev@i...
• Date: Thu, 17 Sep 1998 13:55:56 +0700

Liam R. E. Quin wrote:

> Should the following produce a warning?
> 
>     <!ELEMENT CHAPTER (LOCATION,DESCRIPTION)>
>     <!--* error: LOCATION has not been declared *-->
>     <!--* error: DESCRIPTION has not been declared *-->
> 
>     <!ELEMENT LOCATION (#PCDATA)>
>     <!ELEMENT DESCRIPTION (#PCDATA)>

Absolutely not.

> It seems to me that the intended interpretation is that the warning should
> only be issued after all declarations have been processed,

Right.

> but this
> is nowhere stated, and the interpretation suggested by my comments
> above appears to be legal.

A processor can issue any warnings it wants, but it's ridiculous to
interpret the XML spec as recommending something so stupid.  Since you
can have mutually recursive content models, it wouldn't even always be
possible to reorder the declarations in a DTD so as to avoid such a
warning.

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

• Follow-Ups:
  • Re: Undeclared elements error
    • From: "Richard L. Goerwitz III" <richard@g...>

• References:
  • Undeclared elements error
    • From: "Liam R. E. Quin" <liamquin@i...>

• Prev by Date: Re: Processing Select Patterns in XSL...
• Next by Date: Re: Processing Select Patterns in XSL...
• Previous by thread: Undeclared elements error
• Next by thread: Re: Undeclared elements error
• Index(es):
  • Date
  • Thread