XML Schema Documentation

Table of Contents

top

Schema Document Properties

Target Namespace http://www.rowa.de/wsdl/posps/types/order
Language en
Element and Attribute Namespaces
  • Global element and attribute declarations belong to this schema's target namespace.
  • By default, local element declarations have no namespace.
  • By default, local attribute declarations have no namespace.
Schema Composition
  • This schema imports schema(s) from the following namespace(s):
    • http://www.rowa.de/wsdl/posps/types (at posps.xsd)

Declared Namespaces

Prefix Namespace
Default namespace http://www.w3.org/1999/xhtml
xml http://www.w3.org/XML/1998/namespace
xsd http://www.w3.org/2001/XMLSchema
pptype http://www.rowa.de/wsdl/posps/types
order http://www.rowa.de/wsdl/posps/types/order
Schema Component Representation
<xsd:schema xml:lang="en" targetNamespace="http://www.rowa.de/wsdl/posps/types/order">
<xsd:import namespace="http://www.rowa.de/wsdl/posps/types" schemaLocation="posps.xsd"/>
...
</xsd:schema>
top

Global Declarations

Element: abortOrder

Name abortOrder
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Input parameter element of the abortOrder operation.
XML Instance Representation
<order:abortOrder>
<orderId> pptype:OrderId </orderId> [1]
</order:abortOrder>
Schema Component Representation
<xsd:element name="abortOrder">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="orderId" type=" pptype:OrderId "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: abortOrderResponse

Name abortOrderResponse
Type pptype:Empty
Nillable no
Abstract no
XML Instance Representation
Schema Component Representation
<xsd:element name="abortOrderResponse" type=" pptype:Empty "/>
top

Element: acceptsOrders

Name acceptsOrders
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Input parameter element of the acceptsOrders operation. Since the operation has no parameters, the element is just a placeholder to fulfill the requirements of the web service specifications.
XML Instance Representation
<order:acceptsOrders>
<posId> pptype:PosId </posId> [0..1]
</order:acceptsOrders>
Schema Component Representation
<xsd:element name="acceptsOrders">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="posId" type=" pptype:PosId " maxOccurs="1" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: acceptsOrdersResponse

Name acceptsOrdersResponse
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Output parameter element of the acceptsOrders operation. true if the server is currently ready to process orders, false otherwise.
XML Instance Representation
<order:acceptsOrdersResponse>
<acceptsOrders> xsd:boolean </acceptsOrders> [1]
</order:acceptsOrdersResponse>
Schema Component Representation
<xsd:element name="acceptsOrdersResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="acceptsOrders" type=" xsd:boolean "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: orderArticles

Name orderArticles
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Input parameter element of the orderArticles operation.
XML Instance Representation
<order:orderArticles>
<order> pptype:OrderArticleList </order> [1]
<posId> pptype:PosId </posId> [1]
<saleId> pptype:SaleId </saleId> [1]
</order:orderArticles>
Schema Component Representation
<xsd:element name="orderArticles">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="order" type=" pptype:OrderArticleList "/>
<xsd:element name="posId" type=" pptype:PosId "/>
<xsd:element name="saleId" type=" pptype:SaleId "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: orderArticlesResponse

Name orderArticlesResponse
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Output parameter element of the orderArticles operations.
XML Instance Representation
<order:orderArticlesResponse>
<orderId> pptype:OrderId </orderId> [0..1]
<saleId> pptype:SaleId </saleId> [1]
<articles> pptype:OrderStatusArticleList </articles> [1]
</order:orderArticlesResponse>
Schema Component Representation
<xsd:element name="orderArticlesResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="orderId" type=" pptype:OrderId " maxOccurs="1" minOccurs="0"/>
<xsd:element name="saleId" type=" pptype:SaleId "/>
<xsd:element name="articles" type=" pptype:OrderStatusArticleList "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: orderPickupOrder

Name orderPickupOrder
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Input parameter element of the orderPickupOrder operation.
XML Instance Representation
<order:orderPickupOrder>
<pickupOrderId> pptype:PickupOrderId </pickupOrderId> [1]
<posId> pptype:PosId </posId> [1]
<pickupId> pptype:PickupId </pickupId> [1]
</order:orderPickupOrder>
Schema Component Representation
<xsd:element name="orderPickupOrder">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="pickupOrderId" type=" pptype:PickupOrderId "/>
<xsd:element name="posId" type=" pptype:PosId "/>
<xsd:element name="pickupId" type=" pptype:PickupId "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: orderPickupOrderResponse

