An , or other document containing an element <xs:schema>, exhibits the NoTargetNamespace pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NoTargetNamespace 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 [ NoTargetNamespace] illustrates the use of the NoTargetNamespace pattern:

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

An , or other document containing an element <xs:schema>, exhibits the UnqualifiedLocalElements pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/UnqualifiedLocalElements 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 [ UnqualifiedLocalElements] illustrates the use of the UnqualifiedLocalElements pattern:

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

An , or other document containing an element <xs:schema>, exhibits the QualifiedLocalAttributes pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/QualifiedLocalAttributes 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 [ QualifiedLocalAttributes] illustrates the use of the QualifiedLocalAttributes pattern:

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

An , or other document containing an element <xs:schema>, exhibits the FinalDefault pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/FinalDefault 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 [ FinalDefault] illustrates the use of the FinalDefault pattern:

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

An , or other document containing an element <xs:schema>, exhibits the BlockDefault pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/BlockDefault 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 [ BlockDefault] illustrates the use of the BlockDefault pattern:

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

An , or other document containing an element <xs:schema>, exhibits the XmlLang pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/XmlLang 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 [ XmlLang] illustrates the use of the XmlLang pattern:

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

An , or other document containing an element <xs:schema>, exhibits the AppinfoElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AppinfoElement 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 AppinfoElement pattern within an document [ AppinfoElement]:

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

An , or other document containing an element <xs:schema>, exhibits the MixedComplexContent pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/MixedComplexContent 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 MixedComplexContent pattern within an document [ MixedComplexContent]:

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

An , or other document containing an element <xs:schema>, exhibits the MixedContentType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/MixedContentType 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 MixedContentType pattern within an document [ MixedContentType]:

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

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

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

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

An , or other document containing an element <xs:schema>, exhibits the ImportSchemaNamespace pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ImportSchemaNamespace 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 ImportSchemaNamespace pattern within an document [ ImportSchemaNamespace]:

An , or other document containing an element <xs:schema>, exhibits the GlobalElementUnqualifiedType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementUnqualifiedType 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 GlobalElementUnqualifiedType pattern within an document [ GlobalElementUnqualifiedType]:

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

An , or other document containing an element <xs:schema>, exhibits the ElementTypeDefaultNamespace pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementTypeDefaultNamespace 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 ElementTypeDefaultNamespace pattern within an document [ ElementTypeDefaultNamespace]:

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

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementAbstract pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementAbstract 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 GlobalElementAbstract pattern within an document [ GlobalElementAbstract]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementBlock pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementBlock 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 GlobalElementBlock pattern within an document [ GlobalElementBlock]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementFinal pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementFinal 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 GlobalElementFinal pattern within an document [ GlobalElementFinal]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementAll pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementAll 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 GlobalElementAll pattern within an document [ GlobalElementAll]:

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

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementChoice pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementChoice 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 GlobalElementChoice pattern within an document [ GlobalElementChoice]:

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

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementSimpleType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementSimpleType 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 GlobalElementSimpleType pattern within an document [ GlobalElementSimpleType]:

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

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementComplexTypeSequenceExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementComplexTypeSequenceExtension 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 GlobalElementComplexTypeSequenceExtension pattern within an document [ GlobalElementComplexTypeSequenceExtension]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementComplexTypeEmptyExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementComplexTypeEmptyExtension 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 GlobalElementComplexTypeEmptyExtension pattern within an document [ GlobalElementComplexTypeEmptyExtension]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalAttributeUnqualifiedType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalAttributeUnqualifiedType 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 GlobalAttributeUnqualifiedType pattern within an document [ GlobalAttributeUnqualifiedType]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalAttributeSimpleType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalAttributeSimpleType 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 GlobalAttributeSimpleType pattern within an document [ GlobalAttributeSimpleType]:

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

An , or other document containing an element <xs:schema>, exhibits the ElementMinOccursFinite pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMinOccursFinite 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 ElementMinOccursFinite pattern within an document [ ElementMinOccursFinite]:

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

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

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

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

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

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

An , or other document containing an element <xs:schema>, exhibits the ElementMinOccurs0MaxOccursFinite pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMinOccurs0MaxOccursFinite 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 ElementMinOccurs0MaxOccursFinite pattern within an document [ ElementMinOccurs0MaxOccursFinite]:

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

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

