2.1.3 [W3C-XSS] Section 3.4.6, Constraints on Complex Type Definition Schema Components

  • Article

V0003:

The specification states:

 Schema Component Constraint: Derivation Valid (Extension)
 If the {derivation method} is extension, the appropriate case among the following 
 must be true:
  
 1 If the {base type definition} is a complex type definition, then all of the 
 following must be true: 
  
      1.1 The {final} of the {base type definition} must not contain extension.
      1.2 Its {attribute uses} must be a subset of the {attribute uses} of the complex type definition itself, that is, for every attribute use in the {attribute uses} of the {base type definition}, there must be an attribute use in the {attribute uses} of the complex type definition itself whose {attribute declaration} has the same {name}, {target namespace} and {type definition} as its attribute declaration.
      1.3 If it has an {attribute wildcard}, the complex type definition must also 
 have one, and the base type definition's {attribute wildcard}'s {namespace 
 constraint} must be a subset of the complex type definition's {attribute 
 wildcard}'s {namespace constraint}, as defined by Wildcard Subset (§3.10.6).

MSXML6

The {namespace constraint} property of the base type definition's {attribute wildcard} property is not required to be a subset of the {namespace constraint} of the complex type definition's {attribute wildcard} property.

The {attribute uses} property of the base type definition is not required to be a subset of the {attribute uses} property of the complex type definition.

V0004:

The specification states:

 2 If the {base type definition} is a simple type definition, then all of the following must be true:
  
      2.1 The {content type} must be the same simple type definition.
      2.2 The {final} of the {base type definition} must not contain extension.

MSXML6

A {final} property of a simple type definition may have a value of extension.