> saying that you can't have restrictions eg (a
> maximum length of 8) and key/keyRef checking at the same time doesn't seem
> like a good design to me.
With respect to the above statement,
> we need to move to relying on the external datatype system
> purely for the collection of builtin datatypes and the facets, and the
> syntax should be defined in TREX. I am going to work on a proposal for this.
what is the advantage of this strategy? I think we still have to rely on
datatype library to test the equality of two types.
To get ride of anonymous types, I think we should rather allow
user-defined types.
For example, usually key and keyref has the same type. As long as we
have @key and @keyref attached to <data/>, we can't reuse the same
<data/> definition from multiple locations.
The "ID/IDREF strawman #1" allows this:
<key>
<ref name="myLocalTimeType"/>
</key>
<keyref>
<ref name="myLocalTimeType"/>
</keyref>
--
Kohsuke KAWAGUCHI +1 650 786 0721
Sun Microsystems
