Lists Home |
Date Index |
- From: "Matthew Gertner" <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Mon, 1 Jun 1998 12:07:56 +0200
IMO: No. By allowing linking of element type definitions (cf. my previous
post) this can be done more cleanly by extending the element type in a
separate schema. This could work in a similar way to "drawing in" an element
type description from another schema, by including the link on the
<ElementTypeDef id="greetings" xml:link="simple" role="XSchema"
<Seq optional="yes" repeatable="yes>
<ElementType xml:link="simple" role="XSchema"
This leads to the question of how the new content affects the old one. The
most conservative approach would be to do exactly the same thing that
SGML/XML does with the internal subset: replace the entire content model
and/or attribute list, as appropriate. A better but more ambitious approach
would be to enable some kind of extension of the existing definition
(leading us back into our inheritance/subtyping discussion, but perhaps with
more chance of a concrete outcome).
Even if the general opinion is that these issues should be left for later,
one the more fundamental aspects of XSchema have been ironed out, it might
still be helpful to keep them in mind to ensure that more powerful
mechanisms such as these fit into the model.
BTW: Now that I think about it, there is absolutely no reason why the above
definition could not be included in a document, if the schema anticipates
this by adding an optional "xschema" child to certain elements. This is both
more rigorous and more powerful than the internal subset (which is always
allowed, but only once in a specific location). I suspect that we are only
beginning to discover the power that a unified schema/document syntax
From: Simon St.Laurent <SimonStL@classic.msn.com>
To: Xml-Dev (E-mail) <email@example.com>
Date: Saturday, May 30, 1998 7:00 PM
Subject: XSchema Question 3: Internal/External subsets
>This was actually one of the questions I was planning for the end, but
>recent examples have made me move it to the front.
>Should XSchema provide internal and external subsets, as do XML DTD's?
>Note: Please keep in mind that answering no at this stage does not imply
>internal subsets will be banished for all time. It simply means that
>1.0 would not support internal subsets. (We could banish external subsets,
>but I doubt that makes sense to anyone.)
>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)