Lists Home |
Date Index |
- From: "Simon St.Laurent" <SimonStL@classic.msn.com>
- To: email@example.com
- Date: Wed, 10 Jun 98 23:50:14 UT
Ron Bourret writes:
>This is a mistake in the current DTD, where we use id attributes for both
>ElementDecl and Notation (but not AttDef). It's not quite clear to me if
>notations are in or out at the moment. If they stay in, we could retain an
>ID attribute on ElementDecls and get uniqueness checking from validating
>parsers for free. On the other hand, because a validator is looking like a
>reasonable application to build, there seems no reason to do this, since the
>validator would need to check uniqueness for non-validating parsers anyway.
>Note also that attribute names are required to be unique only within the
>attributes of a single element, not all attributes.
It's not quite clear to me either whether NOTATION is in or out, though it
does have a place in the current outline. If NOTATION is in, ID attributes
should not be used for both types of declarations.
We need to define behavior for the verifier (my term for validator, since I
don't want to get twisted in DTDs). The verifier could check that all element
names are unique, or it could accept the first or last element declaration
made. Allowing repeated declarations - which override would make it easier to
combine XSchemas, but could also create a mess. (Attributes? Content models?)
Whatever we decide, the verifier is going to have some work to do.
I would like to be able to build XSchema applications on top of non-validating
parsers - dealing with validation as well as XSchemas seems like a lot of
redundant effort to me. I don't think we gain that much from using ID.
Dynamic HTML: A Primer / XML: A Primer / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)