The presentation of this document has been augmented to identify changes from a previous version. Three kinds of changes are highlighted: new, added text, changed text, and deleted text. NOTE: the status section of the document has not been augmented to identify changes from a previous version.
This document is also available in these non-normative formats: PDF, PostScript, XML, and plain text.
Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
WSDL 1.1 Element Identifiers defines a syntax to identify individual elements in a WSDL 1 WSDL 1.1 Element Identifiers specification. It was produced by the members of the Web Services Policy Working Group, which is part of the W3C Web Services Activity.
A list of changes in this version of the document and a diff-marked version against the previous version of this document are available. There are no major editorial changes in this version of the document.
As of the publication of this document as a Working Group Note, the Web Services Policy Working Group has completed work on this document. Discussion of this document took place on the public public-ws-policy@w3.org mailing list (public archive) and within Bugzilla. Further comments on this specification should be made following the Description for Issues of the. Fragment Identifiers
3. IRI-References for WSDL 1.1 Elements
3.1 WSDL 1.1 IRIs
3.2 IRI Identification Of SOAP Binding elements
3.3 Canonical Form for WSDL 1.1 element identifiers
3.4 Example
4. References
4.1 Normative References
A. Change Log (Non-Normative)
This document defines an element identifier syntax for WSDL 1.1 elements. a fragment identifier syntax for identifying elements of a WSDL 1.1 document. This fragment identifier syntax is compliant with the [XPointer Framework]. This document is primarily based upon [WSDL 2.0 Core]. There is a substantial difference between the WSDL 1.1 and WSDL 2.0 fragment identifiers.WSDL 2.0 defines fragment identifiers with respect to the WSDL 2.0 component model, whereas WSDL 1.1 defines XML element and attribute syntax only. Because there is no WSDL 1.1 component model, the WSDL 1.1 fragment identifiers identify WSDL 1.1 elements. Note: the fragment identifers identify the WSDL 1.1 elements prior to any processing of the WSDL document, such as validation, inclusion, imports, schema type validation, etc. Note further: WSDL 1.1 fragment identifiers require a targetNamespace so WSDL 1.1 documents without a targetNamespace will not have fragment identifiers.
A WSDL 1.1 fragment identifier is an XPointer [XPointer Framework],
augmented with WSDL 1.1 pointer parts as defined below. Note that many
of these parts require the pre-appearance of one or more
xmlns pointer
parts (see 3.4 Namespace Binding Context in [XPointer Framework]).
The pointer parts have a scheme name that corresponds to one
of the standard WSDL 1.1 element names, and scheme data that is a path composed
of names that identify the elements.
The scheme names all begin with the prefix "wsdl11." to avoid
name conflicts with other schemes.
The names in the path are of type either QName, NCName,
IRI, URI, or Pointer Part depending on the context.
The scheme data for WSDL 1.1 extension elements is defined by the
corresponding extension specification.
For QNames, any prefix MUST be defined by a preceding xmlns pointer part. If a QName does not have a prefix then its namespace name is the target namespace of the WSDL 1.1 document.
The fragment identifier is typically constructed from the
name
property of the element and the
name properties of its
ancestors as a path according to
Table 2-1.
The first column of this table gives the name of the WSDL 1.1
element. Columns labeled 1 through 3 specify the identifiers that
uniquely identify the element within its context. Identifiers
are typically formed from the
name property, although in
several cases references to other elements are used. These
identifiers are then used to construct the pointer part in
the last column.
The fragment identifier in a WSDL 1.1 element IRI-reference
MUST resolve to some element as defined by the construction rules
in Table 2-1.
This section provides a syntax for IRI-references for all elements found in a [WSDL 1.1] document. The IRI-references are easy to understand and compare, while imposing no burden on the WSDL 1.1 author.
There are two main cases for WSDL 1.1 IRIs:
the IRI of a WSDL 1.1 document
the IRI of a WSDL 1.1 namespace
The IRI of a WSDL 1.1 document can be dereferenced to give a resource representation that contributes elements to a single WSDL 1.1 namespace. If the media type is set to the WSDL 1.1 media type i.e. application/xml, then the fragment identifiers can be used to identify the main elements that are defined in the document.
In keeping with WSDL 1.1, which has a recommendation that that the namespace URI be dereferencible to a WSDL 1.1 document, this section specifies the use of the namespace IRI with the WSDL 1.1 fragment identifiers to form an IRI-reference.
The IRI in an IRI-reference for a WSDL 1.1 element is the
namespace name of the
name
property of either the element itself, in the case of
portType
,
Binding
, and
Service
elements, or the
name
property of the ancestor top-level element. The IRI provided
by the namespace name of the
name
property is combined with a zero or more
xmlns
pointer parts (see
3.4 Namespace Binding Context
in
[XPointer Framework]
) followed by a single WSDL 1.1 pointer part, following the same rules as defined for WSDL 1.1 fragment ids
2. Fragment Identifiers
.
SOAP Binding elements (binding, operation, body, header, fault, headerfault, and address) can be identified using the
wsdl11.extension
XPointer Framework scheme according to the following rules:
wsdl11.extension(,
w11soap.binding(
parent
)), where:
parent
is the pointer part of the
SOAP Binding's parent element
wsdl11.extension(,
w11soap.operation(
parent
))
parent
is the pointer part of the
SOAP Operation's parent element
wsdl11.extension(,
w11soap.body(
parent
))
parent
is the pointer part of the
SOAP Body's parent element
wsdl11.extension(,
w11soap.header(
parent
))
parent
is the pointer part of the
SOAP Header's parent element
wsdl11.extension(,
w11soap.headerfault(
parent
))
parent
is the pointer part of the
SOAP HeaderFault's parent element
wsdl11.extension(,
w11soap.fault(
parent
))
parent
is the pointer part of the
SOAP Fault's parent element
wsdl11.extension(,
w11soap.address(
parent
))
parent
is the pointer part of the
SOAP Address's parent element
The IRI-references described above MAY be used as WSDL 1.1 element identifiers. For ease of comparison, the fragment identifier of WSDL 1.1 element identifiers SHOULD conform to the following canonicalization rules:
The fragment identifier consists of a sequence
zero or more
xmlns()
pointer parts followed by exactly one
wsd11.*()
pointer part.
Each
xmlns()
pointer part that appears in the fragment
identifier defines a namespace that is
referenced by the
wsd11.*()
pointer part.
Each
xmlns()
pointer part defines a unique namespace.
The
xmlns()
pointer parts define namespaces in the same
order as they are referenced in the
wsd11.*()
pointer part.
The namespace prefixes defined by the
xmlns()
pointer parts are named
ns1
,
ns2
, etc., in the order of their appearance.
The fragment identifier contains no optional whitespace.
Consider WSDL 1.1 document located at. Each WSDL 1.1 Element Identifier is shown in comments above the WSDL 1.1 element
Example 3-1. IRI-References - Example WSDL 1.1 Document
<?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions <!-- --> <wsdl:types> <xs:schema xmlns: :schema> </wsdl:types> <wsdl:message <!-- Starting from here, will be shortened to http://... --> <!-- --> 11soap.binding( wsdl11.binding(TicketAgentSoap)) --> <wsdl:operation <!-- --> <wsdl:input> <!-- --> <soap:body <!--(, w11soap.body(wsdl11.bindingOperation.input (TicketAgentSoap/listFlights)) --> </wsdl:input> <wsdl:output> <!-- --> <soap:body <!--(, w11soap.body(wsdl11.bindingOperation.output (TicketAgentSoap/listFlights)) --> </wsdl:output> </wsdl:operation> </wsdl:binding> </wsdl:definitions>