Cart
[Home] [By Thread] [By Date] [Recent Entries]
Ron> Ron Bourret <URL:mailto:rbourret@d...> => In article <199806041616.SAA11609@b...>, Ron => wrote: Ron> John Cowan wrote: >> 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. Ron> I'm not sure what you mean by redeclaring every notation name Ron> with every attribute. In the above structure, the notation value Ron> is simply a NMTOKEN. Why would I need to redeclare notation Ron> names? Are you thinking that the NotationValue attribute is an Ron> enumerated (not NMTOKEN) attribute? I think the confusion is caused by my misunderstanding. From your DTD: Ron> <!ELEMENT NotationType (NotationValue+)> Ron> <!ELEMENT NotationValue (#PCDATA)> Ron> <!ATTLIST NotationValue Ron> Notation IDREF #REQUIRED> In particular, NotationType contains a list of Notation values. Why? What's wrong with the following? <!ELEMENT NotationType EMPTY> -- xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
