W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > April 2005

2002/ws/desc/wsdl20 wsdl20.html,1.165,1.166 wsdl20.xml,1.195,1.196 wsdl20.xsd,1.22,1.23

From: Sanjiva Weerawarana via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 03 Apr 2005 23:45:11 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1DIEmF-0000I8-Lc@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv1082

Modified Files:
	wsdl20.html wsdl20.xml wsdl20.xsd 
Log Message:
dealt with many editorial AIs; see email

Index: wsdl20.xsd
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xsd,v
retrieving revision 1.22
retrieving revision 1.23
diff -C2 -d -r1.22 -r1.23
*** wsdl20.xsd	1 Mar 2005 19:58:43 -0000	1.22
--- wsdl20.xsd	3 Apr 2005 23:45:09 -0000	1.23
***************
*** 268,272 ****
          </xs:sequence>
          <xs:attribute name='uri' type='xs:QName' use='required' />
-         <xs:attribute name='required' type='xs:boolean' use='optional' />
        </xs:extension>
      </xs:complexContent>
--- 268,271 ----

Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.165
retrieving revision 1.166
diff -C2 -d -r1.165 -r1.166
*** wsdl20.html	23 Mar 2005 03:40:09 -0000	1.165
--- wsdl20.html	3 Apr 2005 23:45:08 -0000	1.166
***************
*** 81,85 ****
  <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-uri-references">URI References for WSDL Components</a> (Non-Normative)<br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>E. <a href="#other-schemalang">Examples of Specifications of Extension Elements for Alternative Schem
  Language Support.</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</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="#intro">Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#intro_ws">Web Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#meaning">The Meaning of a Service Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.3 <a href="#notation">Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.4 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.5 <a href="#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.6 <a href="#znotation"Z Notation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.7 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.4 <a href="#terminology">WSDL Terminology</a><br>2. <a href="#component_model">Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#Description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.1 <a href="#Description_details">The Description Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
        Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#Interface">Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.1 <a href="#Interface_details">The Interface Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
  	  Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#InterfaceOperation">Interface Operation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.1 <a href="#InterfaceOperation_details">The Interface Operation Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.1.1 <a href="#InterfaceOperationStyle">Operation Style</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2 <a href="#InterfaceOperation_XMLRep">XML Representation of Interface Operation Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2.1 <a href="#Interfaceoperation_name_attribute">name attribute information item with operation [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2.2 <a href="#Interfaceoperation_pattern_attribute">pattern attribute information item with operation [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2.3 <a href="#InterfaceOpertion_style_attribute">style attribute information item with operation [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2.4 <a href="#InterfaceOperation_safe_attribute">safe attribute information item with operation [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.3 <a href="#InterfaceOperation_Mapping">Mapping Interface Operation's XML Representation to
--- 81,85 ----
  <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-uri-references">URI References for WSDL Components</a> (Non-Normative)<br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>E. <a href="#other-schemalang">Examples of Specifications of Extension Elements for Alternative Schem
  Language Support.</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</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="#intro">Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#intro_ws">Web Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#meaning">The Meaning of a Service Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.3 <a href="#notation">Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.4 <a href="#terminology">Terms Used in This Specification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.5 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.6 <a href="#wsdlcomponentmodelpropertis">WSDL Component Model Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.7 <a href="#znotation">Z Notation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.3.8 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br>2. <a href="#component_model">Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#Description">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.1 <a href="#Description_details">The Description Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
        Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#Interface">Interface</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.1 <a href="#Interface_details">The Interface Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
[...1339 lines suppressed...]
        <th rowspan="1" colspan="1">Description</th>
      </tr>
! 
!     <tr>
!     	<td rowspan="1" colspan="1">20050331</td>
!     	<td rowspan="1" colspan="1">AGR</td>
!     	<td rowspan="1" colspan="1">
!     		<a href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC113">
!     			LC113
!     		</a>: In the Feature and Property Composition sections, the
!     		in-scope components for Binding Operation, Binding Fault,
!     		Binding Message Reference, and Binding Fault Reference
!     		should include those of the corresponding Interface
!     		Operation, Interface Fault, ,Message Reference, and Fault
!     		Reference, respectively. Also updated specification references use Part 2: Adjuncts, and corrected validation errors.
!     	</td>
!     </tr>
! 
      <tr>
      	<td rowspan="1" colspan="1">20050320</td>

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.195
retrieving revision 1.196
diff -C2 -d -r1.195 -r1.196
*** wsdl20.xml	31 Mar 2005 14:43:59 -0000	1.195
--- wsdl20.xml	3 Apr 2005 23:45:08 -0000	1.196
***************
*** 1,3 ****
! <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
  <!-- $Id$ -->
  <?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl' ?>
--- 1,3 ----
! <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
  <!-- $Id$ -->
  <?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl' ?>
***************
*** 181,185 ****
  
  <p>All parts of this specification are normative, with the EXCEPTION
