Lists Home |
Date Index |
- From: "Simon St.Laurent" <SimonStL@classic.msn.com>
- To: firstname.lastname@example.org
- Date: Thu, 25 Jun 98 23:26:25 UT
>This seems unnecessarily verbose in the extreme.
>Here's where it gets interesting: Does XSchema have to limit itself to
>the capabilities of DTDs? If so, why bother? Think about this:
I like the proposal, and I don't mind using attributes. The concern I have is
that processing XSchemas now requires a lot of extra checking on the
'correctness' of the XSchema. Using the elements, convoluted though it was,
allowed the use of a simple validation (okay, it's ironic) to make sure that
the XSchema wasn't attempting to provide an odd combination of functionality.
Does this extra overhead for checking XSchemas bother anyone? The goals said
that XSchema would have a DTD, not that an XSchema that can validate against
the DTD would be functionally correct. (Or some such weirdness.) So far
we've been using the DTD to constrain the XSchema's possible content. This
would be a change of philosophy in that regard.
Dynamic HTML: A Primer / XML: A Primer / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)