- From: Hugo Haas <hugo@dev.w3.org>
- Date: Mon, 26 Jul 2004 10:33:51 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv14737
Modified Files:
wsdl20-bindings.xml
Log Message:
Swapped 3.8 and 3.9
Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.83
retrieving revision 1.84
diff -C2 -d -r1.83 -r1.84
*** wsdl20-bindings.xml 26 Jul 2004 10:30:47 -0000 1.83
--- wsdl20-bindings.xml 26 Jul 2004 10:33:49 -0000 1.84
***************
*** 1728,1875 ****
</div2>
- <div2 id="_operation_styles">
- <head>Operation Styles</head>
- <p>
- This section defines operation styles in use in parallel to the
- HTTP 1.1 binding.
- </p>
- <div3 id="_operation_uri_style">
- <head>URI Style</head>
- <p>
- The URI style is selected by assigning the Interface
- Operation component's &interface_operation-style-p; property the value
- <emph>&URI-STYLE;</emph>.
- </p>
- <p>
- The URI style may only be used for Interface Operation
- components whose &interface_operation-message_exchange_pattern-p; property has the
- value '&wsdl-mep-in-only;', '&wsdl-mep-robust-in-only;' or
- '&wsdl-mep-in-out;'.
- </p>
- <p>
- Use of this value indicates that XML Schema <bibref ref="XMLSchemaP1"/> was used to define the schemas of the
- &message_reference-element-p; properties of all Message Reference components
- of the Interface Operation component with &message_reference-direction-p;
- property <emph>in</emph>. Those schemas MUST adhere to the
- rules below.
- </p>
- <ulist>
- <item>
- <p>
- The content model of input message elements
- are defined using a complex type that contains a
- sequence from XML Schema.
- </p>
- </item>
- <item>
- <p>
- The sequence MUST only contain elements. It MUST NOT
- contain other structures such as xs:choice.
- </p>
- </item>
- <item>
- <p>
- The sequence MUST contain only local element
- children. These child elements MAY contain the
- <att>nillable</att> attribute, and the attributes
- <att>minOccurs</att> and <att>maxOccurs</att> MUST have
- a value <code>0</code> or <code>1</code>.
- </p>
- </item>
- <item>
- <p>
- The localPart of input element's QName MUST be the same
- as the Interface operation component's name.
- </p>
- </item>
- <item>
- <p>
- The complex types that defines the body of an input
- element or its children elements MUST NOT contain any
- attributes.
- </p>
- </item>
- <item>
- <p>
- The input sequence MUST NOT contain multiple children
- element declared with the same local name.
- </p>
- </item>
- <item>
- <p>
- If the children elements of the input sequence are
- defined using an XML Schema type, they MUST derive from
- <code>xsd:simpleType</code>, and MUST NOT derive from
- <code>xsd:hexBinary</code> or
- <code>xsd:base64Binary</code>.
- </p>
- </item>
- </ulist>
- </div3>
- <div3 id="_operation_multipart_style">
- <head>Multipart style</head>
- <p>
- The Multipart style is selected by assigning the Interface
- Operation component's &interface_operation-style-p; property the value
- <emph>&MULTIPART-STYLE;</emph>.
- </p>
- <p>
- The Multipart style may only be used for Interface Operation
- components whose &interface_operation-message_exchange_pattern-p; property has the
- value '&wsdl-mep-in-only;', '&wsdl-mep-robust-in-only;' or
- '&wsdl-mep-in-out;'.
- </p>
- <p>
- Use of this value indicates that XML Schema <bibref ref="XMLSchemaP1"/> was used to define the schemas of the
- &message_reference-element-p; properties of all Message Reference components
- of the Interface Operation component with &message_reference-direction-p;
- property <emph>in</emph>. Those schemas MUST adhere to the
- rules below.
- </p>
- <ulist>
- <item>
- <p>
- The content model of input message elements
- are defined using a complex type that contains a
- sequence from XML Schema.
- </p>
- </item>
- <item>
- <p>
- The sequence MUST only contain elements. It MUST NOT
- contain other structures such as xs:choice.
- </p>
- </item>
- <item>
- <p>
- The sequence MUST contain only local element
- children. These child elements MAY contain the
- <att>nillable</att> attribute, and the attributes
- <att>minOccurs</att> and <att>maxOccurs</att> MUST have
- a value <code>1</code>.
- </p>
- </item>
- <item>
- <p>
- The localPart of input element's QName MUST be the same
- as the Interface operation component's name.
- </p>
- </item>
- <item>
- <p>
- The complex types that defines the body of an input
- element or its children elements MUST NOT contain any
- attributes.
- </p>
- </item>
- <item>
- <p>
- The input sequence MUST NOT contain multiple children
- element declared with the same local name.
- </p>
- </item>
- </ulist>
- </div3>
- </div2>
<div2 id="_http_serialization">
<head>Serialization format of instance data</head>
--- 1728,1731 ----
***************
*** 1881,1885 ****
</p>
<p>
! Other serialization formats may be used. Those may place
restrictions on the style of the interface operation bound.
</p>
--- 1737,1741 ----
</p>
<p>
! Other serialization formats may be used. Those MAY place
restrictions on the style of the interface operation bound.
</p>
***************
*** 2193,2196 ****
--- 2049,2199 ----
<!-- +++++++++ -->
+ <div2 id="_operation_styles">
+ <head>Operation Styles</head>
+ <p>
+ This section defines operation styles in use in parallel to the
+ HTTP 1.1 binding.
+ </p>
+ <div3 id="_operation_uri_style">
+ <head>URI Style</head>
+ <p>
+ The URI style is selected by assigning the Interface
+ Operation component's &interface_operation-style-p; property the value
+ <emph>&URI-STYLE;</emph>.
+ </p>
+ <p>
+ The URI style may only be used for Interface Operation
+ components whose &interface_operation-message_exchange_pattern-p; property has the
+ value '&wsdl-mep-in-only;', '&wsdl-mep-robust-in-only;' or
+ '&wsdl-mep-in-out;'.
+ </p>
+ <p>
+ Use of this value indicates that XML Schema <bibref ref="XMLSchemaP1"/> was used to define the schemas of the
+ &message_reference-element-p; properties of all Message Reference components
+ of the Interface Operation component with &message_reference-direction-p;
+ property <emph>in</emph>. Those schemas MUST adhere to the
+ rules below.
+ </p>
+ <ulist>
+ <item>
+ <p>
+ The content model of input message elements
+ are defined using a complex type that contains a
+ sequence from XML Schema.
+ </p>
+ </item>
+ <item>
+ <p>
+ The sequence MUST only contain elements. It MUST NOT
+ contain other structures such as xs:choice.
+ </p>
+ </item>
+ <item>
+ <p>
+ The sequence MUST contain only local element
+ children. These child elements MAY contain the
+ <att>nillable</att> attribute, and the attributes
+ <att>minOccurs</att> and <att>maxOccurs</att> MUST have
+ a value <code>0</code> or <code>1</code>.
+ </p>
+ </item>
+ <item>
+ <p>
+ The localPart of input element's QName MUST be the same
+ as the Interface operation component's name.
+ </p>
+ </item>
+ <item>
+ <p>
+ The complex types that defines the body of an input
+ element or its children elements MUST NOT contain any
+ attributes.
+ </p>
+ </item>
+ <item>
+ <p>
+ The input sequence MUST NOT contain multiple children
+ element declared with the same local name.
+ </p>
+ </item>
+ <item>
+ <p>
+ If the children elements of the input sequence are
+ defined using an XML Schema type, they MUST derive from
+ <code>xsd:simpleType</code>, and MUST NOT derive from
+ <code>xsd:hexBinary</code> or
+ <code>xsd:base64Binary</code>.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+ <div3 id="_operation_multipart_style">
+ <head>Multipart style</head>
+ <p>
+ The Multipart style is selected by assigning the Interface
+ Operation component's &interface_operation-style-p; property the value
+ <emph>&MULTIPART-STYLE;</emph>.
+ </p>
+ <p>
+ The Multipart style may only be used for Interface Operation
+ components whose &interface_operation-message_exchange_pattern-p; property has the
+ value '&wsdl-mep-in-only;', '&wsdl-mep-robust-in-only;' or
+ '&wsdl-mep-in-out;'.
+ </p>
+ <p>
+ Use of this value indicates that XML Schema <bibref ref="XMLSchemaP1"/> was used to define the schemas of the
+ &message_reference-element-p; properties of all Message Reference components
+ of the Interface Operation component with &message_reference-direction-p;
+ property <emph>in</emph>. Those schemas MUST adhere to the
+ rules below.
+ </p>
+ <ulist>
+ <item>
+ <p>
+ The content model of input message elements
+ are defined using a complex type that contains a
+ sequence from XML Schema.
+ </p>
+ </item>
+ <item>
+ <p>
+ The sequence MUST only contain elements. It MUST NOT
+ contain other structures such as xs:choice.
+ </p>
+ </item>
+ <item>
+ <p>
+ The sequence MUST contain only local element
+ children. These child elements MAY contain the
+ <att>nillable</att> attribute, and the attributes
+ <att>minOccurs</att> and <att>maxOccurs</att> MUST have
+ a value <code>1</code>.
+ </p>
+ </item>
+ <item>
+ <p>
+ The localPart of input element's QName MUST be the same
+ as the Interface operation component's name.
+ </p>
+ </item>
+ <item>
+ <p>
+ The complex types that defines the body of an input
+ element or its children elements MUST NOT contain any
+ attributes.
+ </p>
+ </item>
+ <item>
+ <p>
+ The input sequence MUST NOT contain multiple children
+ element declared with the same local name.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+ </div2>
+
+ <!-- +++++++++ -->
+
<div2 id="http-transfer-coding-decl">
<head>Specifying the transfer coding</head>
Received on Monday, 26 July 2004 06:33:52 UTC