Lists Home |
Date Index |
- From: John Cowan <email@example.com>
- To: XML Dev <firstname.lastname@example.org>
- Date: Tue, 09 Jun 1998 11:27:33 -0400
Many, many XML-DEVers wrote, in effect:
> Entities in XSchemas suck big ones.
I surrender. Even when the XSchema-processors-can't-expand-entities
meme has worked its way out of the system, there remains the
Why-would-you-want-to-do-that???? meme, and I very well realize there's
no end to that argument. "Eleven men well armed", as Jno. Swift
has it, "will certainly subdue one single man in his shirt."
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.
Without information on the names of valid entities and notations,
and potentially without information on IDs, then ID, IDREF,
ENTITY and NOTATION are indistinguishable; IDREFS, ENTITIES, and
NOTATIONS also all look the same. The only remaining distinction
Saying what the specific default value is or whether there is none
is overspecific (the DTD must bear this information, and
an XSchema would be either redundant or conflicting, a Bad Thing);
the only three cases are: a) the value must be present and must
be "foo" (#FIXED), b) the value must be present but can be anything
(#REQUIRED), or c) the value need not be present.
John Cowan http://www.ccil.org/~cowan email@example.com
You tollerday donsk? N. You tolkatiff scowegian? Nn.
You spigotty anglease? Nnn. You phonio saxo? Nnnn.
Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)
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)