• From: rbourret@d... (Ron Bourret)
• To: xml-dev@i..., carl@c...
• Date: Wed, 22 Jul 1998 17:32:07 +0200

Carl Hage wrote:

> However, moving <EnumerationValue>+ into a token string creates a severe 
> problem. It's impossible to add information associated with each code value, 
> for example documentation on the semantics for each. Also, it may be common 
> to import enumeration values defined within an external standard, e.g. by 
> using xml links.
> 
> To correct the problem, simply add <EnumerationValue> back in, e.g.
> <!ELEMENT XSC:AttDef (XSC:Doc?, XSC:More?, XSC:EnumerationValue*)>

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.

-- Ron Bourret

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

• Follow-Ups:
  • Re: XSchema Spec - Attribute Declarations (Section 2.4), Draft 5
    • From: John Cowan <cowan@l...>

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