!    of notes, pseudo-schemas, examples, and sections explicitly marked as &ldquo;Non-Normative&rdquo;.</p>
  
  <div3 id="rfc2119keywords">
--- 181,186 ----
  
  <p>All parts of this specification are normative, with the EXCEPTION
! of notes, pseudo-schemas, examples, and sections explicitly marked as
! &ldquo;Non-Normative&rdquo;.</p>
  
  <div3 id="rfc2119keywords">
***************
*** 209,217 ****
  <head>Prefixes and Namespaces Used in This Specification</head>
          
! <p>This specification uses predefined namespace prefixes throughout; they are
!    given in the following list. Note that the choice of
!    any namespace prefix is arbitrary and not semantically significant
!    (see <bibref ref="XMLInfoSet"/>).
! </p>
     
     <glist>
--- 210,217 ----
  <head>Prefixes and Namespaces Used in This Specification</head>
          
! <p>This specification uses predefined namespace prefixes throughout;
! they are given in the following list. Note that the choice of any
! namespace prefix is arbitrary and not semantically significant (see
! <bibref ref="XMLInfoSet"/>).</p>
     
     <glist>
***************
*** 222,235 ****
        	<attval>&wsdl-ns;</attval>
  	</p>
!       	<p>
!       	A normative XML Schema <bibref ref="XMLSchemaP1"/>, <bibref
!         ref="XMLSchemaP2"/> document for the
!         <attval>&wsdl-ns;</attval> namespace can be found at <loc
!         href="&wsdl-ns;">&wsdl-ns;</loc>.  WSDL documents that do NOT
!         conform to this schema are not valid WSDL documents. WSDL
!         documents that DO conform to this schema and also conform to
!         the other constraints defined in this specification are valid
!         WSDL documents.
!         </p>
        </def>
       </gitem>
--- 222,226 ----
        	<attval>&wsdl-ns;</attval>
  	</p>
!       	<p>Defined by this specification.</p>
        </def>
       </gitem>
***************
*** 239,246 ****
  	<p><attval>&wsdl-i-ns;</attval></p>
        	<p>
!       	A normative XML Schema <bibref ref="XMLSchemaP1"/>, <bibref
!         ref="XMLSchemaP2"/> document for the
!         <attval>&wsdl-i-ns;</attval> namespace can be found at <loc
!         href="&wsdl-i-ns;">&wsdl-i-ns;</loc>. 
          </p>
        </def>
--- 230,234 ----
  	<p><attval>&wsdl-i-ns;</attval></p>
        	<p>
!       	Defined by this specification <specref ref="wsdlLocation-aii"/>.
          </p>
        </def>
***************
*** 251,264 ****
        <def>
        	<p><attval>&wsdl-rpc-ns;</attval></p>
!       	<p>
!       	A normative XML Schema <bibref ref="XMLSchemaP1"/>, <bibref
!         ref="XMLSchemaP2"/> document for the
!         <attval>&wsdl-rpc-ns;</attval> namespace can be found at <loc
!         href="&wsdl-rpc-ns;">&wsdl-rpc-ns;</loc>.  WSDL documents that
!         do NOT conform to this schema are not valid WSDL
!         documents. WSDL documents that DO conform to this schema and
!         also conform to the other constraints defined in this
!         specification are valid WSDL documents.
!         </p>
        </def>
       </gitem>
--- 239,243 ----
        <def>
        	<p><attval>&wsdl-rpc-ns;</attval></p>
!       	<p>Defined by this specification.</p>
        </def>
       </gitem>
***************
*** 315,318 ****
--- 294,316 ----
  </div3>
  
+ <div3 id="terminology">
+   <head>Terms Used in This Specification</head>
+   
+   <p>This section describes the terms and concepts introduced
+   in Part 1 of the WSDL Version 2.0 specification (this document).</p>
+ 
+   <glist>
+     <gitem>
+       <label>Actual Value</label> <def><p>As in <bibref ref="XMLSchemaP1"/>,
+   the phrase actual value is used to refer to the member of
+   the value space of the simple type definition associated
+   with an attribute information item which corresponds to
+   its normalized value. This will often be a string, but may also be
+   an integer, a boolean, a URI reference, etc.</p></def>
+     </gitem>
+   </glist>
+   
+ </div3>
+ 
  <div3 id="xmlinfosetproperties">
  <head>XML Infomation Set Properties</head>
***************
*** 406,428 ****
  </div2>
  
- <div2 id="terminology">
-   <head>WSDL Terminology</head>
-   
-   <p>This section describes the terms and concepts introduced
-   in Part 1 of the WSDL Version 2.0 specification (this document).</p>
- 
-   <glist>
-     <gitem>
-       <label>Actual Value</label> <def><p>As in <bibref ref="XMLSchemaP1"/>,
-   the phrase actual value is used to refer to the member of
-   the value space of the simple type definition associated
-   with an attribute information item which corresponds to
-   its normalized value. This will often be a string, but may also be
-   an integer, a boolean, a URI reference, etc.</p></def>
-     </gitem>
-   </glist>
-   
- </div2>
- 
  </div1>
  
