- From: Kevin Liu via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 03 Oct 2005 21:13:21 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv4469/ws/desc/wsdl20
Modified Files:
wsdl20-primer.html wsdl20-primer.xml
Log Message:
Minor editings in "More on Message Types" section
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.133
retrieving revision 1.134
diff -C2 -d -r1.133 -r1.134
*** wsdl20-primer.xml 30 Sep 2005 05:27:02 -0000 1.133
--- wsdl20-primer.xml 3 Oct 2005 21:13:18 -0000 1.134
***************
*** 691,696 ****
<div2 id="more-types"><head>More on Message Types</head>
! <p>Message types may be defined in various schema languages. In this primer, we will only focus on the use of XML Schema <bibref ref="XMLSchemaP1"/> since XML Schema
! support is required and natively supported by WSDL 2.0. Message type definitions written in other schema languages may be introduced into a WSDL 2.0 via extensions. The W3C notes on <bibref ref="altschemalangs"/> provides examples of using other schema languages. </p>
<p>The following is the XML syntax for the <code>wsdl:types</code> element:</p>
--- 691,695 ----
<div2 id="more-types"><head>More on Message Types</head>
! <p>Message types may be defined in various schema languages. In this primer, we will only focus on the use of XML Schema <bibref ref="XMLSchemaP1"/> since it's natively supported by WSDL 2.0. Message types defined in other languages may be introduced into a WSDL 2.0 <code>description</code> via extensions, see the W3C notes <bibref ref="altschemalangs"/> for more details. </p>
<p>The following is the XML syntax for the <code>wsdl:types</code> element:</p>
***************
*** 727,731 ****
<example id="example-schema-import">
! <head> <code>xs:import</code>ed Message Definitions are made Available to the Containing WSDL 2.0 Description</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
<description ]]>xmlns="&wsdl-ns;"<![CDATA[
--- 726,730 ----
<example id="example-schema-import">
! <head> <code>xs:import</code>ed Message Definitions that Are Visible to the Containing WSDL 2.0 Description</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
<description ]]>xmlns="&wsdl-ns;"<![CDATA[
***************
*** 751,755 ****
<example id="example-schema-import1">
! <head><code>xs:import</code>ed Message Definitions are not Available to the Containing WSDL 2.0 Description</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
<description ]]>xmlns="&wsdl-ns;"<![CDATA[
--- 750,754 ----
<example id="example-schema-import1">
! <head><code>xs:import</code>ed Message Definitions in Inlined Schema Are Not Visible to the Containing WSDL 2.0 Description</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
<description ]]>xmlns="&wsdl-ns;"<![CDATA[
***************
*** 777,781 ****
<example id="example-schema-import2">
! <head><code>xs:included</code> Message Definitions are Available to the Containing WSDL 2.0 Description</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
<description ]]>xmlns="&wsdl-ns;"<![CDATA[
--- 776,780 ----
<example id="example-schema-import2">
! <head><code>xs:included</code> Message Definitions in Inlined Schema Are Visible to the Containing WSDL 2.0 Description</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
<description ]]>xmlns="&wsdl-ns;"<![CDATA[
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.97
retrieving revision 1.98
diff -C2 -d -r1.97 -r1.98
*** wsdl20-primer.html 30 Sep 2005 05:27:02 -0000 1.97
--- wsdl20-primer.html 3 Oct 2005 21:13:18 -0000 1.98
***************
*** 87,93 ****
<hr><div class="toc">
<h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br>6. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br></p></div><hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br> 1.1 <a href="#Prerequisites">Prerequisites</a><br> 1.2 <a href="#PrimerStructure">Structure of this Primer</a><br> 1.3 <a href="#UseIRI">Use of URI and IRI</a><br> 1.4 <a href="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br> 2.1 <a href="#basic-example">Getting Started: The GreatH Hotel Example</a><br> 2.1.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br> 2.1.2 <a href="#basics-getting-started">Defining a WSDL 2.0 Target Namespace</a><br> 2.1.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br>   2.1.3 <a href="#basics-types">Defining Message Types</a><br> 2.1.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br> 2.1.4 <a href="#basics-interface">Defining an Interface</a><br> 2.1.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br> 2.1.5 <a href="#basics-binding">Defining a Binding</a><br> 2.1.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br> 2.1.6 <a href="#basics-service">Defining a Service</a><br> 2.1.6.1 <a href="#example-initial-service-explanation">Explanationof Example</a><br> 2.1.7 <a href="#basics-documentation">Documenting the Service</a><br> 2.1.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br> 2.2 <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br> 2.2.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br> 2.2.2 <a href="#wsdl-schema">WSDL 2.0 Schema</a><br> 2.2.2.1 <a href="#element-order">WSDL 2.0 Element Ordering</a><br> 2.2.3 <a href="#component-model">WSDL 2.0 Component Model</a><br> 2.2.3.1 <a href="#import-component">WSDL 2.0 Import and Include</a><br>  2.3 <a href="#more-types">More on Message Types</a><br> 2.3.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br> 2.3.2 <a href="#more-types-schema-import">Importing XML Schema</a><br> 2.3.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br> 2.4 <a href="#more-interfaces">More on Interfaces</a><br> 2.4.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br> 2.4.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br> 2.4.3 <a href="#more-interfaces-faults">Interface Faults</a><br> 2.4.4 <a href="#more-interfaces-operations">Interface Operations</a><br> &nbp; 2.4.4.1 <a href="#more-interfaces-op-attr">Operation Attributes</a><br> 2.4.4.2 <a href="#N68045">Operation Message References</a><br> 2.4.4.2.1 <a href="#N68074">The messageLabel Attribute</a><br> 2.4.4.2.2 <a href="#N68098">The element Attribute</a><br> 2.4.4.2.3 <a href="#N68179">Multiple infault or outfault Elements</a><br> 2.4.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br> 2.5 <a href="#more-bindings">More on Bindings</a><br> &nsp; 2.5.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br> 2.5.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br> 2.5.3 <a href="#more-bindings-faults">Binding Faults</a><br> 2.5.4 <a href="#bindingOperations">Binding Operations</a><br> 2.5.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br> 2.5.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br> 2.5.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br> 2.5.6.1 <a href="#N68641">Explanation of
! Example</a><br> 2.5.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br> 3.1 <a href="#adv-import-and-authoring">Importing WSDL</a><br> 3.2 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br> 3.2.1 <a href="#N68977">Schemas in Imported Documents</a><br> 3.2.2 <a href="#N69116">Multiple Inline Schemas in One Document</a><br> 3.2.3 <a href="#adv-schema-location">The schemaLocation Attribute</a><br> 3.2.3.1 <a href="#N69212">Using the id Attribute to Identify Inline
! Schemas</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br> 4.1 <a href="#adv-extensibility">Extensibility</a><br> 4.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br> 4.2 <a href="#adv-FP">Features and Properties</a><br> 4.2.1 <a href="#adv-FP-soap-modules">SOAP Modules</a><br> 4.2.2 <a href="#adv-FP-abstract-features">Abstract Features</a><br> 4.2.3 <a href="#adv-fp-properties">Properties</a><br> 4.3 <a href="#adv-MEP">Defining New MEPs</a><br> 4.3.1 <a href="#challenge-confirm">Confirmed Challenge</a><br> 4.4 <a href="#adv-RPCstyle">RPC Style</a><br> 4.5 <a href"#adv-MTOM">MTOM and Attachments Support</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br> 5.1 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br> 5.2 <a href="#adv-versioning">Web Service Versioning</a><br> 5.2.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br> 5.2.2 <a href="#adv-versioning-big-bang">Big Bang</a><br> 5.2.3 <a href="#ad-versioing-migration">Evolving a Service</a><br> 5.2.4 <a href="#adv-versioning-combined">Combined Approaches</a><br> 5.2.5 <a href="#adv-versioning-examples">Examples of Versioning and Extending a Service</a><br> 5.2.5.1 <a href="#N70204">Additional Opional Elements Added in Content</a><br> 5.2.5.2 <a href="#N70227">Additional Optional Elements Added to a Header</a><br> 5.2.5.3 <a href="#N70250">Additional Mandatory Elements in Content</a><br> 5.2.5.4 <a href="#N70273">Additional Optional Operation Added to Interface</a><br> 5.2.5.5 <a href="#N70285">Additional Mandatory Operation Added to Interface</a><br> 5.2.5.6 <a href="#N70311">Indicating Incompatibility by Changing the Endpoint URI</a><br> 5.2.5.7 <a href="#N70320">Indicating Incompatibility by Changing the SOAP Action</a><br> &bsp; 5.2.5.8 <a href="#N70343">Indicating Incompatibility by Changing the Element Content</a><br> 5.3 <a href="#adv-service-references">
Describing Web Service Messages That Refer to Other Web
Services
--- 87,93 ----
<hr><div class="toc">
<h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br>6. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br></p></div><hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br> 1.1 <a href="#Prerequisites">Prerequisites</a><br> 1.2 <a href="#PrimerStructure">Structure of this Primer</a><br> 1.3 <a href="#UseIRI">Use of URI and IRI</a><br> 1.4 <a href="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br> 2.1 <a href="#basic-example">Getting Started: The GreatH Hotel Example</a><br> 2.1.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br> 2.1.2 <a href="#basics-getting-started">Defining a WSDL 2.0 Target Namespace</a><br> 2.1.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br>   2.1.3 <a href="#basics-types">Defining Message Types</a><br> 2.1.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br> 2.1.4 <a href="#basics-interface">Defining an Interface</a><br> 2.1.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br> 2.1.5 <a href="#basics-binding">Defining a Binding</a><br> 2.1.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br> 2.1.6 <a href="#basics-service">Defining a Service</a><br> 2.1.6.1 <a href="#example-initial-service-explanation">Explanationof Example</a><br> 2.1.7 <a href="#basics-documentation">Documenting the Service</a><br> 2.1.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br> 2.2 <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br> 2.2.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br> 2.2.2 <a href="#wsdl-schema">WSDL 2.0 Schema</a><br> 2.2.2.1 <a href="#element-order">WSDL 2.0 Element Ordering</a><br> 2.2.3 <a href="#component-model">WSDL 2.0 Component Model</a><br> 2.2.3.1 <a href="#import-component">WSDL 2.0 Import and Include</a><br>  2.3 <a href="#more-types">More on Message Types</a><br> 2.3.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br> 2.3.2 <a href="#more-types-schema-import">Importing XML Schema</a><br> 2.3.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br> 2.4 <a href="#more-interfaces">More on Interfaces</a><br> 2.4.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br> 2.4.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br> 2.4.3 <a href="#more-interfaces-faults">Interface Faults</a><br> 2.4.4 <a href="#more-interfaces-operations">Interface Operations</a><br> &nbp; 2.4.4.1 <a href="#more-interfaces-op-attr">Operation Attributes</a><br> 2.4.4.2 <a href="#N68048">Operation Message References</a><br> 2.4.4.2.1 <a href="#N68077">The messageLabel Attribute</a><br> 2.4.4.2.2 <a href="#N68101">The element Attribute</a><br> 2.4.4.2.3 <a href="#N68182">Multiple infault or outfault Elements</a><br> 2.4.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br> 2.5 <a href="#more-bindings">More on Bindings</a><br> &nsp; 2.5.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br> 2.5.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br> 2.5.3 <a href="#more-bindings-faults">Binding Faults</a><br> 2.5.4 <a href="#bindingOperations">Binding Operations</a><br> 2.5.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br> 2.5.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br> 2.5.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br> 2.5.6.1 <a href="#N68644">Explanation of
! Example</a><br> 2.5.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br> 3.1 <a href="#adv-import-and-authoring">Importing WSDL</a><br> 3.2 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br> 3.2.1 <a href="#N68980">Schemas in Imported Documents</a><br> 3.2.2 <a href="#N69119">Multiple Inline Schemas in One Document</a><br> 3.2.3 <a href="#adv-schema-location">The schemaLocation Attribute</a><br> 3.2.3.1 <a href="#N69215">Using the id Attribute to Identify Inline
! Schemas</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br> 4.1 <a href="#adv-extensibility">Extensibility</a><br> 4.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br> 4.2 <a href="#adv-FP">Features and Properties</a><br> 4.2.1 <a href="#adv-FP-soap-modules">SOAP Modules</a><br> 4.2.2 <a href="#adv-FP-abstract-features">Abstract Features</a><br> 4.2.3 <a href="#adv-fp-properties">Properties</a><br> 4.3 <a href="#adv-MEP">Defining New MEPs</a><br> 4.3.1 <a href="#challenge-confirm">Confirmed Challenge</a><br> 4.4 <a href="#adv-RPCstyle">RPC Style</a><br> 4.5 <a href"#adv-MTOM">MTOM and Attachments Support</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br> 5.1 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br> 5.2 <a href="#adv-versioning">Web Service Versioning</a><br> 5.2.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br> 5.2.2 <a href="#adv-versioning-big-bang">Big Bang</a><br> 5.2.3 <a href="#ad-versioing-migration">Evolving a Service</a><br> 5.2.4 <a href="#adv-versioning-combined">Combined Approaches</a><br> 5.2.5 <a href="#adv-versioning-examples">Examples of Versioning and Extending a Service</a><br> 5.2.5.1 <a href="#N70207">Additional Opional Elements Added in Content</a><br> 5.2.5.2 <a href="#N70230">Additional Optional Elements Added to a Header</a><br> 5.2.5.3 <a href="#N70253">Additional Mandatory Elements in Content</a><br> 5.2.5.4 <a href="#N70276">Additional Optional Operation Added to Interface</a><br> 5.2.5.5 <a href="#N70288">Additional Mandatory Operation Added to Interface</a><br> 5.2.5.6 <a href="#N70314">Indicating Incompatibility by Changing the Endpoint URI</a><br> 5.2.5.7 <a href="#N70323">Indicating Incompatibility by Changing the SOAP Action</a><br> &bsp; 5.2.5.8 <a href="#N70346">Indicating Incompatibility by Changing the Element Content</a><br> 5.3 <a href="#adv-service-references">
Describing Web Service Messages That Refer to Other Web
Services
***************
*** 737,742 ****
<h3><a name="more-types"></a>2.3 More on Message Types</h3>
! <p>Message types may be defined in various schema languages. In this primer, we will only focus on the use of XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>] since XML Schema
! support is required and natively supported by WSDL 2.0. Message type definitions written in other schema languages may be introduced into a WSDL 2.0 via extensions. The W3C notes on [<cite><a href="#altschemalangs">Alternative Schema Languages Support</a></cite>] provides examples of using other schema languages. </p>
<p>The following is the XML syntax for the <code>wsdl:types</code> element:</p>
--- 737,741 ----
<h3><a name="more-types"></a>2.3 More on Message Types</h3>
! <p>Message types may be defined in various schema languages. In this primer, we will only focus on the use of XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>] since it's natively supported by WSDL 2.0. Message types defined in other languages may be introduced into a WSDL 2.0 <code>description</code> via extensions, see the W3C notes [<cite><a href="#altschemalangs">Alternative Schema Languages Support</a></cite>] for more details. </p>
<p>The following is the XML syntax for the <code>wsdl:types</code> element:</p>
***************
*** 775,779 ****
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="example-schema-import"></a><i><span>Example 2-8. </span> <code>xs:import</code>ed Message Definitions are made Available to the Containing WSDL 2.0 Description</i></p>
<div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8" ?>
<description xmlns="http://www.w3.org/@@@@/@@/wsdl"
--- 774,778 ----
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="example-schema-import"></a><i><span>Example 2-8. </span> <code>xs:import</code>ed Message Definitions that Are Visible to the Containing WSDL 2.0 Description</i></p>
<div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8" ?>
<description xmlns="http://www.w3.org/@@@@/@@/wsdl"
***************
*** 799,803 ****
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="example-schema-import1"></a><i><span>Example 2-9. </span><code>xs:import</code>ed Message Definitions are not Available to the Containing WSDL 2.0 Description</i></p>
<div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8" ?>
<description xmlns="http://www.w3.org/@@@@/@@/wsdl"
--- 798,802 ----
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="example-schema-import1"></a><i><span>Example 2-9. </span><code>xs:import</code>ed Message Definitions in Inlined Schema Are Not Visible to the Containing WSDL 2.0 Description</i></p>
<div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8" ?>
<description xmlns="http://www.w3.org/@@@@/@@/wsdl"
***************
*** 825,829 ****
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="example-schema-import2"></a><i><span>Example 2-10. </span><code>xs:included</code> Message Definitions are Available to the Containing WSDL 2.0 Description</i></p>
<div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8" ?>
<description xmlns="http://www.w3.org/@@@@/@@/wsdl"
--- 824,828 ----
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="example-schema-import2"></a><i><span>Example 2-10. </span><code>xs:included</code> Message Definitions in Inlined Schema Are Visible to the Containing WSDL 2.0 Description</i></p>
<div class="exampleInner"><pre><?xml version="1.0" encoding="utf-8" ?>
<description xmlns="http://www.w3.org/@@@@/@@/wsdl"
***************
*** 1170,1177 ****
</div><div class="div4">
! <h5><a name="N68045"></a>2.4.4.2 Operation Message References</h5><p>An <code>operation</code> will also have <code>input</code>, <code>output</code>,<code>infault</code>, and/or <code>outfault</code> element children that specify the ordinary and fault message types to be used by that operation. The MEP specified by the <code>pattern</code> attribute determines which of these elements should be included, since each MEP has placeholders for the message types involved in its pattern. </p><p>Since operations were already discussed in <a href="#basics-interface"><b>2.1.4 Defining an Interface</b></a>, this section will merely comment on additional capabilities that were not previously explained.</p>
<div class="div5">
! <h6><a name="N68074"></a>2.4.4.2.1 The messageLabel Attribute</h6>
<p>
The
--- 1169,1176 ----
</div><div class="div4">
! <h5><a name="N68048"></a>2.4.4.2 Operation Message References</h5><p>An <code>operation</code> will also have <code>input</code>, <code>output</code>,<code>infault</code>, and/or <code>outfault</code> element children that specify the ordinary and fault message types to be used by that operation. The MEP specified by the <code>pattern</code> attribute determines which of these elements should be included, since each MEP has placeholders for the message types involved in its pattern. </p><p>Since operations were already discussed in <a href="#basics-interface"><b>2.1.4 Defining an Interface</b></a>, this section will merely comment on additional capabilities that were not previously explained.</p>
<div class="div5">
! <h6><a name="N68077"></a>2.4.4.2.1 The messageLabel Attribute</h6>
<p>
The
***************
*** 1193,1197 ****
<div class="div5">
! <h6><a name="N68098"></a>2.4.4.2.2 The element Attribute</h6>
<p>
The
--- 1192,1196 ----
<div class="div5">
! <h6><a name="N68101"></a>2.4.4.2.2 The element Attribute</h6>
<p>
The
***************
*** 1254,1258 ****
</div>
<div class="div5">
! <h6><a name="N68179"></a>2.4.4.2.3 Multiple infault or outfault Elements</h6><p>When <code>infault</code> and/or <code>outfault</code> occur multiple times within an <code>operation</code>, they define alternative fault messages. </p></div></div>
--- 1253,1257 ----
</div>
<div class="div5">
! <h6><a name="N68182"></a>2.4.4.2.3 Multiple infault or outfault Elements</h6><p>When <code>infault</code> and/or <code>outfault</code> occur multiple times within an <code>operation</code>, they define alternative fault messages. </p></div></div>
***************
*** 1476,1480 ****
</div>
<div class="div4">
! <h5><a name="N68641"></a>2.5.6.1 Explanation of
Example</h5>
--- 1475,1479 ----
</div>
<div class="div4">
! <h5><a name="N68644"></a>2.5.6.1 Explanation of
Example</h5>
***************
*** 1722,1726 ****
<div class="div3">
! <h4><a name="N68977"></a>3.2.1 Schemas in Imported Documents</h4>
<p>
In this example, we consider some GreatH Hotel
--- 1721,1725 ----
<div class="div3">
! <h4><a name="N68980"></a>3.2.1 Schemas in Imported Documents</h4>
<p>
In this example, we consider some GreatH Hotel
***************
*** 1929,1933 ****
<div class="div3">
! <h4><a name="N69116"></a>3.2.2 Multiple Inline Schemas in One Document</h4>
<p>
A WSDL 2.0 document may define multiple inline
--- 1928,1932 ----
<div class="div3">
! <h4><a name="N69119"></a>3.2.2 Multiple Inline Schemas in One Document</h4>
<p>
A WSDL 2.0 document may define multiple inline
***************
*** 2063,2067 ****
the <code>schema</code> element. The simplest way to accomplish this is to use the <code>id</code> attribute, however XPointer (see [<cite><a href="#XPTR">XPointer Framework</a></cite>]) can also be used.
</p><div class="div4">
! <h5><a name="N69212"></a>3.2.3.1 Using the id Attribute to Identify Inline
Schemas</h5><p>
<a href="#schemaIds.wsdl">Example 3-6</a>
--- 2062,2066 ----
the <code>schema</code> element. The simplest way to accomplish this is to use the <code>id</code> attribute, however XPointer (see [<cite><a href="#XPTR">XPointer Framework</a></cite>]) can also be used.
</p><div class="div4">
! <h5><a name="N69215"></a>3.2.3.1 Using the id Attribute to Identify Inline
Schemas</h5><p>
<a href="#schemaIds.wsdl">Example 3-6</a>
***************
*** 2840,2844 ****
<div class="div4">
! <h5><a name="N70204"></a>5.2.5.1 Additional Optional Elements Added in Content</h5>
<p> The following example demonstrates how content may be extended with
additional content. The reservation service is changed to a newer version that can accept an optional
--- 2839,2843 ----
<div class="div4">
! <h5><a name="N70207"></a>5.2.5.1 Additional Optional Elements Added in Content</h5>
<p> The following example demonstrates how content may be extended with
additional content. The reservation service is changed to a newer version that can accept an optional
***************
*** 2869,2873 ****
<div class="div4">
! <h5><a name="N70227"></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 is
accomplished by defining an element for the extension and adding a
--- 2868,2872 ----
<div class="div4">
! <h5><a name="N70230"></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 is
accomplished by defining an element for the extension and adding a
***************
*** 2904,2908 ****
<div class="div4">
! <h5><a name="N70250"></a>5.2.5.3 Additional Mandatory Elements in Content</h5>
<p> This following example demonstrates an extension with additional
content. The reservation service requires a number of guests parameter.
--- 2903,2907 ----
<div class="div4">
! <h5><a name="N70253"></a>5.2.5.3 Additional Mandatory Elements in Content</h5>
<p> This following example demonstrates an extension with additional
content. The reservation service requires a number of guests parameter.
***************
*** 2932,2936 ****
<div class="div4">
! <h5><a name="N70273"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5>
<p> Section <a href="#more-interfaces-inheritance"><b>2.4.2 Interface Inheritance</b></a> shows another type
of versioning or extension, where the reservationInterface extends the
--- 2931,2935 ----
<div class="div4">
! <h5><a name="N70276"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5>
<p> Section <a href="#more-interfaces-inheritance"><b>2.4.2 Interface Inheritance</b></a> shows another type
of versioning or extension, where the reservationInterface extends the
***************
*** 2941,2945 ****
<div class="div4">
! <h5><a name="N70285"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5>
<p> Often mandatory operations are added to an interface. The Hotel service
decides to add an operation to the reservation service which is a
--- 2940,2944 ----
<div class="div4">
! <h5><a name="N70288"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5>
<p> Often mandatory operations are added to an interface. The Hotel service
decides to add an operation to the reservation service which is a
***************
*** 2984,2988 ****
<div class="div4">
! <h5><a name="N70311"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5>
<p> To indicate incompatibility, the URI of the Hotel Endpoint can be
changed and messages send to the old Endpoint return a Fault.</p>
--- 2983,2987 ----
<div class="div4">
! <h5><a name="N70314"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5>
<p> To indicate incompatibility, the URI of the Hotel Endpoint can be
changed and messages send to the old Endpoint return a Fault.</p>
***************
*** 2990,2994 ****
<div class="div4">
! <h5><a name="N70320"></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 making
it different than the earlier version should indicate incompatibility.</p>
--- 2989,2993 ----
<div class="div4">
! <h5><a name="N70323"></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 making
it different than the earlier version should indicate incompatibility.</p>
***************
*** 3011,3015 ****
<div class="div4">
! <h5><a name="N70343"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5>
<p> The namespace or name of the makeReservation element can be changed, and
then the interface and bindings changed. To indicate incompatibility,
--- 3010,3014 ----
<div class="div4">
! <h5><a name="N70346"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5>
<p> The namespace or name of the makeReservation element can be changed, and
then the interface and bindings changed. To indicate incompatibility,
Received on Monday, 3 October 2005 21:13:38 UTC