- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 14 Jun 2005 15:56:01 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv6155/ws/desc/wsdl20
Modified Files:
wsdl20-adjuncts.xml
Log Message:
Fix a few remaining properties, and remove the now unncessary properties.dtd.
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.64
retrieving revision 1.65
diff -C2 -d -r1.64 -r1.65
*** wsdl20-adjuncts.xml 14 Jun 2005 15:50:52 -0000 1.64
--- wsdl20-adjuncts.xml 14 Jun 2005 15:55:59 -0000 1.65
***************
*** 18,23 ****
about the one-way MEP addition -->
<!ENTITY status SYSTEM "status-adjuncts.xml">
- <!ENTITY % properties-refs SYSTEM "properties.dtd">
- %properties-refs;
]>
<spec w3c-doctype="wd" role="&document.role;">
--- 18,21 ----
***************
*** 773,778 ****
<p>If the <comp>Interface Operation</comp> component uses a
! &interface_operation-message_exchange_pattern-p; for which there is no output
! element, i.e. '&wsdl-ns;/in-only', then the conditions
stated below that refer to output elements MUST be considered
to be implicitly satisfied.</p>
--- 771,776 ----
<p>If the <comp>Interface Operation</comp> component uses a
! <prop comp="Interface Operation">message exchange pattern</prop> for which there is no output
! element, i.e. <attval>&wsdl-ns;/in-only</attval>, then the conditions
stated below that refer to output elements MUST be considered
to be implicitly satisfied.</p>
***************
*** 780,784 ****
<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>
--- 778,782 ----
<ulist>
! <item><p> The content model of input and output <prop comp="Interface Message Reference">element</prop>
elements MUST be defined using a complex type that contains a
sequence from XML Schema.</p></item>
***************
*** 3034,3038 ****
<p><propdef comp="Binding Operation">http location</propdef> OPTIONAL. A <emph>xs:anyURI</emph>. This
IRI is combined with the base IRI specified in the
! &endpoint-address-p; property of the <comp>Endpoint</comp> component to
form the full IRI for the HTTP request to invoke the
operation. It MUST contain an absolute or a relative
--- 3032,3036 ----
<p><propdef comp="Binding Operation">http location</propdef> OPTIONAL. A <emph>xs:anyURI</emph>. This
IRI is combined with the base IRI specified in the
! <prop comp="Endpoint">address</prop> property of the <comp>Endpoint</comp> component to
form the full IRI for the HTTP request to invoke the
operation. It MUST contain an absolute or a relative
***************
*** 3671,3675 ****
<p>In this serialization, the value of the <prop comp="Binding Operation">http location</prop>
property is used as a template which is combined with the
! &endpoint-address-p; property of the endpoint element to
form the full IRI to be used in an HTTP request, as
specified in section <specref ref="http-operation-decl-relate"/>.</p>
--- 3669,3673 ----
<p>In this serialization, the value of the <prop comp="Binding Operation">http location</prop>
property is used as a template which is combined with the
! <prop comp="Endpoint">address</prop> property of the endpoint element to
form the full IRI to be used in an HTTP request, as
specified in section <specref ref="http-operation-decl-relate"/>.</p>
Received on Tuesday, 14 June 2005 15:56:03 UTC