- From: Paul Downey via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 10 Jun 2005 23:50:22 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv5089/2002/ws/desc/wsdl20 Modified Files: wsdl20-primer.xml wsdl20-primer.html Log Message: added versioning using SOAP headers Index: wsdl20-primer.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v retrieving revision 1.90 retrieving revision 1.91 diff -C2 -d -r1.90 -r1.91 *** wsdl20-primer.xml 10 Jun 2005 23:16:37 -0000 1.90 --- wsdl20-primer.xml 10 Jun 2005 23:50:19 -0000 1.91 *************** *** 1388,1393 **** Again, in compatible evolution this is usually safe, given that adding an additional operation to an abstract interface should not impact any ! existing interactions.</p></item><item><p>The messages exchanged may include additional data. ! How the messages themselves may change within a description depends to a large extent upon the type system being used to describe the message contents. RelaxNG <bibref ref="relax-ng"/> has good support for describing vocabularies that --- 1388,1393 ---- Again, in compatible evolution this is usually safe, given that adding an additional operation to an abstract interface should not impact any ! existing interactions.</p></item><item><p>The message bodies may include additional data. ! How the message contents may change within a description depends to a large extent upon the type system being used to describe the message contents. RelaxNG <bibref ref="relax-ng"/> has good support for describing vocabularies that *************** *** 1396,1402 **** <code>xs:anyAttribute</code> constructs. XML Schema 1.1 has been chartered to provide "changes necessary to provide better support for versioning of ! schemas", and it is anticipated that this will include improved support for more "open content" and therefore better support for compatible ! evolution of messages.</p></item></ulist></div3><div3 id="adv-versioning-big-bang"><head>Big Bang</head><p>The <emph>big bang</emph> approach to versioning is the simplest to currently represent in WSDL 2.0. In this approach, any change to a WSDL 2.0 document implies a change to the document's namespace, a change to the interface --- 1396,1413 ---- <code>xs:anyAttribute</code> constructs. XML Schema 1.1 has been chartered to provide "changes necessary to provide better support for versioning of ! schemas", and it is anticipated that this may include improved support for more "open content" and therefore better support for compatible ! evolution of messages.</p></item> ! <item><p>The protocol used to exchange messages may provide mechanisms for exchanging ! data outside of the message body. In the case of SOAP, the WSDL binding ! provides the ability to describe application data to be exchanged as headers. The ! SOAP processing model has a very good extensibility model with unknown headers ! being ignored by a receiver by default. There is also a mechanism whereby ! headers which are required as a part of an incompatible change ! may be marked with a 'mustUnderstand' flag. ! Passing additional items as headers may be the only way to compatibly ! evolve messages with fixed bodies.</p></item></ulist></div3> ! ! <div3 id="adv-versioning-big-bang"><head>Big Bang</head><p>The <emph>big bang</emph> approach to versioning is the simplest to currently represent in WSDL 2.0. In this approach, any change to a WSDL 2.0 document implies a change to the document's namespace, a change to the interface Index: wsdl20-primer.html =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v retrieving revision 1.62 retrieving revision 1.63 diff -C2 -d -r1.62 -r1.63 *** wsdl20-primer.html 10 Jun 2005 23:17:39 -0000 1.62 --- wsdl20-primer.html 10 Jun 2005 23:50:20 -0000 1.63 *************** *** 297,307 **** "#adv-multiple-inline-schemas">Importing Schemas</a><br /> 7.10.1 <a href= ! "#id349145">Schemas in Imported Documents</a><br /> 7.10.2 <a href= ! "#id349381">Multiple Inline Schemas in One Document</a><br /> 7.10.3 <a href= "#adv-schema-location">The schemaLocation Attribute</a><br /> 7.10.3.1 ! <a href="#id367025">Using the id Attribute to Identify Inline Schemas</a><br /> 7.11 <a href="#adv-rdf-mapping">Mapping to --- 297,307 ---- "#adv-multiple-inline-schemas">Importing Schemas</a><br /> 7.10.1 <a href= ! "#id349152">Schemas in Imported Documents</a><br /> 7.10.2 <a href= ! "#id349387">Multiple Inline Schemas in One Document</a><br /> 7.10.3 <a href= "#adv-schema-location">The schemaLocation Attribute</a><br /> 7.10.3.1 ! <a href="#id367036">Using the id Attribute to Identify Inline Schemas</a><br /> 7.11 <a href="#adv-rdf-mapping">Mapping to *************** *** 3384,3400 **** </li> <li> ! <p>The messages exchanged may include additional data. How the ! messages themselves may change within a description depends to a ! large extent upon the type system being used to describe the ! message contents. RelaxNG [<cite><a href="#relax-ng">RELAX ! NG</a></cite>] has good support for describing vocabularies that ! ignore unknown XML, as does OWL/RDF. XML Schema 1.0 has limited ! support for extending the description of a message via the ! <code>xs:any</code> and <code>xs:anyAttribute</code> constructs. ! XML Schema 1.1 has been chartered to provide "changes necessary to ! provide better support for versioning of schemas", and it is ! anticipated that this will include improved support for more "open ! content" and therefore better support for compatible evolution of ! messages.</p> </li> </ul> --- 3384,3411 ---- </li> <li> ! <p>The message bodies may include additional data. How the message ! contents may change within a description depends to a large extent ! upon the type system being used to describe the message contents. ! RelaxNG [<cite><a href="#relax-ng">RELAX NG</a></cite>] has good ! support for describing vocabularies that ignore unknown XML, as ! does OWL/RDF. XML Schema 1.0 has limited support for extending the ! description of a message via the <code>xs:any</code> and ! <code>xs:anyAttribute</code> constructs. XML Schema 1.1 has been ! chartered to provide "changes necessary to provide better support ! for versioning of schemas", and it is anticipated that this may ! include improved support for more "open content" and therefore ! better support for compatible evolution of messages.</p> ! </li> ! <li> ! <p>The protocol used to exchange messages may provide mechanisms ! for exchanging data outside of the message body. In the case of ! SOAP, the WSDL binding provides the ability to describe application ! data to be exchanged as headers. The SOAP processing model has a ! very good extensibility model with unknown headers being ignored by ! a receiver by default. There is also a mechanism whereby headers ! which are required as a part of an incompatible change may be ! marked with a 'mustUnderstand' flag. Passing additional items as ! headers may be the only way to compatibly evolve messages with ! fixed bodies.</p> </li> </ul> *************** *** 4509,4513 **** within the same document and from other documents.</p> <div class="div3"> ! <h4><a name="id349145" id="id349145"></a>7.10.1 Schemas in Imported Documents</h4> <p>In this example, we consider some GreatH Hotel Web services that --- 4520,4524 ---- within the same document and from other documents.</p> <div class="div3"> ! <h4><a name="id349152" id="id349152"></a>7.10.1 Schemas in Imported Documents</h4> <p>In this example, we consider some GreatH Hotel Web services that *************** *** 4667,4671 **** </div> <div class="div3"> ! <h4><a name="id349381" id="id349381"></a>7.10.2 Multiple Inline Schemas in One Document</h4> <p>A WSDL 2.0 document may define multiple inline schemas in its --- 4678,4682 ---- </div> <div class="div3"> ! <h4><a name="id349387" id="id349387"></a>7.10.2 Multiple Inline Schemas in One Document</h4> <p>A WSDL 2.0 document may define multiple inline schemas in its *************** *** 4788,4792 **** Framework</a></cite>]) can also be used.</p> <div class="div4"> ! <h5><a name="id367025" id="id367025"></a>7.10.3.1 Using the id Attribute to Identify Inline Schemas</h5> <p><a href="#schemaIds.wsdl">Example 7-27</a> shows the use of the --- 4799,4803 ---- Framework</a></cite>]) can also be used.</p> <div class="div4"> ! <h5><a name="id367036" id="id367036"></a>7.10.3.1 Using the id Attribute to Identify Inline Schemas</h5> <p><a href="#schemaIds.wsdl">Example 7-27</a> shows the use of the
Received on Friday, 10 June 2005 23:50:29 UTC