--- 404,407 ----
***************
*** 1100,1112 ****
        <p>WSDL components are interfaces, bindings and services.</p>
  
!       <p>Type system components describe the constraints on a message's 
! content. By default, these constraints are expressed in terms of the 
! <bibref ref="XMLInfoSet"/>, i.e. they define the [local name], [namespace name], 
! [children] and [attributes] properties of an element information item. 
! Type systems based upon other data models are generally accommodated by 
! extensions to WSDL; see <specref ref="language-extensibility"/>.
!       In the case where they define information equivalent to that of a XML Schema
!       global element declaration, they can more simply be treated as if they were
!       such a declaration.</p>
        
        <z:notation name="ElementContentModel">
--- 1079,1096 ----
        <p>WSDL components are interfaces, bindings and services.</p>
  
!       <p>Type system components describe the constraints on a
!       message's content. By default, these constraints are expressed
!       in terms of the <bibref ref="XMLInfoSet"/>, i.e. they define the
!       [local name], [namespace name], [children] and [attributes]
!       properties of an element information item.  Type systems based
!       upon other data models are generally accommodated by extensions
!       to WSDL; see <specref ref="language-extensibility"/>.  In the
!       case where they define information equivalent to that of a XML
!       Schema global element declaration, they can more simply be
!       treated as if they were such a declaration.</p>
! 
!       <p>This specification does not define the behavior of a WSDL
!       document that uses multiple schema languages for describing type
!       system components simultaneously.</p>
        
        <z:notation name="ElementContentModel">
***************
*** 1264,1268 ****
  
           <p>Note that it is RECOMMENDED that the value of the
!          <att>targetNamespace</att> &AII; be a dereferencible
           URI and that it resolves to a WSDL document which provides
           service description information for that namespace.</p>
--- 1248,1252 ----
  
           <p>Note that it is RECOMMENDED that the value of the
!          <att>targetNamespace</att> &AII; be a dereferencable
           URI and that it resolves to a WSDL document which provides
           service description information for that namespace.</p>
***************
*** 1589,1594 ****
          related messages into operations. An operation is a sequence
          of input and output messages, and an interface is a set of
!         operations. Thus, an interface defines the design of the
!         application.</p>
  
          <p diff="chg"> An interface can optionally extend one or more other
--- 1573,1577 ----
          related messages into operations. An operation is a sequence
          of input and output messages, and an interface is a set of
!         operations.</p>
  
          <p diff="chg"> An interface can optionally extend one or more other
***************
*** 1944,1949 ****
          <head><att>styleDefault</att> &AII;</head>
  	    <p>
! 		The <att>styleDefault</att> &AII; indicates
! 		the default style used to construct the
  		{element} properties of {message references} of all
  		operations contained within the [owner]
--- 1927,1933 ----
          <head><att>styleDefault</att> &AII;</head>
  	    <p>
! 		The <att>styleDefault</att> &AII; indicates the
! 		default style (see <specref
! 		ref="InterfaceOperationStyle"/>) used to construct the
  		{element} properties of {message references} of all
  		operations contained within the [owner]
***************
*** 2923,2936 ****
              contained within. </p></item>
  
!             <item><p>{message content model} OPTIONAL. An <emph>xs:token</emph>
! 	    with one of
!             the values <emph>#any</emph>, <emph>#none</emph>, or
!             <emph>#element</emph>.  A value of <emph>#any</emph>
!             indicates that the message content is any single
!             element. A value of <emph>#none</emph> indicates there is
!             no message content. A value of <emph>#element</emph>
!             indicates that the message consists of a single element
!             described by the global element declaration reference by
!             the {element} property.</p></item>
  
              <item><p> {element} OPTIONAL. A reference to an XML element
--- 2907,2922 ----
              contained within. </p></item>
  
!             <item><p>{message content model} OPTIONAL. An
! 	    <emph>xs:token</emph> with one of the values
! 	    <emph>#any</emph>, <emph>#none</emph>, or
! 	    <emph>#element</emph>.  A value of <emph>#any</emph>
! 	    indicates that the message content is any single
! 	    element. A value of <emph>#none</emph> indicates there is
! 	    no message content. A value of <emph>#element</emph>
! 	    indicates that the message consists of a single element
! 	    described by the global element declaration referenced by
! 	    the {element} property. This property is used only when
! 	    the message is described using an XML based data
! 	    model.</p></item>
  
              <item><p> {element} OPTIONAL. A reference to an XML element
***************
*** 3530,3535 ****
  		  </tr>
  		  <tr>
! 		    <td>{fault reference}</td>
! 			<td>The actual value of the <att>ref</att> &AII;</td>
  		  </tr>
  
--- 3516,3523 ----
  		  </tr>
  		  <tr>
! 		    <td>{fault reference}</td> <td>The Interface Fault
!                     component from {faults} property of the parent
!                     Interface component whose {name} property is the
!                     actual value of the <att>ref</att> &AII;.</td>
  		  </tr>
  
***************
*** 3596,3608 ****
        between communicating parties.  Although WSDL poses no
        constraints on the potential scope of such features, examples
!       might include &ldquo;reliability&rdquo;, &ldquo;security&rdquo;, &ldquo;correlation&rdquo;, and
!       &ldquo;routing&rdquo;.  The presence of a feature component in a WSDL description 
!       indicates that the service supports the feature and may require a
!       client that interacts with the service to use that feature.
!       Each Feature is identified by its URI.</p>
  	  
  	  <p>The properties of the Feature component are as follows:</p>
  	  <ulist>
! 	    <item><p>{name} REQUIRED. An <emph>xs:anyURI</emph>. 
  	    This URI MUST be
  	    absolute as defined by <bibref ref="RFC3986"/>. This URI SHOULD be
--- 3584,3602 ----
        between communicating parties.  Although WSDL poses no
        constraints on the potential scope of such features, examples
!       might include &ldquo;reliability&rdquo;, &ldquo;security&rdquo;,
!       &ldquo;correlation&rdquo;, and &ldquo;routing&rdquo;.  The
!       presence of a feature component in a WSDL description indicates
!       that the service supports the feature and may require a client
!       that interacts with the service to use that feature.  Each
!       Feature is identified by its URI.</p>
! 
!       <p>WSDL's feature concept is derived from SOAP 1.2's abstract
!       feature concept (<bibref ref="SOAP12-PART1"/>). Thus, by
!       definition, every SOAP 1.2 abstract feature is also a WSDL
!       feature and does not have to be declared as such.</p>
  	  
  	  <p>The properties of the Feature component are as follows:</p>
  	  <ulist>
! 	    <item><p>{uri} REQUIRED. An <emph>xs:anyURI</emph>. 
  	    This URI MUST be
  	    absolute as defined by <bibref ref="RFC3986"/>. This URI SHOULD be
***************
*** 3613,3620 ****
  	     If the value of this property is <emph>true</emph>, 
           then the client MUST use the Feature that is identified
!          by the {name} URI.  Otherwise, the client MAY use the
!          Feature that is identified by the {name} URI.  In either case,
           if the client does use the Feature that is identified
!          by the {name} URI, then the client MUST obey all semantics
           implied by the definition of that Feature.</p></item>
  	  </ulist>
--- 3607,3614 ----
  	     If the value of this property is <emph>true</emph>, 
           then the client MUST use the Feature that is identified
!          by the {uri} URI.  Otherwise, the client MAY use the
!          Feature that is identified by the {uri} URI.  In either case,
           if the client does use the Feature that is identified
!          by the {uri} URI, then the client MUST obey all semantics
           implied by the definition of that Feature.</p></item>
  	  </ulist>
***************
*** 3952,3956 ****
  		  </tr>
  		  <tr>
! 		    <td>{name}</td>
  			<td>The actual value of the <att>uri</att> &AII;</td>
  		  </tr>
--- 3946,3950 ----
  		  </tr>
  		  <tr>
! 		    <td>{uri}</td>
  			<td>The actual value of the <att>uri</att> &AII;</td>
  		  </tr>
***************
*** 3975,4012 ****
        <head>The Property Component</head>
  	  
!           <p>A &ldquo;property&rdquo; in the Features and Properties architecture
!           represents a named runtime value which affects the behaviour
!           of some aspect of a Web service interaction, much like an
!           environment variable.  For example, a reliable messaging SOAP
!           module may specify a property to control the number of retries
!           in the case of network failure.  WSDL documents may specify the
!           value constraints for these properties by referring to a Schema
!           type, or by specifying a particular value.  Properties, and hence
!           property values, can be shared amongst features/bindings/modules, and
!           are named with URIs precisely to allow this type of sharing.
            </p>
  
  	  <p>The properties of the Property component are as follows:</p>
  	  <ulist>
! 	    <item><p>{name} REQUIRED. An <emph>xs:anyURI</emph>. This URI MUST be
! 	    absolute as defined by <bibref ref="RFC3986"/>. This URI SHOULD be
!          dereferenceable to a document that directly or indirectly defines
!          the meaning and use of the Property that it identifies.</p></item>
  
