Lists Home |
Date Index |
- From: Tim Bray <firstname.lastname@example.org>
- To: email@example.com
- Date: Wed, 01 Apr 1998 11:20:54 -0800
At 11:22 AM 4/1/98 -0600, W. Eliot Kimber wrote:
>The reason it's practically impossible is because getting agreement among a
>community of interest as wide and varried as the XML community on a subject
>of such importance as how to represent the definitions of document types is
>one of the hardest types of things there is to do. There are simply too
>many different ways to do it, too many different ways to represent things,
>too many interested parties. The degree of expressibility of schemas is
>open ended, meaning that any design, to be useful, must be maximally
>extensible. Defining extensible languages is hard.
For the record, I disagree with the first half of Eliot's thesis here.
I think that there is an *excellent* chance of getting consortium and
leading vendors to coalesce in support of a schema proposal which attains
the notorious MPRDV (Minimum Progress Required to Declare Victory) level
but does not rule out downstream extensibility.
MPRDV components IMHO are
1. does what DTDs do in as intuitive as possible a way
2. uses XML syntax
3. is compatible with the RDF data model
4. does basic lexical data typing of character data and attribute
The other big thing you need, of course, is data types which are
inheritable and abstracted, to facilitate schema engineering.
It can be (and has been) argued that we have that already with
architectural forms. I think there is a practical determinant as
to whether we are doing OK: if we can build an MPRDV schema facility
which rules out neither AFs nor RDF schema types (two very different
approaches to related but not identical problems) then that's a
On the other hand, when Eliot points out that doing this will be
technically difficult, he is correct. -T.
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)