XSchema Spec - Attribute Declarations (Section 2.4), Draft 5

[Ron Bourret]

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 at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)