! 	    <item><p>{required} REQUIRED. An <emph>xs:boolean</emph> value. 
! 	     If the {required} property is <emph>true</emph>,
!          then the client MUST use the Property that is identified
!          by the {name} URI.  Otherwise, the client MAY use the
!          Property that is identified by the {name} URI.  In either case,
!          if the client does use the Property that is identified
!          by the {name} URI, then the client MUST obey all semantics
!          implied by the definition of that Property.</p></item>
! 	    <item><p>{value constraint} OPTIONAL. A reference to a type definition 
! 	    in the {type definitions} property of <specref ref='Description_details' />
! 	    constraining the value of the property, or the token <emph>#value</emph>
! 	    if the {value} property is not empty.</p></item>
!             <item><p>{value} OPTIONAL. The value of the property, an ordered list
!             of child information items, as specified by the [children] property
!             of &EII;s in <bibref ref="XMLInfoSet"/>.</p></item>
  	  </ulist>
  
--- 3969,4003 ----
        <head>The Property Component</head>
  	  
!           <p>A &ldquo;property&rdquo; in the Features and Properties
!           architecture represents a named runtime value which affects
!           the behaviour of some aspect of a Web service interaction,
!           much like an environment variable.  For example, a reliable
!           messaging SOAP module may specify a property to control the
!           number of retries in the case of network failure.  WSDL
!           documents may specify the value constraints for these
!           properties by referring to a Schema type, or by specifying a
!           particular value.  Properties, and hence property values,
!           can be shared amongst features/bindings/modules, and are
!           named with URIs precisely to allow this type of sharing.
            </p>
  
  	  <p>The properties of the Property component are as follows:</p>
  	  <ulist>
! 	    <item><p>{uri} REQUIRED. An <emph>xs:anyURI</emph>. This
! 	    URI MUST be absolute as defined by <bibref
! 	    ref="RFC3986"/>. This URI SHOULD be dereferenceable to a
! 	    document that directly or indirectly defines the meaning
! 	    and use of the Property that it identifies.</p></item>
  
! 	    <item><p>{value constraint} OPTIONAL. A reference to a
! 	    type definition in the {type definitions} property of
! 	    <specref ref='Description_details' /> constraining the
! 	    value of the property, or the token <emph>#value</emph> if
! 	    the {value} property is not empty.</p></item>
! 
!             <item><p>{value} OPTIONAL. The value of the property, an
!             ordered list of child information items, as specified by
!             the [children] property of &EII;s in <bibref
!             ref="XMLInfoSet"/>.</p></item>
  	  </ulist>
  
***************
*** 4283,4288 ****
  
  <eg xml:space="preserve">&lt;<b>property</b>
!       uri=&quot;<emph>xs:anyURI</emph>&quot; 
!       required=&quot;<emph>xs:boolean</emph>&quot;? &gt;
    &lt;documentation /&gt;?
    [ &lt;value /&gt; | &lt;constraint /&gt; ]?
--- 4274,4278 ----
  
  <eg xml:space="preserve">&lt;<b>property</b>
!       uri=&quot;<emph>xs:anyURI</emph>&quot; &gt;
    &lt;documentation /&gt;?
    [ &lt;value /&gt; | &lt;constraint /&gt; ]?
***************
*** 4305,4315 ****
                <specref ref="Property_uri_attribute"/>.</p>
  		  	</item>
- 		  <item>
-               <p>
- 		  An OPTIONAL <att>required</att> &AII; as described
- 		  below in <specref
- 		  ref="Property_required_attribute"/>.
- 		  </p>
- 		</item>
  			<item>
  		      <p>
--- 4295,4298 ----
***************
*** 4370,4392 ****
        </div4>
  
-       <div4 id="Property_required_attribute">
-         <head><att>required</att> &AII; with <el>property</el> [owner]</head>
- 		<p>
- 		The <att>required</att> &AII; specifies whether use of the property
- 		is mandatory or optional.
- 		</p>
- 	    <p>
- 		The <att>required</att> &AII; has the following
- 		Infoset properties:
- 		</p>
- 		<ulist>
- 		  <item><p>A [local name] of <att>required</att></p></item>
- 		  <item><p>A [namespace name] which has no value</p></item>
- 		</ulist>
- 		<p>
- 		The type of the <att>required</att> &AII; is <att>xs:boolean</att>.
- 		</p>
-       </div4>
- 
        <div4 id="Property_value_element">
          <head><att>value</att> &EII; with <el>property</el> [parent]</head>
--- 4353,4356 ----
***************
*** 4460,4471 ****
  		  </tr>
  		  <tr>
! 		    <td>{name}</td>
  			<td>The actual value of the <att>uri</att> &AII;.</td>
  		  </tr>
  		  <tr>
- 		    <td>{required}</td> <td>The actual value of the
- 		    <att>required</att> &AII; if present, otherwise <attval>false</attval>.</td>
- 		  </tr>
- 		  <tr>
  		    <td>{value constraint}</td> <td>If the
  		    <el>constraint</el> &EII; is present, the type
