Lists Home |
Date Index |
- From: John Cowan <firstname.lastname@example.org>
- To: XML Dev <email@example.com>
- Date: Tue, 09 Jun 1998 16:19:16 -0400
Paul Prescod wrote:
> SAX provides information on ID/IDREF attributes, but I don't think that
> ESIS did, so this is more debatable.
But not all SAX-compliant parsers do: attribute type checking is a
validity constraint only, so non-validating parsers are free to
return CDATA as the type of all attributes.
As one who is fairly SGML-ignorant, I would like to know: Just what
is in the ESIS? (If you will, limit the answer to things XML also
> Anyhow, I wouldn't care much if we cut loose all of those types. I just
> don't think that removing them is the natural extension of not checking
> text entities.
I was attempting to adopt the distinction between "what IS so" and
"what MUST BE so" (which DTDs conflate) and see where it led.
Content models say what must be so, and entity declarations say
what is so, that much is clear. Attribute declarations are
> We might not need fixed attributes. A fixed attribute is merely an
> attribute with a single choice. Can't that be represented directly as a
> choice attribute with a single choice (yes, this implies that we would
> open up "choice" attributes beyond names...any arguments with that?)
> So that would allow us to reduce the "optionality" requirement to
> "optional or required".
Okay, that leads to a model with the following (meta-)attributes
name CDATA #REQUIRED
syntax (name | nmtoken | names | nmtokens | general) #IMPLIED
choices CDATA #IMPLIED -- a list of choices or "free" if none --
optionality: (optional | required) "optional"
John Cowan http://www.ccil.org/~cowan firstname.lastname@example.org
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:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
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)