An , or other document containing an element <xs:schema>, exhibits the ElementMaxOccursFinite pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementMaxOccursFinite 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 ElementMaxOccursFinite pattern within an document [ ElementMaxOccursFinite]:

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

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

An , or other document containing an element <xs:schema>, exhibits the ElementFormUnqualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementFormUnqualified 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 ElementFormUnqualified pattern within an document [ ElementFormUnqualified]:

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

An , or other document containing an element <xs:schema>, exhibits the ChoiceElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ChoiceElement 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 ChoiceElement pattern within an document [ ChoiceElement]:

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

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

An , or other document containing an element <xs:schema>, exhibits the AllElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AllElement 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 AllElement pattern within an document [ AllElement]:

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

An , or other document containing an element <xs:schema>, exhibits the ElementFixed pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementFixed 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 ElementFixed pattern within an document [ ElementFixed]:

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

An , or other document containing an element <xs:schema>, exhibits the AttributeElementNameClash pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeElementNameClash 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 AttributeElementNameClash pattern within an document [ AttributeElementNameClash]:

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

An , or other document containing an element <xs:schema>, exhibits the NillableOptionalElement pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NillableOptionalElement 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 NillableOptionalElement pattern within an document [ NillableOptionalElement]:

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

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

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

An , or other document containing an element <xs:schema>, exhibits the ElementTypeReferenceUnqualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementTypeReferenceUnqualified 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 ElementTypeReferenceUnqualified pattern within an document [ ElementTypeReferenceUnqualified]:

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

An , or other document containing an element <xs:schema>, exhibits the ElementReferenceUnqualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementReferenceUnqualified 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 ElementReferenceUnqualified pattern within an document [ ElementReferenceUnqualified]:

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

An , or other document containing an element <xs:schema>, exhibits the LocalElementSimpleType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LocalElementSimpleType 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 LocalElementSimpleType pattern within an document [ LocalElementSimpleType]:

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

An , or other document containing an element <xs:schema>, exhibits the LocalElementComplexTypeEmptyExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LocalElementComplexTypeEmptyExtension 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 LocalElementComplexTypeEmptyExtension pattern within an document [ LocalElementComplexTypeEmptyExtension]:

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

An , or other document containing an element <xs:schema>, exhibits the ElementDefaultAnyType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementDefaultAnyType 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 ElementDefaultAnyType pattern within an document [ ElementDefaultAnyType]:

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

An , or other document containing an element <xs:schema>, exhibits the ElementKey pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementKey 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 ElementKey pattern within an document [ ElementKey]:

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

An , or other document containing an element <xs:schema>, exhibits the MaxOccurs0 pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/MaxOccurs0 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 MaxOccurs0 pattern within an document [ MaxOccurs0]:

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

An , or other document containing an element <xs:schema>, exhibits the AttributeFormQualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeFormQualified 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 AttributeFormQualified pattern within an document [ AttributeFormQualified]:

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

An , or other document containing an element <xs:schema>, exhibits the ElementDefault pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ElementDefault 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 ElementDefault pattern within an document [ GlobalElementDefault]:

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

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

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

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

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

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

An , or other document containing an element <xs:schema>, exhibits the AttributeRequired pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeRequired 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 AttributeRequired pattern within an document [ AttributeRequired]:

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

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

An , or other document containing an element <xs:schema>, exhibits the AttributeFixed pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeFixed 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 AttributeFixed pattern within an document [ AttributeFixed]:

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

An , or other document containing an element <xs:schema>, exhibits the AttributeDefault pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeDefault 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 AttributeDefault pattern within an document [ AttributeDefault]:

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

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

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

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

An , or other document containing an element <xs:schema>, exhibits the AttributeReferenceUnqualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeReferenceUnqualified 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 AttributeReferenceUnqualified pattern within an document [ AttributeReferenceUnqualified]:

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

An , or other document containing an element <xs:schema>, exhibits the AttributeTypeReferenceUnqualified pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeTypeReferenceUnqualified 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 AttributeTypeReferenceUnqualified pattern within an document [ AttributeTypeReferenceUnqualified]:

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

