- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 22 Jun 2005 14:35:03 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv26415/wsdl20
Modified Files:
wsdl20.html wsdl20-adjuncts.html wsdl20.tex wsdl20-primer.xml
build.xml wsdl20-primer.html
Log Message:
Fixed validation errors in Primer and regenerated documents.
Index: build.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/build.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -C2 -d -r1.26 -r1.27
*** build.xml 22 Jun 2005 14:24:26 -0000 1.26
--- build.xml 22 Jun 2005 14:35:01 -0000 1.27
***************
*** 136,140 ****
</xmlvalidate>
<xmlvalidate lenient="false">
! <fileset dir="." includes="wsdl20*.xml" excludes="wsdl20-primer.xml, wsdl20-defs.xml, wsdl20-specs.xml"/>
</xmlvalidate>
</target>
--- 136,140 ----
</xmlvalidate>
<xmlvalidate lenient="false">
! <fileset dir="." includes="wsdl20*.xml" excludes="wsdl20-defs.xml, wsdl20-specs.xml"/>
</xmlvalidate>
</target>
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.62
retrieving revision 1.63
diff -C2 -d -r1.62 -r1.63
*** wsdl20.tex 22 Jun 2005 14:24:25 -0000 1.62
--- wsdl20.tex 22 Jun 2005 14:35:01 -0000 1.63
***************
*** 12375,12379 ****
\multicolumn{1}{|c}{\bf Component}&
! \multicolumn{1}{|c|}{\bf Properties}
\\ \hline
--- 12375,12379 ----
\multicolumn{1}{|c}{\bf Component}&
! \multicolumn{1}{|c|}{\bf Defined Properties}
\\ \hline
***************
*** 12382,12386 ****
&
! features,name,parent,properties
\\ \hline
--- 12382,12386 ----
&
! features, name, parent, properties
\\ \hline
***************
*** 12390,12394 ****
&
! binding faults,binding operations,features,interface,name,properties,type
\\ \hline
--- 12390,12394 ----
&
! binding faults, binding operations, features, interface, name, properties, type
\\ \hline
***************
*** 12398,12404 ****
&
! features,
interface fault
! ,parent,properties
\\ \hline
--- 12398,12404 ----
&
! features,
interface fault
! , parent, properties
\\ \hline
***************
*** 12410,12418 ****
features
! ,
interface fault reference
! ,
parent
! ,
properties
--- 12410,12418 ----
features
! ,
interface fault reference
! ,
parent
! ,
properties
***************
*** 12426,12434 ****
features
! ,
interface message reference
! ,
parent
! ,
properties
--- 12426,12434 ----
features
! ,
interface message reference
! ,
parent
! ,
properties
***************
*** 12442,12450 ****
binding fault references
! ,
binding message references
! ,features,
interface operation
! ,parent,properties
\\ \hline
--- 12442,12450 ----
binding fault references
! ,
binding message references
! , features,
interface operation
! , parent, properties
\\ \hline
***************
*** 12454,12458 ****
&
! bindings,element declarations,interfaces,services,type definitions
\\ \hline
--- 12454,12458 ----
&
! bindings, element declarations, interfaces, services, type definitions
\\ \hline
***************
*** 12470,12474 ****
&
! address,binding,features,name,parent,properties
\\ \hline
--- 12470,12474 ----
&
! address, binding, features, name, parent, properties
\\ \hline
***************
*** 12478,12482 ****
&
! parent,ref,required
\\ \hline
--- 12478,12482 ----
&
! parent, ref, required
\\ \hline
***************
*** 12486,12490 ****
&
! extended interfaces,features,interface faults,interface operations,name,properties
\\ \hline
--- 12486,12490 ----
&
! extended interfaces, features, interface faults, interface operations, name, properties
\\ \hline
***************
*** 12494,12498 ****
&
! element declaration,features,name,parent,properties
\\ \hline
--- 12494,12498 ----
&
! element declaration, features, name, parent, properties
\\ \hline
***************
*** 12502,12506 ****
&
! direction,features,interface fault,message label,parent,properties
\\ \hline
--- 12502,12506 ----
&
! direction, features, interface fault, message label, parent, properties
\\ \hline
***************
*** 12510,12514 ****
&
! direction,element declaration,features,message content model,message label,parent,properties
\\ \hline
--- 12510,12514 ----
&
! direction, element declaration, features, message content model, message label, parent, properties
\\ \hline
***************
*** 12518,12522 ****
&
! features,interface fault references,interface message references,message exchange pattern,name,parent,properties,style
\\ \hline
--- 12518,12522 ----
&
! features, interface fault references, interface message references, message exchange pattern, name, parent, properties, style
\\ \hline
***************
*** 12526,12530 ****
&
! parent,ref,value,value constraint
\\ \hline
--- 12526,12530 ----
&
! parent, ref, value, value constraint
\\ \hline
***************
*** 12534,12538 ****
&
! endpoints,features,interface,name,properties
\\ \hline
--- 12534,12538 ----
&
! endpoints, features, interface, name, properties
\\ \hline
***************
*** 12547,12679 ****
\multicolumn{1}{|c}{\bf Property}&
! \multicolumn{1}{|c|}{\bf Components}
\\ \hline
address&
! Endpoint
\\ \hline
binding&
! Endpoint
\\ \hline
binding faults&
! Binding
\\ \hline
binding operations&
! Binding
\\ \hline
bindings&
! Description
\\ \hline
direction&
! Interface Message Reference,Interface Fault Reference
\\ \hline
element declaration&
! Interface Fault,Interface Message Reference
\\ \hline
element declarations&
! Description
\\ \hline
endpoints&
! Service
\\ \hline
extended interfaces&
! Interface
\\ \hline
features&
! Interface,Interface Fault,Interface Operation,Interface Message Reference,Interface Fault Reference,,Binding,Binding Fault,Binding Operation,Service,Endpoint,Binding Message Reference,Binding Fault Reference
\\ \hline
interface&
! Binding,Service
\\ \hline
interface fault&
! Interface Fault Reference,Binding Fault
\\ \hline
interface fault references&
! Interface Operation
\\ \hline
interface faults&
! Interface
\\ \hline
interface message references&
! Interface Operation
\\ \hline
interface operations&
! Interface
\\ \hline
interfaces&
! Description
\\ \hline
message content model&
! Interface Message Reference
\\ \hline
message exchange pattern&
! Interface Operation
\\ \hline
message label&
! Interface Message Reference,Interface Fault Reference
\\ \hline
name&
! Element Declaration,Type Definition,Interface,Interface Fault,Interface Operation,Binding,Service,Endpoint,
\\ \hline
parent&
! ,Interface Fault,Interface Operation,Interface Message Reference,Interface Fault Reference,Feature,Property,Binding Fault,Binding Operation,Endpoint,Binding Message Reference,Binding Fault Reference
\\ \hline
properties&
! Interface,Interface Fault,Interface Operation,Interface Message Reference,Interface Fault Reference,,Binding,Binding Fault,Binding Operation,Service,Endpoint,Binding Message Reference,Binding Fault Reference
\\ \hline
ref&
! Feature,Property
\\ \hline
required&
! Feature
\\ \hline
services&
! Description
\\ \hline
style&
! Interface Operation
\\ \hline
type&
! Binding
\\ \hline
type definitions&
! Description
\\ \hline
value&
! Property
\\ \hline
value constraint&
! Property
\\ \hline
\end{longtable}
--- 12547,12725 ----
\multicolumn{1}{|c}{\bf Property}&
! \multicolumn{1}{|c|}{\bf Where Defined}
\\ \hline
address&
! Endpoint.address
!
\\ \hline
binding&
! Endpoint.binding
!
\\ \hline
binding faults&
! Binding.binding faults
!
\\ \hline
binding operations&
! Binding.binding operations
!
\\ \hline
bindings&
! Description.bindings
!
\\ \hline
direction&
! Interface Message Reference.direction, Interface Fault Reference.direction
!
\\ \hline
element declaration&
! Interface Fault.element declaration, Interface Message Reference.element declaration
!
\\ \hline
element declarations&
! Description.element declarations
!
\\ \hline
endpoints&
! Service.endpoints
!
\\ \hline
extended interfaces&
! Interface.extended interfaces
!
\\ \hline
features&
! Interface.features, Interface Fault.features, Interface Operation.features, Interface Message Reference.features, Interface Fault Reference.features, .features, Binding.features, Binding Fault.features, Binding Operation.features, Service.features, Endpoint.features, Binding Message Reference.
! features
! , Binding Fault Reference.
! features
!
!
\\ \hline
interface&
! Binding.interface, Service.interface
!
\\ \hline
interface fault&
! Interface Fault Reference.interface fault, Binding Fault.
! interface fault
!
!
\\ \hline
interface fault references&
! Interface Operation.interface fault references
!
\\ \hline
interface faults&
! Interface.interface faults
!
\\ \hline
interface message references&
! Interface Operation.interface message references
!
\\ \hline
interface operations&
! Interface.interface operations
!
\\ \hline
interfaces&
! Description.interfaces
!
\\ \hline
message content model&
! Interface Message Reference.message content model
!
\\ \hline
message exchange pattern&
! Interface Operation.message exchange pattern
!
\\ \hline
message label&
! Interface Message Reference.message label, Interface Fault Reference.message label
!
\\ \hline
name&
! Element Declaration.name, Type Definition.name, Interface.name, Interface Fault.name, Interface Operation.name, Binding.name, Service.name, Endpoint.name, .name
!
\\ \hline
parent&
! .parent, Interface Fault.parent, Interface Operation.parent, Interface Message Reference.parent, Interface Fault Reference.parent, Feature.parent, Property.parent, Binding Fault.parent, Binding Operation.parent, Endpoint.parent, Binding Message Reference.
! parent
! , Binding Fault Reference.
! parent
!
!
\\ \hline
properties&
! Interface.properties, Interface Fault.properties, Interface Operation.properties, Interface Message Reference.properties, Interface Fault Reference.properties, .properties, Binding.properties, Binding Fault.properties, Binding Operation.properties, Service.properties, Endpoint.properties, Binding Message Reference.
! properties
! , Binding Fault Reference.
! properties
!
!
\\ \hline
ref&
! Feature.ref, Property.ref
!
\\ \hline
required&
! Feature.required
!
\\ \hline
services&
! Description.services
!
\\ \hline
style&
! Interface Operation.style
!
\\ \hline
type&
! Binding.type
!
\\ \hline
type definitions&
! Description.type definitions
!
\\ \hline
value&
! Property.value
!
\\ \hline
value constraint&
! Property.value constraint
!
\\ \hline
\end{longtable}
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.75
retrieving revision 1.76
diff -C2 -d -r1.75 -r1.76
*** wsdl20-primer.html 22 Jun 2005 14:24:26 -0000 1.75
--- wsdl20-primer.html 22 Jun 2005 14:35:01 -0000 1.76
***************
*** 97,101 ****
<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="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br>4. <a href="#more-types">More on Message Types</a><br>5. <a href="#more-interfaces">More on Interfaces</a><br>6. <a href="#more-bindings">More on Bindings</a><br>7. <a href="#advanced-topic_ii">Advanced Topics</a><br>8. <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="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br> 2.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br> 2.2 <a href="#basics-getting-started">Getting Started: Defining a WSDL 2.0 Target Namespace</a><br> 2.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br> 2.3 <a href="#basics-types">Defining Message Types</a><br> 2.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br> 2.4 <a href="#bascs-interface">Defining an Interface</a><br> 2.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br> 2.5 <a href="#basics-binding">Defining a Binding</a><br> 2.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br> 2.6 <a href="#basics-service">Defining a Service</a><br> 2.6.1 <a href="#example-initial-service-explanation">Explanation of Example</a><br> 2.7 <a href="#basics-documentation">Documenting the Service</a><br> 2.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br>3. <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br> 3.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br> &nbs;3.2 <a href="#wsdl-schema">WSDL 2.0 Schema and Element Ordering</a><br> 3.3 <a href="#component-model">WSDL 2.0 Component Model</a><br>4. <a href="#more-types">More on Message Types</a><br> 4.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br> 4.2 <a href="#more-types-schema-import">Importing XML Schema</a><br> 4.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br>5. <a href="#more-interfaces">More on Interfaces</a><br> 5.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br> 5.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br> 5.3 <a href="#more-interfaces-faults">Interface Faults</a><br> 5.4 <a href="#more-interfaces-operations">Interface Operations</a><br> 5.4.1 <a href="#more-interfaces-opattr">Operation Attributes</a><br> 5.4.2 <a href="#N10922">Operation Message References</a><br> 5.4.2.1 <a href="#N1093F">The messageLabel Attribute</a><br> 5.4.2.2 <a href="#N10957">The element Attribute</a><br> 5.4.2.3 <a href="#N109A8">Multiple infault or outfault Elements</a><br> 5.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br>6. <a href="#more-bindings">More on Bindings</a><br> 6.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br> 6.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br> 6.3 <a href="#more-bindings-faults">Binding Faults</a><br> .4 <a href="#bindingOperations">Binding Operations</a><br> 6.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br> 6.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br> 6.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br> 6.6.1 <a href="#N10B65">Explanation of
! Example</a><br> 6.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>7. <a href="#advanced-topic_ii">Advanced Topics</a><br> 7.1 <a href="#adv-extensibility">Extensibility</a><br> 7.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br> 7.2 <a href="#adv-FP">Features and Properties</a><br> 7.2.1 <a href="#adv-FP-soap-modules">SOAP Modules</a><br> 7.2.2 <a href="#adv-FP-abstract-features">Abstract Features</a><br> 7.2.3 <a href="#adv-fp-properties">Properties</a><br> 7.3 <a href="#adv-MEP">Defining New MEPs</a><br> 7.3.1 <a href="#challenge-confirm">Confirmed Challenge</a><br> 7.4 <a href="#adv-import-and-athoring">Import mechanism and authoring style</a><br> 7.5 <a href="#adv-multiple-docs-describing-same-service">Multiple Interfaces for the Same Service</a><br> 7.6 <a href="#adv-versioning">Web Service Versioning</a><br> 7.6.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br> 7.6.2 <a href="#adv-versioning-big-bang">Big Bang</a><br> 7.6.3 <a href="#ad-versioing-migration">Evolving a Service</a><br> 7.6.4 <a href="#adv-versioning-combined">Combined Approaches</a><br> 7.7 <a href="#adv-MTOM">MTOM Support</a><br> 7.8 <a href="#adv-RPCstyle">RPC Style</a><br> 7.9 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br> 7.10 <a href="#adv-service-refereces">Describing Web Service Messages That Refer to Other Web Services</a><br> 7.10.1 <a href="#reservationDetails">The Reservation Details Web Service</a><br> 7.10.2 <a href="#reservationList">The Reservation List Web Service</a><br> 7.10.3 <a href="#reservationDetails_HTTP">Reservation Details Web Service Using HTTP Transfer</a><br> 7.10.4 <a href="#reservationList_HTTP_GET">Reservation List Web Service Using HTTP GET</a><br> 7.11 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br> 7.11.1 <a href="#N111BE">Schemas in Imported Documents</a><br> 7.11.2 <a href="#N11249">Multiple Inline Schemas in One Document</a><br> 7.11.3 <a href="#adv-schema-locaton">The schemaLocation Attribute</a><br> 7.11.3.1 <a href="#N112A9">Using the id Attribute to Identify Inline
Schemas</a><br> 7.12 <a href="#adv-rdf-mapping">Mapping to RDF and Semantic Web</a><br> 7.12.1 <a href="#adv-rdf-rep-wsdl">RDF Representation of WSDL 2.0</a><br> 7.13 <a href="#adv-notes-on-uris">Notes on URIs</a><br> 7.13.1 <a href="#adv-namespaces-and-schema-locations">XML Namespaces and Schema Locations</a><br> 7.13.2 <a href="#adv-relative-uris">Relative URIs</a><br> 7.13.3 <a href="#adv-generating-uris">Generating Temporary URIs</a><br>8. <a href="#References">References</a><br> 8.1 <a href="#Normative-References">Normative References</a><br> 8.2 <a href="#Informative-References">Informative References</a><br></p>
<h3><a id="appendix" name="appendix">Appendix</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br></p></div><hr><div class="body">
--- 97,101 ----
<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="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br>4. <a href="#more-types">More on Message Types</a><br>5. <a href="#more-interfaces">More on Interfaces</a><br>6. <a href="#more-bindings">More on Bindings</a><br>7. <a href="#advanced-topic_ii">Advanced Topics</a><br>8. <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="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br> 2.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br> 2.2 <a href="#basics-getting-started">Getting Started: Defining a WSDL 2.0 Target Namespace</a><br> 2.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br> 2.3 <a href="#basics-types">Defining Message Types</a><br> 2.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br> 2.4 <a href="#bascs-interface">Defining an Interface</a><br> 2.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br> 2.5 <a href="#basics-binding">Defining a Binding</a><br> 2.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br> 2.6 <a href="#basics-service">Defining a Service</a><br> 2.6.1 <a href="#example-initial-service-explanation">Explanation of Example</a><br> 2.7 <a href="#basics-documentation">Documenting the Service</a><br> 2.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br>3. <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br> 3.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br> &nbs;3.2 <a href="#wsdl-schema">WSDL 2.0 Schema and Element Ordering</a><br> 3.3 <a href="#component-model">WSDL 2.0 Component Model</a><br>4. <a href="#more-types">More on Message Types</a><br> 4.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br> 4.2 <a href="#more-types-schema-import">Importing XML Schema</a><br> 4.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br>5. <a href="#more-interfaces">More on Interfaces</a><br> 5.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br> 5.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br> 5.3 <a href="#more-interfaces-faults">Interface Faults</a><br> 5.4 <a href="#more-interfaces-operations">Interface Operations</a><br> 5.4.1 <a href="#more-interfaces-opattr">Operation Attributes</a><br> 5.4.2 <a href="#N10922">Operation Message References</a><br> 5.4.2.1 <a href="#N1093F">The messageLabel Attribute</a><br> 5.4.2.2 <a href="#N10957">The element Attribute</a><br> 5.4.2.3 <a href="#N109A8">Multiple infault or outfault Elements</a><br> 5.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br>6. <a href="#more-bindings">More on Bindings</a><br> 6.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br> 6.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br> 6.3 <a href="#more-bindings-faults">Binding Faults</a><br> .4 <a href="#bindingOperations">Binding Operations</a><br> 6.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br> 6.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br> 6.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br> 6.6.1 <a href="#N10B65">Explanation of
! Example</a><br> 6.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>7. <a href="#advanced-topic_ii">Advanced Topics</a><br> 7.1 <a href="#adv-extensibility">Extensibility</a><br> 7.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br> 7.2 <a href="#adv-FP">Features and Properties</a><br> 7.2.1 <a href="#adv-FP-soap-modules">SOAP Modules</a><br> 7.2.2 <a href="#adv-FP-abstract-features">Abstract Features</a><br> 7.2.3 <a href="#adv-fp-properties">Properties</a><br> 7.3 <a href="#adv-MEP">Defining New MEPs</a><br> 7.3.1 <a href="#challenge-confirm">Confirmed Challenge</a><br> 7.4 <a href="#adv-import-and-athoring">Import mechanism and authoring style</a><br> 7.5 <a href="#adv-multiple-docs-describing-same-service">Multiple Interfaces for the Same Service</a><br> 7.6 <a href="#adv-versioning">Web Service Versioning</a><br> 7.6.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br> 7.6.2 <a href="#adv-versioning-big-bang">Big Bang</a><br> 7.6.3 <a href="#ad-versioing-migration">Evolving a Service</a><br> 7.6.4 <a href="#adv-versioning-combined">Combined Approaches</a><br> 7.7 <a href="#adv-MTOM">MTOM Support</a><br> 7.8 <a href="#adv-RPCstyle">RPC Style</a><br> 7.9 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br> 7.10 <a href="#adv-service-refereces">Describing Web Service Messages That Refer to Other Web Services</a><br> 7.10.1 <a href="#reservationDetails">The Reservation Details Web Service</a><br> 7.10.2 <a href="#reservationList">The Reservation List Web Service</a><br> 7.10.3 <a href="#reservationDetails_HTTP">Reservation Details Web Service Using HTTP Transfer</a><br> 7.10.4 <a href="#reservationList_HTTP_GET">Reservation List Web Service Using HTTP GET</a><br> 7.11 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br> 7.11.1 <a href="#N111D0">Schemas in Imported Documents</a><br> 7.11.2 <a href="#N1125B">Multiple Inline Schemas in One Document</a><br> 7.11.3 <a href="#adv-schema-locaton">The schemaLocation Attribute</a><br> 7.11.3.1 <a href="#N112BB">Using the id Attribute to Identify Inline
Schemas</a><br> 7.12 <a href="#adv-rdf-mapping">Mapping to RDF and Semantic Web</a><br> 7.12.1 <a href="#adv-rdf-rep-wsdl">RDF Representation of WSDL 2.0</a><br> 7.13 <a href="#adv-notes-on-uris">Notes on URIs</a><br> 7.13.1 <a href="#adv-namespaces-and-schema-locations">XML Namespaces and Schema Locations</a><br> 7.13.2 <a href="#adv-relative-uris">Relative URIs</a><br> 7.13.3 <a href="#adv-generating-uris">Generating Temporary URIs</a><br>8. <a href="#References">References</a><br> 8.1 <a href="#Normative-References">Normative References</a><br> 8.2 <a href="#Informative-References">Informative References</a><br></p>
<h3><a id="appendix" name="appendix">Appendix</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br></p></div><hr><div class="body">
***************
*** 1433,1436 ****
--- 1433,1439 ----
<dt class="label"><code>wsdlx:safe="true" </code></dt><dd><p> on the bound <code>interface operation </code>. When the above two items are not explicitly set, and when the bound interface operation is marked safe, the HTTP Binding will by default set the method to GET.</p></dd>
+
+
+ </dl><p></p></li></ul>
<p>For example, in the GreatH interface definition shown in <a href="#example-initial-interface">Example 2-4</a>, the wsdlx:safe attribute is set to "true". The HTTP binding definition in <a href="#example-bindings-http">Example 6-2</a> may take advantage of that and be simplified as below and still have the http method set to GET by default: </p>
***************
*** 1454,1460 ****
</div>
-
-
- </dl><p></p></li></ul>
</div></div>
--- 1457,1460 ----
***************
*** 2246,2273 ****
<p>As explained in <a href="#more-interfaces-op-attr"><b>5.4.1 Operation Attributes</b></a>, when XSD is used as the type system, a few special tokens can be used for the <code>element</code> attributes. Uniquely identifying a message may become very difficult when:
! <ul>
! <li>
! any of these input elements within an interface has a value of “#any”; or
! </li>
! <li>
! more than one of these input elements (see below) has a value of “#none”; or
! </li>
! <li>
! the qualified names of the global element declarations that are specified as input elements are NOT unique when considered together.
! </li>
! </ul>
</p>
! <p>If any of the three cases above arise, then one of the following two alternatives can be used within the context of a single WSDL service by WSDL authors: </p>
! <ul>
! <li>
! Feature. The service or the interface element contains a Feature element declaration, having a required attribute with a value of true. The feature unambiguously identifies the mechanism that a message sender is required to support in order to enable the message recipient to unambiguously determine the message received.
! </li>
! <li>
! Extension. The interface element contains an extension element (i.e., an element that is not in the http://www.w3.org/2005/05/wsdl namespace), having a wsdl:required attribute with a value of "true". The extension element unambiguously identifies the mechanism that a message sender is required to support in order to enable the message recipient to unambiguously determine the message received.
! </li>
! </ul>
! <p>In addition, WS-Addressing [WS-Addressing] specification already provides a disambiguation mechanism. It defines a required [action] property whose value is always present in a message delivery. The value of the action property can be used to disambiguate the message by the receiver and there is a well defined way to associate actions to messages in WS-Addressing specifications. Further, WS-Addressing also provides an appropriate default action value that identifies each message uniquely. </p>
--- 2246,2310 ----
<p>As explained in <a href="#more-interfaces-op-attr"><b>5.4.1 Operation Attributes</b></a>, when XSD is used as the type system, a few special tokens can be used for the <code>element</code> attributes. Uniquely identifying a message may become very difficult when:
! <ul>
! <li>
! <p>
! any of these input elements within an interface has a value
! of “#any”; or
! </p>
! </li>
! <li>
! <p>
! more than one of these input elements (see below) has a
! value of “#none”; or
! </p>
! </li>
! <li>
! <p>
! the qualified names of the global element declarations that
! are specified as input elements are NOT unique when
! considered together.
! </p>
! </li>
! </ul>
</p>
! <p>
! If any of the three cases above arise, then one of
! the following two alternatives can be used within
! the context of a single WSDL service by WSDL
! authors:
! </p>
! <ul>
! <li>
! <p>
! <em>Feature.</em>
! The service or the interface element
! contains a Feature element declaration,
! having a required attribute with a value of
! true. The feature unambiguously identifies
! the mechanism that a message sender is
! required to support in order to enable the
! message recipient to unambiguously determine
! the message received.
! </p>
! </li>
! <li>
! <p>
! <em>Extension.</em>
! The interface element contains an extension
! element (i.e., an element that is not in the
! http://www.w3.org/2005/05/wsdl namespace),
! having a wsdl:required attribute with a
! value of "true". The extension element
! unambiguously identifies the mechanism that
! a message sender is required to support in
! order to enable the message recipient to
! unambiguously determine the message
! received.
! </p>
! </li>
! </ul>
! <p>In addition, WS-Addressing [WS-Addressing] specification already provides a disambiguation mechanism. It defines a required [action] property whose value is always present in a message delivery. The value of the action property can be used to disambiguate the message by the receiver and there is a well defined way to associate actions to messages in WS-Addressing specifications. Further, WS-Addressing also provides an appropriate default action value that identifies each message uniquely. </p>
***************
*** 2987,2991 ****
<div class="div3">
! <h4><a name="N111BE"></a>7.11.1 Schemas in Imported Documents</h4>
<p>
In this example, we consider some GreatH Hotel
--- 3024,3028 ----
<div class="div3">
! <h4><a name="N111D0"></a>7.11.1 Schemas in Imported Documents</h4>
<p>
In this example, we consider some GreatH Hotel
***************
*** 3194,3198 ****
<div class="div3">
! <h4><a name="N11249"></a>7.11.2 Multiple Inline Schemas in One Document</h4>
<p>
A WSDL 2.0 document may define multiple inline
--- 3231,3235 ----
<div class="div3">
! <h4><a name="N1125B"></a>7.11.2 Multiple Inline Schemas in One Document</h4>
<p>
A WSDL 2.0 document may define multiple inline
***************
*** 3328,3332 ****
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="N112A9"></a>7.11.3.1 Using the id Attribute to Identify Inline
Schemas</h5><p>
<a href="#schemaIds.wsdl">Example 7-29</a>
--- 3365,3369 ----
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="N112BB"></a>7.11.3.1 Using the id Attribute to Identify Inline
Schemas</h5><p>
<a href="#schemaIds.wsdl">Example 7-29</a>
***************
*** 3795,3798 ****
--- 3832,3836 ----
<dt class="label"><a name="rdf"></a>[RDF] </dt><dd>
+
<cite><a href="http://www.w3.org/TR/rdf-concepts/">Resource Description Framework (RDF): Concepts and Abstract Syntax</a></cite>, Graham Klyne, Jeremy J. Carroll, Editors. W3C Recommendation, 10 February 2004. Available at http://www.w3.org/TR/rdf-concepts/
</dd>
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.103
retrieving revision 1.104
diff -C2 -d -r1.103 -r1.104
*** wsdl20-primer.xml 17 Jun 2005 23:32:32 -0000 1.103
--- wsdl20-primer.xml 22 Jun 2005 14:35:01 -0000 1.104
***************
*** 1374,1377 ****
--- 1374,1380 ----
<gitem><label><code>wsdlx:safe="true" </code></label><def><p> on the bound <code>interface operation </code>. When the above two items are not explicitly set, and when the bound interface operation is marked safe, the HTTP Binding will by default set the method to GET.</p></def>
+ </gitem>
+
+ </glist></p></item></ulist>
<p>For example, in the GreatH interface definition shown in <specref ref= "example-initial-interface"/>, the wsdlx:safe attribute is set to "true". The HTTP binding definition in <specref ref= "example-bindings-http"/> may take advantage of that and be simplified as below and still have the http method set to GET by default: </p>
***************
*** 1395,1401 ****
</example>
- </gitem>
-
- </glist></p></item></ulist>
</div2></div1>
--- 1398,1401 ----
***************
*** 2172,2199 ****
<p>As explained in <specref ref= "more-interfaces-op-attr"/>, when XSD is used as the type system, a few special tokens can be used for the <code>element</code> attributes. Uniquely identifying a message may become very difficult when:
! <ulist>
! <item>
! any of these input elements within an interface has a value of “#any”; or
! </item>
! <item>
! more than one of these input elements (see below) has a value of “#none”; or
! </item>
! <item>
! the qualified names of the global element declarations that are specified as input elements are NOT unique when considered together.
! </item>
! </ulist>
</p>
! <p>If any of the three cases above arise, then one of the following two alternatives can be used within the context of a single WSDL service by WSDL authors: </p>
! <ulist>
! <item>
! <emphasis>Feature</emphasis>. The service or the interface element contains a Feature element declaration, having a required attribute with a value of true. The feature unambiguously identifies the mechanism that a message sender is required to support in order to enable the message recipient to unambiguously determine the message received.
! </item>
! <item>
! Extension. The interface element contains an extension element (i.e., an element that is not in the http://www.w3.org/2005/05/wsdl namespace), having a wsdl:required attribute with a value of "true". The extension element unambiguously identifies the mechanism that a message sender is required to support in order to enable the message recipient to unambiguously determine the message received.
! </item>
! </ulist>
! <p>In addition, WS-Addressing [WS-Addressing] specification already provides a disambiguation mechanism. It defines a required [action] property whose value is always present in a message delivery. The value of the action property can be used to disambiguate the message by the receiver and there is a well defined way to associate actions to messages in WS-Addressing specifications. Further, WS-Addressing also provides an appropriate default action value that identifies each message uniquely. </p>
<!-- old text for this section, replaced by contribution from Umit
--- 2172,2236 ----
<p>As explained in <specref ref= "more-interfaces-op-attr"/>, when XSD is used as the type system, a few special tokens can be used for the <code>element</code> attributes. Uniquely identifying a message may become very difficult when:
! <ulist>
! <item>
! <p>
! any of these input elements within an interface has a value
! of “#any”; or
! </p>
! </item>
! <item>
! <p>
! more than one of these input elements (see below) has a
! value of “#none”; or
! </p>
! </item>
! <item>
! <p>
! the qualified names of the global element declarations that
! are specified as input elements are NOT unique when
! considered together.
! </p>
! </item>
! </ulist>
</p>
! <p>
! If any of the three cases above arise, then one of
! the following two alternatives can be used within
! the context of a single WSDL service by WSDL
! authors:
! </p>
! <ulist>
! <item>
! <p>
! <emph>Feature.</emph>
! The service or the interface element
! contains a Feature element declaration,
! having a required attribute with a value of
! true. The feature unambiguously identifies
! the mechanism that a message sender is
! required to support in order to enable the
! message recipient to unambiguously determine
! the message received.
! </p>
! </item>
! <item>
! <p>
! <emph>Extension.</emph>
! The interface element contains an extension
! element (i.e., an element that is not in the
! http://www.w3.org/2005/05/wsdl namespace),
! having a wsdl:required attribute with a
! value of "true". The extension element
! unambiguously identifies the mechanism that
! a message sender is required to support in
! order to enable the message recipient to
! unambiguously determine the message
! received.
! </p>
! </item>
! </ulist>
! <p>In addition, WS-Addressing [WS-Addressing] specification already provides a disambiguation mechanism. It defines a required [action] property whose value is always present in a message delivery. The value of the action property can be used to disambiguate the message by the receiver and there is a well defined way to associate actions to messages in WS-Addressing specifications. Further, WS-Addressing also provides an appropriate default action value that identifies each message uniquely. </p>
<!-- old text for this section, replaced by contribution from Umit
Received on Wednesday, 22 June 2005 14:35:12 UTC