- From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 03 May 2005 09:55:38 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv4795
Modified Files:
wsdl20-adjuncts.xml
Log Message:
Message Reference is now Interface Message Reference
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -C2 -d -r1.38 -r1.39
*** wsdl20-adjuncts.xml 3 May 2005 09:40:06 -0000 1.38
--- wsdl20-adjuncts.xml 3 May 2005 09:55:36 -0000 1.39
***************
*** 615,619 ****
<ulist>
! <item><p> The content model of input and output &message_reference-element-p;
elements MUST be defined using a complex type that contains a
sequence from XML Schema.</p></item>
--- 615,619 ----
<ulist>
! <item><p> The content model of input and output &interface_message_reference-element-p;
elements MUST be defined using a complex type that contains a
sequence from XML Schema.</p></item>
***************
*** 849,853 ****
Use of this value indicates that XML Schema <bibref
ref="XMLSchemaP1"/> was used to define the schema of the
! &message_reference-element-p; property of the Message
Reference component of the Interface Operation component
corresponding to the initial message of the message exchange
--- 849,853 ----
Use of this value indicates that XML Schema <bibref
ref="XMLSchemaP1"/> was used to define the schema of the
! &interface_message_reference-element-p; property of the Interface Message
Reference component of the Interface Operation component
corresponding to the initial message of the message exchange
***************
*** 923,927 ****
Use of this value indicates that XML Schema <bibref
ref="XMLSchemaP1"/> was used to define the schema of the
! &message_reference-element-p; property of the Message
Reference component of the Interface Operation component
corresponding to the initial message of the message exchange
--- 923,927 ----
Use of this value indicates that XML Schema <bibref
ref="XMLSchemaP1"/> was used to define the schema of the
! &interface_message_reference-element-p; property of the Interface Message
Reference component of the Interface Operation component
corresponding to the initial message of the message exchange
***************
*** 1178,1182 ****
payload (i.e., the contents of the SOAP Body &EII;
of the SOAP envelope) MUST be what is defined by the
! corresponding Message Reference component. This is subject
to optimization by a feature that is in use which may affect
serialization, such as MTOM <bibref ref="MTOM"/>. The
--- 1178,1182 ----
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
to optimization by a feature that is in use which may affect
serialization, such as MTOM <bibref ref="MTOM"/>. The
***************
*** 1185,1190 ****
<ulist>
<item><p>If the value of the
! &message_reference-message_content_model-p; property of
! the Message Reference component is <emph>#any</emph> then
the payload MAY be any one XML element.</p></item>
--- 1185,1190 ----
<ulist>
<item><p>If the value of the
! &interface_message_reference-message_content_model-p; property of
! the Interface Message Reference component is <emph>#any</emph> then
the payload MAY be any one XML element.</p></item>
***************
*** 1194,1201 ****
<item><p>If the value is <emph>#element</emph> then the
payload will be the &EII; identified by the
! &message_reference-element-p; property of the Message
Reference component.</p></item>
! <item> <p>If the Message Reference component is declared
using a non-XML type system (as considered in the Types
section of <bibref ref="WSDL-PART1"/>) then additional
--- 1194,1201 ----
<item><p>If the value is <emph>#element</emph> then the
payload will be the &EII; identified by the
! &interface_message_reference-element-p; property of the Interface Message
Reference component.</p></item>
! <item> <p>If the Interface Message Reference component is declared
using a non-XML type system (as considered in the Types
section of <bibref ref="WSDL-PART1"/>) then additional
***************
*** 2268,2273 ****
called an <term>instance data</term>, and is constrained by
the schema definition associated the message: the XML element
! referenced in the &message_reference-element-p; property of
! the Message Reference component for input and output messages,
and in the &interface_fault-element-p; property of an
Interface Fault component for faults.</termdef>
--- 2268,2273 ----
called an <term>instance data</term>, and is constrained by
the schema definition associated the message: the XML element
! referenced in the &interface_message_reference-element-p; property of
! the Interface Message Reference component for input and output messages,
and in the &interface_fault-element-p; property of an
Interface Fault component for faults.</termdef>
***************
*** 2383,2397 ****
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 Message
Reference or Interface Fault components:</p>
<ulist>
! <item><p>Message Reference component: if the value of the
! &message_reference-message_content_model-p; property is
<emph>#any</emph> then the payload MAY be any one XML
element. If the value is <emph>#none</emph> then the payload
MUST be empty. Finally if the value is <emph>#element</emph>
then the payload will be the &EII; identified by the
! &message_reference-element-p; property.</p></item>
<item><p>Interface Fault component: the payload will be the
&EII; identified by the &interface_fault-element-p;
--- 2383,2397 ----
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:</p>
<ulist>
! <item><p>Interface Message Reference component: if the value of the
! &interface_message_reference-message_content_model-p; property is
<emph>#any</emph> then the payload MAY be any one XML
element. If the value is <emph>#none</emph> then the payload
MUST be empty. Finally if the value is <emph>#element</emph>
then the payload will be the &EII; identified by the
! &interface_message_reference-element-p; property.</p></item>
<item><p>Interface Fault component: the payload will be the
&EII; identified by the &interface_fault-element-p;
***************
*** 2399,2403 ****
</ulist>
! <p>If the Message Reference component or the Interface Fault
component is declared using a non-XML type system (as
considered in the Types section of <bibref ref="WSDL-PART1"/>)
--- 2399,2403 ----
</ulist>
! <p>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 <bibref ref="WSDL-PART1"/>)
***************
*** 3780,3784 ****
<table border="1" id="tab_HTTP_Transfer_Coding_Mapping">
! <caption>Mapping from XML Representation to Message Reference Component Extension
Properties</caption>
<tbody>
--- 3780,3784 ----
<table border="1" id="tab_HTTP_Transfer_Coding_Mapping">
! <caption>Mapping from XML Representation to Interface Message Reference Component Extension
Properties</caption>
<tbody>
Received on Tuesday, 3 May 2005 09:55:41 UTC