Stylus Studio XML Editor

Table of contents

Appendices

1.1 Notational Conventions

Notational Conventions

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 RFC2119 [RFC2119].

This specification uses a number of namespace prefixes throughout; they are listed in [tabprefns]. Note that the choice of any namespace prefix is arbitrary and not semantically significant (see [XMLInfoSet]).

1Mapping of prefixes used in this document to their associated namespace nametabprefns Prefixes and Namespaces used in this specification Prefix Namespace Notes
11wsdl 11 http://www.w3.org/2004/08/wsdl 11A normative XML Schema [XMLSchemaP1], [XMLSchemaP2] document for the http://www.w3.org/2004/08/wsdl namespace can be found at http://www.w3.org/2004/08/wsdl.
11wsoap 11 http://www.w3.org/2004/08/wsdl/soap12 11A normative XML Schema [XMLSchemaP1], [XMLSchemaP2] document for the http://www.w3.org/2004/08/wsdl/soap12 namespace can be found at http://www.w3.org/2004/08/wsdl/soap12.
11whttp 11 http://www.w3.org/2004/08/wsdl/http 11A normative XML Schema [XMLSchemaP1], [XMLSchemaP2] document for the http://www.w3.org/2004/08/wsdl/http namespace can be found at http://www.w3.org/2004/08/wsdl/http.
11wsdls 11http://www.w3.org/2004/08/wsdl-simple-types 11This prefix and namespace name are used to refer to the simple types defined by [WSDL-PART1] for use in the component model, see [Definition of the Simple Types Used in the Component Model].
11xs 11 http://www.w3.org/2001/XMLSchema 11Defined in the W3C XML Schema specification [XMLSchemaP1], [XMLSchemaP2].

Namespace names of the general form http://example.org/... and http://example.com/... represent application or context-dependent URIs [RFC2396].

All parts of this specification are normative, with the EXCEPTION of pseudo-schemas, examples, and sections explicitly marked as "Non-Normative". Pseudo-schemas are provided for each component, before the description of this component. They provide visual help for the XML 1.0-based [XML10] serialization, but do not limit the ability of the bindings to be expressed with other versions of XML such as XML 1.1 [XML11] or futures versions of XML Schema [XMLSchemaP1], [XMLSchemaP2].

Note that the WSDL binding specifications in this document are defined in terms of a component model defined by this specification. As such, it is explicitly NOT a conformance requirement to be able to process documents encoded in a particular version of XML.