Name orderPickupOrderResponse
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Output parameter element of the orderPickupOrder operations.
XML Instance Representation
<order:orderPickupOrderResponse>
<orderId> pptype:OrderId </orderId> [0..1]
<pickupId> pptype:PickupId </pickupId> [1]
<articles> pptype:OrderStatusArticleList </articles> [1]
</order:orderPickupOrderResponse>
Schema Component Representation
<xsd:element name="orderPickupOrderResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="orderId" type=" pptype:OrderId " maxOccurs="1" minOccurs="0"/>
<xsd:element name="pickupId" type=" pptype:PickupId "/>
<xsd:element name="articles" type=" pptype:OrderStatusArticleList "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: trackOrder

Name trackOrder
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Input parameter element of the trackOrder operation.
XML Instance Representation
<order:trackOrder>
<trackingId> pptype:TrackingId </trackingId> [1]
</order:trackOrder>
Schema Component Representation
<xsd:element name="trackOrder">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="trackingId" type=" pptype:TrackingId "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Element: trackOrderResponse

Name trackOrderResponse
Type Locally-defined complex type
Nillable no
Abstract no
XML Instance Representation
<order:trackOrderResponse>
<articles> pptype:OrderStatusArticleList </articles> [1]
<trackingId> pptype:TrackingId </trackingId> [1]
</order:trackOrderResponse>
Schema Component Representation
<xsd:element name="trackOrderResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="articles" type=" pptype:OrderStatusArticleList "/>
<xsd:element name="trackingId" type=" pptype:TrackingId "/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
top

Legend

Complex Type:

Schema Component Type

AusAddress

Schema Component Name
Super-types: Address < AusAddress (by extension)
Sub-types:
  • QLDAddress (by restriction)
If this schema component is a type definition, its type hierarchy is shown in a gray-bordered box.
Name AusAddress
Abstract no
The table above displays the properties of this schema component.
XML Instance Representation
<... country="Australia" >
<unitNo> string </unitNo> [0..1]
<houseNo> string </houseNo> [1]
<street> string </street> [1]
Start Choice [1]
<city> string </city> [1]
<town> string </town> [1]
End Choice
<state> AusStates </state> [1]
<postcode> string <<pattern = [1-9][0-9]{3}>> </postcode> [1] ?
</...>

The XML Instance Representation table above shows the schema component's content as an XML instance.

  • The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
  • Model group information are shown in gray, e.g. Start Choice ... End Choice.
  • For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
  • If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
  • Otherwise, the type of the element/attribute is displayed.
    • If the element/attribute's type is in the schema, a link is provided to it.
    • For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
  • If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Schema Component Representation
<complexType name="AusAddress">
<complexContent>
<extension base=" Address ">
<sequence>
<element name="state" type=" AusStates "/>
<element name="postcode">
<simpleType>
<restriction base=" string ">
<pattern value="[1-9][0-9]{3}"/>
</restriction>
</simpleType>
</element>
</sequence>
<attribute name="country" type=" string " fixed="Australia"/>
</extension>
</complexContent>
</complexType>
The Schema Component Representation table above displays the underlying XML representation of the schema component. (Annotations are not shown.)
top

Glossary

Abstract (Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.

All Model Group Child elements can be provided in any order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-all.

Choice Model Group Only one from the list of child elements and model groups can be provided in instances. See: http://www.w3.org/TR/xmlschema-1/#element-choice.

Collapse Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.

Disallowed Substitutions (Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.

Key Constraint Like Uniqueness Constraint, but additionally requires that the specified value(s) must be provided. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

Key Reference Constraint Ensures that the specified value(s) must match value(s) from a Key Constraint or Uniqueness Constraint. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

Model Group Groups together element content, specifying the order in which the element content can occur and the number of times the group of element content may be repeated. See: http://www.w3.org/TR/xmlschema-1/#Model_Groups.

Nillable (Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.

Notation A notation is used to identify the format of a piece of data. Values of elements and attributes that are of type, NOTATION, must come from the names of declared notations. See: http://www.w3.org/TR/xmlschema-1/#cNotation_Declarations.

Preserve Whitespace Policy Preserve whitespaces exactly as they appear in instances.

Prohibited Derivations (Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.

Prohibited Substitutions (Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.

Replace Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32).

Sequence Model Group Child elements and model groups must be provided in the specified order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-sequence.

Substitution Group Elements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.

Substitution Group Exclusions (Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.

Target Namespace The target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.

Uniqueness Constraint Ensures uniqueness of an element/attribute value, or a combination of values, within a specified scope. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

top

Generated by xs3p. Last modified: