- From: Paul Downey via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 06 Jul 2005 18:51:09 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv6801/2002/ws/desc/wsdl20 Modified Files: wsdl20-primer.xml wsdl20-primer.html Log Message: added ednote for LC124 in the Versioning and Extensibility section Index: wsdl20-primer.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v retrieving revision 1.111 retrieving revision 1.112 diff -C2 -d -r1.111 -r1.112 *** wsdl20-primer.xml 6 Jul 2005 18:28:14 -0000 1.111 --- wsdl20-primer.xml 6 Jul 2005 18:51:07 -0000 1.112 *************** *** 2605,2609 **** upon the technical note on Web Architecture: Extensible Languages <bibref ref="web-extensible"/>.</p></item><item><p>The <loc href="http://www.w3.org/XML/Schema">XML Schema Working Group</loc> is collecting a series of use cases for schema versioning as a part of the Schema 1.1 activity. See XML Schema Versioning Use Cases <bibref ref="xsd-versioning"/>.</p></item><item><p>The <loc href="http://www.w3.org/2001/sw/BestPractices/">Semantic Web Best Practices and Deployments Working Group</loc> is ! examining how vocabularies may evolve. See <bibref ref="sw-vocabulary"/></p></item></ulist><p>While incomplete, these activities all agree in one important respect: that versioning is difficult, but you should anticipate and plan for change.</p><p>The draft finding on Versioning and Extensibility details two key --- 2605,2615 ---- upon the technical note on Web Architecture: Extensible Languages <bibref ref="web-extensible"/>.</p></item><item><p>The <loc href="http://www.w3.org/XML/Schema">XML Schema Working Group</loc> is collecting a series of use cases for schema versioning as a part of the Schema 1.1 activity. See XML Schema Versioning Use Cases <bibref ref="xsd-versioning"/>.</p></item><item><p>The <loc href="http://www.w3.org/2001/sw/BestPractices/">Semantic Web Best Practices and Deployments Working Group</loc> is ! examining how vocabularies may evolve. See <bibref ref="sw-vocabulary"/></p></item></ulist> ! <ednote> ! <name>PaulD</name> ! <date>20050706</date> ! <edtext>This section may be subject to change dependent upon the outcome of the WSDL Last Call Issue LC124, which discusses support compatible evolution of messages described using XML Schema 1.0.</edtext></ednote> ! ! <p>While incomplete, these activities all agree in one important respect: that versioning is difficult, but you should anticipate and plan for change.</p><p>The draft finding on Versioning and Extensibility details two key Index: wsdl20-primer.html =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v retrieving revision 1.83 retrieving revision 1.84 diff -C2 -d -r1.83 -r1.84 *** wsdl20-primer.html 6 Jul 2005 18:28:14 -0000 1.83 --- wsdl20-primer.html 6 Jul 2005 18:51:07 -0000 1.84 *************** *** 309,334 **** Service</a><br /> 5.2.5.1 ! <a href="#id367246">Additional Optional Elements Added in Content</a><br /> 5.2.5.2 ! <a href="#id367301">Additional Optional Elements Added to a Header</a><br /> 5.2.5.3 ! <a href="#id367341">Additional Mandatory Elements in Content</a><br /> 5.2.5.4 ! <a href="#id367392">Additional Optional Operation Added to Interface</a><br /> 5.2.5.5 ! <a href="#id367405">Additional Mandatory Operation Added to Interface</a><br /> 5.2.5.6 ! <a href="#id367453">Indicating Incompatibility by Changing the Endpoint URI</a><br /> 5.2.5.7 ! <a href="#id367466">Indicating Incompatibility by Changing the SOAP Action</a><br /> 5.2.5.8 ! <a href="#id367509">Indicating Incompatibility by Changing the Element Content</a><br /> 5.3 <a href= --- 309,334 ---- Service</a><br /> 5.2.5.1 ! <a href="#id367263">Additional Optional Elements Added in Content</a><br /> 5.2.5.2 ! <a href="#id367318">Additional Optional Elements Added to a Header</a><br /> 5.2.5.3 ! <a href="#id367357">Additional Mandatory Elements in Content</a><br /> 5.2.5.4 ! <a href="#id367408">Additional Optional Operation Added to Interface</a><br /> 5.2.5.5 ! <a href="#id367427">Additional Mandatory Operation Added to Interface</a><br /> 5.2.5.6 ! <a href="#id367475">Indicating Incompatibility by Changing the Endpoint URI</a><br /> 5.2.5.7 ! <a href="#id367488">Indicating Incompatibility by Changing the SOAP Action</a><br /> 5.2.5.8 ! <a href="#id367530">Indicating Incompatibility by Changing the Element Content</a><br /> 5.3 <a href= *************** *** 4316,4319 **** --- 4316,4332 ---- </li> </ul> + <table border="1" summary="Editorial note: PaulD"> + <tr> + <td align="left" valign="top" width="50%"><b>Editorial note: + PaulD</b></td> + <td align="right" valign="top" width="50%">20050706</td> + </tr> + <tr> + <td colspan="2" align="left" valign="top">This section may be + subject to change dependent upon the outcome of the WSDL Last Call + Issue LC124, which discusses support compatible evolution of + messages described using XML Schema 1.0.</td> + </tr> + </table> <p>While incomplete, these activities all agree in one important respect: that versioning is difficult, but you should anticipate *************** *** 4452,4456 **** Extending a Service</h4> <div class="div4"> ! <h5><a name="id367246" id="id367246"></a>5.2.5.1 Additional Optional Elements Added in Content</h5> <p>The following example demonstrates how content may be extended --- 4465,4469 ---- Extending a Service</h4> <div class="div4"> ! <h5><a name="id367263" id="id367263"></a>5.2.5.1 Additional Optional Elements Added in Content</h5> <p>The following example demonstrates how content may be extended *************** *** 4487,4491 **** </div> <div class="div4"> ! <h5><a name="id367301" id="id367301"></a>5.2.5.2 Additional Optional Elements Added to a Header</h5> <p>Another option is to add the extension as a header block. This --- 4500,4504 ---- </div> <div class="div4"> ! <h5><a name="id367318" id="id367318"></a>5.2.5.2 Additional Optional Elements Added to a Header</h5> <p>Another option is to add the extension as a header block. This *************** *** 4528,4532 **** </div> <div class="div4"> ! <h5><a name="id367341" id="id367341"></a>5.2.5.3 Additional Mandatory Elements in Content</h5> <p>This following example demonstrates an extention with additional --- 4541,4545 ---- </div> <div class="div4"> ! <h5><a name="id367357" id="id367357"></a>5.2.5.3 Additional Mandatory Elements in Content</h5> <p>This following example demonstrates an extention with additional *************** *** 4562,4566 **** </div> <div class="div4"> ! <h5><a name="id367392" id="id367392"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5> <p>Section <a href="#more-interfaces-inheritance"><b>2.4.2 --- 4575,4579 ---- </div> <div class="div4"> ! <h5><a name="id367408" id="id367408"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5> <p>Section <a href="#more-interfaces-inheritance"><b>2.4.2 *************** *** 4573,4577 **** </div> <div class="div4"> ! <h5><a name="id367405" id="id367405"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5> <p>Often mandatory operations are added to an interface. The Hotel --- 4586,4590 ---- </div> <div class="div4"> ! <h5><a name="id367427" id="id367427"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5> <p>Often mandatory operations are added to an interface. The Hotel *************** *** 4623,4627 **** </div> <div class="div4"> ! <h5><a name="id367453" id="id367453"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5> <p>To indicate incompatibility, the URI of the Hotel Endpoint can --- 4636,4640 ---- </div> <div class="div4"> ! <h5><a name="id367475" id="id367475"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5> <p>To indicate incompatibility, the URI of the Hotel Endpoint can *************** *** 4630,4634 **** </div> <div class="div4"> ! <h5><a name="id367466" id="id367466"></a>5.2.5.7 Indicating Incompatibility by Changing the SOAP Action</h5> <p>The SOAP Action can be set for the makeReservation request, and --- 4643,4647 ---- </div> <div class="div4"> ! <h5><a name="id367488" id="id367488"></a>5.2.5.7 Indicating Incompatibility by Changing the SOAP Action</h5> <p>The SOAP Action can be set for the makeReservation request, and *************** *** 4657,4661 **** </div> <div class="div4"> ! <h5><a name="id367509" id="id367509"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5> <p>The namespace or name of the makeReservation element can be --- 4670,4674 ---- </div> <div class="div4"> ! <h5><a name="id367530" id="id367530"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5> <p>The namespace or name of the makeReservation element can be
Received on Wednesday, 6 July 2005 18:51:20 UTC