--- 4424,4431 ----
  		  </tr>
  		  <tr>
! 		    <td>{uri}</td>
  			<td>The actual value of the <att>uri</att> &AII;.</td>
  		  </tr>
  		  <tr>
  		    <td>{value constraint}</td> <td>If the
  		    <el>constraint</el> &EII; is present, the type
***************
*** 6658,6665 ****
      Qualified Name, or QName, of the component being referred
      to. QNames are a tuple, consisting of two parts; a namespace name
!     and a local name. For example, in the case of an Interface
!     component, the namespace name is represented by the {namespace
!     name} property and the local name is represented by the {name}
!     property. </p>
  
      <p> QName references are resolved by looking in the appropriate
--- 6618,6625 ----
      Qualified Name, or QName, of the component being referred
      to. QNames are a tuple, consisting of two parts; a namespace name
!     and a local name. The namespace name for a component is
!     represented by the value of the &AII; <attr>targetNamespace</attr> of
!     the parent <el>description</el> &EII; and the local name is
!     represented by the {name} property of the component.</p>
  
      <p> QName references are resolved by looking in the appropriate
***************
*** 6726,6730 ****
        <note>
          <p>
! Support for the W3C XML Schema Description Language
    <bibref ref='XMLSchemaP1'/>,<bibref ref='XMLSchemaP2' /> is required
    of all WSDL processors.  
--- 6686,6690 ----
        <note>
          <p>
! Support for the W3C XML Schema 
    <bibref ref='XMLSchemaP1'/>,<bibref ref='XMLSchemaP2' /> is required
    of all WSDL processors.  
***************
*** 6791,6796 ****
  <p>
  XML Schema MAY be used as the schema language via import or
! embedding. Each method defines a different &EII; for use within
! a <el>types</el> &EII;.  All WSDL processors MUST support XML Schema
  type definitions.
  </p>
--- 6751,6755 ----
  <p>
  XML Schema MAY be used as the schema language via import or
! embedding. All WSDL processors MUST support XML Schema
  type definitions.
  </p>
***************
*** 6863,6872 ****
  <head>Importing XML Schema</head>
  
! <p>Importing an XML Schema uses the syntax and semantics of the <el>xs:import</el>
! mechanism defined by XML Schema <bibref ref='XMLSchemaP1'/>,<bibref ref='XMLSchemaP2' />,
! with some additional restrictions. The schema components defined in the imported
! schema are available for reference by QName (see <specref ref='qnameres' />).
! Note that only components in the imported namespace are
! available for reference in the WSDL document.</p>
  
  <p>A child &EII; of the
--- 6822,6832 ----
  <head>Importing XML Schema</head>
  
! <p>Importing an XML Schema uses the syntax and semantics of the
! <el>xs:import</el> mechanism defined by XML Schema <bibref
! ref='XMLSchemaP1'/>,<bibref ref='XMLSchemaP2' />, with some additional
! restrictions. The schema components defined in the imported namespace are
! available for reference by QName (see <specref ref='qnameres' />).
! Note that only components in the imported namespace are available for
! reference in the WSDL document.</p>
  
  <p>A child &EII; of the
***************
*** 6928,6946 ****
  
  <p>Embedding an XML schema uses the existing top-level
! <el>xs:schema</el> &EII; defined by XML Schema <bibref ref='XMLSchemaP1'/>.  
! It may be viewed as simply cutting and pasting an
! existing, stand-alone schema, to a location inside the types &EII;.</p>
! <p>The schema components defined in the embedded schema are available to
! WSDL for reference by QName (see <specref ref='qnameres' />). Note
! that only components in the namespace corresponding
! to the targetNamespace attribute of the embedded schema
! element are available for reference in the WSDL document.</p>
! <p> Similarly, components defined in an embedded XML schema are NOT automatically
! made available to a WSDL description that imported (using <el>wsdl:import</el>)
! the description that embeds the schema (see <specref ref="imports"/> for more details).
! For this reason, it is recommended that XML schema documents intended
! to be shared across several WSDL descriptions be placed in separate
! documents and imported using <el>xs:import</el>, rather than
! embedded inside a WSDL document.</p>
  <p>Inside an embedded XML schema, the <el>xs:import</el> and <el>xs:include</el>
  &EII;s MAY be used to refer to other XML schemas embedded in the same
--- 6888,6911 ----
  
  <p>Embedding an XML schema uses the existing top-level
! <el>xs:schema</el> &EII; defined by XML Schema <bibref
! ref='XMLSchemaP1'/>.  It may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types &EII;.</p>
! 
! <p>The schema components defined and declared in the embedded schema
! document are available to WSDL for reference by QName (see <specref
! ref='qnameres'/>). Note that only components defined and declared in
! the schema itself and components included by it via xs:include are
! available to WSDL.  Specifically components that the schema imports
! via xs:import are NOT available to WSDL.</p>
! 
! <p> Similarly, components defined in an embedded XML schema are NOT
! automatically made available to a WSDL description that imported
! (using <el>wsdl:import</el>) the description that embeds the schema
! (see <specref ref="imports"/> for more details).  For this reason, it
! is recommended that XML schema documents intended to be shared across
! several WSDL descriptions be placed in separate documents and imported
! using <el>xs:import</el>, rather than embedded inside a WSDL
! document.</p>
! 
  <p>Inside an embedded XML schema, the <el>xs:import</el> and <el>xs:include</el>
  &EII;s MAY be used to refer to other XML schemas embedded in the same
***************
*** 7206,7210 ****
  <el>xs:import</el> statement to that purpose.</p>
  
! <p>This specification DOES NOT preclude repeating the <el>import</el>
  &EII; for the same value of the <att>namespace</att> &AII; as long as
  they provide different values for the <att>location</att>
--- 7171,7175 ----
  <el>xs:import</el> statement to that purpose.</p>
  
! <p>This specification does not preclude repeating the <el>import</el>
  &EII; for the same value of the <att>namespace</att> &AII; as long as
  they provide different values for the <att>location</att>
***************
*** 7580,7583 ****
--- 7545,7552 ----
      semantics.</p>
  
+     <p>Extensibility elements SHOULD NOT alter the existing semantics
+     in ways that are likely to confuse users.</p>
+ 
+ 
  <note><p>However, once the client and service both know that an optional feature
  has been engaged (because the service has received a message explicitly
***************
*** 7590,7597 ****
  decrypted).</p></note>
  
-       <note><p>Authors of extensibility elements should avoid
-       altering the existing semantics in ways that are likely to
-       confuse users.</p></note>
- 
        <note><p>Authors of extensibility elements should make sure to
        include in the specification for such elements a clear statement
--- 7559,7562 ----
***************
*** 7621,7624 ****
--- 7586,7594 ----
    children/descendants.</p>
  
+   <p>A normative XML Schema <bibref ref="XMLSchemaP1"/>, <bibref
+   ref="XMLSchemaP2"/> document for the <attval>&wsdl-i-ns;</attval>
+   namespace can be found at <loc href="&wsdl-i-ns;">&wsdl-i-ns;</loc>.
+   </p>
+ 
      <div2 id='wsdlLocation-aii'>
        <head><att>wsdli:wsdlLocation</att> &AII;</head>
***************
*** 7660,7673 ****
      <p>An &EII; whose namespace name is <attval>&wsdl-ns;</attval> and
      whose local part is <el>description</el> conforms to this
!     specification if it is valid coording to the XML Schema for that element as
!     defined by this specification (<loc href="&wsdl-ns;">&wsdl-ns;</loc>)
!     and additionally adheres to all the constraints contained in this specification
!     family and conforms to the specifications of any extensions contained in it.</p>
  
      <p>Note that the WSDL language is defined in terms of the
!     component model defined by this specification. As such, it is
!     explicitly NOT a conformance requirement to be able to process
!     documents encoded in a particular version of XML, in particular XML
!     1.1 <bibref ref="XML11"/>.</p>
  
    </div2>
--- 7630,7646 ----
      <p>An &EII; whose namespace name is <attval>&wsdl-ns;</attval> and
      whose local part is <el>description</el> conforms to this
!     specification if it is valid acoording to the XML Schema for that
!     element as defined by this specification (<loc
!     href="&wsdl-ns;/wsdl20.xsd">&wsdl-ns;/wsdl20.xsd</loc>) and
!     additionally adheres to all the constraints contained in this
!     specification family and conforms to the specifications of any
!     extensions contained in it.</p>
  
      <p>Note that the WSDL language is defined in terms of the
!     component model defined by this specification.  As such, it is not
!     a requirement to support any particular serialization of the
!     normative XML Infoset mapping of the component model. For
!     instance, a conformant processor MAY only support XML 1.0 and not
!     XML 1.1 <bibref ref="XML11"/>.</p>
  
    </div2>
***************
*** 7701,7817 ****
    </div2>
  
