An , or other document containing an element <xs:schema>, exhibits the TargetNamespace pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/TargetNamespace when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example document [TargetNamespace] illustrates the use of the TargetNamespace pattern:

The following example element is valid against the above example when included inside an instance document [TargetNamespace01]:

An , or other document containing an element <xs:schema>, exhibits the QualifiedLocalElements pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/QualifiedLocalElements when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example document [QualifiedLocalElements] illustrates the use of the QualifiedLocalElements pattern:

The following example element is valid against the above example when included inside an instance document [QualifiedLocalElements01]:

An , or other document containing an element <xs:schema>, exhibits the UnqualifiedLocalAttributes pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/UnqualifiedLocalAttributes when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example document [UnqualifiedLocalAttributes] illustrates the use of the UnqualifiedLocalAttributes pattern:

The following example element is valid against the above example when included inside an instance document [UnqualifiedLocalAttributes01]:

An , or other document containing an element <xs:schema>, exhibits the SchemaVersion pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SchemaVersion when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example document [SchemaVersion] illustrates the use of the SchemaVersion pattern:

The following example element is valid against the above example when included inside an instance document [SchemaVersion01]:

An , or other document containing an element <xs:schema>, exhibits the DocumentationElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DocumentationElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the DocumentationElement pattern within an document [DocumentationElement]:

The following example element is valid against the above example when included inside an instance document [DocumentationElement01]:

An , or other document containing an element <xs:schema>, exhibits the IdentifierName pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/IdentifierName when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the IdentifierName pattern within an document [IdentifierName]:

The following example element is valid against the above example when included inside an instance document [IdentifierName02]:

An , or other document containing an element <xs:schema>, exhibits the NonIdentifierName pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NonIdentifierName when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NonIdentifierName pattern within an document [NonIdentifierName]:

The following example element is valid against the above example when included inside an instance document [NonIdentifierName02]:

An , or other document containing an element <xs:schema>, exhibits the NotMixed pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NotMixed when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NotMixed pattern within an document [NotMixed]:

The following example element is valid against the above example when included inside an instance document [NotMixedExample01]:

An , or other document containing an element <xs:schema>, exhibits the MinOccurs1 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/MinOccurs1 when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the MinOccurs1 pattern within an document [MinOccurs1]:

The following example element is valid against the above example when included inside an instance document [MinOccurs01]:

An , or other document containing an element <xs:schema>, exhibits the MaxOccurs1 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/MaxOccurs1 when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the MaxOccurs1 pattern within an document [MaxOccurs1]:

The following example element is valid against the above example when included inside an instance document [MaxOccurs01]:

as is the following element when included in an instance document [MaxOccurs02]:

An , or other document containing an element <xs:schema>, exhibits the Id pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/Id when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the Id pattern within an document [Id]:

The following example element is valid against the above example when included inside an instance document [IdExample01]:

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeConcrete pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeConcrete when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ComplexTypeConcrete pattern within an document [ComplexTypeConcrete]:

The following example element is valid against the above example when included inside an instance document [ComplexTypeConcreteExample01]:

An , or other document containing an element <xs:schema>, exhibits the GlobalElementConcrete pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementConcrete when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the GlobalElementConcrete pattern within an document [GlobalElementConcrete]:

The following example element is valid against the above example when included inside an instance document [GlobalElementConcreteExample01]:

An , or other document containing an element <xs:schema>, exhibits the ImportTypesNamespace pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ImportTypesNamespace when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ImportTypesNamespace pattern within an document [ImportTypesNamespace]:

An , or other document containing an element <xs:schema>, exhibits the ImportNamespace pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ImportNamespace when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ImportNamespace pattern within an document [ImportNamespace]:

An , or other document containing an element <xs:schema>, exhibits the ImportSchema pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ImportSchema when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ImportSchema pattern within an document [ImportSchema]:

An , or other document containing an element <xs:schema>, exhibits the Include pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/Include when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the Include pattern within an document [Include]:

An , or other document containing an element <xs:schema>, exhibits the GlobalElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the GlobalElement pattern within an document [GlobalElement]:

The following example element is valid against the above example when included inside an instance document [GlobalElement01]:

as is the following element when included in an instance document [GlobalElement02]:

and the following element when included in an instance document [GlobalElement03]:

An , or other document containing an element <xs:schema>, exhibits the GlobalElementSequence pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementSequence when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the GlobalElementSequence pattern within an document [GlobalElementSequence]:

The following example element is valid against the above example when included inside an instance document [GlobalElementSequence01]:

An , or other document containing an element <xs:schema>, exhibits the GlobalElementComplexType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementComplexType when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the GlobalElementComplexType pattern within an document [GlobalElementComplexType]:

The following example element is valid against the above example when included inside an instance document [GlobalElementComplexType01]:

An , or other document containing an element <xs:schema>, exhibits the GlobalAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the GlobalAttribute pattern within an document [GlobalAttribute]:

The following example element is valid against the above example when included inside an instance document [GlobalAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the ElementMinOccurs0 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMinOccurs0 when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementMinOccurs0 pattern within an document [ElementMinOccurs0]:

The following example element is valid against the above example when included inside an instance document [ElementMinOccurs001]:

as is the following element when included in an instance document [ElementMinOccurs002]:

An , or other document containing an element <xs:schema>, exhibits the ElementMinOccurs1 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMinOccurs1 when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementMinOccurs1 pattern within an document [ElementMinOccurs1]:

The following example element is valid against the above example when included inside an instance document [ElementMinOccurs101]:

An , or other document containing an element <xs:schema>, exhibits the ElementMaxOccurs1 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMaxOccurs1 when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementMaxOccurs1 pattern within an document [ElementMaxOccurs1]:

The following example element is valid against the above example when included inside an instance document [ElementMaxOccurs101]:

as is the following element when included in an instance document [ElementMaxOccurs102]:

An , or other document containing an element <xs:schema>, exhibits the ElementMinOccurs0MaxOccursUnbounded pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMinOccurs0MaxOccursUnbounded when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementMinOccurs0MaxOccursUnbounded pattern within an document [NestedSequenceElementList]:

The following example element is valid against the above example when included inside an instance document [NestedSequenceElementList01]:

The following example extract illustrates the use of the ElementMinOccurs0MaxOccursUnbounded pattern within an document [ElementMinOccurs0MaxOccursUnbounded]:

The following example element is valid against the above example when included inside an instance document [ElementMinOccurs0MaxOccursUnbounded101]:

as is the following element when included in an instance document [ElementMinOccurs0MaxOccursUnbounded102]:

An , or other document containing an element <xs:schema>, exhibits the ElementMinOccurs1MaxOccursUnbounded pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMinOccurs1MaxOccursUnbounded when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementMinOccurs1MaxOccursUnbounded pattern within an document [ElementMaxOccursUnbounded]:

The following example element is valid against the above example when included inside an instance document [ElementMaxOccursUnbounded01]:

as is the following element when included in an instance document [ElementMaxOccursUnbounded02]:

The following example extract illustrates the use of the ElementMinOccurs1MaxOccursUnbounded pattern within an document [ElementMinOccurs1MaxOccursUnbounded]:

The following example element is valid against the above example when included inside an instance document [ElementMinOccurs1MaxOccursUnbounded101]:

as is the following element when included in an instance document [ElementMinOccurs1MaxOccursUnbounded102]:

An , or other document containing an element <xs:schema>, exhibits the ElementFormQualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementFormQualified when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementFormQualified pattern within an document [ElementFormQualified]:

The following example element is valid against the above example when included inside an instance document [ElementFormQualified01]:

An , or other document containing an element <xs:schema>, exhibits the SequenceElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SequenceElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the SequenceElement pattern within an document [SequenceElement]:

The following example element is valid against the above example when included inside an instance document [SequenceElement01]:

An , or other document containing an element <xs:schema>, exhibits the SequenceSingleRepeatedElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SequenceSingleRepeatedElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the SequenceSingleRepeatedElement pattern within an document [SequenceSingleRepeatedElement]:

The following example element is valid against the above example when included inside an instance document [SequenceSingleRepeatedElement01]:

as is the following element when included in an instance document [SequenceSingleRepeatedElement02]:

An , or other document containing an element <xs:schema>, exhibits the ElementEmptySequence pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementEmptySequence when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementEmptySequence pattern within an document [ElementEmptySequence]:

The following example element is valid against the above example when included inside an instance document [ElementEmptySequence01]:

An , or other document containing an element <xs:schema>, exhibits the ElementEmptyComplexType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementEmptyComplexType when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementEmptyComplexType pattern within an document [ElementEmptyComplexType]:

The following example element is valid against the above example when included inside an instance document [ElementEmptyComplexType01]:

An , or other document containing an element <xs:schema>, exhibits the NillableElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NillableElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NillableElement pattern within an document [NillableElement]:

The following example element is valid against the above example when included inside an instance document [NillableElement01]:

as is the following element when included in an instance document [NillableElement02]:

An , or other document containing an element <xs:schema>, exhibits the NotNillableElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NotNillableElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NotNillableElement pattern within an document [NotNillableElement]:

The following example element is valid against the above example when included inside an instance document [NotNillableElement01]:

An , or other document containing an element <xs:schema>, exhibits the ElementTypeReference pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementTypeReference when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementTypeReference pattern within an document [ElementTypeReference]:

The following example element is valid against the above example when included inside an instance document [ElementTypeReference01]:

An , or other document containing an element <xs:schema>, exhibits the ElementReference pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementReference when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ElementReference pattern within an document [ElementReference]:

The following example element is valid against the above example when included inside an instance document [ElementReference01]:

An , or other document containing an element <xs:schema>, exhibits the LocalElementComplexType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LocalElementComplexType when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the LocalElementComplexType pattern within an document [LocalElementComplexType]:

The following example element is valid against the above example when included inside an instance document [LocalElementComplexType01]:

An , or other document containing an element <xs:schema>, exhibits the AttributeFormUnqualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeFormUnqualified when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the AttributeFormUnqualified pattern within an document [AttributeFormUnqualified]:

The following example element is valid against the above example when included inside an instance document [AttributeFormUnqualifiedExample01]:

An , or other document containing an element <xs:schema>, exhibits the AttributeOptional pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeOptional when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the AttributeOptional pattern within an document [AttributeOptional]:

The following example element is valid against the above example when included inside an instance document [AttributeOptional01]:

as is the following element when included in an instance document [AttributeOptional02]:

An , or other document containing an element <xs:schema>, exhibits the AttributeReference pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeReference when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the AttributeReference pattern within an document [AttributeReference]:

The following example element is valid against the above example when included inside an instance document [AttributeReference01]:

An , or other document containing an element <xs:schema>, exhibits the AttributeTypeReference pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeTypeReference when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the AttributeTypeReference pattern within an document [AttributeTypeReference]:

The following example element is valid against the above example when included inside an instance document [AttributeTypeReference01]:

as is the following element when included in an instance document [AttributeTypeReference02]:

An , or other document containing an element <xs:schema>, exhibits the GlobalSimpleType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalSimpleType when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the GlobalSimpleType pattern within an document [GlobalSimpleType]:

The following example element is valid against the above example when included inside an instance document [GlobalSimpleType01]:

An , or other document containing an element <xs:schema>, exhibits the GlobalComplexType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalComplexType when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the GlobalComplexType pattern within an document [GlobalComplexType]:

The following example element is valid against the above example when included inside an instance document [GlobalComplexTypeExample01]:

An , or other document containing an element <xs:schema>, exhibits the StringEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/StringEnumerationType when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the StringEnumerationType pattern within an document [StringEnumerationType]:

The following example element is valid against the above example when included inside an instance document [StringEnumerationType01]:

as is the following element when included in an instance document [StringEnumerationType02]:

and the following element when included in an instance document [StringEnumerationType03]:

An , or other document containing an element <xs:schema>, exhibits the NullEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NullEnumerationType when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NullEnumerationType pattern within an document [NullEnumerationType]:

The following example element is valid against the above example when included inside an instance document [NullEnumerationType01]:

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ComplexTypeAttribute pattern within an document [ComplexTypeAttribute]:

The following example element is valid against the above example when included inside an instance document [ComplexTypeAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeSequence pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeSequence when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ComplexTypeSequence pattern within an document [ComplexTypeSequence]:

The following example element is valid against the above example when included inside an instance document [ComplexTypeSequence01]:

as is the following element when included in an instance document [ComplexTypeSequence02]:

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeAttributeExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeAttributeExtension when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ComplexTypeAttributeExtension pattern within an document [ComplexTypeAttributeExtension]:

The following example element is valid against the above example when included inside an instance document [ComplexTypeAttributeExtension01]:

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeSequenceExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeSequenceExtension when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ComplexTypeSequenceExtension pattern within an document [ComplexTypeSequenceExtension]:

The following example element is valid against the above example when included inside an instance document [ComplexTypeSequenceExtension01]:

An , or other document containing an element <xs:schema>, exhibits the SequenceMinOccurs1 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SequenceMinOccurs1 when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the SequenceMinOccurs1 pattern within an document [SequenceMinOccurs1]:

The following example element is valid against the above example when included inside an instance document [SequenceMinOccurs101]:

An , or other document containing an element <xs:schema>, exhibits the SequenceMaxOccurs1 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SequenceMaxOccurs1 when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the SequenceMaxOccurs1 pattern within an document [SequenceMaxOccurs1]:

The following example element is valid against the above example when included inside an instance document [SequenceMaxOccurs101]:

as is the following element when included in an instance document [SequenceMaxOccurs102]:

An , or other document containing an element <xs:schema>, exhibits the StringElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/StringElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the StringElement pattern within an document [StringElement]:

The following example element is valid against the above example when included inside an instance document [StringElement01]:

as is the following element when included in an instance document [StringElement02]:

An , or other document containing an element <xs:schema>, exhibits the BooleanElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/BooleanElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the BooleanElement pattern within an document [BooleanElement]:

The following example element is valid against the above example when included inside an instance document [BooleanElement01]:

as is the following element when included in an instance document [BooleanElement02]:

and the following element when included in an instance document [BooleanElement03]:

and the following element when included in an instance document [BooleanElement04]:

An , or other document containing an element <xs:schema>, exhibits the DoubleElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DoubleElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the DoubleElement pattern within an document [DoubleElement]:

The following example element is valid against the above example when included inside an instance document [DoubleElement01]:

as is the following element when included in an instance document [DoubleElement02]:

and the following element when included in an instance document [DoubleElement03]:

and the following element when included in an instance document [DoubleElement04]:

and the following element when included in an instance document [DoubleElement05]:

An , or other document containing an element <xs:schema>, exhibits the DateTimeElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DateTimeElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the DateTimeElement pattern within an document [DateTimeElement]:

The following example element is valid against the above example when included inside an instance document [DateTimeElement01]:

as is the following element when included in an instance document [DateTimeElement02]:

and the following element when included in an instance document [DateTimeElement03]:

and the following element when included in an instance document [DateTimeElement04]:

and the following element when included in an instance document [DateTimeElement05]:

and the following element when included in an instance document [DateTimeElement06]:

An , or other document containing an element <xs:schema>, exhibits the Base64BinaryElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/Base64BinaryElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the Base64BinaryElement pattern within an document [Base64BinaryElement]:

The following example element is valid against the above example when included inside an instance document [Base64BinaryElement01]:

as is the following element when included in an instance document [Base64BinaryElement02]:

and the following element when included in an instance document [Base64BinaryElement03]:

An , or other document containing an element <xs:schema>, exhibits the AnyURIElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyURIElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the AnyURIElement pattern within an document [AnyURIElement]:

The following example element is valid against the above example when included inside an instance document [AnyURIElement01]:

An , or other document containing an element <xs:schema>, exhibits the QNameElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/QNameElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the QNameElement pattern within an document [QNameElement]:

The following example element is valid against the above example when included inside an instance document [QNameElement01]:

An , or other document containing an element <xs:schema>, exhibits the NormalizedStringElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NormalizedStringElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NormalizedStringElement pattern within an document [NormalizedStringElement]:

The following example element is valid against the above example when included inside an instance document [NormalizedStringElement01]:

as is the following element when included in an instance document [NormalizedStringElement02]:

An , or other document containing an element <xs:schema>, exhibits the TokenElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/TokenElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the TokenElement pattern within an document [TokenElement]:

The following example element is valid against the above example when included inside an instance document [TokenElement01]:

An , or other document containing an element <xs:schema>, exhibits the NameElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NameElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NameElement pattern within an document [NameElement]:

The following example element is valid against the above example when included inside an instance document [NameElement01]:

An , or other document containing an element <xs:schema>, exhibits the NCNameElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NCNameElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NCNameElement pattern within an document [NCNameElement]:

The following example element is valid against the above example when included inside an instance document [NCNameElement01]:

An , or other document containing an element <xs:schema>, exhibits the LongElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LongElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the LongElement pattern within an document [LongElement]:

The following example element is valid against the above example when included inside an instance document [LongElement01]:

as is the following element when included in an instance document [LongElement02]:

and the following element when included in an instance document [LongElement03]:

and the following element when included in an instance document [LongElement04]:

and the following element when included in an instance document [LongElement05]:

An , or other document containing an element <xs:schema>, exhibits the IntElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/IntElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the IntElement pattern within an document [IntElement]:

The following example element is valid against the above example when included inside an instance document [IntElement01]:

as is the following element when included in an instance document [IntElement02]:

and the following element when included in an instance document [IntElement03]:

and the following element when included in an instance document [IntElement04]:

and the following element when included in an instance document [IntElement05]:

An , or other document containing an element <xs:schema>, exhibits the ShortElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ShortElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ShortElement pattern within an document [ShortElement]:

The following example element is valid against the above example when included inside an instance document [ShortElement01]:

as is the following element when included in an instance document [ShortElement02]:

and the following element when included in an instance document [ShortElement03]:

and the following element when included in an instance document [ShortElement04]:

An , or other document containing an element <xs:schema>, exhibits the ByteElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ByteElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ByteElement pattern within an document [ByteElement]:

The following example element is valid against the above example when included inside an instance document [ByteElement01]:

as is the following element when included in an instance document [ByteElement02]:

and the following element when included in an instance document [ByteElement03]:

An , or other document containing an element <xs:schema>, exhibits the PositiveIntegerElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/PositiveIntegerElement when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the PositiveIntegerElement pattern within an document [PositiveIntegerElement]:

The following example element is valid against the above example when included inside an instance document [PositiveIntegerElement01]:

as is the following element when included in an instance document [PositiveIntegerElement02]:

and the following element when included in an instance document [PositiveIntegerElement03]:

An , or other document containing an element <xs:schema>, exhibits the StringAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/StringAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the StringAttribute pattern within an document [StringAttribute]:

The following example element is valid against the above example when included inside an instance document [StringAttribute01]:

as is the following element when included in an instance document [StringAttribute02]:

An , or other document containing an element <xs:schema>, exhibits the BooleanAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/BooleanAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the BooleanAttribute pattern within an document [BooleanAttribute]:

The following example element is valid against the above example when included inside an instance document [BooleanAttribute01]:

as is the following element when included in an instance document [BooleanAttribute02]:

An , or other document containing an element <xs:schema>, exhibits the DoubleAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DoubleAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the DoubleAttribute pattern within an document [DoubleAttribute]:

The following example element is valid against the above example when included inside an instance document [DoubleAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the DateTimeAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DateTimeAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the DateTimeAttribute pattern within an document [DateTimeAttribute]:

The following example element is valid against the above example when included inside an instance document [DateTimeAttribute01]:

as is the following element when included in an instance document [DateTimeAttribute02]:

and the following element when included in an instance document [DateTimeAttribute03]:

and the following element when included in an instance document [DateTimeAttribute04]:

and the following element when included in an instance document [DateTimeAttribute05]:

and the following element when included in an instance document [DateTimeAttribute06]:

An , or other document containing an element <xs:schema>, exhibits the AnyURIAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyURIAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the AnyURIAttribute pattern within an document [AnyURIAttribute]:

The following example element is valid against the above example when included inside an instance document [AnyURIAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the QNameAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/QNameAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the QNameAttribute pattern within an document [QNameAttribute]:

The following example element is valid against the above example when included inside an instance document [QNameAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the NormalizedStringAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NormalizedStringAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NormalizedStringAttribute pattern within an document [NormalizedStringAttribute]:

The following example element is valid against the above example when included inside an instance document [NormalizedStringAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the TokenAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/TokenAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the TokenAttribute pattern within an document [TokenAttribute]:

The following example element is valid against the above example when included inside an instance document [TokenAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the NameAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NameAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NameAttribute pattern within an document [NameAttribute]:

The following example element is valid against the above example when included inside an instance document [NameAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the NCNameAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NCNameAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NCNameAttribute pattern within an document [NCNameAttribute]:

The following example element is valid against the above example when included inside an instance document [NCNameAttribute01]:

An , or other document containing an element <xs:schema>, exhibits the LongAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LongAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the LongAttribute pattern within an document [LongAttribute]:

The following example element is valid against the above example when included inside an instance document [LongAttribute01]:

as is the following element when included in an instance document [LongAttribute02]:

and the following element when included in an instance document [LongAttribute03]:

and the following element when included in an instance document [LongAttribute04]:

and the following element when included in an instance document [LongAttribute05]:

An , or other document containing an element <xs:schema>, exhibits the IntAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/IntAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the IntAttribute pattern within an document [IntAttribute]:

The following example element is valid against the above example when included inside an instance document [IntAttribute01]:

as is the following element when included in an instance document [IntAttribute02]:

and the following element when included in an instance document [IntAttribute03]:

and the following element when included in an instance document [IntAttribute04]:

and the following element when included in an instance document [IntAttribute05]:

An , or other document containing an element <xs:schema>, exhibits the ShortAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ShortAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ShortAttribute pattern within an document [ShortAttribute]:

The following example element is valid against the above example when included inside an instance document [ShortAttribute01]:

as is the following element when included in an instance document [ShortAttribute02]:

and the following element when included in an instance document [ShortAttribute03]:

and the following element when included in an instance document [ShortAttribute04]:

An , or other document containing an element <xs:schema>, exhibits the ByteAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ByteAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the ByteAttribute pattern within an document [ByteAttribute]:

The following example element is valid against the above example when included inside an instance document [ByteAttribute01]:

as is the following element when included in an instance document [ByteAttribute02]:

and the following element when included in an instance document [ByteAttribute03]:

An , or other document containing an element <xs:schema>, exhibits the NonNegativeIntegerAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NonNegativeIntegerAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the NonNegativeIntegerAttribute pattern within an document [NonNegativeIntegerAttribute]:

The following example element is valid against the above example when included inside an instance document [NonNegativeIntegerAttribute01]:

as is the following element when included in an instance document [NonNegativeIntegerAttribute02]:

and the following element when included in an instance document [NonNegativeIntegerAttribute03]:

and the following element when included in an instance document [NonNegativeIntegerAttribute04]:

and the following element when included in an instance document [NonNegativeIntegerAttribute05]:

An , or other document containing an element <xs:schema>, exhibits the PositiveIntegerAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/PositiveIntegerAttribute when the following expression applied to a document or element node with a context node of //xs:schema results in an node-set containing at least one node:

The following example extract illustrates the use of the PositiveIntegerAttribute pattern within an document [PositiveIntegerAttribute]:

The following example element is valid against the above example when included inside an instance document [PositiveIntegerAttribute01]:

as is the following element when included in an instance document [PositiveIntegerAttribute02]:

and the following element when included in an instance document [PositiveIntegerAttribute03]: