Lists Home |
Date Index |
- From: John Cowan <email@example.com>
- To: XML Dev <firstname.lastname@example.org>
- Date: Thu, 04 Jun 1998 14:54:58 -0400
Blunderingly I wrote:
> > That's what my draft does wrt enumerations. I have more problems
> > with notations, because it doesn't make sense to me to have to
> > redeclare every notation name with every notation attribute,
> > since any notation attribute can refer to any notation name.
> > Thus I treat notation attributes like other attributes with
> > predefined types.
> I'm not sure what you mean by redeclaring every notation name with every
> attribute. In the above structure, the notation value is simply a NMTOKEN. Why
> would I need to redeclare notation names? Are you thinking that the
> NotationValue attribute is an enumerated (not NMTOKEN) attribute?
No, I was muddled about notation attributes. Until today I did not
grasp that a specific notation attribute can only assume the value
of one of the notations defined for it, so my remark above ("any
notation attribute can refer to any notation name") is false, if
"any notation name" is understood as "the name of any notation
declared in the DTD".
Consequently, my draft is simply in error in treating NOTATION on
a par with ID, IDREF, ENTITY, ....
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)