Stylus Studio XML Editor

Table of contents

Appendices

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

This specification uses properties from the XML Information Set [XMLInfoSet]. Such properties are denoted by square brackets, e.g. [namespace name].

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

This specification uses curly brackets (e.g., {property}) to indicate a property in the WSDL component model, as defined in [Component Model].

1Mapping of prefixes used in this document to their associated namespace nametabnsprefixes Prefixes and Namespaces used in this specification Prefix Namespace Notes
11wsdl 11http://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. WSDL documents that do NOT conform to this schema are not valid WSDL documents. WSDL documents that DO conform to this schema and also conform to the other constraints defined in this specification are valid WSDL documents.
11wsdli 11http://www.w3.org/2004/08/wsdl-instance 11A normative XML Schema [XMLSchemaP1], [XMLSchemaP2] document for the http://www.w3.org/2004/08/wsdl-instance namespace can be found at http://www.w3.org/2004/08/wsdl-instance.
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 this specification for use in the component model, see [Definition of the Simple Types Used in the Component Model].
11wrpc 11http://www.w3.org/2004/08/wsdl/rpc 11A normative XML Schema [XMLSchemaP1], [XMLSchemaP2] document for the http://www.w3.org/2004/08/wsdl/rpc namespace can be found at http://www.w3.org/2004/08/wsdl/rpc. WSDL documents that do NOT conform to this schema are not valid WSDL documents. WSDL documents that DO conform to this schema and also conform to the other constraints defined in this specification are valid WSDL documents.
11wsoap 11http://www.w3.org/2004/08/wsdl/soap12 21Defined by WSDL 2.0: Bindings [WSDL-PART3].
11whttp 11http://www.w3.org/2004/08/wsdl/http
11xs 11http://www.w3.org/2001/XMLSchema 21Defined in the W3C XML Schema specification [XMLSchemaP1], [XMLSchemaP2].
11xsi 11http://www.w3.org/2001/XMLSchema-instance

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 notes, pseudo-schemas, examples, and sections explicitly marked as "Non-Normative".

Pseudo-schemas are provided for each component, before the description of the component. They use BNF-style conventions for attributes and elements: `?' denotes optionality (i.e. zero or one occurrences), `*' denotes zero or more occurrences, `+' one or more occurrences, `[' and `]' are used to form groups, `|' represents choice. Attributes are conventionally assigned a value which corresponds to their type, as defined in the normative schema.

<!-- sample pseudo-schema -->
<defined_element
      required_attribute_of_type_string="xs:string"
      optional_attribute_of_type_int="xs:int"? >
  <required_element />
  <optional_element />?
  <one_or_more_of_these_elements />+
  [ <choice_1 /> | <choice_2 /> ]*
</defined_element>