• From: "Simon St.Laurent" <SimonStL@c...>
• To: xml-dev@i...
• Date: Wed, 22 Jul 98 16:06:58 UT

Carl Hage writes:
> To correct the problem, simply add <EnumerationValue> back in, e.g.
> <!ELEMENT XSC:AttDef (XSC:Doc?, XSC:More?, XSC:EnumerationValue*)>

Ron Bourret writes:
>I agree, although for a different reason.  I've just gotten to writing 
>this part of the code and have to admit that having to parse 
>something the parser can parse for me makes me very grumpy indeed.  
>Note that the EnumerationValue element is used by both enumerated 
>attributes and notation attributes.

I have no objections to this; it seems to return some of the flexibility and 
documentability we lost by moving to the attributes model, without bringing 
back too much verbosity.

Anyone disagree?

Simon St.Laurent
Dynamic HTML: A Primer / XML: A Primer / Cookies


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...)

• Prev by Date: Re: C/C++ Parser/Tokenizer
• Next by Date: Xschema comments
• Previous by thread: Re: XSchema Spec - Attribute Declarations (Section 2.4), Draft 5
• Next by thread: XSchema Specification - Notations (Section 2.5), Draft 4
• Index(es):
  • Date
  • Thread