WSDL-related XML Schema language basics

The XML Schema Definition Language (XSD) has become a central and very common part of XML and Web services architectures. The hierarchical structure of XML documents can be formally defined by creating an XSD schemahence an XML document is considered an instance of its corresponding schema. Further, the structure established within an XSD schema (Figure 13.3) contains a series of rules and constraints to which XML document instances must comply for parsers and processors to deem them valid.

Figure 13.3. An XSD schema document.

The fundamental data representation rules provided by XSD schemas are related to representing data according to type. As with data types used in programming languages, XSD schemas provide a set of non-proprietary data types used to represent information in XML document instances.

The data types supported by XSD schemas are extensive, but they do not always map cleanly to the proprietary types used by programming languages. Therefore, many environments must go through a mapping process to select the XSD schema types best suited to represent data originating from or being delivered to proprietary application logic and data sources.

XSD schemas can exist as separate documents (typically identified by .xsd file extensions), or they may be embedded in other types of documents, such as XML document instances or WSDL definitions. XML document instances commonly link to a separate XSD schema file so that the same schema can be used to validate multiple document instances. WSDL definitions can import the contents of an XSD file, or they also can have schema content embedded inline.

Because almost all XML and Web services specifications are themselves written in XML, XSD schemas have become an intrinsic part of XML data representation and service-oriented architectures. Regardless of whether you explicitly define an XSD schema for your solution, your underlying processors will be using XSD schemas to execute many tasks related to the processing of XML documents through Web services. (The role of XSD schemas within SOA is explained further in the XML Schema and SOA section in Chapter 14.)

"Elements" vs. "Constructs"

Each of the specifications we explore in this and subsequent chapters provides a markup language that is expressed as an XML dialect. This means that the language itself is written in XML and is comprised of XML elements. Our focus is on describing key elements that provide features relevant to the topics discussed in this book. Sometimes we refer to language elements as constructs. A construct simply represents a key parent element likely to contain a set of related child elements. Therefore we use this term to communicate that the element we are discussing will contain additional elements that form a block of XML.

13.2.1. The schema element

The schema element is the root element of every XSD schema. It contains a series of common attributes used primarily to establish important namespace references. The xmlns attribute, for example, establishes a default namespace on its own, or can be used to declare a prefix that acts as an identifier to qualify other elements in the schema.

The namespace always is present so that it can be used to represent content in the schema that originates from the XSD specification and the elements in the schema document itself. This allows processors to distinguish native XSD schema content from user-defined content.

Example 13.1. The most basic form of schema declaration.


Other important attributes include targetNamespace, used to assign a namespace to the custom elements and attributes declared in the schema document, and the element-FormDefault attribute, which when set to a value of "qualified," requires that all elements in the XML document be associated with their corresponding namespace.

13.2.2. The element element

Using this element, you can declare a custom element that is then referenced by its name within an XML document instance.

For example, the following element declaration in an XSD schema:

Example 13.2. An element declaration in an XSD schema.


...will be represented within an XML document as follows:

Example 13.3. The usage of this element in an XML document instance.


...where the value in between the opening and closing InvoiceNumber tags is required to be an integer.

The type attribute of an element can be set to one of the predefined data types established by the XML Schema specification, or it can be assigned a complex type, as explained next.

13.2.3. The complexType and simpleType elements

With a complexType you can group elements and attributes into a composite type that can be used to represent a set of related data representations. The following example groups two elements named ID and WeeklyHoursLimit into a complexType named EmployeeHours.

Example 13.4. A complexType containing two element declarations.

<complexType name="EmployeeHours">

The EmployeeHours complexType can be assigned to one or more elements. This facilitates standardization and reuse of commonly grouped information and avoids redundant element declarations. Note that the sequence element is a type of indicator used within the complexType construct to establish a specific order for element elements.

simpleType elements also allow you to group related data representations, but these constructs cannot contain attributes or further child elements. (None of the examples used in this book contain simpleType elements.)

13.2.4. The import and include elements

XSD schemas can be modularized. This allows for one schema document to import the contents of another. Both the import and include elements are used to point to the location of the XSD schema file that will be pulled in when the schema is processed at runtime.

Example 13.5. The import and include elements.

 <import schemaLocation="..."
 <include schemaLocation="..."/>

The difference between these two elements is that include is used to reference schemas that use the same target namespace as the parent schema, whereas import is used to point to schemas that use a different target namespace. As per the previous example, a namespace attribute only is used with the import element.

13.2.5. Other important elements

The XML Schema Definition Language is large and complex and provides numerous options for structuring and validating XML document data. There are many other important parts of the language that are not used in the examples provided in this book, including:

  • additional type definition elements (attribute, complexContent, simpleContent)
  • constraint related elements (restriction, enumeration, pattern)
  • element indicators (maxOccurs, minOccurs, group)
  • extensibility elements (any, extension, redefine)
  • elements for simulating relationships between elements (unique, key, keyref)

Entire books have been written to explain the XML Schema Definition Language. See for recommended reading resources.


  • The XML Schema Definition Language is an intrinsic member of the XML and Web services specification landscape and is key to the service interface definition we are required to build as part of the service-oriented design process.
  • XSD schemas can be embedded or imported into WSDL definitions.


Case Studies

Part I: SOA and Web Services Fundamentals

Introducing SOA

The Evolution of SOA

Web Services and Primitive SOA

Part II: SOA and WS-* Extensions

Web Services and Contemporary SOA (Part I: Activity Management and Composition)

Web Services and Contemporary SOA (Part II: Advanced Messaging, Metadata, and Security)

Part III: SOA and Service-Orientation

Principles of Service-Orientation

Service Layers

Part IV: Building SOA (Planning and Analysis)

SOA Delivery Strategies

Service-Oriented Analysis (Part I: Introduction)

Service-Oriented Analysis (Part II: Service Modeling)

Part V: Building SOA (Technology and Design)

Service-Oriented Design (Part I: Introduction)

Service-Oriented Design (Part II: SOA Composition Guidelines)

Service-Oriented Design (Part III: Service Design)

Service-Oriented Design (Part IV: Business Process Design)

Fundamental WS-* Extensions

SOA Platforms

Appendix A. Case Studies: Conclusion

Service-Oriented Architecture. Concepts, Technology, and Design
Service-Oriented Architecture (SOA): Concepts, Technology, and Design
ISBN: 0131858580
EAN: 2147483647
Year: 2004
Pages: 150
Authors: Thomas Erl © 2008-2020.
If you may any questions please contact us: