Index: wsdl20-adjuncts.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v retrieving revision 1.150 diff -u -r1.150 wsdl20-adjuncts.xml --- wsdl20-adjuncts.xml 22 Nov 2005 11:37:14 -0000 1.150 +++ wsdl20-adjuncts.xml 10 Jan 2006 03:57:44 -0000 @@ -347,14 +347,14 @@ the fault message to its designated recipient.

WSDL patterns specify propagation of faults, not their generation. -Nodes which generate a fault MUST attempt to propagate the faults in +Nodes which generate a fault MUST attempt to propagate the faults in accordance with the governing ruleset, but it is understood that any -delivery of a network message is best effort, not guaranteed. The +delivery of a network message is best effort, not guaranteed. The rulesets establish the direction of the fault message and the fault recipient, they do not provide reliability or other delivery guarantees. -When a fault is generated, the generating node MUST attempt to +When a fault is generated, the generating node MUST attempt to propagate the fault, and MUST do so in the direction and to the -recipient specified by the ruleset. However, extensions or binding extensions +recipient specified by the ruleset. However, extensions or binding extensions MAY modify these rulesets. For example, WS-Addressing defines a "FaultTo" address for messages, which is used in lieu of the recipient nominated by the ruleset.

@@ -373,10 +373,10 @@ Any message after the first in the pattern MAY be replaced with a fault message, which MUST have identical direction. - The fault message MUST be delivered to the same target node as the + The fault message MUST be delivered to the same target node as the message it replaces, unless otherwise specified by an extension or binding extension. If there is no path to this node, the fault MUST - be discarded. + be discarded.

This fault propagation rule is identified by the following URI: &wsdl-fault-replace;

@@ -391,11 +391,11 @@ Any message, including the first in the pattern, MAY trigger a fault message, which MUST have opposite direction. - The fault message MUST be delivered to the originator of the + The fault message MUST be delivered to the originator of the triggering message, unless otherwise specified by an extension of binding extension. Any node MAY propagate a fault message, and MUST not do so more than once for each triggering message. If there is no - path to the originator, the fault MUST be discarded. + path to the originator, the fault MUST be discarded.

This fault propagation rule is identified by the following URI: &wsdl-fault-trigger;

@@ -844,9 +844,9 @@ in and .

-

The RPC style MUST NOT be used for Interface Operation +

The RPC style MUST NOT be used for Interface Operation components whose message exchange pattern - property has a value other than &wsdl-mep-in-only; or &wsdl-mep-in-out;.

+ property has a value other than &wsdl-mep-in-only; or &wsdl-mep-in-out;.

The RPC style places restrictions for Remote Procedure Call-types of interactions. When this value is used, the @@ -865,40 +865,40 @@ -

The value of the message content model property for the +

The value of the message content model property for the Interface Message Reference components of the interface message references property MUST be - #element.

+ #element.

-

The content model of input and output +

The content model of input and output element declaration elements MUST be defined using a complex type that contains a - sequence from XML Schema.

 + sequence from XML Schema.

-

The input sequence MUST only contain elements and element wildcards. - It MUST NOT contain other structures such as xs:choice. The input sequence - MUST NOT contain more than one element wildcard. The element wildcard, if - present, MUST appear after any elements.

 +

The input sequence MUST only contain elements and element wildcards. + It MUST NOT contain other structures such as xs:choice. The input sequence + MUST NOT contain more than one element wildcard. The element wildcard, if + present, MUST appear after any elements.

 -

The output sequence MUST only contain elements. It MUST NOT contain +

The output sequence MUST only contain elements. It MUST NOT contain other structures such as xs:choice.

 -

The sequence MUST contain only local element - children. Note that these child elements MAY contain the +

The sequence MUST contain only local element + children. Note that these child elements MAY contain the following attributes: nillable, minOccurs and maxOccurs.

 -

The local name of input element's QName MUST be +

The local name of input element's QName MUST be the same as the Interface Operation component's - name.

 + name.

-

Input and output elements MUST both be in the - same namespace.

 +

Input and output elements MUST both be in the + same namespace.

 -

The complex type that defines the body of an +

The complex type that defines the body of an input or an output element MUST NOT contain any local - attributes. Extension attributes are allowed for purposes + attributes. Extension attributes are allowed for purposes of managing the message infrastructure (e.g. adding identifiers to facilitate digitally signing the contents of the message). They must not be considered as part of the application data @@ -907,13 +907,13 @@ ref="InterfaceOperation_RPC_Signature_Definition"/>).

-

If elements with the same qualified name appear +

If elements with the same qualified name appear as children of both the input and output elements, then - they MUST both be declared using the same named type.

 + they MUST both be declared using the same named type.

-

The input or output sequence MUST NOT contain +

The input or output sequence MUST NOT contain multiple children elements declared with the same - name.

 + name.

@@ -929,34 +929,34 @@

rpc signature REQUIRED. A list of pairs (q, t) whose first component is of type xs:QName and whose second component is of type xs:token. - Values for the second component MUST be chosen among the following four: - "#in", "#out", "#inout" "#return".

 + Values for the second component MUST be chosen among the following four: + "#in", "#out", "#inout" "#return".

The value of the rpc signature property MUST satisfy the following conditions:

-

The value of the first component of each pair (q, t) MUST - be unique within the list.

 -

For each child element of the input and output messages of the operation, +

The value of the first component of each pair (q, t) MUST + be unique within the list.

 +

For each child element of the input and output messages of the operation, a pair (q, t) whose first component q is equal to the qualified name of that element MUST be present in the list, with the caveat that elements that appear with cardinality greater than one MUST be treated as - a single element.

 -

For each pair (q, #in), there MUST be a child element of the + a single element.

 +

For each pair (q, #in), there MUST be a child element of the input element with a name of q and there MUST NOT be a child element - of the output element with the same name.

 -

For each pair (q, #out), there MUST be a child element of the + of the output element with the same name.

 +

For each pair (q, #out), there MUST be a child element of the output element with a name of q and there MUST NOT be a child element - of the input element with the same name.

 -

For each pair (q, #inout), there MUST be a child element of the + of the input element with the same name.

 +

For each pair (q, #inout), there MUST be a child element of the input element with a name of q and there MUST be a child element of the output element with the same name. Furthermore, those two elements MUST - have the same type.

 -

For each pair (q, #return), there MUST be a child element of the + have the same type.

 +

For each pair (q, #return), there MUST be a child element of the output element with a name of q and there MUST NOT be a child element - of the input element with the same name.

 + of the input element with the same name.

The function signature defined by a wrpc:signature extension is @@ -1036,10 +1036,10 @@ See for an excerpt from the normative schema definition of this type.

-

Additionally, each even-numbered item (0, 2, 4, ...) in the list +

Additionally, each even-numbered item (0, 2, 4, ...) in the list MUST be of type xs:QName and each odd-numbered item (1, 3, 5, ...) in the list MUST be of the subtype of xs:token described in the - previous paragraph. + previous paragraph.

@@ -1110,12 +1110,12 @@ &IRI-STYLE;.

-

When using this style, the value of the When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be - #element.

+ #element.

Use of this value indicates that XML Schema

- The sequence MUST only contain elements. It MUST NOT + The sequence MUST only contain elements. It MUST NOT contain other structures such as xs:choice.

- The sequence MUST contain only local element + The sequence MUST contain only local element children. These child elements MAY contain the nillable attribute, and the attributes minOccurs and maxOccurs MUST have - a value 0 or 1. + a value 0 or 1.

- The localPart of the element's QName MUST be the same + The localPart of the element's QName MUST be the same as the Interface Operation component's - name. + name.

- The complex type that defines the body of the + The complex type that defines the body of the element or its children elements MUST NOT contain any - attributes. + attributes.

- The sequence MUST NOT contain multiple children - elements declared with the same local name. + The sequence MUST NOT contain multiple children + elements declared with the same local name.

- If the children elements of the sequence are + If the children elements of the sequence are defined using an XML Schema type, they MUST derive from xs:simpleType, and MUST NOT be of the type or derive from xs:QName, xs:NOTATION, xs:hexBinary or - xs:base64Binary. + xs:base64Binary.

@@ -1189,12 +1189,12 @@ &MULTIPART-STYLE;.

-

When using this style, the value of the When using this style, the value of the message content model property of the Interface Message Reference component corresponding to the initial message of the message exchange pattern MUST be - #element.

+ #element.

Use of this value indicates that XML Schema

- The sequence MUST only contain elements. It MUST NOT + The sequence MUST only contain elements. It MUST NOT contain other structures such as xs:choice.

- The sequence MUST contain only local element + The sequence MUST contain only local element children. These child elements MAY contain the nillable attribute, and the attributes minOccurs and maxOccurs MUST have - a value 1. + a value 1.

- The localPart of the element's QName MUST be the same + The localPart of the element's QName MUST be the same as the Interface Operation component's - name. + name.

- The complex type that defines the body of the + The complex type that defines the body of the element or its children elements MUST NOT contain any - attributes. + attributes.

- The sequence MUST NOT contain multiple children - element declared with the same local name. + The sequence MUST NOT contain multiple children + element declared with the same local name.

@@ -1440,11 +1440,11 @@ -

Payload Construction. When formulating +

Payload Construction. When formulating the SOAP envelope to be transmitted, the contents of the payload (i.e., the contents of the SOAP Body &EII; of the SOAP envelope) MUST be what is defined by the - corresponding Interface Message Reference component. This is subject + corresponding Interface Message Reference component. This is subject to optimization by a feature that is in use which may affect serialization, such as MTOM . The following binding rules MUST be adhered to:

@@ -1455,19 +1455,19 @@ property of the Interface Message Reference component is #any then the payload MAY be any one XML element.

 -

If the value is #none then the - payload MUST be empty.

 +

If the value is #none then the + payload MUST be empty.

If the value is #element then the payload will be the &EII; identified by the element declaration property of the Interface Message Reference component.

 -

If the Interface Message Reference component is declared +

If the Interface Message Reference component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined to indicate how to map those - components into the SOAP envelope.

+ components into the SOAP envelope.

This SOAP binding extension only allows one single element in @@ -1517,8 +1517,8 @@ Description -

Every SOAP binding MUST indicate what version of SOAP is in use - for the operations of the interface that this binding applies to.

+

Every SOAP binding MUST indicate what version of SOAP is in use + for the operations of the interface that this binding applies to.

By default, SOAP 1.2 is used.

 @@ -1599,8 +1599,8 @@ Description -

Every SOAP binding MUST indicate what underlying protocol is in - use.

+

Every SOAP binding MUST indicate what underlying protocol is in + use.

@@ -1680,9 +1680,9 @@ Description -

For every Interface Fault component contained in an - Interface component, a mapping to a SOAP Fault must be - described. This binding extension specification allows the user to +

For every Interface Fault component contained in an + Interface component, a mapping to a SOAP Fault MUST be + described. This binding extension specification allows the user to indicate the SOAP fault code and subcodes that are transmitted for a given Interface Fault component.

 @@ -1818,23 +1818,23 @@

soap mep - default OPTIONAL. A xs:anyURI, + default OPTIONAL. A xs:anyURI, which is an absolute IRI as defined by , to the Binding - component. The value of this property identifies the + component. The value of this property identifies the default SOAP Message Exchange Pattern (MEP) for all the Interface Operation components of any Interface component that uses this Binding component.

soap mep OPTIONAL. - A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component. The + A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component. The value of this property identifies the SOAP Message Exchange Pattern (MEP) for this specific operation.

soap action OPTIONAL. - A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component. The + A xs:anyURI, which is an absolute IRI as defined by , to the Binding Operation component. The value of this property identifies the value of the SOAP Action Feature for the initial message of the message exchange pattern of the Interface Operation bound, as specified in the binding rules of bindings to specific @@ -2003,8 +2003,8 @@

ref REQUIRED. - A xs:anyURI, which is an absolute IRI as defined by . The value of this property identifies the + A xs:anyURI, which is an absolute IRI as defined by . The value of this property identifies the specific SOAP module that is in use.

required REQUIRED. @@ -2268,20 +2268,20 @@

mustUnderstand REQUIRED. A - xs:boolean. When its value is + xs:boolean. When its value is true, the SOAP header block MUST be decorated with a SOAP mustUnderstand &AII; with a value of true; if so, it is an error for the XML element declaration referenced by the element declaration property not to allow this SOAP mustUnderstand - &AII;. Otherwise, no additional constraint is placed on + &AII;. Otherwise, no additional constraint is placed on the presence and value of a SOAP mustUnderstand &AII;.

required REQUIRED. A xs:boolean indicating if the SOAP - header block is required. If the value is true, then the SOAP header block MUST be included in the message. If it is false, then the SOAP header block MAY be included.

 + header block is required. If the value is true, then the SOAP header block MUST be included in the message. If it is false, then the SOAP header block MAY be included.

parent REQUIRED. The Binding Fault @@ -2435,12 +2435,12 @@ element declaration The element declaration from the element declarations resolved - to by the value of the element &AII;. It is + to by the value of the element &AII;. It is an error for the element &AII; to have a value and that value does not resolve to a global element declaration from the element declarations property of the - Description component. + Description component. mustUnderstand @@ -2575,7 +2575,7 @@ of the message exchange pattern.

SOAP MEP Selection. - + For a given Interface Operation component, if there is a Binding Operation component whose interface operation @@ -2595,7 +2595,7 @@ Otherwise (i.e. if the Interface Operation component has any other value for the message exchange pattern property), it is - an ERROR.

+ an ERROR.

One-way MEP defaulting @@ -2609,7 +2609,7 @@ -

HTTP Method Selection. This default +

HTTP Method Selection. This default binding rule is applicable when the value of the soap underlying protocol property of the Binding component is &soap12-http-uri;. If @@ -2619,19 +2619,19 @@ POST. If the SOAP MEP selected has the value &soap12-soap-response-mep-uri; then the HTTP method used is - GET.

 + GET.

HTTP IRI Generation. This default binding rule is applicable when the value of the soap underlying protocol property of the Binding component is - &soap12-http-uri;. If + &soap12-http-uri;. If the SOAP MEP selected is &soap12-soap-response-mep-uri; then the value of the SOAP &soap12-mep;ImmediateDestination property MUST be generated using the HTTP binding extension's rules for generating a - IRI for HTTP GET (see ). The + IRI for HTTP GET (see ). The input serialization format of application/x-www-form-urlencoded is the only supported serialization format for HTTP GET in the SOAP Response @@ -2898,8 +2898,8 @@ HTTP Method Selection -

When formulating the HTTP message to be transmitted, the - HTTP request method used MUST be the following:

+

When formulating the HTTP message to be transmitted, the + HTTP request method used MUST be the following:

@@ -2939,11 +2939,11 @@ Payload Construction And Serialization Format -

When formulating the HTTP message to be transmitted, the +

When formulating the HTTP message to be transmitted, the contents of the payload (i.e. the contents of the HTTP message body) MUST be what is defined by the corresponding Interface Message Reference or Interface Fault components, - serialized as specified by the serialization format used.

+ serialized as specified by the serialization format used.

The serialization format is a media type token (type/subtype). It identifies rules to @@ -2971,8 +2971,8 @@ #any or #element, the serialization of the instance data is specified as defined in section .

 -

If the value is #none then the - payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.

+

If the value is #none then the + payload MUST be empty and the value of the corresponding serialization property (http input serialization or http output serialization) is ignored.

If the value is #other then the @@ -2985,11 +2985,11 @@ -

If the Interface Message Reference component or the Interface Fault +

If the Interface Message Reference component or the Interface Fault component is declared using a non-XML type system (as considered in the Types section of ) then additional binding rules MUST be defined to indicate how - to map those components into the HTTP envelope.

+ to map those components into the HTTP envelope.

Serialization rules for XML messages @@ -3136,12 +3136,12 @@

The HTTP header field name used is the value of the name property of the - HTTP Header component. If an HTTP + HTTP Header component. If an HTTP header field corresponding to the value of the name property is set by a mechanism other than the HTTP binding, such as the HTTP stack or another feature, then an error MUST be - raised. + raised.

@@ -3169,9 +3169,9 @@ Description -

Every Binding component MUST indicate what version of HTTP +

Every Binding component MUST indicate what version of HTTP is in use for the operations of the interface that this - binding applies to.

+ binding applies to.

By default, HTTP/1.1 is used.

@@ -3268,9 +3268,9 @@

Each of the supported message exchange patterns involves one to two messages or faults being exchanged. The first is transmitted using an HTTP request, and the second is - transmitted using the corresponding HTTP response. In cases + transmitted using the corresponding HTTP response. In cases where only one message is being sent, the message body of - the HTTP response MUST be empty.

+ the HTTP response MUST be empty.

For every Binding Operation component corresponding to such Interface Operation components, this binding extension @@ -3291,9 +3291,9 @@ IRI is combined with the base IRI specified in the address property of the Endpoint component to form the full IRI for the HTTP request to invoke the - operation. It MUST contain an absolute or a relative + operation. It MUST contain an absolute or a relative IRI, i.e. it MUST NOT include a fragment identifier in - the IRI. Input serializations may define additional + the IRI. Input serializations may define additional processing rules to be applied to the value of http location before combining it with the address property of the endpoint element to @@ -3367,14 +3367,14 @@ Specification of serialization rules allowed -

The value of the http input +

The value of the http input serialization, http output serialization and http fault serialization properties is similar to the value allowed for the Accept HTTP header defined by the HTTP 1.1 specification, Section 14.1 (see ) and MUST follow the production rules defined in that section - except for the following: + except for the following:

@@ -3388,7 +3388,6 @@

This change is made to disallow non-US-ASCII OCTETs.

 -

These properties allow to indicate the range of media types and/or associated parameters with which an instance MAY be serialized. The value of the serialization format used for a @@ -3667,11 +3666,11 @@

Similarly, http headers OPTIONAL, to the Binding Fault component.

 -

It is an ERROR for a Binding Message +

It is an ERROR for a Binding Message Reference or a Binding Fault component's http headers property to contain multiple HTTP Header components - with the same name property.

+ with the same name property.

@@ -3701,12 +3700,12 @@ A xs:QName, being a reference to a Type Definition component in the type definitions property of the Description component - constraining the value of the HTTP header field. This type MUST be a simple type.

+ constraining the value of the HTTP header field. This type MUST be a simple type.

required REQUIRED. A xs:boolean indicating if the HTTP - header field is required. If the value is true, then the HTTP header field MUST be included in the message. If it is false, then the HTTP header field MAY be included.

 + header field is required. If the value is true, then the HTTP header field MUST be included in the message. If it is false, then the HTTP header field MAY be included.

parent REQUIRED. The Binding Fault @@ -4195,10 +4194,10 @@ request, as specified in section .

-

The resulting IRI MUST be mapped to an URI for use in +

The resulting IRI MUST be mapped to an URI for use in the HTTP Request as per section 3.1 "Mapping of IRIs to URIs" of the IRI specification . Additional rules for the serialization of + ref="RFC3987"/>. Additional rules for the serialization of the HTTP request IRI MAY be defined by a serialization format.

@@ -4228,13 +4227,13 @@ a single, literal curly brace in the request IRI.

 -

An element MUST NOT be cited more than once within - the http location property.

-

Strings enclosed within single curly braces MUST be +

An element MUST NOT be cited more than once within + the http location property.

+

Strings enclosed within single curly braces MUST be element names from the instance data of the input message, possibly followed by a slash; any other strings enclosed - within single curly braces are a fatal error. + within single curly braces are a fatal error.

@@ -4319,10 +4318,10 @@ the instance data.

-

It is an error for the It is an error for the instance data to contain elements with an xs:nil attribute whose value is - true.

+ true.

Each parameter pair is separated by the value of the

- The Content-Type HTTP header MUST have the value + The Content-Type HTTP header MUST have the value application/xml, or a media type compatible with - application/xml as specified in section . Other HTTP headers, such as + application/xml as specified in section . Other HTTP headers, such as Content-Encoding or Transfer-Encoding, MAY be used.

@@ -4583,14 +4582,14 @@

- Specifically, for the HTTP binding defined in this section + Specifically, for the HTTP binding defined in this section (), multipart/form-data MAY be used as a serialization format for an input message (HTTP Request), but MUST NOT be used as a serialization format - for an output or fault message (HTTP Response). + for an output or fault message (HTTP Response). This format serializes the instance data in the HTTP message body, making it only suitable for HTTP requests using methods allowing message bodies.

@@ -4602,14 +4601,14 @@

- The Content-Disposition header MUST have the + The Content-Disposition header MUST have the value form-data, and its name - parameter is the local name of the element. + parameter is the local name of the element.

- The Content-Type header MUST have the value: + The Content-Type header MUST have the value:

@@ -4646,10 +4645,10 @@

-

It is an error for the It is an error for the instance data to contain elements with an xs:nil attribute whose value is - true.

+ true.

Example of multipart/form-data

@@ -5000,9 +4999,9 @@

http authentication realm OPTIONAL. A xs:string to the Endpoint component. It corresponds to the realm authentication - parameter defined in . If the + parameter defined in . If the http authentication scheme property is present, then - this property MUST be present. + this property MUST be present.