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 against the above example when included inside an instance document [SimpleContentAnyAttributeSkip01]:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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