-   <div2 id="processor">
-   <head>Processor Conformance</head>
- 
- 	<p>
- 	This section defines a class of conformant WSDL processors that
- 	are intended to act on behalf of a party that wishes to make use
- 	of a Web service (i.e., the requester entity or requester agent), 
- 	rather than the party that implements the
- 	Web service (i.e., the provider entity or provider agent).
- 	</p>
- 
- 	<p>
- 	An extension element is said to be <emph>processed</emph> if the
- 	WSDL processor decides (through whatever means) that its parent
- 	(an &EII; in the <attval>&wsdl-ns;</attval> namespace) will be
- 	processed. Note that it is possible for WSDL processors to process
- 	only a subset of a given WSDL document. For instance, a tool may
- 	wish to focus on interfaces and operations only, and 
- 	ignore bindings.
- 	</p>
- 
-     <p>A conformant WSDL processor MUST adhere to the following
-     rules:</p>
-  
-     <ulist>
- 
-       <item>
- 	<p>Except as noted below for mandatory extensions, a
-         conformant WSDL processor MUST accept any legal WSDL document
-         as defined by this specification (WSDL 2.0 Part 1: Core Language, that is).</p>
- 	</item>
- 
-       <item>
-         <p>A conformant WSDL processor MUST fault if a portion of a
-         WSDL document is illegal according to this specification
-         (WSDL 2.0 Part 1: Core Language, that is)
-         and the WSDL processor attempts to process that portion.</p>
-       </item>
- 
-       <item>
- 	<p>A conformant WSDL processor MUST support at least XML
- 	Schema as a type system language.
- 	</p>
- 	</item>
- 
-       <item>
- 	<p>A conformant WSDL processor MUST fail if it processes an
-         element containing a wsdl:include statement having a URI that
-         is not dereferenceable to a legal WSDL document.
- 	</p>
- 	</item>
- 
-       <item>
-         <p>If a mandatory extension (i.e., a mandatory element,
-         feature or property) is processed, a conformant WSDL processor
-         MUST either agree to fully abide by all the rules and
-         semantics signaled by that extension, or immediately cease
-         processing (fault). In particular, if the WSDL processor does
-         not recognize the extension, it MUST fault. If the WSDL
-         processor recognizes the extension, and determines that the
-         extension in question is incompatible with any other aspect of
-         the document (including other required extensions), it MUST
-         fault.</p>
-       </item>
- 
-       <item>
- 	<p>A conformant WSDL processor MAY safely ignore a
- 	NON-mandatory extension or feature that it does not
- 	recognize or that it does not implement.
- 	</p>
- 
-           <note><p>If a WSDL document declares an extension or feature
-           as optional, then if that extension or feature could apply
-           to messages sent by the Web service as well, then the
-           Web service MUST NOT send any messages that require the
-           client to support that extension or feature. The
-           client, on the other hand, MAY engage that extension or
-           feature in messages it sends to the Web service.</p>
- 
-           <p>If finer-grain control of extensions and features is
-           desired then such extensions and features must be designed
-           in a direction (from client or from Web service) sensitive
-           manner so that any direction may be marked required or
-           optional.</p></note>
-       </item>
- 
-       <item><p>If a wsdl:description element is processed, a
-       conformant WSDL processor MUST also process the wsdl:import,
-       wsdl:include, and wsdl:types children of that
-       element.</p></item>
- 
-       <item><p>If a wsdl:interface element is processed, a conformant
-       WSDL processor MUST also process the wsdl:operation, wsdl:fault,
-       wsdl:feature, and wsdl:property children of that
-       element.</p></item>
- 
-       <item><p>If a wsdl:binding element is processed, a conformant
-       WSDL processor MUST also process the wsdl:operation, wsdl:fault,
-       wsdl:feature, and wsdl:property children of that element.
-       </p></item>
- 
-       <item><p>If a wsdl:operation element is processed, a conformant
-       WSDL processor MUST also process the wsdl:input, wsdl:output,
-       wsdl:infault, wsdl:outfault, wsdl:feature, and wsdl:property
-       children of that element.  </p></item>
- 
-       <item><p>If a wsdl:property element is processed, a conformant
-       WSDL processor MUST also process the wsdl:value and
-       wsdl:constraint children of that element.  </p></item>
- 
-     </ulist>
-   </div2>
- 
  </div1>
  
--- 7674,7677 ----
***************
*** 7890,7894 ****
      &lt;/feature&gt;*
  
!     &lt;property uri=&quot;<emph>xs:anyURI</emph>&quot; required=&quot;<emph>xs:boolean</emph>&quot;? &gt;
        &lt;documentation /&gt;?
  
--- 7750,7754 ----
      &lt;/feature&gt;*
  
!     &lt;property uri=&quot;<emph>xs:anyURI</emph>&quot; &gt;
        &lt;documentation /&gt;?
  
***************
*** 8746,8750 ****
      xmlns:xs="http://www.w3.org/2001/XMLSchema" 
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
!     xsi:schemaLocation="&wsdl-ns; wsdl20.xsd"&gt;
  	
      &lt;wsdl:types&gt;
--- 8606,8610 ----
      xmlns:xs="http://www.w3.org/2001/XMLSchema" 
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
!     xsi:schemaLocation="&wsdl-ns; &wsdl-ns;/wsdl20.xsd"&gt;
  	
      &lt;wsdl:types&gt;
Received on Sunday, 3 April 2005 23:45:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:34 UTC