This specification provides a set of basic
This is a public Working Group Note produced by the XML Schema Patterns for Databinding Working Group, which is part of the W3C Web Services Activity. This publication as a Working Group Note coincides with the end of the Working Group's charter period, and represents the culmination of the group's work.
Comments from interested parties and incorporates comments received since the first Last Call publication on
2006-11-22 of this document were sent to the public
This document was built using evidence and experience gained examining the interoperability of a significant number of
state of the art databinding implementations using a
The Working Group also produced an accompanying
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft specification and may be updated, replaced or obsoleted by other specification at any time. It is inappropriate to cite this specification as other than work in progress.
This document was produced by a Working Group operating under the
A databinding tool generates a mapping between
A representative collection of databinding implementations in common use has been used
to provide an indication of the "state of the art".
State of the art databinding implementations have displayed uneven and inconsistent
support of the W3C
This specification provides a basic set of example
Authors of
Implementers of databinding tools may find these patterns useful to represent simple and common place data structures. Ensuring tools recognize at least these simple
All parts of this specification are normative, with the EXCEPTION of notes, examples, and sections explicitly marked as Non-Normative.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be
interpreted as described in
Each
Each
Assertions about documents and implementations that are
not enforced by the normative patterns are
marked by a dagger symbol (†) at the end of a sentence.
Each assertion has been assigned a unique and stable identifier.
The assertion identifiers may be used
by implementations of this specification for any purpose,
such as error reporting.
The assertions and their identifiers are
summarized in section
This specification uses a number of namespace prefixes throughout; they are
listed in
| Prefix | Namespace |
|---|---|
| xs | http://www.w3.org/2001/XMLSchema |
| xsi | http://www.w3.org/2001/XMLSchema-instance |
| soap11 | http://schemas.xmlsoap.org/soap/envelope/ |
| soap12 | http://www.w3.org/2003/05/soap-envelope |
| wsdl11 | http://schemas.xmlsoap.org/wsdl/ |
| wsdl20 | http://www.w3.org/2005/08/wsdl |
| pat | http://www.w3.org/2002/ws/databinding/patterns/6/09/ |
| ex | http://www.w3.org/2002/ws/databinding/examples/6/09/ |
A document claiming conformance to this specification:
An implementation that claims conformance to this specification:
Describing the form of the data model provided by a databinding implementation is
beyond the scope of this specification. For example, the unconstrained built-in numeric
primitive types,
xs:decimal,
xs:integer,
xs:negativeInteger,
xs:positiveInteger,
xs:nonNegativeInteger and
xs:nonPositiveInteger,
do not map directly to native types
in many programming languages and are likely to be presented as a toolkit specific construct
or more generalised ways, such as a 'string'.
Note that although the patterns contained in this document are defined using
This section defines the set of concrete
A URI
A normative
<xs:schema>
element node which may be an
<xs:schema> element contained inside
an
Note, the
Optionally one or more non-normative
A collection of patterns, including patterns beyond the scope of this
specification, are available from
http://www.w3.org/2002/ws/databinding/patterns/6/09/.
This document offers no additional semantics for the schema patterns presented
beyond those specified by the
xs:schema
element MAY be the document element,
but MAY also appear within other descriptions such as a
Note, this pattern represents a subset of the native identifier formats
supported by many, but not all, implementations and is therefore most likely to be
supported by a databinding tools which directly maps an
Note, this pattern may be further constrained by the regular expression used by the
xs:enumeration
value to an native identifier.
targetNamespace whose value is an absolute URI.
This pattern is designed to capture a reference to a namespace defined within a WSDL document types section.
elementFormDefault attribute value of
qualified.
An
<xs:schema>, exhibits the
TargetNamespace
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
QualifiedLocalElements
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
UnqualifiedLocalAttributes
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
SchemaVersion
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
DocumentationElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
IdentifierName
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NonIdentifierName
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NotMixed
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
MinOccurs1
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
MaxOccurs1
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ MaxOccurs02]:
An
<xs:schema>, exhibits the
Id
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ComplexTypeConcrete
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
GlobalElementConcrete
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ImportTypesNamespace
pattern identified using the URI
//xs:schema
results in an
The following example
An
<xs:schema>, exhibits the
ImportNamespace
pattern identified using the URI
//xs:schema
results in an
The following example
An
<xs:schema>, exhibits the
ImportSchema
pattern identified using the URI
//xs:schema
results in an
The following example
An
<xs:schema>, exhibits the
Include
pattern identified using the URI
//xs:schema
results in an
The following example
An
<xs:schema>, exhibits the
GlobalElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ GlobalElement02]:
and the following element when included in an instance document [ GlobalElement03]:
An
<xs:schema>, exhibits the
GlobalElementSequence
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
GlobalElementComplexType
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
GlobalAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ElementMinOccurs0
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ElementMinOccurs002]:
An
<xs:schema>, exhibits the
ElementMinOccurs1
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ElementMaxOccurs1
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ElementMaxOccurs102]:
An
<xs:schema>, exhibits the
ElementMinOccurs0MaxOccursUnbounded
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
The following example
The following example
as is the following element when included in an instance document [ ElementMinOccurs0MaxOccursUnbounded102]:
An
<xs:schema>, exhibits the
ElementMinOccurs1MaxOccursUnbounded
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ElementMaxOccursUnbounded02]:
The following example
The following example
as is the following element when included in an instance document [ ElementMinOccurs1MaxOccursUnbounded102]:
An
<xs:schema>, exhibits the
ElementFormQualified
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
SequenceElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
SequenceSingleRepeatedElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ SequenceSingleRepeatedElement02]:
An
<xs:schema>, exhibits the
ElementEmptySequence
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ElementEmptyComplexType
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NillableElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ NillableElement02]:
An
<xs:schema>, exhibits the
NotNillableElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ElementTypeReference
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ElementReference
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
LocalElementComplexType
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
AttributeFormUnqualified
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
AttributeOptional
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ AttributeOptional02]:
An
<xs:schema>, exhibits the
AttributeReference
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
AttributeTypeReference
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ AttributeTypeReference02]:
An
<xs:schema>, exhibits the
GlobalSimpleType
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
GlobalComplexType
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
StringEnumerationType
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ StringEnumerationType02]:
and the following element when included in an instance document [ StringEnumerationType03]:
An
<xs:schema>, exhibits the
NullEnumerationType
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ComplexTypeAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ComplexTypeSequence
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ComplexTypeSequence02]:
An
<xs:schema>, exhibits the
ComplexTypeAttributeExtension
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
ComplexTypeSequenceExtension
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
SequenceMinOccurs1
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
SequenceMaxOccurs1
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ SequenceMaxOccurs102]:
An
<xs:schema>, exhibits the
StringElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ StringElement02]:
An
<xs:schema>, exhibits the
BooleanElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ BooleanElement02]:
and the following element when included in an instance document [ BooleanElement03]:
and the following element when included in an instance document [ BooleanElement04]:
An
<xs:schema>, exhibits the
DoubleElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ DoubleElement02]:
and the following element when included in an instance document [ DoubleElement03]:
and the following element when included in an instance document [ DoubleElement04]:
and the following element when included in an instance document [ DoubleElement05]:
An
<xs:schema>, exhibits the
DateTimeElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ DateTimeElement02]:
and the following element when included in an instance document [ DateTimeElement03]:
and the following element when included in an instance document [ DateTimeElement04]:
and the following element when included in an instance document [ DateTimeElement05]:
and the following element when included in an instance document [ DateTimeElement06]:
An
<xs:schema>, exhibits the
Base64BinaryElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ Base64BinaryElement02]:
and the following element when included in an instance document [ Base64BinaryElement03]:
An
<xs:schema>, exhibits the
AnyURIElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
QNameElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NormalizedStringElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ NormalizedStringElement02]:
An
<xs:schema>, exhibits the
TokenElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NameElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NCNameElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
LongElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ LongElement02]:
and the following element when included in an instance document [ LongElement03]:
and the following element when included in an instance document [ LongElement04]:
and the following element when included in an instance document [ LongElement05]:
An
<xs:schema>, exhibits the
IntElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ IntElement02]:
and the following element when included in an instance document [ IntElement03]:
and the following element when included in an instance document [ IntElement04]:
and the following element when included in an instance document [ IntElement05]:
An
<xs:schema>, exhibits the
ShortElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ShortElement02]:
and the following element when included in an instance document [ ShortElement03]:
and the following element when included in an instance document [ ShortElement04]:
An
<xs:schema>, exhibits the
ByteElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ByteElement02]:
and the following element when included in an instance document [ ByteElement03]:
An
<xs:schema>, exhibits the
PositiveIntegerElement
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ PositiveIntegerElement02]:
and the following element when included in an instance document [ PositiveIntegerElement03]:
An
<xs:schema>, exhibits the
StringAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ StringAttribute02]:
An
<xs:schema>, exhibits the
BooleanAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ BooleanAttribute02]:
An
<xs:schema>, exhibits the
DoubleAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
DateTimeAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ DateTimeAttribute02]:
and the following element when included in an instance document [ DateTimeAttribute03]:
and the following element when included in an instance document [ DateTimeAttribute04]:
and the following element when included in an instance document [ DateTimeAttribute05]:
and the following element when included in an instance document [ DateTimeAttribute06]:
An
<xs:schema>, exhibits the
AnyURIAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
QNameAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NormalizedStringAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
TokenAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NameAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
NCNameAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
An
<xs:schema>, exhibits the
LongAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ LongAttribute02]:
and the following element when included in an instance document [ LongAttribute03]:
and the following element when included in an instance document [ LongAttribute04]:
and the following element when included in an instance document [ LongAttribute05]:
An
<xs:schema>, exhibits the
IntAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ IntAttribute02]:
and the following element when included in an instance document [ IntAttribute03]:
and the following element when included in an instance document [ IntAttribute04]:
and the following element when included in an instance document [ IntAttribute05]:
An
<xs:schema>, exhibits the
ShortAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ShortAttribute02]:
and the following element when included in an instance document [ ShortAttribute03]:
and the following element when included in an instance document [ ShortAttribute04]:
An
<xs:schema>, exhibits the
ByteAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ ByteAttribute02]:
and the following element when included in an instance document [ ByteAttribute03]:
An
<xs:schema>, exhibits the
NonNegativeIntegerAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ NonNegativeIntegerAttribute02]:
and the following element when included in an instance document [ NonNegativeIntegerAttribute03]:
and the following element when included in an instance document [ NonNegativeIntegerAttribute04]:
and the following element when included in an instance document [ NonNegativeIntegerAttribute05]:
An
<xs:schema>, exhibits the
PositiveIntegerAttribute
pattern identified using the URI
//xs:schema
results in an
The following example
The following example
as is the following element when included in an instance document [ PositiveIntegerAttribute02]:
and the following element when included in an instance document [ PositiveIntegerAttribute03]:
This section offers one or more patterns which may be used to represent an abstract data structure. Each data structure presented is intended to be independent of any particular programming language, database or modeling environment. No semantics are implied by the order in which patterns are listed for a given abstract data structure.
The patterns defined by this specification may be detected in a description
such as an
Similarly a
The
The following
elementFormDefault attribute of the
xs:schema element
elementFormDefault attribute of the
xs:schema element, where the contents of the
elementFormDefault attribute is the string
'qualified'.
mixed attributes contained on any element found beneath the
xs:schema element, where the contents of the
mixed attribute is the string value
'false'.
xs:complexType element where the parent node is not the element
xs:schema.
xs:documentation elements.
type attribute where the QName value of the
type attribute is a local part
string in the namespace found by resolving the prefix
xs in
'http://www.w3.org/2001/XMLSchema'.
xs:element,
name and
type attributes where the string value of the
type attribute contains a ':' character,
and the resultant QName value is not the
##targetNamespace or
##other namespace.
xs:import element and
namespace attribute for an
xs:import element with an absent
schemaLocation attribute
or one matching the
minOccurs and
maxOccurs attributes for an
xs:element element where the
minOccurs
attribute has a string value of
'0' and the
maxOccurs attribute is absent or has a string value of
'1'.
xs:element element and
maxOccurs attribute
where a
sequence has a single
xs:element element that is defined with
maxOccurs attribute string value of
'unbounded'.
xs:complexType and
xs:element element, and the
xs:element
name attribute where the complexType does not have any child nodes.
| Id | Pattern |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Id | Assertion |
|---|---|
|
|
The
NCName used
to declare an
|
|
|
MAY include the
|
|
|
MUST only contain
|
|
|
MAY contain additional
|
|
|
An
elementFormDefault attribute value of
qualified.
|
|
|
The
xs:schema
element MAY be the document element,
but MAY also appear within other descriptions such as a
|
|
|
An
targetNamespace whose value is an absolute URI.
|
|
|
MUST use either the UTF-8 or UTF-16
|
|
|
MUST be a well-formed
|
|
|
MUST be a 'schema
document', as defined in
|
| Id | Assertion |
|---|---|
|
|
MAY consume well-formed
|
|
|
MUST be able to consume any well-formed
|
|
|
MUST produce a data model exposing all of the
|
|
|
MAY allow the production of well-formed
|
|
|
MUST be able to produce well-formed
|
|
|
MUST be able to process any
|
This section lists all the elements, attributes and simple types defined by the XML Schema specifications and indicates if it is referenced from one of the patterns.
This document is the work of the
Members of the Working Group are (at the time of writing, and by alphabetical order): Vladislav Bezrukov (SAP AG), Jonathan Calladine (BT), George Cowe (Origo Services Limited), Paul Downey (BT), Paul Fremantle (WSO2), Anthony Julian (Health Level Seven, Inc.), Yves Lafon (W3C/ERCIM), Ajith Ranabahu (WSO2), Adrian Smith (BT), Amila Suriarachchi (WSO2), Priscilla Walmsley (W3C Invited Experts), Scott Wood (National Association of Convenience Stores (NACS)).
Previous members of the Working Group were: Paul Biron (Health Level Seven, Inc.), Otu Ekanem (BT), Sekhar Vajjhala (Sun Microsystems).
The people who have contributed to