Hi,

on 9/20/2004 11:07 AM Michael Kay wrote:

> In Schema Part 1 (PER 18 Mar 2004), section 3.14.6, Schema Component
> Constraint: Derivation Valid (Restriction, Simple), is the rule:
> 
> 3.3.2.3 The {member type definitions}, in order, must be validly derived
> from the corresponding type definitions in the {base type definition}'s
> {member type definitions} given the empty set, as defined in ...
> 
> However, I'm having trouble seeing how one can define a union as a
> restriction of another union in which the member type definitions differ i=
n
> any way from those of the base type definition. <xs:restriction> only allo=
ws
> me to change the pattern and enumeration facets, not the member types.
> 
> For example:
> 
> (a) if the base type is a union of decimal and string, can I make the
> derived type be a union of integer and string? Unless I'm missing somethin=
g,
> I think not.
> 
> (b) if the base type is a union of dateTime, date, and time, can I make th=
e
> derived type be a union of dateTime and date? Again, I think not.
> 
> So what does rule 3.3.2.3 mean? My suspicion is that it is vacuous.

If you derive a union type from a union type, the "Derivation Valid" 
constraint is not needed, since the derivation process ensures that this 
constraint holds. AFAIK this constraint is needed if you are confronted 
with two type definitions, for which you don't know if one of them has 
been derived from the other, e.g. if using xsi:type [1].


[1]
http://www.w3.org/TR/2004/PER-xmlschema-1-20040318/#cvc-elt

Regards,

Kasimier


From mhk@m... Mon Sep 20 10:35:25 2004
Received: from lisa.w3.org ([128.30.