Entities in XSchema
crism at oreilly.com
Tue Jun 9 22:30:07 BST 1998
> If, however, purely declarative information is to be removed from
> XSchemas, then I think that parts of the attribute-type and
> attribute-value declaration syntax should go. In particular,
> attribute types are reduced to Name (ID, IDREF, ENTITY, NOTATION),
> Names (IDREFS, ENTITIES, NOTATIONS), Nmtoken, Nmtokens, and CData;
> attribute values are reduced to #REQUIRED, #FIXED "foo", and other.
Nay. ID, IDREF, and IDREFS are important to identify; an XSchema-
based validator can ensure that IDs are unique, and that IDREFs all
have a corresponding ID.
Likewise, NOTATION(S) says, "here's the attribute on which the
element's content is declared".
I think keeping ENTITY and ENTITIES is also a good idea. It says that
the attribute points to an entity, but doesn't mean that the same
schema has to actually declare the permitted entities.
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev