WSDL Part4 -Notational Conventions

Notational Conventions

1. The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2].

2. The following namespace prefixes are used throughout this document:

prefix namespace URI definition
wsdl WSDL namespace for WSDL framework.
soap WSDL namespace for WSDL SOAP binding.
http WSDL namespace for WSDL HTTP GET & POST binding.
mime WSDL namespace for WSDL MIME binding.
soapenc Encoding namespace as defined by SOAP 1.1 [8].
soapenv Envelope namespace as defined by SOAP 1.1 [8].
xsi Instance namespace as defined by XSD [10].
xsd Schema namespace as defined by XSD [10].
tns (various) The “this namespace” (tns) prefix is used as a convention to refer to the current document.
(other) (various) All other namespace prefixes are samples only. In particular, URIs starting with “” represent some application-dependent or context-dependent URI [4].

3. This specification uses an informal syntax to describe the XML grammar of a WSDL document:

  • The syntax appears as an XML instance, but the values indicate the data types instead of values.
  • Characters are appended to elements and attributes as follows: "?" (0 or 1), "*" (0 or more), "+" (1 or more).
  • Elements names ending in "…" (such as or ) indicate that elements/attributes irrelevant to the context are being omitted.
  • Grammar in bold has not been introduced earlier in the document, or is of particular interest in an example.
  • <-- extensibility element --> is a placeholder for elements from some "other" namespace (like ##other in XSD).
  • The XML namespace prefixes (defined above) are used to indicate the namespace of the element being defined.
  • Examples starting with

XSD schemas are provided as a formal definition of WSDL grammar (see section A4).

Post a Comment