Lists Home |
Date Index |
- From: "Liam R. E. Quin" <firstname.lastname@example.org>
- To: email@example.com
- Date: Thu, 17 Sep 1998 02:45:07 -0400 (EDT)
A quick question about error messages...
The XML spec says (in section 3.2)
An element type declaration constrains the element's content.
Element type declarations often constrain which types can appear
as children of the element.
At user option, an XML processor may issue a warning when a
declaration mentions an element type for which no declaration
is provided, but this is not an error.
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)>
It seems to me that the intended interpretation is that the warning should
only be issued after all declarations have been processed, but this
is nowhere stated, and the interpretation suggested by my comments
above appears to be legal.
You could say that market forces would eliminate any such XML processor,
Has anyone implemented this warning/
Liam Quin, GroveWare Inc., Toronto; The barefoot agitator
l i a m q u i n at i n t e r l o g dot c o m
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)
- OO Schemas
- From: Paul Prescod <firstname.lastname@example.org>