Issue: overlapping with XML Schema Part 2

TREX overlaps with XML Schema part 2.  If we assume that XML Schema Part 2 is 
THE datatype system, such overlapping should be avoided.  If we plan to make 
a new datatype spec or provide a subset of XML Schema Part 2, such overlapping 
is probably acceptable.

Subissue 1: Lists

E.g.,    
<t:oneOrMore>
  <t:data type="NCName" ns="namespaceURI"/>
</t:oneOrMore>

Subissue 2: Union

<t:choice> 
  <t:data type="NCName" ns="namespaceURI"/> 
  <t:data type="NCName" ns="namespaceURI"/>
</t:choice> 

Subissue 3: User-defined datatypes

E,g, <t:define name="foo"><t:data type="NCName" ns="namespaceURI"/></t:define>
and <t:ref name="NCName" parent/>

Cheers,



Makoto
 
Internet: 
Nifty: VEQ00625

Makoto
 
Internet: 
Nifty: VEQ00625