[
Lists Home |
Date Index |
Thread Index
]
- From: "Simon St.Laurent" <SimonStL@classic.msn.com>
- To: xml-dev@ic.ac.uk
- 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@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|
