Lists Home |
Date Index |
- From: Toby Speight <firstname.lastname@example.org>
- To: "XML developers' list" <email@example.com>
- Date: 04 Jun 1998 19:03:10 +0100
Ron> Ron Bourret <URL:mailto:firstname.lastname@example.org>
=> In article <199806041616.SAA11609@berlin.dvs1.tu-darmstadt.de>, Ron
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: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)