An , or other document containing an element <xs:schema>, exhibits the LocalAttributeSimpleType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LocalAttributeSimpleType 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 LocalAttributeSimpleType pattern within an document [ LocalAttributeSimpleType]:

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

An , or other document containing an element <xs:schema>, exhibits the AttributeProhibited pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AttributeProhibited 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 AttributeProhibited pattern within an document [ AttributeProhibited]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalComplexTypeAbstract pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalComplexTypeAbstract 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 GlobalComplexTypeAbstract pattern within an document [ GlobalComplexTypeAbstract]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalComplexTypeBlock pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalComplexTypeBlock 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 GlobalComplexTypeBlock pattern within an document [ GlobalComplexTypeBlock]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalComplexTypeEmptyExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalComplexTypeEmptyExtension 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 GlobalComplexTypeEmptyExtension pattern within an document [ GlobalComplexTypeEmptyExtension]:

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

An , or other document containing an element <xs:schema>, exhibits the NMTOKENEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NMTOKENEnumerationType 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 NMTOKENEnumerationType pattern within an document [ NMTOKENEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the IntEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/IntEnumerationType 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 IntEnumerationType pattern within an document [ IntEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the ShortEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ShortEnumerationType 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 ShortEnumerationType pattern within an document [ ShortEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the LongEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LongEnumerationType 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 LongEnumerationType pattern within an document [ LongEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the DoubleEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DoubleEnumerationType 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 DoubleEnumerationType pattern within an document [ DoubleEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the IntegerEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/IntegerEnumerationType 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 IntegerEnumerationType pattern within an document [ IntegerEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the DecimalEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DecimalEnumerationType 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 DecimalEnumerationType pattern within an document [ DecimalEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the FloatEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/FloatEnumerationType 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 FloatEnumerationType pattern within an document [ FloatEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the NonNegativeIntegerEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/NonNegativeIntegerEnumerationType 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 NonNegativeIntegerEnumerationType pattern within an document [ NonNegativeIntegerEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the PositiveIntegerEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/PositiveIntegerEnumerationType 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 PositiveIntegerEnumerationType pattern within an document [ PositiveIntegerEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the UnsignedIntEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/UnsignedIntEnumerationType 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 UnsignedIntEnumerationType pattern within an document [ UnsignedIntEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the UnsignedLongEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/UnsignedLongEnumerationType 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 UnsignedLongEnumerationType pattern within an document [ UnsignedLongEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the UnsignedShortEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/UnsignedShortEnumerationType 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 UnsignedShortEnumerationType pattern within an document [ UnsignedShortEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the TokenEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/TokenEnumerationType 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 TokenEnumerationType pattern within an document [ TokenEnumerationType]:

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

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

An , or other document containing an element <xs:schema>, exhibits the LanguageEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/LanguageEnumerationType 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 LanguageEnumerationType pattern within an document [ LanguageEnumerationType]:

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

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

An , or other document containing an element <xs:schema>, exhibits the SimpleTypeEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SimpleTypeEnumerationType 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 SimpleTypeEnumerationType pattern within an document [ SimpleTypeEnumerationType]:

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

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

An , or other document containing an element <xs:schema>, exhibits the DecimalSimpleTypeTotalDigits pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DecimalSimpleTypeTotalDigits 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 DecimalSimpleTypeTotalDigits pattern within an document [ DecimalSimpleTypeTotalDigits]:

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

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

An , or other document containing an element <xs:schema>, exhibits the DecimalSimpleTypeFractionDigits pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/DecimalSimpleTypeFractionDigits 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 DecimalSimpleTypeFractionDigits pattern within an document [ DecimalSimpleTypeFractionDigits]:

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

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

An , or other document containing an element <xs:schema>, exhibits the QNameEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/QNameEnumerationType 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 QNameEnumerationType pattern within an document [ QNameEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the AnyURIEnumerationType pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyURIEnumerationType 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 AnyURIEnumerationType pattern within an document [ AnyURIEnumerationType]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeAll pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeAll 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 ComplexTypeAll pattern within an document [ ComplexTypeAll]:

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

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeChoice pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeChoice 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 ComplexTypeChoice pattern within an document [ ComplexTypeChoice]:

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

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

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeOnlyAttributes pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeOnlyAttributes 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 ComplexTypeOnlyAttributes pattern within an document [ ComplexTypeOnlyAttributes]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeOnlyAttributeGroup pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeOnlyAttributeGroup 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 ComplexTypeOnlyAttributeGroup pattern within an document [ ComplexTypeOnlyAttributeGroup]:

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

An , or other document containing an element <xs:schema>, exhibits the GlobalElementSequenceAny pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/GlobalElementSequenceAny 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 GlobalElementSequenceAny pattern within an document [ GlobalElementSequenceAny]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeAnyAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeAnyAttribute 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 ComplexTypeAnyAttribute pattern within an document [ ComplexTypeAnyAttribute]:

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

An , or other document containing an element <xs:schema>, exhibits the AnyAttributeStrict pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyAttributeStrict 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 AnyAttributeStrict pattern within an document [ AnyAttributeStrict]:

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

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

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

An , or other document containing an element <xs:schema>, exhibits the AnyAttributeLax pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyAttributeLax 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 AnyAttributeLax pattern within an document [ AnyAttributeLax]:

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

An , or other document containing an element <xs:schema>, exhibits the AnyAttributeSkip pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyAttributeSkip 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 AnyAttributeSkip pattern within an document [ AnyAttributeSkip]:

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

An , or other document containing an element <xs:schema>, exhibits the AnyAttributeOtherStrict pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyAttributeOtherStrict 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 AnyAttributeOtherStrict pattern within an document [ AnyAttributeOtherStrict]:

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

An , or other document containing an element <xs:schema>, exhibits the AnyAttributeOtherLax pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyAttributeOtherLax 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 AnyAttributeOtherLax pattern within an document [ AnyAttributeOtherLax]:

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

An , or other document containing an element <xs:schema>, exhibits the AnyAttributeOtherSkip pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/AnyAttributeOtherSkip 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 AnyAttributeOtherSkip pattern within an document [ AnyAttributeOtherSkip]:

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

An , or other document containing an element <xs:schema>, exhibits the ExtendedSimpleContent pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ExtendedSimpleContent 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 ExtendedSimpleContent pattern within an document [ ExtendedSimpleContent]:

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

An , or other document containing an element <xs:schema>, exhibits the SOAPEncodedArray pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SOAPEncodedArray 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 [ SOAPEncodedArray] illustrates the use of the SOAPEncodedArray pattern:

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

An , or other document containing an element <xs:schema>, exhibits the RestrictedSimpleContent pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/RestrictedSimpleContent 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 RestrictedSimpleContent pattern within an document [ RestrictedSimpleContent]:

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

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeChoiceExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeChoiceExtension 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 ComplexTypeChoiceExtension pattern within an document [ ComplexTypeChoiceExtension]:

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

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeAttributeGroupExtension pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeAttributeGroupExtension 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 ComplexTypeAttributeGroupExtension pattern within an document [ ComplexTypeAttributeGroupExtension]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeAttributeRestriction pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeAttributeRestriction 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 ComplexTypeAttributeRestriction pattern within an document [ ComplexTypeAttributeRestriction]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeSequenceRestriction pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeSequenceRestriction 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 ComplexTypeSequenceRestriction pattern within an document [ ComplexTypeSequenceRestriction]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexContentRestrictionAnyAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexContentRestrictionAnyAttribute 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 ComplexContentRestrictionAnyAttribute pattern within an document [ ComplexContentRestrictionAnyAttribute]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexContentExtensionAnyAttribute pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexContentExtensionAnyAttribute 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 ComplexContentExtensionAnyAttribute pattern within an document [ ComplexContentExtensionAnyAttribute]:

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

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeFinal pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeFinal 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 ComplexTypeFinal pattern within an document [ ComplexTypeFinal]:

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

An , or other document containing an element <xs:schema>, exhibits the ComplexTypeExtensionAnnotationOnly pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/ComplexTypeExtensionAnnotationOnly 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 ComplexTypeExtensionAnnotationOnly pattern within an document [ ComplexTypeExtensionAnnotationOnly]:

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

An , or other document containing an element <xs:schema>, exhibits the SimpleContentAnyAttributeSkip pattern identified using the URI http://www.w3.org/2002/ws/databinding/patterns/6/09/SimpleContentAnyAttributeSkip 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 SimpleContentAnyAttributeSkip pattern within an document [ SimpleContentAnyAttributeSkip]:

The following example element is valid