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

2002/ws/desc/wsdl20 wsdl20-z.html,1.13,1.14 wsdl20.pdf,1.26,1.27 wsdl20.html,1.169,1.170 wsdl20-primer.html,1.29,1.30 wsdl20.xml,1.203,1.204 wsdl20-z-ie.html,1.6,1.7 wsdl20.tex,1.33,1.34 wsdl20-adjuncts.html,1.23,1.24 wsdl20.toc,1.18,1.19

From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
Date: Sat, 16 Apr 2005 23:40:25 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1DMwtn-0004Dv-8d@lionel-hutz.w3.org>

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

Modified Files:
	wsdl20-z.html wsdl20.pdf wsdl20.html wsdl20-primer.html 
	wsdl20.xml wsdl20-z-ie.html wsdl20.tex wsdl20-adjuncts.html 
	wsdl20.toc 
Log Message:
Moved the fragment identifer definition into the media registration appendix.

Index: wsdl20-adjuncts.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -d -r1.23 -r1.24
*** wsdl20-adjuncts.html	15 Apr 2005 09:55:50 -0000	1.23
--- wsdl20-adjuncts.html	16 Apr 2005 23:40:23 -0000	1.24
***************
*** 1,15 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
!     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
! <html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
! <head>
! <meta name="generator" content=
! "HTML Tidy for Linux/x86 (vers 1st August 2004), see www.w3.org" />
! <meta http-equiv="Content-Type" content=
! "text/html; charset=utf-8" />
! <title>Web Services Description Language (WSDL) Version 2.0 Part 2:
! Adjuncts</title>
[...10823 lines suppressed...]
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Simplified the introduction; referred to Part1 for a longer introduction</td>
!             </tr>
!             <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Renamed to "Part 2: Bindings"</td>
!             </tr>
!             <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Created from http://www.w3.org/TR/2001/NOTE-wsdl-20010315</td>
!             </tr>
!           </tbody>
!         </table><br>
!       </div>
!     </div>
!   </div>
! </body></html>
\ No newline at end of file

Index: wsdl20-z-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z-ie.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** wsdl20-z-ie.html	14 Apr 2005 02:12:27 -0000	1.6
--- wsdl20-z-ie.html	16 Apr 2005 23:40:23 -0000	1.7
***************
*** 96,100 ****
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.2 <a href="#Binding_Fault_Reference_messageLabel_attribute">messageLabel attribute information item with infault or
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.3 <a href="#Binding_Fault_Reference_extension_elements">Binding Fault Reference extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.3 <a href="#Binding_Fault_Reference_Mapping">Mapping Binding Fault Reference's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.14 <a href="#Service">Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1 <a href="#Service_details">The Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1.1 <a href="#Service_OperationName">Operation Name Mapping Requirement</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2 <a href="#Service_XMLRep">XML Representation of Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.1 <a href="#Service_name_attribute">name attribute information item with service [ower]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.2 <a href="#Service_interface_attribute">interface attribute information item with service [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.3 <a href="#Service_Mapping">Mapping Service's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.15 <a href="#Endpoint">Endpoint</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.1 <a href="#Endpoint_details">The Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2 <a href="#Endpoint_XMLRep">XML Representation of Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.1 <a href="#Endpoint_name_attribute">name attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.2 <a href="#Endpoint_binding_attribute">binding attribute information item with endpoint [owner]</a><br>&nbsp;&nsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.3 <a href="#Endpoint_address_attribute">address attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.4 <a href="#Endpoint_extension_elements">Endpoint extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.3 <a href="#Endpoint_Mapping">Mapping Endpoint's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.16 <a href="#simpletypes">XML Schema 1.0 Simple Types Used in the Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.1 <a href="#ncname_type">NCName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.2 <a href="#anyuri_type">anyURI Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.3 <a href="#qname_type">QName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.4 <a href="#boolean_type">boolean Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.17 <a href="compequiv">Equivalence of Components</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.18 <a href="#symbolspaces">Symbol Spaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.19 <a href="#qnameres">QName resolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.20 <a href="#uricompare">Comparing URIs</a><br>3. <a href="#eii-types">Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#xsd-types">Using W3C XML Schema Description Language</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#import-xsd">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.1 <a href="#namespace-attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.2 <a href="#schemaLocation-attribute">schemaLocation attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#embed-xsd">Embedding XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2.1 <a href="#targetamespace-attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href="#references-definitions">References to Element Declarations and Type Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#other-types">Using Other Schema Languages</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#includes">Including Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#imports">Importing Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner]</a><br>5. <a href="#eii-documentation">Documentation</a><r>6. <a href="#language-extensibility">Language Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#eii-extensibility">Element based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.2 <a href="#required-aii">required attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#markup">Document Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10.<a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#ietf-reg">Registration</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.2 <a href="#ietf-sec">Security considerations</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>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#wsdl-uris">WSDL URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#frag-ids">Fragment Identifiers</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.1 <a href="#wsdl.interface">wsdl.interface(interface)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.2 <a href="#wsdl.interfaceFault">wsdl.interfaceFault(interface/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.3 <a href="#wsdl.interfaceOperation">wsdl.interfaceOperation(interface/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbspC.2.4 <a href="#wsdl.messageReference">wsdl.messageReference(interface/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.5 <a href="#wsdl.faultReference">wsdl.faultReference(interface/operation/message/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.6 <a href="#wsdl.binding">wsdl.binding(binding)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.7 <a href="#wsdl.bindingFault">wsdl.bindingFault(binding/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.8 <a href="#wsdl.bindingOperation">wsdl.bindingOperation(binding/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.9 <a href="#wsdl.bindingMessageReference">wsdl.bindingMessageReference(binding/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.10 <a href="#wsdl.bindingFaultReference">wsdl.bindingFaultReference(binding/operation/fault/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.11 <a href="#wsdl.service">wsdl.service(servce)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.12 <a href="#wsdl.endpoint">wsdl.endpoint(service/endpoint)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.13 <a href="#wsdl.feature">wsdl.feature(parent/feature)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.14 <a href="#wsdl.property">wsdl.property(parent/property)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#extension-elements">Extension Elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#Uri-ref-ex">Example</a><br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;D.1 <a href="#mig_ops">Operation Overloading</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.2 <a href="#mig_porttypes">PortTypes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.3 <a href="#mig_ports">Ports</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.4 <a href="#single_interface_per_service">Single Interface per Service</a><br>E. <a href="#other-schemalang">Examples of Specifications of Extension Elements for Alternative Schema
  Language Support.</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;E.1 <a href="#dtd">DTD</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.1 <a href="#dtd-namespaceaii">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.2 <a href="#dtd-locationaii">location attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.3 <a href="#dtd-ref">References to Element Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;E.2 <a href="#relax">RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1 <a href="#import-relax">Importing RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.1 <a href="#relax-import-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.2 <a href="#relax-import-hrefaii">href attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2 <a href="#relax-embed">Embedding RELAX NG</a<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2.1 <a href="#relax-embed-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.3 <a href="#relax-ref">References to Element Declarations</a><br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;F.1 <a href="#wsdl-changelog">WSDL Specification Changes</a><br></p></div><hr><div class="body">
  
--- 96,100 ----
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.2 <a href="#Binding_Fault_Reference_messageLabel_attribute">messageLabel attribute information item with infault or
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.3 <a href="#Binding_Fault_Reference_extension_elements">Binding Fault Reference extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.3 <a href="#Binding_Fault_Reference_Mapping">Mapping Binding Fault Reference's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.14 <a href="#Service">Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1 <a href="#Service_details">The Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1.1 <a href="#Service_OperationName">Operation Name Mapping Requirement</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2 <a href="#Service_XMLRep">XML Representation of Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.1 <a href="#Service_name_attribute">name attribute information item with service [ower]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.2 <a href="#Service_interface_attribute">interface attribute information item with service [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.3 <a href="#Service_Mapping">Mapping Service's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.15 <a href="#Endpoint">Endpoint</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.1 <a href="#Endpoint_details">The Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2 <a href="#Endpoint_XMLRep">XML Representation of Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.1 <a href="#Endpoint_name_attribute">name attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.2 <a href="#Endpoint_binding_attribute">binding attribute information item with endpoint [owner]</a><br>&nbsp;&nsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.3 <a href="#Endpoint_address_attribute">address attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.4 <a href="#Endpoint_extension_elements">Endpoint extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.3 <a href="#Endpoint_Mapping">Mapping Endpoint's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.16 <a href="#simpletypes">XML Schema 1.0 Simple Types Used in the Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.1 <a href="#ncname_type">NCName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.2 <a href="#anyuri_type">anyURI Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.3 <a href="#qname_type">QName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.4 <a href="#boolean_type">boolean Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.17 <a href="compequiv">Equivalence of Components</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.18 <a href="#symbolspaces">Symbol Spaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.19 <a href="#qnameres">QName resolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.20 <a href="#uricompare">Comparing URIs</a><br>3. <a href="#eii-types">Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#xsd-types">Using W3C XML Schema Description Language</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#import-xsd">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.1 <a href="#namespace-attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.2 <a href="#schemaLocation-attribute">schemaLocation attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#embed-xsd">Embedding XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2.1 <a href="#targetamespace-attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href="#references-definitions">References to Element Declarations and Type Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#other-types">Using Other Schema Languages</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#includes">Including Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#imports">Importing Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner]</a><br>5. <a href="#eii-documentation">Documentation</a><r>6. <a href="#language-extensibility">Language Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#eii-extensibility">Element based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.2 <a href="#required-aii">required attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#markup">Document Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10.<a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#ietf-reg">Registration</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.2 <a href="#frag-ids">Fragment Identifiers</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#wsdl.interface">wsdl.interface(interface)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.2 <a href="#wsdl.interfaceFault">wsdl.interfaceFault(interface/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.3 <a href="#wsdl.interfaceOperation">wsdl.interfaceOperation(interface/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.4 <a href="#wsdl.messageReference">wsdl.messageReference(interface/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.5 <a href="#wsdl.faultReference">wsdl.faultReference(interface/operation/message/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.6 <a href=#wsdl.binding">wsdl.binding(binding)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.7 <a href="#wsdl.bindingFault">wsdl.bindingFault(binding/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.8 <a href="#wsdl.bindingOperation">wsdl.bindingOperation(binding/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.9 <a href="#wsdl.bindingMessageReference">wsdl.bindingMessageReference(binding/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.10 <a href="#wsdl.bindingFaultReference">wsdl.bindingFaultReference(binding/operation/fault/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.11 <a href="#wsdl.service">wsdl.service(service)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.12 <a href="#wsdl.endpoint">wsdl.endpoint(service/endpoint)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.13 <a href="#wsdl.feature">wsdl.feature(parent/feature)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.14 <a hre="#wsdl.property">wsdl.property(parent/property)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.15 <a href="#wsdl.extension">wsdl.extension(extension-namespace, extension-specific-syntax)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.3 <a href="#ietf-sec">Security considerations</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>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#wsdl-uris">WSDL URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#Uri-ref-ex">Example</a><br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;D.1 <a href="#mig_ops">Operation Overloading</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.2 <a href="#mig_porttypes">PortTypes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.3 <a href="#mig_ports">Ports</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.4 <a href="#single_interface_per_service">Single Interface per Service</a><br>E. <a href="#other-schemalang">Examples of Speciications of Extension Elements for Alternative Schema
  Language Support.</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;E.1 <a href="#dtd">DTD</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.1 <a href="#dtd-namespaceaii">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.2 <a href="#dtd-locationaii">location attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.3 <a href="#dtd-ref">References to Element Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;E.2 <a href="#relax">RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1 <a href="#import-relax">Importing RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.1 <a href="#relax-import-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.2 <a href="#relax-import-hrefaii">href attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2 <a href="#relax-embed">Embedding RELAX NG</a<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2.1 <a href="#relax-embed-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.3 <a href="#relax-ref">References to Element Declarations</a><br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;F.1 <a href="#wsdl-changelog">WSDL Specification Changes</a><br></p></div><hr><div class="body">
  
***************
*** 1850,1854 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 1850,1854 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 2181,2185 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 2181,2185 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 2314,2318 ****
  		  <p>
  		  Zero or more namespace qualified <em>attribute information item</em>s.
- 
  		  The [namespace name] of such
  		  <em>attribute information item</em>s MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".
--- 2314,2317 ----
***************
*** 3189,3192 ****
--- 3188,3192 ----
  		  </tr>
  
+ 
                    <tr>
                      <td rowspan="1" colspan="1">{direction}</td> 
***************
*** 4069,4072 ****
--- 4069,4073 ----
  
  
+ 
    <div class="div2">
      
***************
*** 5710,5714 ****
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
--- 5711,5715 ----
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
***************
*** 5792,5797 ****
        &lt;documentation /&gt;?
        [ &lt;feature /&gt; | &lt;property /&gt; ]*
!     &lt;/<b>endpoint</b>&gt;
!   &lt;/service&gt;+
  &lt;/description&gt;
  </pre></div>
--- 5793,5798 ----
        &lt;documentation /&gt;?
        [ &lt;feature /&gt; | &lt;property /&gt; ]*
!     &lt;/<b>endpoint</b>&gt;+
!   &lt;/service&gt;
  &lt;/description&gt;
  </pre></div>
***************
*** 7435,7451 ****
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema: Structures] </dt><dd>	    
! 	    <cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">XML Schema Part 1: Structures</a></cite>,
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 2 May 2001. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-1-20010502. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of
  	    XML Schema Part 1</a> is available at
  	    http://www.w3.org/TR/xmlschema-1.
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema: Datatypes] </dt><dd>
! 	    <cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">XML Schema Part 2: Datatypes</a></cite>, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 2
! 	    May 2001.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-2-20010502. The <a href="http://www.w3.org/TR/xmlschema-2/">latest version of
  	    XML Schema Part 2</a> is available at
  	    http://www.w3.org/TR/xmlschema-2.
--- 7436,7452 ----
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema: Structures] </dt><dd>	    
! 	    <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema Part 1: Structures</a></cite>,
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 28 October 2004. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of
  	    XML Schema Part 1</a> is available at
  	    http://www.w3.org/TR/xmlschema-1.
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema: Datatypes] </dt><dd>
! 	    <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema Part 2: Datatypes</a></cite>, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 28
! 	    October 2004.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href="http://www.w3.org/TR/xmlschema-2/">latest version of
  	    XML Schema Part 2</a> is available at
  	    http://www.w3.org/TR/xmlschema-2.
***************
*** 7708,7712 ****
  
    <dt class="label">Security considerations:</dt>
!      <dd><p>See section <a href="#ietf-sec"><b>A.2 Security considerations</b></a>.</p></dd>
  
    <dt class="label">Interoperability considerations:</dt>
--- 7709,7713 ----
  
    <dt class="label">Security considerations:</dt>
!      <dd><p>See section <a href="#ietf-sec"><b>A.3 Security considerations</b></a>.</p></dd>
  
    <dt class="label">Interoperability considerations:</dt>
***************
*** 7730,7734 ****
            <dt class="label">Fragment identifiers:</dt>
            <dd><p>Either a syntax identical to that of
!           "application/xml" as described in [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 5 or the syntax defined in <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>.</p></dd>
         
  
--- 7731,7735 ----
            <dt class="label">Fragment identifiers:</dt>
            <dd><p>Either a syntax identical to that of
!           "application/xml" as described in [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 5 or the syntax defined in <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>.</p></dd>
         
  
***************
*** 7758,7905 ****
       
       </dl>
  
-     </div>
-     
-     <div class="div2">
-     
- <h3><a name="ietf-sec"></a>A.2 Security considerations</h3>
-     
-   <p>This media type uses the "+xml" convention, it shares
-   the same security considerations as described in
-   [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 10.</p>
- 
-     </div>
-         
-     </div>
- 
-     
- <div class="div1">
- 
- <h2><a name="acknowledgments"></a>B. Acknowledgements (Non-Normative)</h2>
- <p>This document is the work of the <a href="http://www.w3.org/2002/ws/desc/">W3C Web Service
-       Description Working Group</a>.</p>
- <p>Members of the Working Group are (at the time of writing, and by
-       alphabetical order):
-       David Booth
- 	(W3C), Allen Brookes
- 	(Rogue Wave Softwave), Helen Chen
- 	(Agfa-Gevaert N. V.), Roberto Chinnici
- 	(Sun Microsystems), Ugo Corda
- 	(SeeBeyond), Glen Daniels
- 	(Sonic Software), Paul Downey
- 	(British Telecommunications), Youenn Fablet
- 	(Canon), Martin Gudgin
- 	(Microsoft Corporation), Hugo Haas
- 	(W3C), Hao He
- 	(The Thomson Corporation), Tom Jordahl
- 	(Macromedia), Jacek Kopecky
- 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
- 	(TIBCO Software, Inc.), Kevin Canyang Liu
- 	(SAP), Jonathan Marsh
- 	(Microsoft Corporation), Peter Madziak
- 	(Agfa-Gevaert N. V.), Josephine Micallef
- 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
- 	(Oracle Corporation), Dale Moberg
- 	(Cyclone Commerce), Jean-Jacques Moreau
- 	(Canon), Mark Nottingham
- 	(BEA Systems, Inc.), David Orchard
- 	(BEA Systems, Inc.), Bijan Parsia
- 	(University of Maryland), Arthur Ryman
- 	(IBM), Adi Sakala
- 	(IONA Technologies), Jeffrey Schlimmer
- 	(Microsoft Corporation), Igor Sedukhin
- 	(Computer Associates), Jerry Thrasher
- 	(Lexmark), William Vambenepe
- 	(Hewlett-Packard Company), Asir Vedamuthu
- 	(webMethods, Inc.), Sanjiva Weerawarana
- 	(IBM), &Uuml;mit Yal&ccedil;ınalp
- 	(Oracle Corporation), Prasad Yendluri
- 	(webMethods, Inc.).</p>
- <p>Previous members were:
-       Lily Liu
- 	(webMethods, Inc.), Don Wright
- 	(Lexmark), Joyce Yang
- 	(Oracle Corporation), Daniel Schutzer
- 	(Citigroup), Dave Solo
- 	(Citigroup), Stefano Pogliani
- 	(Sun Microsystems), William Stumbo
- 	(Xerox), Stephen White
- 	(SeeBeyond), Barbara Zengler
- 	(DaimlerChrysler Research and Technology), Tim Finin
- 	(University of Maryland), Laurent De Teneuille
- 	(L'Echangeur), Johan Pauhlsson
- 	(L'Echangeur), Mark Jones
- 	(AT&amp;T), Steve Lind
- 	(AT&amp;T), Sandra Swearingen
- 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H&eacute;garet
- 	(W3C), Jim Hendler
- 	(University of Maryland), Dietmar Gaertner
- 	(Software AG), Michael Champion
- 	(Software AG), Don Mullen
- 	(TIBCO Software, Inc.), Steve Graham
- 	(Global Grid Forum), Steve Tuecke
- 	(Global Grid Forum), Michael Mahan
- 	(Nokia), Bryan Thompson
- 	(Hicks &amp; Associates), Ingo Melzer
- 	(DaimlerChrysler Research and Technology), Sandeep Kumar
- 	(Cisco Systems), Alan Davies
- 	(SeeBeyond), Jacek Kopecky
- 	(Systinet), Mike Ballantyne
- 	(Electronic Data Systems), Mike Davoren
- 	(W. W. Grainger), Dan Kulp
- 	(IONA Technologies), Mike McHugh
- 	(W. W. Grainger), Michael Mealling
- 	(Verisign), Waqar Sadiq
- 	(Electronic Data Systems), Yaron Goland
- 	(BEA Systems, Inc.).</p>
- <p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/www-ws-desc/">discussions
-       on www-ws-desc@w3.org</a> are also gratefully
-       acknowledged.</p>
- </div>
- 
- 
-     <div class="div1">
- 	
- <h2><a name="wsdl-uri-references"></a>C. URI References for WSDL Components (Non-Normative)</h2>
- 
- 	<p> This appendix provides a syntax for URI references for
- 	named components found in a WSDL document. This includes the
- 	top level components: Interface, Binding and Service and the
- 	subordinate components: Interface Operation, Interface Fault, 
- 	Message Reference, Fault Reference, Feature, Property,
- 	Binding Operation, Binding Fault, Binding Message Reference
- 	and Endpoint. The
- 	URI references are easy to understand and compare, while
- 	imposing no burden on the WSDL author.</p>
- 
- 	<div class="div2">
- 	
- <h3><a name="wsdl-uris"></a>C.1 WSDL URIs</h3>
- 	<p>
- 	There are two main cases for WSDL URIs: 
- 	</p>
- 	<ul>
- 	<li><p>the URI of a WSDL document</p></li>
- 	<li><p>the URI of a WSDL namespace</p></li>
- 	</ul>
- 	<p>
- 	The URI of a WSDL document can be dereferenced to give a resource
- 	representation that contributes component definitions to a single
- 	WSDL namespace. If the media type is set to the WSDL media type,
- 	then the fragment identifiers can be used to identify the
- 	main components that are defined in the document. 
- 	</p>
- 
- 	<p> However, in keeping with the recommendation in <a href="#Description_details"><b>2.1.1 The Description Component</b></a> that the namespace URI be
-         dereferencible to a WSDL document, this appendix specifies the
-         use of the namespace URI with the WSDL fragment identifiers to
-         form a URI-reference.</p>
- 
- 	</div>
  	<div class="div2">
  	
! <h3><a name="frag-ids"></a>C.2 Fragment Identifiers</h3>
  	<p>
! 	The following fragment identifier syntax is compliant with the
  	[<cite><a href="#XPTR">XPointer Framework</a></cite>].
  	</p>
--- 7759,7770 ----
       
       </dl>
+      </div>
  
  	<div class="div2">
  	
! <h3><a name="frag-ids"></a>A.2 Fragment Identifiers</h3>
  	<p>
! 	This section defined a fragment identifier syntax for identifying components of a WSDL document.
! 	This fragment identifier syntax is compliant with the
  	[<cite><a href="#XPTR">XPointer Framework</a></cite>].
  	</p>
***************
*** 7908,7917 ****
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names are of type either QName, NCName,
! 	URI, or Pointer Part, depending on the context.
  	</p>
  	<p>
--- 7773,7782 ----
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the standard WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names in the path are of type either QName, NCName,
! 	URI, or Pointer Part depending on the context.
  	</p>
  	<p>
***************
*** 7919,7936 ****
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the URI of the URI-reference.
  	</p>
  
  	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier, where the fragment identifier is typically
! 		constructed from the {name} property of the component and the
! 		{name} properties of its ancestors as a path according to
! 		<a href="#uriRefFragTable">Table C-1</a>. 
! 		In that table the first column gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
--- 7784,7796 ----
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the target namespace of the WSDL document.
  	</p>
  
  	<p>
! 		The fragment identifier is typically constructed from the {name}
! 		property of the component and the {name} properties of its
! 		ancestors as a path according to
! 		<a href="#frag-ids-table">Table A-1</a>.
! 	    The first column of this table gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
***************
*** 7941,7946 ****
  	</p>
  
! 	<a name="uriRefFragTable"></a><br><table border="1">
! 	  <caption>Table C-1. Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" span="1">
  	    <col width="10%" span="1">
--- 7801,7806 ----
  	</p>
  
! 	<a name="frag-ids-table"></a><br><table border="1">
! 	  <caption>Table A-1. Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" span="1">
  	    <col width="10%" span="1">
***************
*** 8070,8078 ****
            <td rowspan="1" colspan="1"><a href="#wsdl.property"><code>wsdl.property(<em>parent</em>/<em>property</em>)</code></a></td>
  	</tr>
        </tbody>
        </table><br>
  
        <p>Note that the above rules are defined in terms of component
!       properties rather the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
--- 7930,7948 ----
            <td rowspan="1" colspan="1"><a href="#wsdl.property"><code>wsdl.property(<em>parent</em>/<em>property</em>)</code></a></td>
  	</tr>
+ 	
        </tbody>
        </table><br>
  
+ 	<p>
+ 		WSDL is extensible and it is possible for an
+ 		extension to define new components types. The XPointer Framework
+ 		scheme for extension components is:
+ 	</p>
+ 
+ 	<p><a href="#wsdl.extension"><code>wsdl.extension(<em>extension-namespace</em>, <em>extension-specific-syntax</em>)</code></a>
+ 	</p>
+ 
        <p>Note that the above rules are defined in terms of component
!       properties rather than the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
***************
*** 8080,8084 ****
        <div class="div3">
        
! <h4><a name="wsdl.interface"></a>C.2.1 <code>wsdl.interface(<em>interface</em>)</code></h4>
        <ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the <a href="#Interface">Interface</a> component.</li>
--- 7950,7954 ----
        <div class="div3">
        
! <h4><a name="wsdl.interface"></a>A.2.1 <code>wsdl.interface(<em>interface</em>)</code></h4>
        <ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the <a href="#Interface">Interface</a> component.</li>
***************
*** 8088,8092 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceFault"></a>C.2.2 <code>wsdl.interfaceFault(<em>interface</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
--- 7958,7962 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceFault"></a>A.2.2 <code>wsdl.interfaceFault(<em>interface</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
***************
*** 8097,8101 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceOperation"></a>C.2.3 <code>wsdl.interfaceOperation(<em>interface</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
--- 7967,7971 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceOperation"></a>A.2.3 <code>wsdl.interfaceOperation(<em>interface</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
***************
*** 8106,8110 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.messageReference"></a>C.2.4 <code>wsdl.messageReference(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
--- 7976,7980 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.messageReference"></a>A.2.4 <code>wsdl.messageReference(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
***************
*** 8116,8120 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.faultReference"></a>C.2.5 <code>wsdl.faultReference(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
--- 7986,7990 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.faultReference"></a>A.2.5 <code>wsdl.faultReference(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
***************
*** 8128,8132 ****
        <div class="div3">
        
! <h4><a name="wsdl.binding"></a>C.2.6 <code>wsdl.binding(<em>binding</em>)</code></h4>
        <ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the <a href="#Binding">Binding</a> component.</li>
--- 7998,8002 ----
        <div class="div3">
        
! <h4><a name="wsdl.binding"></a>A.2.6 <code>wsdl.binding(<em>binding</em>)</code></h4>
        <ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the <a href="#Binding">Binding</a> component.</li>
***************
*** 8136,8140 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFault"></a>C.2.7 <code>wsdl.bindingFault(<em>binding</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
--- 8006,8010 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFault"></a>A.2.7 <code>wsdl.bindingFault(<em>binding</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
***************
*** 8146,8150 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingOperation"></a>C.2.8 <code>wsdl.bindingOperation(<em>binding</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
--- 8016,8020 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingOperation"></a>A.2.8 <code>wsdl.bindingOperation(<em>binding</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
***************
*** 8156,8160 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingMessageReference"></a>C.2.9 <code>wsdl.bindingMessageReference(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
--- 8026,8030 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingMessageReference"></a>A.2.9 <code>wsdl.bindingMessageReference(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
***************
*** 8168,8172 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFaultReference"></a>C.2.10 <code>wsdl.bindingFaultReference(<em>binding</em>/<em>operation</em>/<em>fault</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
--- 8038,8042 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFaultReference"></a>A.2.10 <code>wsdl.bindingFaultReference(<em>binding</em>/<em>operation</em>/<em>fault</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
***************
*** 8184,8188 ****
        <div class="div3">
        
! <h4><a name="wsdl.service"></a>C.2.11 <code>wsdl.service(<em>service</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the <a href="#Service">Service</a> component.</li>
--- 8054,8058 ----
        <div class="div3">
        
! <h4><a name="wsdl.service"></a>A.2.11 <code>wsdl.service(<em>service</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the <a href="#Service">Service</a> component.</li>
***************
*** 8192,8196 ****
        <div class="div3">
        
! <h4><a name="wsdl.endpoint"></a>C.2.12 <code>wsdl.endpoint(<em>service</em>/<em>endpoint</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the parent <a href="#Service">Service</a> component.</li>
--- 8062,8066 ----
        <div class="div3">
        
! <h4><a name="wsdl.endpoint"></a>A.2.12 <code>wsdl.endpoint(<em>service</em>/<em>endpoint</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the parent <a href="#Service">Service</a> component.</li>
***************
*** 8201,8205 ****
        <div class="div3">
        
! <h4><a name="wsdl.feature"></a>C.2.13 <code>wsdl.feature(<em>parent</em>/<em>feature</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
--- 8071,8075 ----
        <div class="div3">
        
! <h4><a name="wsdl.feature"></a>A.2.13 <code>wsdl.feature(<em>parent</em>/<em>feature</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
***************
*** 8210,8214 ****
        <div class="div3">
        
! <h4><a name="wsdl.property"></a>C.2.14 <code>wsdl.property(<em>parent</em>/<em>property</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
--- 8080,8084 ----
        <div class="div3">
        
! <h4><a name="wsdl.property"></a>A.2.14 <code>wsdl.property(<em>parent</em>/<em>property</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
***************
*** 8216,8245 ****
        </ol>
        </div>
        </div>
  
  	<div class="div2">
  	
! <h3><a name="extension-elements"></a>C.3 Extension Elements</h3>
  	<p>
! 	WSDL has an open content model. It is therefore possible for an
! 	extension to define new components. The XPointer
! 	Framework scheme for components added by extensions is:
  	</p>
! 	<p><code>
! 	wsdl.extension(extension-namespace, extension-specific-syntax)</code>
  	</p>
  	<p>
! 	where extension-namespace is the namespace that identifies the
! 	extension, e.g. for SOAP the namespace is
! 	http://www.w3.org/2003/06/wsdl/soap12, and
! 	extension-specific-syntax is defined by the extension. The owner
! 	of the extension must define any components contributed by the
! 	extension and a syntax for identifying them.
  	</p>
- 	</div>
  
  	<div class="div2">
  	
! <h3><a name="Uri-ref-ex"></a>C.4 Example</h3>
  	<p>Consider the following WSDL located at
  	http://example.org/TicketAgent.wsdl:
--- 8086,8260 ----
        </ol>
        </div>
+ 
+       <div class="div3">
+       	
+ <h4><a name="wsdl.extension"></a>A.2.15 <code>wsdl.extension(<em>extension-namespace</em>, <em>extension-specific-syntax</em>)</code></h4>
+       	<ol>
+       		<li>
+       			<code>
+       				<em>extension-namespace</em>
+       			</code>
+       			is the namespace that identifies the extension, e.g.
+       			for SOAP the namespace is
+       			http://www.w3.org/2003/06/wsdl/soap12.
+       		</li>
+       		<li>
+       			<code>
+       				<em>extension-specific-syntax</em>
+       			</code>
+       			is defined by the extension. The owner of the
+       			extension must define any components contributed by
+       			the extension and a syntax for identifying them.
+       		</li>
+       	</ol>
        </div>
+ 	</div>
+     
+     <div class="div2">
+     
+ <h3><a name="ietf-sec"></a>A.3 Security considerations</h3>
+     
+   <p>This media type uses the "+xml" convention, it shares
+   the same security considerations as described in
+   [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 10.</p>
+ 
+     </div>
+         
+     </div>
+ 
+     
+ <div class="div1">
+ 
+ <h2><a name="acknowledgments"></a>B. Acknowledgements (Non-Normative)</h2>
+ <p>This document is the work of the <a href="http://www.w3.org/2002/ws/desc/">W3C Web Service
+       Description Working Group</a>.</p>
+ <p>Members of the Working Group are (at the time of writing, and by
+       alphabetical order):
+       David Booth
+ 	(W3C), Allen Brookes
+ 	(Rogue Wave Softwave), Helen Chen
+ 	(Agfa-Gevaert N. V.), Roberto Chinnici
+ 	(Sun Microsystems), Ugo Corda
+ 	(SeeBeyond), Glen Daniels
+ 	(Sonic Software), Paul Downey
+ 	(British Telecommunications), Youenn Fablet
+ 	(Canon), Martin Gudgin
+ 	(Microsoft Corporation), Hugo Haas
+ 	(W3C), Hao He
+ 	(The Thomson Corporation), Tom Jordahl
+ 	(Macromedia), Jacek Kopecky
+ 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
+ 	(TIBCO Software, Inc.), Kevin Canyang Liu
+ 	(SAP), Jonathan Marsh
+ 	(Microsoft Corporation), Peter Madziak
+ 	(Agfa-Gevaert N. V.), Josephine Micallef
+ 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
+ 	(Oracle Corporation), Dale Moberg
+ 	(Cyclone Commerce), Jean-Jacques Moreau
+ 	(Canon), Mark Nottingham
+ 	(BEA Systems, Inc.), David Orchard
+ 	(BEA Systems, Inc.), Bijan Parsia
+ 	(University of Maryland), Arthur Ryman
+ 	(IBM), Adi Sakala
+ 	(IONA Technologies), Jeffrey Schlimmer
+ 	(Microsoft Corporation), Igor Sedukhin
+ 	(Computer Associates), Jerry Thrasher
+ 	(Lexmark), William Vambenepe
+ 	(Hewlett-Packard Company), Asir Vedamuthu
+ 	(webMethods, Inc.), Sanjiva Weerawarana
+ 	(IBM), &Uuml;mit Yal&ccedil;ınalp
+ 	(Oracle Corporation), Prasad Yendluri
+ 	(webMethods, Inc.).</p>
+ <p>Previous members were:
+       Lily Liu
+ 	(webMethods, Inc.), Don Wright
+ 	(Lexmark), Joyce Yang
+ 	(Oracle Corporation), Daniel Schutzer
+ 	(Citigroup), Dave Solo
+ 	(Citigroup), Stefano Pogliani
+ 	(Sun Microsystems), William Stumbo
+ 	(Xerox), Stephen White
+ 	(SeeBeyond), Barbara Zengler
+ 	(DaimlerChrysler Research and Technology), Tim Finin
+ 	(University of Maryland), Laurent De Teneuille
+ 	(L'Echangeur), Johan Pauhlsson
+ 	(L'Echangeur), Mark Jones
+ 	(AT&amp;T), Steve Lind
+ 	(AT&amp;T), Sandra Swearingen
+ 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H&eacute;garet
+ 	(W3C), Jim Hendler
+ 	(University of Maryland), Dietmar Gaertner
+ 	(Software AG), Michael Champion
+ 	(Software AG), Don Mullen
+ 	(TIBCO Software, Inc.), Steve Graham
+ 	(Global Grid Forum), Steve Tuecke
+ 	(Global Grid Forum), Michael Mahan
+ 	(Nokia), Bryan Thompson
+ 	(Hicks &amp; Associates), Ingo Melzer
+ 	(DaimlerChrysler Research and Technology), Sandeep Kumar
+ 	(Cisco Systems), Alan Davies
+ 	(SeeBeyond), Jacek Kopecky
+ 	(Systinet), Mike Ballantyne
+ 	(Electronic Data Systems), Mike Davoren
+ 	(W. W. Grainger), Dan Kulp
+ 	(IONA Technologies), Mike McHugh
+ 	(W. W. Grainger), Michael Mealling
+ 	(Verisign), Waqar Sadiq
+ 	(Electronic Data Systems), Yaron Goland
+ 	(BEA Systems, Inc.).</p>
+ <p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/www-ws-desc/">discussions
+       on www-ws-desc@w3.org</a> are also gratefully
+       acknowledged.</p>
+ </div>
+ 
+ 
+     <div class="div1">
+ 	
+ <h2><a name="wsdl-uri-references"></a>C. URI References for WSDL Components (Non-Normative)</h2>
+ 
+ 	<p>
+ 		This appendix provides a syntax for URI references for all
+ 		components found in a WSDL document. The URI references are easy
+ 		to understand and compare, while imposing no burden on the WSDL
+ 		author.
+ 	</p>
  
  	<div class="div2">
  	
! <h3><a name="wsdl-uris"></a>C.1 WSDL URIs</h3>
! 	<p>There are two main cases for WSDL URIs:</p>
! 	<ul>
! 	<li><p>the URI of a WSDL document</p></li>
! 	<li><p>the URI of a WSDL namespace</p></li>
! 	</ul>
  	<p>
! 		The URI of a WSDL document can be dereferenced to give a
! 		resource representation that contributes component definitions
! 		to a single WSDL namespace. If the media type is set to the WSDL
! 		media type, then the fragment identifiers can be used to
! 		identify the main components that are defined in the document.
  	</p>
! 
! 	<p>
! 		However, in keeping with the recommendation in
! 		<a href="#Description_details"><b>2.1.1 The Description Component</b></a>
! 		that the namespace URI be dereferencible to a WSDL document,
! 		this appendix specifies the use of the namespace URI with the
! 		WSDL fragment identifiers to form a URI-reference.
  	</p>
+ 
  	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier as defined in <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>.
  	</p>
  
+ 	</div>
  	<div class="div2">
  	
! <h3><a name="Uri-ref-ex"></a>C.2 Example</h3>
  	<p>Consider the following WSDL located at
  	http://example.org/TicketAgent.wsdl:
***************
*** 8281,8285 ****
  </div>
  <p>
! Its conceptual elements have the following URI-references:</p>
  
  <div class="exampleOuter">
--- 8296,8300 ----
  </div>
  <p>
! Its components have the following URI-references:</p>
  
  <div class="exampleOuter">
***************
*** 8566,8571 ****
--- 8581,8599 ----
        <th rowspan="1" colspan="1">Description</th>
      </tr>
+     
+     <tr>
+     	<td rowspan="1" colspan="1">20050416</td>
+     	<td rowspan="1" colspan="1">AGR</td>
+     	<td rowspan="1" colspan="1">Moved the <a href="#frag-ids">fragment identifer</a> definition into the media registration appendix.</td>
+     </tr>
  
      <tr>
+     	<td rowspan="1" colspan="1">20050414</td>
+     	<td rowspan="1" colspan="1">JJM</td>
+     	<td rowspan="1" colspan="1">
+     		Fixed XML Schema P1/P2 version listed in the bibliograpy section.
+     	</td>
+     </tr>
+     <tr>
      	<td rowspan="1" colspan="1">20050413</td>
      	<td rowspan="1" colspan="1">AGR</td>

Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.33
retrieving revision 1.34
diff -C2 -d -r1.33 -r1.34
*** wsdl20.tex	14 Apr 2005 02:12:27 -0000	1.33
--- wsdl20.tex	16 Apr 2005 23:40:23 -0000	1.34
***************
*** 2188,2192 ****
  	components; they cannot be referred to by QName, despite
  	having a \{name\} property
! 	(see \hyperlink{wsdl-uri-references}{\textbf{\ref*{wsdl-uri-references} URI References for WSDL Components}}). That is,
  	two Interface components whose \{name\} property share the same namespace name
  	but with different local names MAY contain
--- 2188,2192 ----
  	components; they cannot be referred to by QName, despite
  	having a \{name\} property
! 	(see \hyperlink{frag-ids}{\textbf{\ref*{frag-ids} Fragment Identifiers}}). That is,
  	two Interface components whose \{name\} property share the same namespace name
  	but with different local names MAY contain
***************
*** 2540,2544 ****
  	components; they cannot be referred to by QName, despite
  	having a \{name\} property
! 	(see \hyperlink{wsdl-uri-references}{\textbf{\ref*{wsdl-uri-references} URI References for WSDL Components}}). That is,
  	two Interface components whose \{name\} property share the same namespace name
  	but with different local names MAY contain
--- 2540,2544 ----
  	components; they cannot be referred to by QName, despite
  	having a \{name\} property
! 	(see \hyperlink{frag-ids}{\textbf{\ref*{frag-ids} Fragment Identifiers}}). That is,
  	two Interface components whose \{name\} property share the same namespace name
  	but with different local names MAY contain
***************
*** 2675,2679 ****
  		  
  		  Zero or more namespace qualified \textit{attribute information item}s.
- 
  		  The [namespace name] of such
  		  \textit{attribute information item}s MUST NOT be {\tt "http://www.w3.org/@@@@/@@/wsdl"}.
--- 2675,2678 ----
***************
*** 3597,3600 ****
--- 3596,3600 ----
  		  \\ \hline 
  
+ 
                    
                      \{direction\}& 
***************
*** 4524,4527 ****
--- 4524,4528 ----
  
  
+ 
    \hypertarget{Binding}{}
  \section{Binding}\label{Binding}
***************
*** 6275,6279 ****
  	  
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see \hyperlink{wsdl-uri-references}{\textbf{\ref*{wsdl-uri-references} URI References for WSDL Components}}).
  	  
  	  The properties of the Endpoint component are as follows:
--- 6276,6280 ----
  	  
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see \hyperlink{frag-ids}{\textbf{\ref*{frag-ids} Fragment Identifiers}}).
  	  
  	  The properties of the Endpoint component are as follows:
***************
*** 6371,6376 ****
        <documentation />?
        [ <feature /> | <property /> ]*
!     </endpoint>
!   </service>+
  </description>
  \end{verbatim}
--- 6372,6377 ----
        <documentation />?
        [ <feature /> | <property /> ]*
!     </endpoint>+
!   </service>
  </description>
  \end{verbatim}
***************
*** 8075,8083 ****
  	  \hypertarget{XMLSchemaP1}{}\item[{[XML Schema: Structures]}] \ 
  	    
! 	    \href{http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/}{XML Schema Part 1: Structures},
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 2 May 2001. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-1-20010502. The \href{http://www.w3.org/TR/xmlschema-1/}{latest version of
  	    XML Schema Part 1} is available at
  	    http://www.w3.org/TR/xmlschema-1.
--- 8076,8084 ----
  	  \hypertarget{XMLSchemaP1}{}\item[{[XML Schema: Structures]}] \ 
  	    
! 	    \href{http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/}{XML Schema Part 1: Structures},
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 28 October 2004. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The \href{http://www.w3.org/TR/xmlschema-1/}{latest version of
  	    XML Schema Part 1} is available at
  	    http://www.w3.org/TR/xmlschema-1.
***************
*** 8085,8092 ****
  	  \hypertarget{XMLSchemaP2}{}\item[{[XML Schema: Datatypes]}] \ 
  
! 	    \href{http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/}{XML Schema Part 2: Datatypes}, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 2
! 	    May 2001.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-2-20010502. The \href{http://www.w3.org/TR/xmlschema-2/}{latest version of
  	    XML Schema Part 2} is available at
  	    http://www.w3.org/TR/xmlschema-2.
--- 8086,8093 ----
  	  \hypertarget{XMLSchemaP2}{}\item[{[XML Schema: Datatypes]}] \ 
  
! 	    \href{http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/}{XML Schema Part 2: Datatypes}, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 28
! 	    October 2004.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The \href{http://www.w3.org/TR/xmlschema-2/}{latest version of
  	    XML Schema Part 2} is available at
  	    http://www.w3.org/TR/xmlschema-2.
***************
*** 8393,8397 ****
            \item[Fragment identifiers:] 
            Either a syntax identical to that of
!           {\tt "application/xml"} as described in \hyperlink{RFC3023}{[\textit{RFC 3023}]}, section 5 or the syntax defined in \hyperlink{wsdl-uri-references}{\textbf{\ref*{wsdl-uri-references} URI References for WSDL Components}}.
         
  
--- 8394,8398 ----
            \item[Fragment identifiers:] 
            Either a syntax identical to that of
!           {\tt "application/xml"} as described in \hyperlink{RFC3023}{[\textit{RFC 3023}]}, section 5 or the syntax defined in \hyperlink{frag-ids}{\textbf{\ref*{frag-ids} Fragment Identifiers}}.
         
  
***************
*** 8421,8567 ****
       
       \end{description}
  
-     
-     
-     \hypertarget{ietf-sec}{}
- \section{Security considerations}\label{ietf-sec}
- 
-     
-     
-   This media type uses the {\tt "+xml"} convention, it shares
-   the same security considerations as described in
-   \hyperlink{RFC3023}{[\textit{RFC 3023}]}, section 10.
- 
-     
-         
-     
- 
-     
- \hypertarget{acknowledgments}{}
- \chapter{Acknowledgements (Non-Normative)}\label{acknowledgments}
- 
- 
- This document is the work of the \href{http://www.w3.org/2002/ws/desc/}{W3C Web Service
-       Description Working Group}.
- Members of the Working Group are (at the time of writing, and by
-       alphabetical order):
-       David Booth
- 	(W3C), Allen Brookes
- 	(Rogue Wave Softwave), Helen Chen
- 	(Agfa-Gevaert N. V.), Roberto Chinnici
- 	(Sun Microsystems), Ugo Corda
- 	(SeeBeyond), Glen Daniels
- 	(Sonic Software), Paul Downey
- 	(British Telecommunications), Youenn Fablet
- 	(Canon), Martin Gudgin
- 	(Microsoft Corporation), Hugo Haas
- 	(W3C), Hao He
- 	(The Thomson Corporation), Tom Jordahl
- 	(Macromedia), Jacek Kopecky
- 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
- 	(TIBCO Software, Inc.), Kevin Canyang Liu
- 	(SAP), Jonathan Marsh
- 	(Microsoft Corporation), Peter Madziak
- 	(Agfa-Gevaert N. V.), Josephine Micallef
- 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
- 	(Oracle Corporation), Dale Moberg
- 	(Cyclone Commerce), Jean-Jacques Moreau
- 	(Canon), Mark Nottingham
- 	(BEA Systems, Inc.), David Orchard
- 	(BEA Systems, Inc.), Bijan Parsia
- 	(University of Maryland), Arthur Ryman
- 	(IBM), Adi Sakala
- 	(IONA Technologies), Jeffrey Schlimmer
- 	(Microsoft Corporation), Igor Sedukhin
- 	(Computer Associates), Jerry Thrasher
- 	(Lexmark), William Vambenepe
- 	(Hewlett-Packard Company), Asir Vedamuthu
- 	(webMethods, Inc.), Sanjiva Weerawarana
- 	(IBM), \"{U}mit Yal\c{c}{\i}nalp
- 	(Oracle Corporation), Prasad Yendluri
- 	(webMethods, Inc.).
- Previous members were:
-       Lily Liu
- 	(webMethods, Inc.), Don Wright
- 	(Lexmark), Joyce Yang
- 	(Oracle Corporation), Daniel Schutzer
- 	(Citigroup), Dave Solo
- 	(Citigroup), Stefano Pogliani
- 	(Sun Microsystems), William Stumbo
- 	(Xerox), Stephen White
- 	(SeeBeyond), Barbara Zengler
- 	(DaimlerChrysler Research and Technology), Tim Finin
- 	(University of Maryland), Laurent De Teneuille
- 	(L'Echangeur), Johan Pauhlsson
- 	(L'Echangeur), Mark Jones
- 	(AT\&T), Steve Lind
- 	(AT\&T), Sandra Swearingen
- 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H\'{e}garet
- 	(W3C), Jim Hendler
- 	(University of Maryland), Dietmar Gaertner
- 	(Software AG), Michael Champion
- 	(Software AG), Don Mullen
- 	(TIBCO Software, Inc.), Steve Graham
- 	(Global Grid Forum), Steve Tuecke
- 	(Global Grid Forum), Michael Mahan
- 	(Nokia), Bryan Thompson
- 	(Hicks \& Associates), Ingo Melzer
- 	(DaimlerChrysler Research and Technology), Sandeep Kumar
- 	(Cisco Systems), Alan Davies
- 	(SeeBeyond), Jacek Kopecky
- 	(Systinet), Mike Ballantyne
- 	(Electronic Data Systems), Mike Davoren
- 	(W. W. Grainger), Dan Kulp
- 	(IONA Technologies), Mike McHugh
- 	(W. W. Grainger), Michael Mealling
- 	(Verisign), Waqar Sadiq
- 	(Electronic Data Systems), Yaron Goland
- 	(BEA Systems, Inc.).
- The people who have contributed to \href{http://lists.w3.org/Archives/Public/www-ws-desc/}{discussions
-       on www-ws-desc@w3.org} are also gratefully
-       acknowledged.
- 
- 
- 
-     \hypertarget{wsdl-uri-references}{}
- \chapter{URI References for WSDL Components (Non-Normative)}\label{wsdl-uri-references}
- 
- 	
- 
- 	 This appendix provides a syntax for URI references for
- 	named components found in a WSDL document. This includes the
- 	top level components: Interface, Binding and Service and the
- 	subordinate components: Interface Operation, Interface Fault, 
- 	Message Reference, Fault Reference, Feature, Property,
- 	Binding Operation, Binding Fault, Binding Message Reference
- 	and Endpoint. The
- 	URI references are easy to understand and compare, while
- 	imposing no burden on the WSDL author.
- 
- 	\hypertarget{wsdl-uris}{}
- \section{WSDL URIs}\label{wsdl-uris}
- 
- 	
- 	
- 	There are two main cases for WSDL URIs: 
- 	
- 	\begin{itemize}
- 	\item the URI of a WSDL document
- 	\item the URI of a WSDL namespace
- 	\end{itemize}
- 	
- 	The URI of a WSDL document can be dereferenced to give a resource
- 	representation that contributes component definitions to a single
- 	WSDL namespace. If the media type is set to the WSDL media type,
- 	then the fragment identifiers can be used to identify the
- 	main components that are defined in the document. 
- 	
- 
- 	 However, in keeping with the recommendation in \hyperlink{Description_details}{\textbf{\ref*{Description_details} The Description Component}} that the namespace URI be
-         dereferencible to a WSDL document, this appendix specifies the
-         use of the namespace URI with the WSDL fragment identifiers to
-         form a URI-reference.
- 
- 	
  	\hypertarget{frag-ids}{}
  \section{Fragment Identifiers}\label{frag-ids}
--- 8422,8427 ----
       
       \end{description}
+      
  
  	\hypertarget{frag-ids}{}
  \section{Fragment Identifiers}\label{frag-ids}
***************
*** 8569,8573 ****
  	
  	
! 	The following fragment identifier syntax is compliant with the
  	\hyperlink{XPTR}{[\textit{XPointer Framework}]}.
  	
--- 8429,8434 ----
  	
  	
! 	This section defined a fragment identifier syntax for identifying components of a WSDL document.
! 	This fragment identifier syntax is compliant with the
  	\hyperlink{XPTR}{[\textit{XPointer Framework}]}.
  	
***************
*** 8576,8585 ****
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names are of type either QName, NCName,
! 	URI, or Pointer Part, depending on the context.
  	
  	
--- 8437,8446 ----
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the standard WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names in the path are of type either QName, NCName,
! 	URI, or Pointer Part depending on the context.
  	
  	
***************
*** 8587,8604 ****
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the URI of the URI-reference.
  	
  
  	
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the \{name\} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		\{name\} property of the ancestor component. The URI provided by
! 		the namespace name of the \{name\} property is combined with a
! 		fragment identifier, where the fragment identifier is typically
! 		constructed from the \{name\} property of the component and the
! 		\{name\} properties of its ancestors as a path according to
! 		\hyperlink{uriRefFragTable}{Table \ref*{uriRefFragTable} }. 
! 		In that table the first column gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
--- 8448,8460 ----
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the target namespace of the WSDL document.
  	
  
  	
! 		The fragment identifier is typically constructed from the \{name\}
! 		property of the component and the \{name\} properties of its
! 		ancestors as a path according to
! 		\hyperlink{frag-ids-table}{Table \ref*{frag-ids-table} }.
! 	    The first column of this table gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
***************
*** 8610,8614 ****
  
  	\begin{longtable}{|p{54pt}|p{36pt}|p{36pt}|p{36pt}|p{36pt}|p{162pt}|}
! \caption{Rules for determining pointer parts for WSDL components\label{uriRefFragTable}}\\
  \hline
  
--- 8466,8470 ----
  
  	\begin{longtable}{|p{54pt}|p{36pt}|p{36pt}|p{36pt}|p{36pt}|p{162pt}|}
! \caption{Rules for determining pointer parts for WSDL components\label{frag-ids-table}}\\
  \hline
  
***************
*** 8733,8740 ****
            \href{#wsdl.property}{wsdl.property(parent/property)}
  	\\ \hline 
        \end{longtable}
  
        Note that the above rules are defined in terms of component
!       properties rather the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.
--- 8589,8606 ----
            \href{#wsdl.property}{wsdl.property(parent/property)}
  	\\ \hline 
+ 	
        \end{longtable}
  
+ 	
+ 		WSDL is extensible and it is possible for an
+ 		extension to define new components types. The XPointer Framework
+ 		scheme for extension components is:
+ 	
+ 
+ 	\href{#wsdl.extension}{wsdl.extension(extension-namespace, extension-specific-syntax)}
+ 	
+ 
        Note that the above rules are defined in terms of component
!       properties rather than the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.
***************
*** 8892,8919 ****
        \end{enumerate}
        
        
  
! 	\hypertarget{extension-elements}{}
! \section{Extension Elements}\label{extension-elements}
  
  	
  	
! 	WSDL has an open content model. It is therefore possible for an
! 	extension to define new components. The XPointer
! 	Framework scheme for components added by extensions is:
  	
  	
! 	wsdl.extension(extension-namespace, extension-specific-syntax)
  	
  	
! 	where extension-namespace is the namespace that identifies the
! 	extension, e.g. for SOAP the namespace is
! 	http://www.w3.org/2003/06/wsdl/soap12, and
! 	extension-specific-syntax is defined by the extension. The owner
! 	of the extension must define any components contributed by the
! 	extension and a syntax for identifying them.
  	
  	
  
  	\hypertarget{Uri-ref-ex}{}
  \section{Example}\label{Uri-ref-ex}
--- 8758,8934 ----
        \end{enumerate}
        
+ 
+       \hypertarget{wsdl.extension}{}
+ \subsection{wsdl.extension(\textit{extension-namespace}, \textit{extension-specific-syntax})}\label{wsdl.extension}
+ 
+       	
+       	\begin{enumerate}
+       		\item 
+       			
+       				\textit{extension-namespace}
+       			
+       			is the namespace that identifies the extension, e.g.
+       			for SOAP the namespace is
+       			http://www.w3.org/2003/06/wsdl/soap12.
+       		
+       		\item 
+       			
+       				\textit{extension-specific-syntax}
+       			
+       			is defined by the extension. The owner of the
+       			extension must define any components contributed by
+       			the extension and a syntax for identifying them.
+       		
+       	\end{enumerate}
        
+ 	
+     
+     \hypertarget{ietf-sec}{}
+ \section{Security considerations}\label{ietf-sec}
  
!     
!     
!   This media type uses the {\tt "+xml"} convention, it shares
!   the same security considerations as described in
!   \hyperlink{RFC3023}{[\textit{RFC 3023}]}, section 10.
! 
!     
!         
!     
! 
!     
! \hypertarget{acknowledgments}{}
! \chapter{Acknowledgements (Non-Normative)}\label{acknowledgments}
! 
! 
! This document is the work of the \href{http://www.w3.org/2002/ws/desc/}{W3C Web Service
!       Description Working Group}.
! Members of the Working Group are (at the time of writing, and by
!       alphabetical order):
!       David Booth
! 	(W3C), Allen Brookes
! 	(Rogue Wave Softwave), Helen Chen
! 	(Agfa-Gevaert N. V.), Roberto Chinnici
! 	(Sun Microsystems), Ugo Corda
! 	(SeeBeyond), Glen Daniels
! 	(Sonic Software), Paul Downey
! 	(British Telecommunications), Youenn Fablet
! 	(Canon), Martin Gudgin
! 	(Microsoft Corporation), Hugo Haas
! 	(W3C), Hao He
! 	(The Thomson Corporation), Tom Jordahl
! 	(Macromedia), Jacek Kopecky
! 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
! 	(TIBCO Software, Inc.), Kevin Canyang Liu
! 	(SAP), Jonathan Marsh
! 	(Microsoft Corporation), Peter Madziak
! 	(Agfa-Gevaert N. V.), Josephine Micallef
! 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
! 	(Oracle Corporation), Dale Moberg
! 	(Cyclone Commerce), Jean-Jacques Moreau
! 	(Canon), Mark Nottingham
! 	(BEA Systems, Inc.), David Orchard
! 	(BEA Systems, Inc.), Bijan Parsia
! 	(University of Maryland), Arthur Ryman
! 	(IBM), Adi Sakala
! 	(IONA Technologies), Jeffrey Schlimmer
! 	(Microsoft Corporation), Igor Sedukhin
! 	(Computer Associates), Jerry Thrasher
! 	(Lexmark), William Vambenepe
! 	(Hewlett-Packard Company), Asir Vedamuthu
! 	(webMethods, Inc.), Sanjiva Weerawarana
! 	(IBM), \"{U}mit Yal\c{c}{\i}nalp
! 	(Oracle Corporation), Prasad Yendluri
! 	(webMethods, Inc.).
! Previous members were:
!       Lily Liu
! 	(webMethods, Inc.), Don Wright
! 	(Lexmark), Joyce Yang
! 	(Oracle Corporation), Daniel Schutzer
! 	(Citigroup), Dave Solo
! 	(Citigroup), Stefano Pogliani
! 	(Sun Microsystems), William Stumbo
! 	(Xerox), Stephen White
! 	(SeeBeyond), Barbara Zengler
! 	(DaimlerChrysler Research and Technology), Tim Finin
! 	(University of Maryland), Laurent De Teneuille
! 	(L'Echangeur), Johan Pauhlsson
! 	(L'Echangeur), Mark Jones
! 	(AT\&T), Steve Lind
! 	(AT\&T), Sandra Swearingen
! 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H\'{e}garet
! 	(W3C), Jim Hendler
! 	(University of Maryland), Dietmar Gaertner
! 	(Software AG), Michael Champion
! 	(Software AG), Don Mullen
! 	(TIBCO Software, Inc.), Steve Graham
! 	(Global Grid Forum), Steve Tuecke
! 	(Global Grid Forum), Michael Mahan
! 	(Nokia), Bryan Thompson
! 	(Hicks \& Associates), Ingo Melzer
! 	(DaimlerChrysler Research and Technology), Sandeep Kumar
! 	(Cisco Systems), Alan Davies
! 	(SeeBeyond), Jacek Kopecky
! 	(Systinet), Mike Ballantyne
! 	(Electronic Data Systems), Mike Davoren
! 	(W. W. Grainger), Dan Kulp
! 	(IONA Technologies), Mike McHugh
! 	(W. W. Grainger), Michael Mealling
! 	(Verisign), Waqar Sadiq
! 	(Electronic Data Systems), Yaron Goland
! 	(BEA Systems, Inc.).
! The people who have contributed to \href{http://lists.w3.org/Archives/Public/www-ws-desc/}{discussions
!       on www-ws-desc@w3.org} are also gratefully
!       acknowledged.
! 
! 
! 
!     \hypertarget{wsdl-uri-references}{}
! \chapter{URI References for WSDL Components (Non-Normative)}\label{wsdl-uri-references}
  
  	
+ 
  	
! 		This appendix provides a syntax for URI references for all
! 		components found in a WSDL document. The URI references are easy
! 		to understand and compare, while imposing no burden on the WSDL
! 		author.
! 	
! 
! 	\hypertarget{wsdl-uris}{}
! \section{WSDL URIs}\label{wsdl-uris}
! 
  	
+ 	There are two main cases for WSDL URIs:
+ 	\begin{itemize}
+ 	\item the URI of a WSDL document
+ 	\item the URI of a WSDL namespace
+ 	\end{itemize}
  	
! 		The URI of a WSDL document can be dereferenced to give a
! 		resource representation that contributes component definitions
! 		to a single WSDL namespace. If the media type is set to the WSDL
! 		media type, then the fragment identifiers can be used to
! 		identify the main components that are defined in the document.
  	
+ 
  	
! 		However, in keeping with the recommendation in
! 		\hyperlink{Description_details}{\textbf{\ref*{Description_details} The Description Component}}
! 		that the namespace URI be dereferencible to a WSDL document,
! 		this appendix specifies the use of the namespace URI with the
! 		WSDL fragment identifiers to form a URI-reference.
  	
+ 
+ 	
+ 		The URI in a URI-reference for a WSDL component is the namespace
+ 		name of the \{name\} property of either the component itself, in
+ 		the case of Interface, Binding, and Service components, or the
+ 		\{name\} property of the ancestor component. The URI provided by
+ 		the namespace name of the \{name\} property is combined with a
+ 		fragment identifier as defined in \hyperlink{frag-ids}{\textbf{\ref*{frag-ids} Fragment Identifiers}}.
  	
  
+ 	
  	\hypertarget{Uri-ref-ex}{}
  \section{Example}\label{Uri-ref-ex}
***************
*** 8959,8963 ****
  
  
! Its conceptual elements have the following URI-references:
  
  
--- 8974,8978 ----
  
  
! Its components have the following URI-references:
  
  
***************
*** 9261,9266 ****
--- 9276,9294 ----
        \multicolumn{1}{|c|}{\bf Description}
      \\ \hline 
+     
+     
+     	20050416&
+     	AGR&
+     	Moved the \href{#frag-ids}{fragment identifer} definition into the media registration appendix.
+     \\ \hline 
  
      
+     	20050414&
+     	JJM&
+     	
+     		Fixed XML Schema P1/P2 version listed in the bibliograpy section.
+     	
+     \\ \hline 
+     
      	20050413&
      	AGR&

Index: wsdl20.toc
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.toc,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -d -r1.18 -r1.19
*** wsdl20.toc	14 Apr 2005 02:07:18 -0000	1.18
--- wsdl20.toc	16 Apr 2005 23:40:23 -0000	1.19
***************
*** 156,197 ****
  \contentsline {chapter}{\numberline {A}The application/wsdl+xml Media Type}{124}{appendix.A}
  \contentsline {section}{\numberline {A.1}Registration}{124}{section.A.1}
! \contentsline {section}{\numberline {A.2}Security considerations}{125}{section.A.2}
! \contentsline {chapter}{\numberline {B}Acknowledgements (Non-Normative)}{126}{appendix.B}
! \contentsline {chapter}{\numberline {C}URI References for WSDL Components (Non-Normative)}{128}{appendix.C}
! \contentsline {section}{\numberline {C.1}WSDL URIs}{128}{section.C.1}
! \contentsline {section}{\numberline {C.2}Fragment Identifiers}{129}{section.C.2}
! \contentsline {subsection}{\numberline {C.2.1}wsdl.interface(\textit {interface})}{130}{subsection.C.2.1}
! \contentsline {subsection}{\numberline {C.2.2}wsdl.interfaceFault(\textit {interface}/\textit {fault})}{130}{subsection.C.2.2}
! \contentsline {subsection}{\numberline {C.2.3}wsdl.interfaceOperation(\textit {interface}/\textit {operation})}{131}{subsection.C.2.3}
! \contentsline {subsection}{\numberline {C.2.4}wsdl.messageReference(\textit {interface}/\textit {operation}/\textit {message})}{131}{subsection.C.2.4}
! \contentsline {subsection}{\numberline {C.2.5}wsdl.faultReference(\textit {interface}/\textit {operation}/\textit {message}/\textit {fault})}{131}{subsection.C.2.5}
! \contentsline {subsection}{\numberline {C.2.6}wsdl.binding(\textit {binding})}{131}{subsection.C.2.6}
! \contentsline {subsection}{\numberline {C.2.7}wsdl.bindingFault(\textit {binding}/\textit {fault})}{131}{subsection.C.2.7}
! \contentsline {subsection}{\numberline {C.2.8}wsdl.bindingOperation(\textit {binding}/\textit {operation})}{132}{subsection.C.2.8}
! \contentsline {subsection}{\numberline {C.2.9}wsdl.bindingMessageReference(\textit {binding}/\textit {operation}/\textit {message})}{132}{subsection.C.2.9}
! \contentsline {subsection}{\numberline {C.2.10}wsdl.bindingFaultReference(\textit {binding}/\textit {operation}/\textit {fault}/\textit {message})}{132}{subsection.C.2.10}
! \contentsline {subsection}{\numberline {C.2.11}wsdl.service(\textit {service})}{132}{subsection.C.2.11}
! \contentsline {subsection}{\numberline {C.2.12}wsdl.endpoint(\textit {service}/\textit {endpoint})}{133}{subsection.C.2.12}
! \contentsline {subsection}{\numberline {C.2.13}wsdl.feature(\textit {parent}/\textit {feature})}{133}{subsection.C.2.13}
! \contentsline {subsection}{\numberline {C.2.14}wsdl.property(\textit {parent}/\textit {property})}{133}{subsection.C.2.14}
! \contentsline {section}{\numberline {C.3}Extension Elements}{133}{section.C.3}
! \contentsline {section}{\numberline {C.4}Example}{133}{section.C.4}
! \contentsline {chapter}{\numberline {D}Migrating from WSDL 1.1 to WSDL 2.0 (Non-Normative)}{135}{appendix.D}
! \contentsline {section}{\numberline {D.1}Operation Overloading}{135}{section.D.1}
! \contentsline {section}{\numberline {D.2}PortTypes}{135}{section.D.2}
! \contentsline {section}{\numberline {D.3}Ports}{135}{section.D.3}
! \contentsline {section}{\numberline {D.4}Single Interface per Service}{135}{section.D.4}
! \contentsline {chapter}{\numberline {E}Examples of Specifications of Extension Elements for Alternative Schema Language Support. (Non-Normative)}{137}{appendix.E}
! \contentsline {section}{\numberline {E.1}DTD}{137}{section.E.1}
! \contentsline {subsection}{\numberline {E.1.1}\texttt {namespace} \textit {attribute information item}}{138}{subsection.E.1.1}
! \contentsline {subsection}{\numberline {E.1.2}\texttt {location} \textit {attribute information item}}{138}{subsection.E.1.2}
! \contentsline {subsection}{\numberline {E.1.3}References to Element Definitions}{138}{subsection.E.1.3}
! \contentsline {section}{\numberline {E.2}RELAX NG}{138}{section.E.2}
! \contentsline {subsection}{\numberline {E.2.1}Importing RELAX NG}{139}{subsection.E.2.1}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{139}{section*.48}
! \contentsline {subsubsection}{\texttt {href} \textit {attribute information item}}{139}{section*.49}
! \contentsline {subsection}{\numberline {E.2.2}Embedding RELAX NG}{140}{subsection.E.2.2}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{140}{section*.50}
! \contentsline {subsection}{\numberline {E.2.3}References to Element Declarations}{140}{subsection.E.2.3}
! \contentsline {chapter}{\numberline {F}Part 1 Change Log (Non-Normative)}{141}{appendix.F}
! \contentsline {section}{\numberline {F.1}WSDL Specification Changes}{141}{section.F.1}
--- 156,197 ----
  \contentsline {chapter}{\numberline {A}The application/wsdl+xml Media Type}{124}{appendix.A}
  \contentsline {section}{\numberline {A.1}Registration}{124}{section.A.1}
! \contentsline {section}{\numberline {A.2}Fragment Identifiers}{125}{section.A.2}
! \contentsline {subsection}{\numberline {A.2.1}wsdl.interface(\textit {interface})}{127}{subsection.A.2.1}
! \contentsline {subsection}{\numberline {A.2.2}wsdl.interfaceFault(\textit {interface}/\textit {fault})}{127}{subsection.A.2.2}
! \contentsline {subsection}{\numberline {A.2.3}wsdl.interfaceOperation(\textit {interface}/\textit {operation})}{127}{subsection.A.2.3}
! \contentsline {subsection}{\numberline {A.2.4}wsdl.messageReference(\textit {interface}/\textit {operation}/\textit {message})}{127}{subsection.A.2.4}
! \contentsline {subsection}{\numberline {A.2.5}wsdl.faultReference(\textit {interface}/\textit {operation}/\textit {message}/\textit {fault})}{127}{subsection.A.2.5}
! \contentsline {subsection}{\numberline {A.2.6}wsdl.binding(\textit {binding})}{128}{subsection.A.2.6}
! \contentsline {subsection}{\numberline {A.2.7}wsdl.bindingFault(\textit {binding}/\textit {fault})}{128}{subsection.A.2.7}
! \contentsline {subsection}{\numberline {A.2.8}wsdl.bindingOperation(\textit {binding}/\textit {operation})}{128}{subsection.A.2.8}
! \contentsline {subsection}{\numberline {A.2.9}wsdl.bindingMessageReference(\textit {binding}/\textit {operation}/\textit {message})}{128}{subsection.A.2.9}
! \contentsline {subsection}{\numberline {A.2.10}wsdl.bindingFaultReference(\textit {binding}/\textit {operation}/\textit {fault}/\textit {message})}{128}{subsection.A.2.10}
! \contentsline {subsection}{\numberline {A.2.11}wsdl.service(\textit {service})}{129}{subsection.A.2.11}
! \contentsline {subsection}{\numberline {A.2.12}wsdl.endpoint(\textit {service}/\textit {endpoint})}{129}{subsection.A.2.12}
! \contentsline {subsection}{\numberline {A.2.13}wsdl.feature(\textit {parent}/\textit {feature})}{129}{subsection.A.2.13}
! \contentsline {subsection}{\numberline {A.2.14}wsdl.property(\textit {parent}/\textit {property})}{129}{subsection.A.2.14}
! \contentsline {subsection}{\numberline {A.2.15}wsdl.extension(\textit {extension-namespace}, \textit {extension-specific-syntax})}{129}{subsection.A.2.15}
! \contentsline {section}{\numberline {A.3}Security considerations}{129}{section.A.3}
! \contentsline {chapter}{\numberline {B}Acknowledgements (Non-Normative)}{130}{appendix.B}
! \contentsline {chapter}{\numberline {C}URI References for WSDL Components (Non-Normative)}{132}{appendix.C}
! \contentsline {section}{\numberline {C.1}WSDL URIs}{132}{section.C.1}
! \contentsline {section}{\numberline {C.2}Example}{133}{section.C.2}
! \contentsline {chapter}{\numberline {D}Migrating from WSDL 1.1 to WSDL 2.0 (Non-Normative)}{134}{appendix.D}
! \contentsline {section}{\numberline {D.1}Operation Overloading}{134}{section.D.1}
! \contentsline {section}{\numberline {D.2}PortTypes}{134}{section.D.2}
! \contentsline {section}{\numberline {D.3}Ports}{134}{section.D.3}
! \contentsline {section}{\numberline {D.4}Single Interface per Service}{134}{section.D.4}
! \contentsline {chapter}{\numberline {E}Examples of Specifications of Extension Elements for Alternative Schema Language Support. (Non-Normative)}{136}{appendix.E}
! \contentsline {section}{\numberline {E.1}DTD}{136}{section.E.1}
! \contentsline {subsection}{\numberline {E.1.1}\texttt {namespace} \textit {attribute information item}}{137}{subsection.E.1.1}
! \contentsline {subsection}{\numberline {E.1.2}\texttt {location} \textit {attribute information item}}{137}{subsection.E.1.2}
! \contentsline {subsection}{\numberline {E.1.3}References to Element Definitions}{137}{subsection.E.1.3}
! \contentsline {section}{\numberline {E.2}RELAX NG}{137}{section.E.2}
! \contentsline {subsection}{\numberline {E.2.1}Importing RELAX NG}{138}{subsection.E.2.1}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{138}{section*.48}
! \contentsline {subsubsection}{\texttt {href} \textit {attribute information item}}{138}{section*.49}
! \contentsline {subsection}{\numberline {E.2.2}Embedding RELAX NG}{139}{subsection.E.2.2}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{139}{section*.50}
! \contentsline {subsection}{\numberline {E.2.3}References to Element Declarations}{139}{subsection.E.2.3}
! \contentsline {chapter}{\numberline {F}Part 1 Change Log (Non-Normative)}{140}{appendix.F}
! \contentsline {section}{\numberline {F.1}WSDL Specification Changes}{140}{section.F.1}

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.203
retrieving revision 1.204
diff -C2 -d -r1.203 -r1.204
*** wsdl20.xml	15 Apr 2005 21:07:55 -0000	1.203
--- wsdl20.xml	16 Apr 2005 23:40:23 -0000	1.204
***************
*** 2156,2160 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <specref ref='wsdl-uri-references' />). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 2156,2160 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <specref ref='frag-ids' />). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 2504,2508 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <specref ref='wsdl-uri-references' />). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 2504,2508 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <specref ref='frag-ids' />). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 6156,6160 ****
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <specref ref='wsdl-uri-references' />).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
--- 6156,6160 ----
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <specref ref='frag-ids' />).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
***************
*** 8306,8310 ****
            <attval>application/xml</attval> as described in <bibref
            ref="RFC3023"/>, section 5 or the syntax defined in <specref
!           ref="wsdl-uri-references"/>.</p></def>
         </gitem>
  
--- 8306,8310 ----
            <attval>application/xml</attval> as described in <bibref
            ref="RFC3023"/>, section 5 or the syntax defined in <specref
!           ref="frag-ids"/>.</p></def>
         </gitem>
  
***************
*** 8336,8396 ****
       
       </glist>
  
-     </div2>
-     
-     <div2 id="ietf-sec">
-     <head>Security considerations</head>
-     
-   <p>This media type uses the <attval>+xml</attval> convention, it shares
-   the same security considerations as described in
-   <bibref ref="RFC3023"/>, section 10.</p>
- 
-     </div2>
-         
-     </div1>
- 
-     &acknowledgements;
- 
-     <inform-div1 id="wsdl-uri-references">
- 	<head>URI References for WSDL Components</head>
- 
- 	<p> This appendix provides a syntax for URI references for
- 	named components found in a WSDL document. This includes the
- 	top level components: Interface, Binding and Service and the
- 	subordinate components: Interface Operation, Interface Fault, 
- 	Message Reference, Fault Reference, Feature, Property,
- 	Binding Operation, Binding Fault, Binding Message Reference
- 	and Endpoint. The
- 	URI references are easy to understand and compare, while
- 	imposing no burden on the WSDL author.</p>
- 
- 	<div2 id="wsdl-uris">
- 	<head>WSDL URIs</head>
- 	<p>
- 	There are two main cases for WSDL URIs: 
- 	</p>
- 	<ulist>
- 	<item><p>the URI of a WSDL document</p></item>
- 	<item><p>the URI of a WSDL namespace</p></item>
- 	</ulist>
- 	<p>
- 	The URI of a WSDL document can be dereferenced to give a resource
- 	representation that contributes component definitions to a single
- 	WSDL namespace. If the media type is set to the WSDL media type,
- 	then the fragment identifiers can be used to identify the
- 	main components that are defined in the document. 
- 	</p>
- 
- 	<p> However, in keeping with the recommendation in <specref
-         ref="Description_details"/> that the namespace URI be
-         dereferencible to a WSDL document, this appendix specifies the
-         use of the namespace URI with the WSDL fragment identifiers to
-         form a URI-reference.</p>
- 
- 	</div2>
  	<div2 id="frag-ids">
  	<head>Fragment Identifiers</head>
  	<p>
! 	The following fragment identifier syntax is compliant with the
  	<bibref ref="XPTR"/>.
  	</p>
--- 8336,8346 ----
       
       </glist>
+      </div2>
  
  	<div2 id="frag-ids">
  	<head>Fragment Identifiers</head>
  	<p>
! 	This section defined a fragment identifier syntax for identifying components of a WSDL document.
! 	This fragment identifier syntax is compliant with the
  	<bibref ref="XPTR"/>.
  	</p>
***************
*** 8399,8408 ****
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names are of type either QName, NCName,
! 	URI, or Pointer Part, depending on the context.
  	</p>
  	<p>
--- 8349,8358 ----
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the standard WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names in the path are of type either QName, NCName,
! 	URI, or Pointer Part depending on the context.
  	</p>
  	<p>
***************
*** 8410,8427 ****
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the URI of the URI-reference.
  	</p>
  
  	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier, where the fragment identifier is typically
! 		constructed from the {name} property of the component and the
! 		{name} properties of its ancestors as a path according to
! 		<specref ref="uriRefFragTable" />. 
! 		In that table the first column gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
--- 8360,8372 ----
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the target namespace of the WSDL document.
  	</p>
  
  	<p>
! 		The fragment identifier is typically constructed from the {name}
! 		property of the component and the {name} properties of its
! 		ancestors as a path according to
! 		<specref ref="frag-ids-table" />.
! 	    The first column of this table gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
***************
*** 8432,8436 ****
  	</p>
  
! 	<table id="uriRefFragTable" border="1">
  	  <caption>Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" />
--- 8377,8381 ----
  	</p>
  
! 	<table id="frag-ids-table" border="1">
  	  <caption>Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" />
***************
*** 8561,8569 ****
            <td><loc href="#wsdl.property"><code>wsdl.property(<emph>parent</emph>/<emph>property</emph>)</code></loc></td>
  	</tr>
        </tbody>
        </table>
  
        <p>Note that the above rules are defined in terms of component
!       properties rather the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
--- 8506,8524 ----
            <td><loc href="#wsdl.property"><code>wsdl.property(<emph>parent</emph>/<emph>property</emph>)</code></loc></td>
  	</tr>
+ 	
        </tbody>
        </table>
  
+ 	<p>
+ 		WSDL is extensible and it is possible for an
+ 		extension to define new components types. The XPointer Framework
+ 		scheme for extension components is:
+ 	</p>
+ 
+ 	<p><loc href="#wsdl.extension"><code>wsdl.extension(<emph>extension-namespace</emph>, <emph>extension-specific-syntax</emph>)</code></loc>
+ 	</p>
+ 
        <p>Note that the above rules are defined in terms of component
!       properties rather than the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
***************
*** 8693,8718 ****
        </olist>
        </div3>
-       </div2>
  
! 	<div2 id="extension-elements">
! 	<head>Extension Elements</head>
  	<p>
! 	WSDL has an open content model. It is therefore possible for an
! 	extension to define new components. The XPointer
! 	Framework scheme for components added by extensions is:
  	</p>
! 	<p><code>
! 	wsdl.extension(extension-namespace, extension-specific-syntax)</code>
  	</p>
  	<p>
! 	where extension-namespace is the namespace that identifies the
! 	extension, e.g. for SOAP the namespace is
! 	http://www.w3.org/2003/06/wsdl/soap12, and
! 	extension-specific-syntax is defined by the extension. The owner
! 	of the extension must define any components contributed by the
! 	extension and a syntax for identifying them.
  	</p>
- 	</div2>
  
  	<div2 id="Uri-ref-ex">
  	<head>Example</head>
--- 8648,8731 ----
        </olist>
        </div3>
  
!       <div3 id="wsdl.extension">
!       	<head><code>wsdl.extension(<emph>extension-namespace</emph>, <emph>extension-specific-syntax</emph>)</code></head>
!       	<olist>
!       		<item>
!       			<code>
!       				<emph>extension-namespace</emph>
!       			</code>
!       			is the namespace that identifies the extension, e.g.
!       			for SOAP the namespace is
!       			http://www.w3.org/2003/06/wsdl/soap12.
!       		</item>
!       		<item>
!       			<code>
!       				<emph>extension-specific-syntax</emph>
!       			</code>
!       			is defined by the extension. The owner of the
!       			extension must define any components contributed by
!       			the extension and a syntax for identifying them.
!       		</item>
!       	</olist>
!       </div3>
! 	</div2>
!     
!     <div2 id="ietf-sec">
!     <head>Security considerations</head>
!     
!   <p>This media type uses the <attval>+xml</attval> convention, it shares
!   the same security considerations as described in
!   <bibref ref="RFC3023"/>, section 10.</p>
! 
!     </div2>
!         
!     </div1>
! 
!     &acknowledgements;
! 
!     <inform-div1 id="wsdl-uri-references">
! 	<head>URI References for WSDL Components</head>
! 
  	<p>
! 		This appendix provides a syntax for URI references for all
! 		components found in a WSDL document. The URI references are easy
! 		to understand and compare, while imposing no burden on the WSDL
! 		author.
  	</p>
! 
! 	<div2 id="wsdl-uris">
! 	<head>WSDL URIs</head>
! 	<p>There are two main cases for WSDL URIs:</p>
! 	<ulist>
! 	<item><p>the URI of a WSDL document</p></item>
! 	<item><p>the URI of a WSDL namespace</p></item>
! 	</ulist>
! 	<p>
! 		The URI of a WSDL document can be dereferenced to give a
! 		resource representation that contributes component definitions
! 		to a single WSDL namespace. If the media type is set to the WSDL
! 		media type, then the fragment identifiers can be used to
! 		identify the main components that are defined in the document.
  	</p>
+ 
  	<p>
! 		However, in keeping with the recommendation in
! 		<specref ref="Description_details" />
! 		that the namespace URI be dereferencible to a WSDL document,
! 		this appendix specifies the use of the namespace URI with the
! 		WSDL fragment identifiers to form a URI-reference.
! 	</p>
! 
! 	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier as defined in <specref ref="frag-ids" />.
  	</p>
  
+ 	</div2>
  	<div2 id="Uri-ref-ex">
  	<head>Example</head>
***************
*** 8756,8760 ****
  </example>
  <p>
! Its conceptual elements have the following URI-references:</p>
  
  <example id="uri-ref-example-uris">
--- 8769,8773 ----
  </example>
  <p>
! Its components have the following URI-references:</p>
  
  <example id="uri-ref-example-uris">
***************
*** 9023,9026 ****
--- 9036,9045 ----
        <th>Description</th>
      </tr>
+     
+     <tr>
+     	<td>20050416</td>
+     	<td>AGR</td>
+     	<td>Moved the <loc href="#frag-ids">fragment identifer</loc> definition into the media registration appendix.</td>
+     </tr>
  
      <tr>

Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** wsdl20-z.html	14 Apr 2005 02:12:26 -0000	1.13
--- wsdl20-z.html	16 Apr 2005 23:40:21 -0000	1.14
***************
*** 96,100 ****
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.2 <a href="#Binding_Fault_Reference_messageLabel_attribute">messageLabel attribute information item with infault or
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.3 <a href="#Binding_Fault_Reference_extension_elements">Binding Fault Reference extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.3 <a href="#Binding_Fault_Reference_Mapping">Mapping Binding Fault Reference's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.14 <a href="#Service">Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1 <a href="#Service_details">The Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1.1 <a href="#Service_OperationName">Operation Name Mapping Requirement</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2 <a href="#Service_XMLRep">XML Representation of Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.1 <a href="#Service_name_attribute">name attribute information item with service [ower]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.2 <a href="#Service_interface_attribute">interface attribute information item with service [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.3 <a href="#Service_Mapping">Mapping Service's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.15 <a href="#Endpoint">Endpoint</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.1 <a href="#Endpoint_details">The Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2 <a href="#Endpoint_XMLRep">XML Representation of Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.1 <a href="#Endpoint_name_attribute">name attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.2 <a href="#Endpoint_binding_attribute">binding attribute information item with endpoint [owner]</a><br>&nbsp;&nsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.3 <a href="#Endpoint_address_attribute">address attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.4 <a href="#Endpoint_extension_elements">Endpoint extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.3 <a href="#Endpoint_Mapping">Mapping Endpoint's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.16 <a href="#simpletypes">XML Schema 1.0 Simple Types Used in the Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.1 <a href="#ncname_type">NCName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.2 <a href="#anyuri_type">anyURI Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.3 <a href="#qname_type">QName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.4 <a href="#boolean_type">boolean Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.17 <a href="compequiv">Equivalence of Components</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.18 <a href="#symbolspaces">Symbol Spaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.19 <a href="#qnameres">QName resolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.20 <a href="#uricompare">Comparing URIs</a><br>3. <a href="#eii-types">Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#xsd-types">Using W3C XML Schema Description Language</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#import-xsd">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.1 <a href="#namespace-attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.2 <a href="#schemaLocation-attribute">schemaLocation attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#embed-xsd">Embedding XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2.1 <a href="#targetamespace-attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href="#references-definitions">References to Element Declarations and Type Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#other-types">Using Other Schema Languages</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#includes">Including Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#imports">Importing Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner]</a><br>5. <a href="#eii-documentation">Documentation</a><r>6. <a href="#language-extensibility">Language Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#eii-extensibility">Element based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.2 <a href="#required-aii">required attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#markup">Document Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10.<a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#ietf-reg">Registration</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.2 <a href="#ietf-sec">Security considerations</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>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#wsdl-uris">WSDL URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#frag-ids">Fragment Identifiers</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.1 <a href="#wsdl.interface">wsdl.interface(interface)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.2 <a href="#wsdl.interfaceFault">wsdl.interfaceFault(interface/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.3 <a href="#wsdl.interfaceOperation">wsdl.interfaceOperation(interface/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbspC.2.4 <a href="#wsdl.messageReference">wsdl.messageReference(interface/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.5 <a href="#wsdl.faultReference">wsdl.faultReference(interface/operation/message/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.6 <a href="#wsdl.binding">wsdl.binding(binding)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.7 <a href="#wsdl.bindingFault">wsdl.bindingFault(binding/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.8 <a href="#wsdl.bindingOperation">wsdl.bindingOperation(binding/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.9 <a href="#wsdl.bindingMessageReference">wsdl.bindingMessageReference(binding/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.10 <a href="#wsdl.bindingFaultReference">wsdl.bindingFaultReference(binding/operation/fault/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.11 <a href="#wsdl.service">wsdl.service(servce)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.12 <a href="#wsdl.endpoint">wsdl.endpoint(service/endpoint)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.13 <a href="#wsdl.feature">wsdl.feature(parent/feature)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.14 <a href="#wsdl.property">wsdl.property(parent/property)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#extension-elements">Extension Elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#Uri-ref-ex">Example</a><br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;D.1 <a href="#mig_ops">Operation Overloading</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.2 <a href="#mig_porttypes">PortTypes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.3 <a href="#mig_ports">Ports</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.4 <a href="#single_interface_per_service">Single Interface per Service</a><br>E. <a href="#other-schemalang">Examples of Specifications of Extension Elements for Alternative Schema
  Language Support.</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;E.1 <a href="#dtd">DTD</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.1 <a href="#dtd-namespaceaii">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.2 <a href="#dtd-locationaii">location attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.3 <a href="#dtd-ref">References to Element Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;E.2 <a href="#relax">RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1 <a href="#import-relax">Importing RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.1 <a href="#relax-import-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.2 <a href="#relax-import-hrefaii">href attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2 <a href="#relax-embed">Embedding RELAX NG</a<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2.1 <a href="#relax-embed-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.3 <a href="#relax-ref">References to Element Declarations</a><br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;F.1 <a href="#wsdl-changelog">WSDL Specification Changes</a><br></p></div><hr><div class="body">
  
--- 96,100 ----
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.2 <a href="#Binding_Fault_Reference_messageLabel_attribute">messageLabel attribute information item with infault or
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.3 <a href="#Binding_Fault_Reference_extension_elements">Binding Fault Reference extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.3 <a href="#Binding_Fault_Reference_Mapping">Mapping Binding Fault Reference's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.14 <a href="#Service">Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1 <a href="#Service_details">The Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1.1 <a href="#Service_OperationName">Operation Name Mapping Requirement</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2 <a href="#Service_XMLRep">XML Representation of Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.1 <a href="#Service_name_attribute">name attribute information item with service [ower]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.2 <a href="#Service_interface_attribute">interface attribute information item with service [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.3 <a href="#Service_Mapping">Mapping Service's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.15 <a href="#Endpoint">Endpoint</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.1 <a href="#Endpoint_details">The Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2 <a href="#Endpoint_XMLRep">XML Representation of Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.1 <a href="#Endpoint_name_attribute">name attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.2 <a href="#Endpoint_binding_attribute">binding attribute information item with endpoint [owner]</a><br>&nbsp;&nsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.3 <a href="#Endpoint_address_attribute">address attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.4 <a href="#Endpoint_extension_elements">Endpoint extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.3 <a href="#Endpoint_Mapping">Mapping Endpoint's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.16 <a href="#simpletypes">XML Schema 1.0 Simple Types Used in the Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.1 <a href="#ncname_type">NCName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.2 <a href="#anyuri_type">anyURI Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.3 <a href="#qname_type">QName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.4 <a href="#boolean_type">boolean Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.17 <a href="compequiv">Equivalence of Components</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.18 <a href="#symbolspaces">Symbol Spaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.19 <a href="#qnameres">QName resolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.20 <a href="#uricompare">Comparing URIs</a><br>3. <a href="#eii-types">Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#xsd-types">Using W3C XML Schema Description Language</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#import-xsd">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.1 <a href="#namespace-attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.2 <a href="#schemaLocation-attribute">schemaLocation attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#embed-xsd">Embedding XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2.1 <a href="#targetamespace-attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href="#references-definitions">References to Element Declarations and Type Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#other-types">Using Other Schema Languages</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#includes">Including Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#imports">Importing Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner]</a><br>5. <a href="#eii-documentation">Documentation</a><r>6. <a href="#language-extensibility">Language Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#eii-extensibility">Element based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.2 <a href="#required-aii">required attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#markup">Document Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10.<a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#ietf-reg">Registration</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.2 <a href="#frag-ids">Fragment Identifiers</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#wsdl.interface">wsdl.interface(interface)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.2 <a href="#wsdl.interfaceFault">wsdl.interfaceFault(interface/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.3 <a href="#wsdl.interfaceOperation">wsdl.interfaceOperation(interface/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.4 <a href="#wsdl.messageReference">wsdl.messageReference(interface/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.5 <a href="#wsdl.faultReference">wsdl.faultReference(interface/operation/message/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.6 <a href=#wsdl.binding">wsdl.binding(binding)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.7 <a href="#wsdl.bindingFault">wsdl.bindingFault(binding/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.8 <a href="#wsdl.bindingOperation">wsdl.bindingOperation(binding/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.9 <a href="#wsdl.bindingMessageReference">wsdl.bindingMessageReference(binding/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.10 <a href="#wsdl.bindingFaultReference">wsdl.bindingFaultReference(binding/operation/fault/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.11 <a href="#wsdl.service">wsdl.service(service)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.12 <a href="#wsdl.endpoint">wsdl.endpoint(service/endpoint)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.13 <a href="#wsdl.feature">wsdl.feature(parent/feature)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.14 <a hre="#wsdl.property">wsdl.property(parent/property)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.15 <a href="#wsdl.extension">wsdl.extension(extension-namespace, extension-specific-syntax)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.3 <a href="#ietf-sec">Security considerations</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>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#wsdl-uris">WSDL URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#Uri-ref-ex">Example</a><br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;D.1 <a href="#mig_ops">Operation Overloading</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.2 <a href="#mig_porttypes">PortTypes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.3 <a href="#mig_ports">Ports</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.4 <a href="#single_interface_per_service">Single Interface per Service</a><br>E. <a href="#other-schemalang">Examples of Speciications of Extension Elements for Alternative Schema
  Language Support.</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;E.1 <a href="#dtd">DTD</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.1 <a href="#dtd-namespaceaii">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.2 <a href="#dtd-locationaii">location attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.3 <a href="#dtd-ref">References to Element Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;E.2 <a href="#relax">RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1 <a href="#import-relax">Importing RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.1 <a href="#relax-import-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.2 <a href="#relax-import-hrefaii">href attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2 <a href="#relax-embed">Embedding RELAX NG</a<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2.1 <a href="#relax-embed-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.3 <a href="#relax-ref">References to Element Declarations</a><br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;F.1 <a href="#wsdl-changelog">WSDL Specification Changes</a><br></p></div><hr><div class="body">
  
***************
*** 1848,1852 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 1848,1852 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 2179,2183 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 2179,2183 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 2312,2316 ****
  		  <p>
  		  Zero or more namespace qualified <em>attribute information item</em>s.
- 
  		  The [namespace name] of such
  		  <em>attribute information item</em>s MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".
--- 2312,2315 ----
***************
*** 3187,3190 ****
--- 3186,3190 ----
  		  </tr>
  
+ 
                    <tr>
                      <td rowspan="1" colspan="1">{direction}</td> 
***************
*** 4067,4070 ****
--- 4067,4071 ----
  
  
+ 
    <div class="div2">
      
***************
*** 5708,5712 ****
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
--- 5709,5713 ----
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
***************
*** 5790,5795 ****
        &lt;documentation /&gt;?
        [ &lt;feature /&gt; | &lt;property /&gt; ]*
!     &lt;/<b>endpoint</b>&gt;
!   &lt;/service&gt;+
  &lt;/description&gt;
  </pre></div>
--- 5791,5796 ----
        &lt;documentation /&gt;?
        [ &lt;feature /&gt; | &lt;property /&gt; ]*
!     &lt;/<b>endpoint</b>&gt;+
!   &lt;/service&gt;
  &lt;/description&gt;
  </pre></div>
***************
*** 7433,7449 ****
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema: Structures] </dt><dd>	    
! 	    <cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">XML Schema Part 1: Structures</a></cite>,
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 2 May 2001. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-1-20010502. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of
  	    XML Schema Part 1</a> is available at
  	    http://www.w3.org/TR/xmlschema-1.
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema: Datatypes] </dt><dd>
! 	    <cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">XML Schema Part 2: Datatypes</a></cite>, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 2
! 	    May 2001.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-2-20010502. The <a href="http://www.w3.org/TR/xmlschema-2/">latest version of
  	    XML Schema Part 2</a> is available at
  	    http://www.w3.org/TR/xmlschema-2.
--- 7434,7450 ----
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema: Structures] </dt><dd>	    
! 	    <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema Part 1: Structures</a></cite>,
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 28 October 2004. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of
  	    XML Schema Part 1</a> is available at
  	    http://www.w3.org/TR/xmlschema-1.
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema: Datatypes] </dt><dd>
! 	    <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema Part 2: Datatypes</a></cite>, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 28
! 	    October 2004.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href="http://www.w3.org/TR/xmlschema-2/">latest version of
  	    XML Schema Part 2</a> is available at
  	    http://www.w3.org/TR/xmlschema-2.
***************
*** 7706,7710 ****
  
    <dt class="label">Security considerations:</dt>
!      <dd><p>See section <a href="#ietf-sec"><b>A.2 Security considerations</b></a>.</p></dd>
  
    <dt class="label">Interoperability considerations:</dt>
--- 7707,7711 ----
  
    <dt class="label">Security considerations:</dt>
!      <dd><p>See section <a href="#ietf-sec"><b>A.3 Security considerations</b></a>.</p></dd>
  
    <dt class="label">Interoperability considerations:</dt>
***************
*** 7728,7732 ****
            <dt class="label">Fragment identifiers:</dt>
            <dd><p>Either a syntax identical to that of
!           "application/xml" as described in [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 5 or the syntax defined in <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>.</p></dd>
         
  
--- 7729,7733 ----
            <dt class="label">Fragment identifiers:</dt>
            <dd><p>Either a syntax identical to that of
!           "application/xml" as described in [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 5 or the syntax defined in <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>.</p></dd>
         
  
***************
*** 7756,7903 ****
       
       </dl>
  
-     </div>
-     
-     <div class="div2">
-     
- <h3><a name="ietf-sec"></a>A.2 Security considerations</h3>
-     
-   <p>This media type uses the "+xml" convention, it shares
-   the same security considerations as described in
-   [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 10.</p>
- 
-     </div>
-         
-     </div>
- 
-     
- <div class="div1">
- 
- <h2><a name="acknowledgments"></a>B. Acknowledgements (Non-Normative)</h2>
- <p>This document is the work of the <a href="http://www.w3.org/2002/ws/desc/">W3C Web Service
-       Description Working Group</a>.</p>
- <p>Members of the Working Group are (at the time of writing, and by
-       alphabetical order):
-       David Booth
- 	(W3C), Allen Brookes
- 	(Rogue Wave Softwave), Helen Chen
- 	(Agfa-Gevaert N. V.), Roberto Chinnici
- 	(Sun Microsystems), Ugo Corda
- 	(SeeBeyond), Glen Daniels
- 	(Sonic Software), Paul Downey
- 	(British Telecommunications), Youenn Fablet
- 	(Canon), Martin Gudgin
- 	(Microsoft Corporation), Hugo Haas
- 	(W3C), Hao He
- 	(The Thomson Corporation), Tom Jordahl
- 	(Macromedia), Jacek Kopecky
- 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
- 	(TIBCO Software, Inc.), Kevin Canyang Liu
- 	(SAP), Jonathan Marsh
- 	(Microsoft Corporation), Peter Madziak
- 	(Agfa-Gevaert N. V.), Josephine Micallef
- 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
- 	(Oracle Corporation), Dale Moberg
- 	(Cyclone Commerce), Jean-Jacques Moreau
- 	(Canon), Mark Nottingham
- 	(BEA Systems, Inc.), David Orchard
- 	(BEA Systems, Inc.), Bijan Parsia
- 	(University of Maryland), Arthur Ryman
- 	(IBM), Adi Sakala
- 	(IONA Technologies), Jeffrey Schlimmer
- 	(Microsoft Corporation), Igor Sedukhin
- 	(Computer Associates), Jerry Thrasher
- 	(Lexmark), William Vambenepe
- 	(Hewlett-Packard Company), Asir Vedamuthu
- 	(webMethods, Inc.), Sanjiva Weerawarana
- 	(IBM), &Uuml;mit Yal&ccedil;ınalp
- 	(Oracle Corporation), Prasad Yendluri
- 	(webMethods, Inc.).</p>
- <p>Previous members were:
-       Lily Liu
- 	(webMethods, Inc.), Don Wright
- 	(Lexmark), Joyce Yang
- 	(Oracle Corporation), Daniel Schutzer
- 	(Citigroup), Dave Solo
- 	(Citigroup), Stefano Pogliani
- 	(Sun Microsystems), William Stumbo
- 	(Xerox), Stephen White
- 	(SeeBeyond), Barbara Zengler
- 	(DaimlerChrysler Research and Technology), Tim Finin
- 	(University of Maryland), Laurent De Teneuille
- 	(L'Echangeur), Johan Pauhlsson
- 	(L'Echangeur), Mark Jones
- 	(AT&amp;T), Steve Lind
- 	(AT&amp;T), Sandra Swearingen
- 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H&eacute;garet
- 	(W3C), Jim Hendler
- 	(University of Maryland), Dietmar Gaertner
- 	(Software AG), Michael Champion
- 	(Software AG), Don Mullen
- 	(TIBCO Software, Inc.), Steve Graham
- 	(Global Grid Forum), Steve Tuecke
- 	(Global Grid Forum), Michael Mahan
- 	(Nokia), Bryan Thompson
- 	(Hicks &amp; Associates), Ingo Melzer
- 	(DaimlerChrysler Research and Technology), Sandeep Kumar
- 	(Cisco Systems), Alan Davies
- 	(SeeBeyond), Jacek Kopecky
- 	(Systinet), Mike Ballantyne
- 	(Electronic Data Systems), Mike Davoren
- 	(W. W. Grainger), Dan Kulp
- 	(IONA Technologies), Mike McHugh
- 	(W. W. Grainger), Michael Mealling
- 	(Verisign), Waqar Sadiq
- 	(Electronic Data Systems), Yaron Goland
- 	(BEA Systems, Inc.).</p>
- <p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/www-ws-desc/">discussions
-       on www-ws-desc@w3.org</a> are also gratefully
-       acknowledged.</p>
- </div>
- 
- 
-     <div class="div1">
- 	
- <h2><a name="wsdl-uri-references"></a>C. URI References for WSDL Components (Non-Normative)</h2>
- 
- 	<p> This appendix provides a syntax for URI references for
- 	named components found in a WSDL document. This includes the
- 	top level components: Interface, Binding and Service and the
- 	subordinate components: Interface Operation, Interface Fault, 
- 	Message Reference, Fault Reference, Feature, Property,
- 	Binding Operation, Binding Fault, Binding Message Reference
- 	and Endpoint. The
- 	URI references are easy to understand and compare, while
- 	imposing no burden on the WSDL author.</p>
- 
- 	<div class="div2">
- 	
- <h3><a name="wsdl-uris"></a>C.1 WSDL URIs</h3>
- 	<p>
- 	There are two main cases for WSDL URIs: 
- 	</p>
- 	<ul>
- 	<li><p>the URI of a WSDL document</p></li>
- 	<li><p>the URI of a WSDL namespace</p></li>
- 	</ul>
- 	<p>
- 	The URI of a WSDL document can be dereferenced to give a resource
- 	representation that contributes component definitions to a single
- 	WSDL namespace. If the media type is set to the WSDL media type,
- 	then the fragment identifiers can be used to identify the
- 	main components that are defined in the document. 
- 	</p>
- 
- 	<p> However, in keeping with the recommendation in <a href="#Description_details"><b>2.1.1 The Description Component</b></a> that the namespace URI be
-         dereferencible to a WSDL document, this appendix specifies the
-         use of the namespace URI with the WSDL fragment identifiers to
-         form a URI-reference.</p>
- 
- 	</div>
  	<div class="div2">
  	
! <h3><a name="frag-ids"></a>C.2 Fragment Identifiers</h3>
  	<p>
! 	The following fragment identifier syntax is compliant with the
  	[<cite><a href="#XPTR">XPointer Framework</a></cite>].
  	</p>
--- 7757,7768 ----
       
       </dl>
+      </div>
  
  	<div class="div2">
  	
! <h3><a name="frag-ids"></a>A.2 Fragment Identifiers</h3>
  	<p>
! 	This section defined a fragment identifier syntax for identifying components of a WSDL document.
! 	This fragment identifier syntax is compliant with the
  	[<cite><a href="#XPTR">XPointer Framework</a></cite>].
  	</p>
***************
*** 7906,7915 ****
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names are of type either QName, NCName,
! 	URI, or Pointer Part, depending on the context.
  	</p>
  	<p>
--- 7771,7780 ----
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the standard WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names in the path are of type either QName, NCName,
! 	URI, or Pointer Part depending on the context.
  	</p>
  	<p>
***************
*** 7917,7934 ****
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the URI of the URI-reference.
  	</p>
  
  	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier, where the fragment identifier is typically
! 		constructed from the {name} property of the component and the
! 		{name} properties of its ancestors as a path according to
! 		<a href="#uriRefFragTable">Table C-1</a>. 
! 		In that table the first column gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
--- 7782,7794 ----
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the target namespace of the WSDL document.
  	</p>
  
  	<p>
! 		The fragment identifier is typically constructed from the {name}
! 		property of the component and the {name} properties of its
! 		ancestors as a path according to
! 		<a href="#frag-ids-table">Table A-1</a>.
! 	    The first column of this table gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
***************
*** 7939,7944 ****
  	</p>
  
! 	<a name="uriRefFragTable"></a><br><table border="1">
! 	  <caption>Table C-1. Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" span="1">
  	    <col width="10%" span="1">
--- 7799,7804 ----
  	</p>
  
! 	<a name="frag-ids-table"></a><br><table border="1">
! 	  <caption>Table A-1. Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" span="1">
  	    <col width="10%" span="1">
***************
*** 8068,8076 ****
            <td rowspan="1" colspan="1"><a href="#wsdl.property"><code>wsdl.property(<em>parent</em>/<em>property</em>)</code></a></td>
  	</tr>
        </tbody>
        </table><br>
  
        <p>Note that the above rules are defined in terms of component
!       properties rather the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
--- 7928,7946 ----
            <td rowspan="1" colspan="1"><a href="#wsdl.property"><code>wsdl.property(<em>parent</em>/<em>property</em>)</code></a></td>
  	</tr>
+ 	
        </tbody>
        </table><br>
  
+ 	<p>
+ 		WSDL is extensible and it is possible for an
+ 		extension to define new components types. The XPointer Framework
+ 		scheme for extension components is:
+ 	</p>
+ 
+ 	<p><a href="#wsdl.extension"><code>wsdl.extension(<em>extension-namespace</em>, <em>extension-specific-syntax</em>)</code></a>
+ 	</p>
+ 
        <p>Note that the above rules are defined in terms of component
!       properties rather than the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
***************
*** 8078,8082 ****
        <div class="div3">
        
! <h4><a name="wsdl.interface"></a>C.2.1 <code>wsdl.interface(<em>interface</em>)</code></h4>
        <ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the <a href="#Interface">Interface</a> component.</li>
--- 7948,7952 ----
        <div class="div3">
        
! <h4><a name="wsdl.interface"></a>A.2.1 <code>wsdl.interface(<em>interface</em>)</code></h4>
        <ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the <a href="#Interface">Interface</a> component.</li>
***************
*** 8086,8090 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceFault"></a>C.2.2 <code>wsdl.interfaceFault(<em>interface</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
--- 7956,7960 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceFault"></a>A.2.2 <code>wsdl.interfaceFault(<em>interface</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
***************
*** 8095,8099 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceOperation"></a>C.2.3 <code>wsdl.interfaceOperation(<em>interface</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
--- 7965,7969 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceOperation"></a>A.2.3 <code>wsdl.interfaceOperation(<em>interface</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
***************
*** 8104,8108 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.messageReference"></a>C.2.4 <code>wsdl.messageReference(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
--- 7974,7978 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.messageReference"></a>A.2.4 <code>wsdl.messageReference(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
***************
*** 8114,8118 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.faultReference"></a>C.2.5 <code>wsdl.faultReference(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
--- 7984,7988 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.faultReference"></a>A.2.5 <code>wsdl.faultReference(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
***************
*** 8126,8130 ****
        <div class="div3">
        
! <h4><a name="wsdl.binding"></a>C.2.6 <code>wsdl.binding(<em>binding</em>)</code></h4>
        <ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the <a href="#Binding">Binding</a> component.</li>
--- 7996,8000 ----
        <div class="div3">
        
! <h4><a name="wsdl.binding"></a>A.2.6 <code>wsdl.binding(<em>binding</em>)</code></h4>
        <ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the <a href="#Binding">Binding</a> component.</li>
***************
*** 8134,8138 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFault"></a>C.2.7 <code>wsdl.bindingFault(<em>binding</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
--- 8004,8008 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFault"></a>A.2.7 <code>wsdl.bindingFault(<em>binding</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
***************
*** 8144,8148 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingOperation"></a>C.2.8 <code>wsdl.bindingOperation(<em>binding</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
--- 8014,8018 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingOperation"></a>A.2.8 <code>wsdl.bindingOperation(<em>binding</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
***************
*** 8154,8158 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingMessageReference"></a>C.2.9 <code>wsdl.bindingMessageReference(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
--- 8024,8028 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingMessageReference"></a>A.2.9 <code>wsdl.bindingMessageReference(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
***************
*** 8166,8170 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFaultReference"></a>C.2.10 <code>wsdl.bindingFaultReference(<em>binding</em>/<em>operation</em>/<em>fault</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
--- 8036,8040 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFaultReference"></a>A.2.10 <code>wsdl.bindingFaultReference(<em>binding</em>/<em>operation</em>/<em>fault</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
***************
*** 8182,8186 ****
        <div class="div3">
        
! <h4><a name="wsdl.service"></a>C.2.11 <code>wsdl.service(<em>service</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the <a href="#Service">Service</a> component.</li>
--- 8052,8056 ----
        <div class="div3">
        
! <h4><a name="wsdl.service"></a>A.2.11 <code>wsdl.service(<em>service</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the <a href="#Service">Service</a> component.</li>
***************
*** 8190,8194 ****
        <div class="div3">
        
! <h4><a name="wsdl.endpoint"></a>C.2.12 <code>wsdl.endpoint(<em>service</em>/<em>endpoint</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the parent <a href="#Service">Service</a> component.</li>
--- 8060,8064 ----
        <div class="div3">
        
! <h4><a name="wsdl.endpoint"></a>A.2.12 <code>wsdl.endpoint(<em>service</em>/<em>endpoint</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the parent <a href="#Service">Service</a> component.</li>
***************
*** 8199,8203 ****
        <div class="div3">
        
! <h4><a name="wsdl.feature"></a>C.2.13 <code>wsdl.feature(<em>parent</em>/<em>feature</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
--- 8069,8073 ----
        <div class="div3">
        
! <h4><a name="wsdl.feature"></a>A.2.13 <code>wsdl.feature(<em>parent</em>/<em>feature</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
***************
*** 8208,8212 ****
        <div class="div3">
        
! <h4><a name="wsdl.property"></a>C.2.14 <code>wsdl.property(<em>parent</em>/<em>property</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
--- 8078,8082 ----
        <div class="div3">
        
! <h4><a name="wsdl.property"></a>A.2.14 <code>wsdl.property(<em>parent</em>/<em>property</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
***************
*** 8214,8243 ****
        </ol>
        </div>
        </div>
  
  	<div class="div2">
  	
! <h3><a name="extension-elements"></a>C.3 Extension Elements</h3>
  	<p>
! 	WSDL has an open content model. It is therefore possible for an
! 	extension to define new components. The XPointer
! 	Framework scheme for components added by extensions is:
  	</p>
! 	<p><code>
! 	wsdl.extension(extension-namespace, extension-specific-syntax)</code>
  	</p>
  	<p>
! 	where extension-namespace is the namespace that identifies the
! 	extension, e.g. for SOAP the namespace is
! 	http://www.w3.org/2003/06/wsdl/soap12, and
! 	extension-specific-syntax is defined by the extension. The owner
! 	of the extension must define any components contributed by the
! 	extension and a syntax for identifying them.
  	</p>
- 	</div>
  
  	<div class="div2">
  	
! <h3><a name="Uri-ref-ex"></a>C.4 Example</h3>
  	<p>Consider the following WSDL located at
  	http://example.org/TicketAgent.wsdl:
--- 8084,8258 ----
        </ol>
        </div>
+ 
+       <div class="div3">
+       	
+ <h4><a name="wsdl.extension"></a>A.2.15 <code>wsdl.extension(<em>extension-namespace</em>, <em>extension-specific-syntax</em>)</code></h4>
+       	<ol>
+       		<li>
+       			<code>
+       				<em>extension-namespace</em>
+       			</code>
+       			is the namespace that identifies the extension, e.g.
+       			for SOAP the namespace is
+       			http://www.w3.org/2003/06/wsdl/soap12.
+       		</li>
+       		<li>
+       			<code>
+       				<em>extension-specific-syntax</em>
+       			</code>
+       			is defined by the extension. The owner of the
+       			extension must define any components contributed by
+       			the extension and a syntax for identifying them.
+       		</li>
+       	</ol>
        </div>
+ 	</div>
+     
+     <div class="div2">
+     
+ <h3><a name="ietf-sec"></a>A.3 Security considerations</h3>
+     
+   <p>This media type uses the "+xml" convention, it shares
+   the same security considerations as described in
+   [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 10.</p>
+ 
+     </div>
+         
+     </div>
+ 
+     
+ <div class="div1">
+ 
+ <h2><a name="acknowledgments"></a>B. Acknowledgements (Non-Normative)</h2>
+ <p>This document is the work of the <a href="http://www.w3.org/2002/ws/desc/">W3C Web Service
+       Description Working Group</a>.</p>
+ <p>Members of the Working Group are (at the time of writing, and by
+       alphabetical order):
+       David Booth
+ 	(W3C), Allen Brookes
+ 	(Rogue Wave Softwave), Helen Chen
+ 	(Agfa-Gevaert N. V.), Roberto Chinnici
+ 	(Sun Microsystems), Ugo Corda
+ 	(SeeBeyond), Glen Daniels
+ 	(Sonic Software), Paul Downey
+ 	(British Telecommunications), Youenn Fablet
+ 	(Canon), Martin Gudgin
+ 	(Microsoft Corporation), Hugo Haas
+ 	(W3C), Hao He
+ 	(The Thomson Corporation), Tom Jordahl
+ 	(Macromedia), Jacek Kopecky
+ 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
+ 	(TIBCO Software, Inc.), Kevin Canyang Liu
+ 	(SAP), Jonathan Marsh
+ 	(Microsoft Corporation), Peter Madziak
+ 	(Agfa-Gevaert N. V.), Josephine Micallef
+ 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
+ 	(Oracle Corporation), Dale Moberg
+ 	(Cyclone Commerce), Jean-Jacques Moreau
+ 	(Canon), Mark Nottingham
+ 	(BEA Systems, Inc.), David Orchard
+ 	(BEA Systems, Inc.), Bijan Parsia
+ 	(University of Maryland), Arthur Ryman
+ 	(IBM), Adi Sakala
+ 	(IONA Technologies), Jeffrey Schlimmer
+ 	(Microsoft Corporation), Igor Sedukhin
+ 	(Computer Associates), Jerry Thrasher
+ 	(Lexmark), William Vambenepe
+ 	(Hewlett-Packard Company), Asir Vedamuthu
+ 	(webMethods, Inc.), Sanjiva Weerawarana
+ 	(IBM), &Uuml;mit Yal&ccedil;ınalp
+ 	(Oracle Corporation), Prasad Yendluri
+ 	(webMethods, Inc.).</p>
+ <p>Previous members were:
+       Lily Liu
+ 	(webMethods, Inc.), Don Wright
+ 	(Lexmark), Joyce Yang
+ 	(Oracle Corporation), Daniel Schutzer
+ 	(Citigroup), Dave Solo
+ 	(Citigroup), Stefano Pogliani
+ 	(Sun Microsystems), William Stumbo
+ 	(Xerox), Stephen White
+ 	(SeeBeyond), Barbara Zengler
+ 	(DaimlerChrysler Research and Technology), Tim Finin
+ 	(University of Maryland), Laurent De Teneuille
+ 	(L'Echangeur), Johan Pauhlsson
+ 	(L'Echangeur), Mark Jones
+ 	(AT&amp;T), Steve Lind
+ 	(AT&amp;T), Sandra Swearingen
+ 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H&eacute;garet
+ 	(W3C), Jim Hendler
+ 	(University of Maryland), Dietmar Gaertner
+ 	(Software AG), Michael Champion
+ 	(Software AG), Don Mullen
+ 	(TIBCO Software, Inc.), Steve Graham
+ 	(Global Grid Forum), Steve Tuecke
+ 	(Global Grid Forum), Michael Mahan
+ 	(Nokia), Bryan Thompson
+ 	(Hicks &amp; Associates), Ingo Melzer
+ 	(DaimlerChrysler Research and Technology), Sandeep Kumar
+ 	(Cisco Systems), Alan Davies
+ 	(SeeBeyond), Jacek Kopecky
+ 	(Systinet), Mike Ballantyne
+ 	(Electronic Data Systems), Mike Davoren
+ 	(W. W. Grainger), Dan Kulp
+ 	(IONA Technologies), Mike McHugh
+ 	(W. W. Grainger), Michael Mealling
+ 	(Verisign), Waqar Sadiq
+ 	(Electronic Data Systems), Yaron Goland
+ 	(BEA Systems, Inc.).</p>
+ <p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/www-ws-desc/">discussions
+       on www-ws-desc@w3.org</a> are also gratefully
+       acknowledged.</p>
+ </div>
+ 
+ 
+     <div class="div1">
+ 	
+ <h2><a name="wsdl-uri-references"></a>C. URI References for WSDL Components (Non-Normative)</h2>
+ 
+ 	<p>
+ 		This appendix provides a syntax for URI references for all
+ 		components found in a WSDL document. The URI references are easy
+ 		to understand and compare, while imposing no burden on the WSDL
+ 		author.
+ 	</p>
  
  	<div class="div2">
  	
! <h3><a name="wsdl-uris"></a>C.1 WSDL URIs</h3>
! 	<p>There are two main cases for WSDL URIs:</p>
! 	<ul>
! 	<li><p>the URI of a WSDL document</p></li>
! 	<li><p>the URI of a WSDL namespace</p></li>
! 	</ul>
  	<p>
! 		The URI of a WSDL document can be dereferenced to give a
! 		resource representation that contributes component definitions
! 		to a single WSDL namespace. If the media type is set to the WSDL
! 		media type, then the fragment identifiers can be used to
! 		identify the main components that are defined in the document.
  	</p>
! 
! 	<p>
! 		However, in keeping with the recommendation in
! 		<a href="#Description_details"><b>2.1.1 The Description Component</b></a>
! 		that the namespace URI be dereferencible to a WSDL document,
! 		this appendix specifies the use of the namespace URI with the
! 		WSDL fragment identifiers to form a URI-reference.
  	</p>
+ 
  	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier as defined in <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>.
  	</p>
  
+ 	</div>
  	<div class="div2">
  	
! <h3><a name="Uri-ref-ex"></a>C.2 Example</h3>
  	<p>Consider the following WSDL located at
  	http://example.org/TicketAgent.wsdl:
***************
*** 8279,8283 ****
  </div>
  <p>
! Its conceptual elements have the following URI-references:</p>
  
  <div class="exampleOuter">
--- 8294,8298 ----
  </div>
  <p>
! Its components have the following URI-references:</p>
  
  <div class="exampleOuter">
***************
*** 8564,8569 ****
--- 8579,8597 ----
        <th rowspan="1" colspan="1">Description</th>
      </tr>
+     
+     <tr>
+     	<td rowspan="1" colspan="1">20050416</td>
+     	<td rowspan="1" colspan="1">AGR</td>
+     	<td rowspan="1" colspan="1">Moved the <a href="#frag-ids">fragment identifer</a> definition into the media registration appendix.</td>
+     </tr>
  
      <tr>
+     	<td rowspan="1" colspan="1">20050414</td>
+     	<td rowspan="1" colspan="1">JJM</td>
+     	<td rowspan="1" colspan="1">
+     		Fixed XML Schema P1/P2 version listed in the bibliograpy section.
+     	</td>
+     </tr>
+     <tr>
      	<td rowspan="1" colspan="1">20050413</td>
      	<td rowspan="1" colspan="1">AGR</td>

Index: wsdl20.pdf
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.pdf,v
retrieving revision 1.26
retrieving revision 1.27
diff -C2 -d -r1.26 -r1.27
*** wsdl20.pdf	14 Apr 2005 02:12:27 -0000	1.26
--- wsdl20.pdf	16 Apr 2005 23:40:21 -0000	1.27
***************
*** 676,797 ****
  endobj
  456 0 obj
! (Security considerations)
  endobj
  457 0 obj
! << /S /GoTo /D (appendix.B) >>
  endobj
  460 0 obj
! (Acknowledgements \(Non-Normative\))
  endobj
[...13264 lines suppressed...]
! 0000827488 00000 n 
  trailer
  <<
***************
*** 19839,19845 ****
  /Root 2821 0 R
  /Info 2822 0 R
! /ID [<30912CAA73210530B7CC4F172A76BD58> <30912CAA73210530B7CC4F172A76BD58>]
  >>
  startxref
! 827370
  %%EOF
--- 19780,19786 ----
  /Root 2821 0 R
  /Info 2822 0 R
! /ID [<F74AB8196DAB0DD4C3E16580203D4B35> <F74AB8196DAB0DD4C3E16580203D4B35>]
  >>
  startxref
! 827736
  %%EOF

Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.169
retrieving revision 1.170
diff -C2 -d -r1.169 -r1.170
*** wsdl20.html	14 Apr 2005 02:12:27 -0000	1.169
--- wsdl20.html	16 Apr 2005 23:40:22 -0000	1.170
***************
*** 96,100 ****
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.2 <a href="#Binding_Fault_Reference_messageLabel_attribute">messageLabel attribute information item with infault or
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.3 <a href="#Binding_Fault_Reference_extension_elements">Binding Fault Reference extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.3 <a href="#Binding_Fault_Reference_Mapping">Mapping Binding Fault Reference's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.14 <a href="#Service">Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1 <a href="#Service_details">The Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1.1 <a href="#Service_OperationName">Operation Name Mapping Requirement</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2 <a href="#Service_XMLRep">XML Representation of Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.1 <a href="#Service_name_attribute">name attribute information item with service [ower]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.2 <a href="#Service_interface_attribute">interface attribute information item with service [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.3 <a href="#Service_Mapping">Mapping Service's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.15 <a href="#Endpoint">Endpoint</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.1 <a href="#Endpoint_details">The Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2 <a href="#Endpoint_XMLRep">XML Representation of Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.1 <a href="#Endpoint_name_attribute">name attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.2 <a href="#Endpoint_binding_attribute">binding attribute information item with endpoint [owner]</a><br>&nbsp;&nsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.3 <a href="#Endpoint_address_attribute">address attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.4 <a href="#Endpoint_extension_elements">Endpoint extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.3 <a href="#Endpoint_Mapping">Mapping Endpoint's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.16 <a href="#simpletypes">XML Schema 1.0 Simple Types Used in the Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.1 <a href="#ncname_type">NCName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.2 <a href="#anyuri_type">anyURI Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.3 <a href="#qname_type">QName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.4 <a href="#boolean_type">boolean Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.17 <a href="compequiv">Equivalence of Components</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.18 <a href="#symbolspaces">Symbol Spaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.19 <a href="#qnameres">QName resolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.20 <a href="#uricompare">Comparing URIs</a><br>3. <a href="#eii-types">Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#xsd-types">Using W3C XML Schema Description Language</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#import-xsd">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.1 <a href="#namespace-attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.2 <a href="#schemaLocation-attribute">schemaLocation attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#embed-xsd">Embedding XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2.1 <a href="#targetamespace-attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href="#references-definitions">References to Element Declarations and Type Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#other-types">Using Other Schema Languages</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#includes">Including Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#imports">Importing Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner]</a><br>5. <a href="#eii-documentation">Documentation</a><r>6. <a href="#language-extensibility">Language Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#eii-extensibility">Element based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.2 <a href="#required-aii">required attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#markup">Document Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10.<a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#ietf-reg">Registration</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.2 <a href="#ietf-sec">Security considerations</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>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#wsdl-uris">WSDL URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#frag-ids">Fragment Identifiers</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.1 <a href="#wsdl.interface">wsdl.interface(interface)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.2 <a href="#wsdl.interfaceFault">wsdl.interfaceFault(interface/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.3 <a href="#wsdl.interfaceOperation">wsdl.interfaceOperation(interface/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbspC.2.4 <a href="#wsdl.messageReference">wsdl.messageReference(interface/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.5 <a href="#wsdl.faultReference">wsdl.faultReference(interface/operation/message/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.6 <a href="#wsdl.binding">wsdl.binding(binding)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.7 <a href="#wsdl.bindingFault">wsdl.bindingFault(binding/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.8 <a href="#wsdl.bindingOperation">wsdl.bindingOperation(binding/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.9 <a href="#wsdl.bindingMessageReference">wsdl.bindingMessageReference(binding/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.10 <a href="#wsdl.bindingFaultReference">wsdl.bindingFaultReference(binding/operation/fault/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.11 <a href="#wsdl.service">wsdl.service(servce)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.12 <a href="#wsdl.endpoint">wsdl.endpoint(service/endpoint)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.13 <a href="#wsdl.feature">wsdl.feature(parent/feature)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C.2.14 <a href="#wsdl.property">wsdl.property(parent/property)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#extension-elements">Extension Elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#Uri-ref-ex">Example</a><br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;D.1 <a href="#mig_ops">Operation Overloading</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.2 <a href="#mig_porttypes">PortTypes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.3 <a href="#mig_ports">Ports</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.4 <a href="#single_interface_per_service">Single Interface per Service</a><br>E. <a href="#other-schemalang">Examples of Specifications of Extension Elements for Alternative Schema
  Language Support.</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;E.1 <a href="#dtd">DTD</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.1 <a href="#dtd-namespaceaii">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.2 <a href="#dtd-locationaii">location attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.3 <a href="#dtd-ref">References to Element Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;E.2 <a href="#relax">RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1 <a href="#import-relax">Importing RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.1 <a href="#relax-import-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.2 <a href="#relax-import-hrefaii">href attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2 <a href="#relax-embed">Embedding RELAX NG</a<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2.1 <a href="#relax-embed-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.3 <a href="#relax-ref">References to Element Declarations</a><br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;F.1 <a href="#wsdl-changelog">WSDL Specification Changes</a><br></p></div><hr><div class="body">
  
--- 96,100 ----
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.2 <a href="#Binding_Fault_Reference_messageLabel_attribute">messageLabel attribute information item with infault or
          outfault [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.2.3 <a href="#Binding_Fault_Reference_extension_elements">Binding Fault Reference extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.13.3 <a href="#Binding_Fault_Reference_Mapping">Mapping Binding Fault Reference's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.14 <a href="#Service">Service</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1 <a href="#Service_details">The Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.1.1 <a href="#Service_OperationName">Operation Name Mapping Requirement</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2 <a href="#Service_XMLRep">XML Representation of Service Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.1 <a href="#Service_name_attribute">name attribute information item with service [ower]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.2.2 <a href="#Service_interface_attribute">interface attribute information item with service [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.14.3 <a href="#Service_Mapping">Mapping Service's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.15 <a href="#Endpoint">Endpoint</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.1 <a href="#Endpoint_details">The Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2 <a href="#Endpoint_XMLRep">XML Representation of Endpoint Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.1 <a href="#Endpoint_name_attribute">name attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.2 <a href="#Endpoint_binding_attribute">binding attribute information item with endpoint [owner]</a><br>&nbsp;&nsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.3 <a href="#Endpoint_address_attribute">address attribute information item with endpoint [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.2.4 <a href="#Endpoint_extension_elements">Endpoint extension elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.15.3 <a href="#Endpoint_Mapping">Mapping Endpoint's XML Representation to Component Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.16 <a href="#simpletypes">XML Schema 1.0 Simple Types Used in the Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.1 <a href="#ncname_type">NCName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.2 <a href="#anyuri_type">anyURI Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.3 <a href="#qname_type">QName Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.16.4 <a href="#boolean_type">boolean Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.17 <a href="compequiv">Equivalence of Components</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.18 <a href="#symbolspaces">Symbol Spaces</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.19 <a href="#qnameres">QName resolution</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.20 <a href="#uricompare">Comparing URIs</a><br>3. <a href="#eii-types">Types</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#xsd-types">Using W3C XML Schema Description Language</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#import-xsd">Importing XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.1 <a href="#namespace-attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1.2 <a href="#schemaLocation-attribute">schemaLocation attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#embed-xsd">Embedding XML Schema</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2.1 <a href="#targetamespace-attribute">targetNamespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href="#references-definitions">References to Element Declarations and Type Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#other-types">Using Other Schema Languages</a><br>4. <a href="#modularize">Modularizing WSDL descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#includes">Including Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner]</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#imports">Importing Descriptions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner]</a><br>5. <a href="#eii-documentation">Documentation</a><r>6. <a href="#language-extensibility">Language Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#eii-extensibility">Element based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.1.2 <a href="#required-aii">required attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL Documents</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#markup">Document Conformance</a><br>&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10.<a href="#References">References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.1 <a href="#Normative-References">Normative References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#ietf-reg">Registration</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.2 <a href="#frag-ids">Fragment Identifiers</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#wsdl.interface">wsdl.interface(interface)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.2 <a href="#wsdl.interfaceFault">wsdl.interfaceFault(interface/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.3 <a href="#wsdl.interfaceOperation">wsdl.interfaceOperation(interface/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.4 <a href="#wsdl.messageReference">wsdl.messageReference(interface/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.5 <a href="#wsdl.faultReference">wsdl.faultReference(interface/operation/message/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.6 <a href=#wsdl.binding">wsdl.binding(binding)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.7 <a href="#wsdl.bindingFault">wsdl.bindingFault(binding/fault)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.8 <a href="#wsdl.bindingOperation">wsdl.bindingOperation(binding/operation)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.9 <a href="#wsdl.bindingMessageReference">wsdl.bindingMessageReference(binding/operation/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.10 <a href="#wsdl.bindingFaultReference">wsdl.bindingFaultReference(binding/operation/fault/message)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.11 <a href="#wsdl.service">wsdl.service(service)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.12 <a href="#wsdl.endpoint">wsdl.endpoint(service/endpoint)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.13 <a href="#wsdl.feature">wsdl.feature(parent/feature)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.14 <a hre="#wsdl.property">wsdl.property(parent/property)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.15 <a href="#wsdl.extension">wsdl.extension(extension-namespace, extension-specific-syntax)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;A.3 <a href="#ietf-sec">Security considerations</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>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#wsdl-uris">WSDL URIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#Uri-ref-ex">Example</a><br>D. <a href="#migration">Migrating from WSDL 1.1 to WSDL 2.0</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;D.1 <a href="#mig_ops">Operation Overloading</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.2 <a href="#mig_porttypes">PortTypes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.3 <a href="#mig_ports">Ports</a><br>&nbsp;&nbsp;&nbsp;&nbsp;D.4 <a href="#single_interface_per_service">Single Interface per Service</a><br>E. <a href="#other-schemalang">Examples of Speciications of Extension Elements for Alternative Schema
  Language Support.</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;E.1 <a href="#dtd">DTD</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.1 <a href="#dtd-namespaceaii">namespace attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.2 <a href="#dtd-locationaii">location attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.1.3 <a href="#dtd-ref">References to Element Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;E.2 <a href="#relax">RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1 <a href="#import-relax">Importing RELAX NG</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.1 <a href="#relax-import-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.1.2 <a href="#relax-import-hrefaii">href attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2 <a href="#relax-embed">Embedding RELAX NG</a<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.2.1 <a href="#relax-embed-nsaii">ns attribute information item</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;E.2.3 <a href="#relax-ref">References to Element Declarations</a><br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;F.1 <a href="#wsdl-changelog">WSDL Specification Changes</a><br></p></div><hr><div class="body">
  
***************
*** 1270,1274 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 1270,1274 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 1572,1576 ****
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
--- 1572,1576 ----
  	components; they cannot be referred to by QName, despite
  	having a {name} property
! 	(see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>). That is,
  	two Interface components whose {name} property share the same namespace name
  	but with different local names MAY contain
***************
*** 1705,1709 ****
  		  <p>
  		  Zero or more namespace qualified <em>attribute information item</em>s.
- 
  		  The [namespace name] of such
  		  <em>attribute information item</em>s MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".
--- 1705,1708 ----
***************
*** 2508,2511 ****
--- 2507,2511 ----
  		  </tr>
  
+ 
                    <tr>
                      <td rowspan="1" colspan="1">{direction}</td> 
***************
*** 3280,3283 ****
--- 3280,3284 ----
  
  
+ 
    <div class="div2">
      
***************
*** 4760,4764 ****
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
--- 4761,4765 ----
  	  <p>
  	  Endpoint components are local to a given Service component; they
! 	  cannot be referred to by QName (see <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>).
  	  </p>
  	  <p>The properties of the Endpoint component are as follows:</p>
***************
*** 4813,4818 ****
        &lt;documentation /&gt;?
        [ &lt;feature /&gt; | &lt;property /&gt; ]*
!     &lt;/<b>endpoint</b>&gt;
!   &lt;/service&gt;+
  &lt;/description&gt;
  </pre></div>
--- 4814,4819 ----
        &lt;documentation /&gt;?
        [ &lt;feature /&gt; | &lt;property /&gt; ]*
!     &lt;/<b>endpoint</b>&gt;+
!   &lt;/service&gt;
  &lt;/description&gt;
  </pre></div>
***************
*** 6411,6427 ****
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema: Structures] </dt><dd>	    
! 	    <cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">XML Schema Part 1: Structures</a></cite>,
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 2 May 2001. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-1-20010502. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of
  	    XML Schema Part 1</a> is available at
  	    http://www.w3.org/TR/xmlschema-1.
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema: Datatypes] </dt><dd>
! 	    <cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">XML Schema Part 2: Datatypes</a></cite>, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 2
! 	    May 2001.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2001/REC-xmlschema-2-20010502. The <a href="http://www.w3.org/TR/xmlschema-2/">latest version of
  	    XML Schema Part 2</a> is available at
  	    http://www.w3.org/TR/xmlschema-2.
--- 6412,6428 ----
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema: Structures] </dt><dd>	    
! 	    <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema Part 1: Structures</a></cite>,
  	    H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! 	    Editors. World Wide Web Consortium, 28 October 2004. This version
  	    of the XML Schema Part 1 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of
  	    XML Schema Part 1</a> is available at
  	    http://www.w3.org/TR/xmlschema-1.
  	  </dd>
  	  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema: Datatypes] </dt><dd>
! 	    <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema Part 2: Datatypes</a></cite>, P. Byron
! 	    and A. Malhotra, Editors. World Wide Web Consortium, 28
! 	    October 2004.  This version of the XML Schema Part 2 Recommendation is
! 	    http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href="http://www.w3.org/TR/xmlschema-2/">latest version of
  	    XML Schema Part 2</a> is available at
  	    http://www.w3.org/TR/xmlschema-2.
***************
*** 6684,6688 ****
  
    <dt class="label">Security considerations:</dt>
!      <dd><p>See section <a href="#ietf-sec"><b>A.2 Security considerations</b></a>.</p></dd>
  
    <dt class="label">Interoperability considerations:</dt>
--- 6685,6689 ----
  
    <dt class="label">Security considerations:</dt>
!      <dd><p>See section <a href="#ietf-sec"><b>A.3 Security considerations</b></a>.</p></dd>
  
    <dt class="label">Interoperability considerations:</dt>
***************
*** 6706,6710 ****
            <dt class="label">Fragment identifiers:</dt>
            <dd><p>Either a syntax identical to that of
!           "application/xml" as described in [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 5 or the syntax defined in <a href="#wsdl-uri-references"><b>C. URI References for WSDL Components</b></a>.</p></dd>
         
  
--- 6707,6711 ----
            <dt class="label">Fragment identifiers:</dt>
            <dd><p>Either a syntax identical to that of
!           "application/xml" as described in [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 5 or the syntax defined in <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>.</p></dd>
         
  
***************
*** 6734,6881 ****
       
       </dl>
  
-     </div>
-     
-     <div class="div2">
-     
- <h3><a name="ietf-sec"></a>A.2 Security considerations</h3>
-     
-   <p>This media type uses the "+xml" convention, it shares
-   the same security considerations as described in
-   [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 10.</p>
- 
-     </div>
-         
-     </div>
- 
-     
- <div class="div1">
- 
- <h2><a name="acknowledgments"></a>B. Acknowledgements (Non-Normative)</h2>
- <p>This document is the work of the <a href="http://www.w3.org/2002/ws/desc/">W3C Web Service
-       Description Working Group</a>.</p>
- <p>Members of the Working Group are (at the time of writing, and by
-       alphabetical order):
-       David Booth
- 	(W3C), Allen Brookes
- 	(Rogue Wave Softwave), Helen Chen
- 	(Agfa-Gevaert N. V.), Roberto Chinnici
- 	(Sun Microsystems), Ugo Corda
- 	(SeeBeyond), Glen Daniels
- 	(Sonic Software), Paul Downey
- 	(British Telecommunications), Youenn Fablet
- 	(Canon), Martin Gudgin
- 	(Microsoft Corporation), Hugo Haas
- 	(W3C), Hao He
- 	(The Thomson Corporation), Tom Jordahl
- 	(Macromedia), Jacek Kopecky
- 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
- 	(TIBCO Software, Inc.), Kevin Canyang Liu
- 	(SAP), Jonathan Marsh
- 	(Microsoft Corporation), Peter Madziak
- 	(Agfa-Gevaert N. V.), Josephine Micallef
- 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
- 	(Oracle Corporation), Dale Moberg
- 	(Cyclone Commerce), Jean-Jacques Moreau
- 	(Canon), Mark Nottingham
- 	(BEA Systems, Inc.), David Orchard
- 	(BEA Systems, Inc.), Bijan Parsia
- 	(University of Maryland), Arthur Ryman
- 	(IBM), Adi Sakala
- 	(IONA Technologies), Jeffrey Schlimmer
- 	(Microsoft Corporation), Igor Sedukhin
- 	(Computer Associates), Jerry Thrasher
- 	(Lexmark), William Vambenepe
- 	(Hewlett-Packard Company), Asir Vedamuthu
- 	(webMethods, Inc.), Sanjiva Weerawarana
- 	(IBM), &Uuml;mit Yal&ccedil;ınalp
- 	(Oracle Corporation), Prasad Yendluri
- 	(webMethods, Inc.).</p>
- <p>Previous members were:
-       Lily Liu
- 	(webMethods, Inc.), Don Wright
- 	(Lexmark), Joyce Yang
- 	(Oracle Corporation), Daniel Schutzer
- 	(Citigroup), Dave Solo
- 	(Citigroup), Stefano Pogliani
- 	(Sun Microsystems), William Stumbo
- 	(Xerox), Stephen White
- 	(SeeBeyond), Barbara Zengler
- 	(DaimlerChrysler Research and Technology), Tim Finin
- 	(University of Maryland), Laurent De Teneuille
- 	(L'Echangeur), Johan Pauhlsson
- 	(L'Echangeur), Mark Jones
- 	(AT&amp;T), Steve Lind
- 	(AT&amp;T), Sandra Swearingen
- 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H&eacute;garet
- 	(W3C), Jim Hendler
- 	(University of Maryland), Dietmar Gaertner
- 	(Software AG), Michael Champion
- 	(Software AG), Don Mullen
- 	(TIBCO Software, Inc.), Steve Graham
- 	(Global Grid Forum), Steve Tuecke
- 	(Global Grid Forum), Michael Mahan
- 	(Nokia), Bryan Thompson
- 	(Hicks &amp; Associates), Ingo Melzer
- 	(DaimlerChrysler Research and Technology), Sandeep Kumar
- 	(Cisco Systems), Alan Davies
- 	(SeeBeyond), Jacek Kopecky
- 	(Systinet), Mike Ballantyne
- 	(Electronic Data Systems), Mike Davoren
- 	(W. W. Grainger), Dan Kulp
- 	(IONA Technologies), Mike McHugh
- 	(W. W. Grainger), Michael Mealling
- 	(Verisign), Waqar Sadiq
- 	(Electronic Data Systems), Yaron Goland
- 	(BEA Systems, Inc.).</p>
- <p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/www-ws-desc/">discussions
-       on www-ws-desc@w3.org</a> are also gratefully
-       acknowledged.</p>
- </div>
- 
- 
-     <div class="div1">
- 	
- <h2><a name="wsdl-uri-references"></a>C. URI References for WSDL Components (Non-Normative)</h2>
- 
- 	<p> This appendix provides a syntax for URI references for
- 	named components found in a WSDL document. This includes the
- 	top level components: Interface, Binding and Service and the
- 	subordinate components: Interface Operation, Interface Fault, 
- 	Message Reference, Fault Reference, Feature, Property,
- 	Binding Operation, Binding Fault, Binding Message Reference
- 	and Endpoint. The
- 	URI references are easy to understand and compare, while
- 	imposing no burden on the WSDL author.</p>
- 
- 	<div class="div2">
- 	
- <h3><a name="wsdl-uris"></a>C.1 WSDL URIs</h3>
- 	<p>
- 	There are two main cases for WSDL URIs: 
- 	</p>
- 	<ul>
- 	<li><p>the URI of a WSDL document</p></li>
- 	<li><p>the URI of a WSDL namespace</p></li>
- 	</ul>
- 	<p>
- 	The URI of a WSDL document can be dereferenced to give a resource
- 	representation that contributes component definitions to a single
- 	WSDL namespace. If the media type is set to the WSDL media type,
- 	then the fragment identifiers can be used to identify the
- 	main components that are defined in the document. 
- 	</p>
- 
- 	<p> However, in keeping with the recommendation in <a href="#Description_details"><b>2.1.1 The Description Component</b></a> that the namespace URI be
-         dereferencible to a WSDL document, this appendix specifies the
-         use of the namespace URI with the WSDL fragment identifiers to
-         form a URI-reference.</p>
- 
- 	</div>
  	<div class="div2">
  	
! <h3><a name="frag-ids"></a>C.2 Fragment Identifiers</h3>
  	<p>
! 	The following fragment identifier syntax is compliant with the
  	[<cite><a href="#XPTR">XPointer Framework</a></cite>].
  	</p>
--- 6735,6746 ----
       
       </dl>
+      </div>
  
  	<div class="div2">
  	
! <h3><a name="frag-ids"></a>A.2 Fragment Identifiers</h3>
  	<p>
! 	This section defined a fragment identifier syntax for identifying components of a WSDL document.
! 	This fragment identifier syntax is compliant with the
  	[<cite><a href="#XPTR">XPointer Framework</a></cite>].
  	</p>
***************
*** 6884,6893 ****
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names are of type either QName, NCName,
! 	URI, or Pointer Part, depending on the context.
  	</p>
  	<p>
--- 6749,6758 ----
  	followed by a pointer part as defined below.
  	The pointer parts have a scheme name that corresponds to one
! 	of the standard WSDL component types, and scheme data that is a path composed
  	of names that identify the components. 
  	The scheme names all begin with the prefix "wsdl." to avoid
  	name conflicts with other schemes.
! 	The names in the path are of type either QName, NCName,
! 	URI, or Pointer Part depending on the context.
  	</p>
  	<p>
***************
*** 6895,6912 ****
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the URI of the URI-reference.
  	</p>
  
  	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier, where the fragment identifier is typically
! 		constructed from the {name} property of the component and the
! 		{name} properties of its ancestors as a path according to
! 		<a href="#uriRefFragTable">Table C-1</a>. 
! 		In that table the first column gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
--- 6760,6772 ----
  	MUST be defined by a preceding xmlns pointer part.
  	If a QName does not have a prefix then its namespace
! 	name is the target namespace of the WSDL document.
  	</p>
  
  	<p>
! 		The fragment identifier is typically constructed from the {name}
! 		property of the component and the {name} properties of its
! 		ancestors as a path according to
! 		<a href="#frag-ids-table">Table A-1</a>.
! 	    The first column of this table gives the name of the WSDL
  		component. Columns labelled 1 through 4 specify the identifiers that
  		uniquely identify the component within its context. Identifiers
***************
*** 6917,6922 ****
  	</p>
  
! 	<a name="uriRefFragTable"></a><br><table border="1">
! 	  <caption>Table C-1. Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" span="1">
  	    <col width="10%" span="1">
--- 6777,6782 ----
  	</p>
  
! 	<a name="frag-ids-table"></a><br><table border="1">
! 	  <caption>Table A-1. Rules for determining pointer parts for WSDL components</caption>
  	    <col width="15%" span="1">
  	    <col width="10%" span="1">
***************
*** 7046,7054 ****
            <td rowspan="1" colspan="1"><a href="#wsdl.property"><code>wsdl.property(<em>parent</em>/<em>property</em>)</code></a></td>
  	</tr>
        </tbody>
        </table><br>
  
        <p>Note that the above rules are defined in terms of component
!       properties rather the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
--- 6906,6924 ----
            <td rowspan="1" colspan="1"><a href="#wsdl.property"><code>wsdl.property(<em>parent</em>/<em>property</em>)</code></a></td>
  	</tr>
+ 	
        </tbody>
        </table><br>
  
+ 	<p>
+ 		WSDL is extensible and it is possible for an
+ 		extension to define new components types. The XPointer Framework
+ 		scheme for extension components is:
+ 	</p>
+ 
+ 	<p><a href="#wsdl.extension"><code>wsdl.extension(<em>extension-namespace</em>, <em>extension-specific-syntax</em>)</code></a>
+ 	</p>
+ 
        <p>Note that the above rules are defined in terms of component
!       properties rather than the XML Infoset representation of the
        component model. The following sections specify in detail how the pointer parts are constructed from the
        component model.</p>
***************
*** 7056,7060 ****
        <div class="div3">
        
! <h4><a name="wsdl.interface"></a>C.2.1 <code>wsdl.interface(<em>interface</em>)</code></h4>
        <ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the <a href="#Interface">Interface</a> component.</li>
--- 6926,6930 ----
        <div class="div3">
        
! <h4><a name="wsdl.interface"></a>A.2.1 <code>wsdl.interface(<em>interface</em>)</code></h4>
        <ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the <a href="#Interface">Interface</a> component.</li>
***************
*** 7064,7068 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceFault"></a>C.2.2 <code>wsdl.interfaceFault(<em>interface</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
--- 6934,6938 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceFault"></a>A.2.2 <code>wsdl.interfaceFault(<em>interface</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
***************
*** 7073,7077 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceOperation"></a>C.2.3 <code>wsdl.interfaceOperation(<em>interface</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
--- 6943,6947 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.interfaceOperation"></a>A.2.3 <code>wsdl.interfaceOperation(<em>interface</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the parent <a href="#Interface">Interface</a> component.</li>
***************
*** 7082,7086 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.messageReference"></a>C.2.4 <code>wsdl.messageReference(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
--- 6952,6956 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.messageReference"></a>A.2.4 <code>wsdl.messageReference(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
***************
*** 7092,7096 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.faultReference"></a>C.2.5 <code>wsdl.faultReference(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
--- 6962,6966 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.faultReference"></a>A.2.5 <code>wsdl.faultReference(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>interface</em></code> is the local name of the {name} property of the grandparent <a href="#Interface">Interface</a> component.</li>
***************
*** 7104,7108 ****
        <div class="div3">
        
! <h4><a name="wsdl.binding"></a>C.2.6 <code>wsdl.binding(<em>binding</em>)</code></h4>
        <ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the <a href="#Binding">Binding</a> component.</li>
--- 6974,6978 ----
        <div class="div3">
        
! <h4><a name="wsdl.binding"></a>A.2.6 <code>wsdl.binding(<em>binding</em>)</code></h4>
        <ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the <a href="#Binding">Binding</a> component.</li>
***************
*** 7112,7116 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFault"></a>C.2.7 <code>wsdl.bindingFault(<em>binding</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
--- 6982,6986 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFault"></a>A.2.7 <code>wsdl.bindingFault(<em>binding</em>/<em>fault</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
***************
*** 7122,7126 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingOperation"></a>C.2.8 <code>wsdl.bindingOperation(<em>binding</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
--- 6992,6996 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingOperation"></a>A.2.8 <code>wsdl.bindingOperation(<em>binding</em>/<em>operation</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the parent <a href="#Binding">Binding</a> component.</li>
***************
*** 7132,7136 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingMessageReference"></a>C.2.9 <code>wsdl.bindingMessageReference(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
--- 7002,7006 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingMessageReference"></a>A.2.9 <code>wsdl.bindingMessageReference(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
***************
*** 7144,7148 ****
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFaultReference"></a>C.2.10 <code>wsdl.bindingFaultReference(<em>binding</em>/<em>operation</em>/<em>fault</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
--- 7014,7018 ----
  	<div class="div3">
  	
! <h4><a name="wsdl.bindingFaultReference"></a>A.2.10 <code>wsdl.bindingFaultReference(<em>binding</em>/<em>operation</em>/<em>fault</em>/<em>message</em>)</code></h4>
  	<ol>
        <li><code><em>binding</em></code> is the local name of the {name} property of the grandparent <a href="#Binding">Binding</a> component.</li>
***************
*** 7160,7164 ****
        <div class="div3">
        
! <h4><a name="wsdl.service"></a>C.2.11 <code>wsdl.service(<em>service</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the <a href="#Service">Service</a> component.</li>
--- 7030,7034 ----
        <div class="div3">
        
! <h4><a name="wsdl.service"></a>A.2.11 <code>wsdl.service(<em>service</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the <a href="#Service">Service</a> component.</li>
***************
*** 7168,7172 ****
        <div class="div3">
        
! <h4><a name="wsdl.endpoint"></a>C.2.12 <code>wsdl.endpoint(<em>service</em>/<em>endpoint</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the parent <a href="#Service">Service</a> component.</li>
--- 7038,7042 ----
        <div class="div3">
        
! <h4><a name="wsdl.endpoint"></a>A.2.12 <code>wsdl.endpoint(<em>service</em>/<em>endpoint</em>)</code></h4>
        <ol>
        <li><code><em>service</em></code> is the local name of the {name} property of the parent <a href="#Service">Service</a> component.</li>
***************
*** 7177,7181 ****
        <div class="div3">
        
! <h4><a name="wsdl.feature"></a>C.2.13 <code>wsdl.feature(<em>parent</em>/<em>feature</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
--- 7047,7051 ----
        <div class="div3">
        
! <h4><a name="wsdl.feature"></a>A.2.13 <code>wsdl.feature(<em>parent</em>/<em>feature</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
***************
*** 7186,7190 ****
        <div class="div3">
        
! <h4><a name="wsdl.property"></a>C.2.14 <code>wsdl.property(<em>parent</em>/<em>property</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
--- 7056,7060 ----
        <div class="div3">
        
! <h4><a name="wsdl.property"></a>A.2.14 <code>wsdl.property(<em>parent</em>/<em>property</em>)</code></h4>
        <ol>
        <li><code><em>parent</em></code> is the pointer part of the parent component.</li>
***************
*** 7192,7221 ****
        </ol>
        </div>
        </div>
  
  	<div class="div2">
  	
! <h3><a name="extension-elements"></a>C.3 Extension Elements</h3>
  	<p>
! 	WSDL has an open content model. It is therefore possible for an
! 	extension to define new components. The XPointer
! 	Framework scheme for components added by extensions is:
  	</p>
! 	<p><code>
! 	wsdl.extension(extension-namespace, extension-specific-syntax)</code>
  	</p>
  	<p>
! 	where extension-namespace is the namespace that identifies the
! 	extension, e.g. for SOAP the namespace is
! 	http://www.w3.org/2003/06/wsdl/soap12, and
! 	extension-specific-syntax is defined by the extension. The owner
! 	of the extension must define any components contributed by the
! 	extension and a syntax for identifying them.
  	</p>
- 	</div>
  
  	<div class="div2">
  	
! <h3><a name="Uri-ref-ex"></a>C.4 Example</h3>
  	<p>Consider the following WSDL located at
  	http://example.org/TicketAgent.wsdl:
--- 7062,7236 ----
        </ol>
        </div>
+ 
+       <div class="div3">
+       	
+ <h4><a name="wsdl.extension"></a>A.2.15 <code>wsdl.extension(<em>extension-namespace</em>, <em>extension-specific-syntax</em>)</code></h4>
+       	<ol>
+       		<li>
+       			<code>
+       				<em>extension-namespace</em>
+       			</code>
+       			is the namespace that identifies the extension, e.g.
+       			for SOAP the namespace is
+       			http://www.w3.org/2003/06/wsdl/soap12.
+       		</li>
+       		<li>
+       			<code>
+       				<em>extension-specific-syntax</em>
+       			</code>
+       			is defined by the extension. The owner of the
+       			extension must define any components contributed by
+       			the extension and a syntax for identifying them.
+       		</li>
+       	</ol>
        </div>
+ 	</div>
+     
+     <div class="div2">
+     
+ <h3><a name="ietf-sec"></a>A.3 Security considerations</h3>
+     
+   <p>This media type uses the "+xml" convention, it shares
+   the same security considerations as described in
+   [<cite><a href="#RFC3023">RFC 3023</a></cite>], section 10.</p>
+ 
+     </div>
+         
+     </div>
+ 
+     
+ <div class="div1">
+ 
+ <h2><a name="acknowledgments"></a>B. Acknowledgements (Non-Normative)</h2>
+ <p>This document is the work of the <a href="http://www.w3.org/2002/ws/desc/">W3C Web Service
+       Description Working Group</a>.</p>
+ <p>Members of the Working Group are (at the time of writing, and by
+       alphabetical order):
+       David Booth
+ 	(W3C), Allen Brookes
+ 	(Rogue Wave Softwave), Helen Chen
+ 	(Agfa-Gevaert N. V.), Roberto Chinnici
+ 	(Sun Microsystems), Ugo Corda
+ 	(SeeBeyond), Glen Daniels
+ 	(Sonic Software), Paul Downey
+ 	(British Telecommunications), Youenn Fablet
+ 	(Canon), Martin Gudgin
+ 	(Microsoft Corporation), Hugo Haas
+ 	(W3C), Hao He
+ 	(The Thomson Corporation), Tom Jordahl
+ 	(Macromedia), Jacek Kopecky
+ 	(Digital Enterprise Research Institute (DERI)), Amelia Lewis
+ 	(TIBCO Software, Inc.), Kevin Canyang Liu
+ 	(SAP), Jonathan Marsh
+ 	(Microsoft Corporation), Peter Madziak
+ 	(Agfa-Gevaert N. V.), Josephine Micallef
+ 	(SAIC - Telcordia Technologies), Jeff Mischkinsky
+ 	(Oracle Corporation), Dale Moberg
+ 	(Cyclone Commerce), Jean-Jacques Moreau
+ 	(Canon), Mark Nottingham
+ 	(BEA Systems, Inc.), David Orchard
+ 	(BEA Systems, Inc.), Bijan Parsia
+ 	(University of Maryland), Arthur Ryman
+ 	(IBM), Adi Sakala
+ 	(IONA Technologies), Jeffrey Schlimmer
+ 	(Microsoft Corporation), Igor Sedukhin
+ 	(Computer Associates), Jerry Thrasher
+ 	(Lexmark), William Vambenepe
+ 	(Hewlett-Packard Company), Asir Vedamuthu
+ 	(webMethods, Inc.), Sanjiva Weerawarana
+ 	(IBM), &Uuml;mit Yal&ccedil;ınalp
+ 	(Oracle Corporation), Prasad Yendluri
+ 	(webMethods, Inc.).</p>
+ <p>Previous members were:
+       Lily Liu
+ 	(webMethods, Inc.), Don Wright
+ 	(Lexmark), Joyce Yang
+ 	(Oracle Corporation), Daniel Schutzer
+ 	(Citigroup), Dave Solo
+ 	(Citigroup), Stefano Pogliani
+ 	(Sun Microsystems), William Stumbo
+ 	(Xerox), Stephen White
+ 	(SeeBeyond), Barbara Zengler
+ 	(DaimlerChrysler Research and Technology), Tim Finin
+ 	(University of Maryland), Laurent De Teneuille
+ 	(L'Echangeur), Johan Pauhlsson
+ 	(L'Echangeur), Mark Jones
+ 	(AT&amp;T), Steve Lind
+ 	(AT&amp;T), Sandra Swearingen
+ 	(U.S. Department of Defense, U.S. Air Force), Philippe Le H&eacute;garet
+ 	(W3C), Jim Hendler
+ 	(University of Maryland), Dietmar Gaertner
+ 	(Software AG), Michael Champion
+ 	(Software AG), Don Mullen
+ 	(TIBCO Software, Inc.), Steve Graham
+ 	(Global Grid Forum), Steve Tuecke
+ 	(Global Grid Forum), Michael Mahan
+ 	(Nokia), Bryan Thompson
+ 	(Hicks &amp; Associates), Ingo Melzer
+ 	(DaimlerChrysler Research and Technology), Sandeep Kumar
+ 	(Cisco Systems), Alan Davies
+ 	(SeeBeyond), Jacek Kopecky
+ 	(Systinet), Mike Ballantyne
+ 	(Electronic Data Systems), Mike Davoren
+ 	(W. W. Grainger), Dan Kulp
+ 	(IONA Technologies), Mike McHugh
+ 	(W. W. Grainger), Michael Mealling
+ 	(Verisign), Waqar Sadiq
+ 	(Electronic Data Systems), Yaron Goland
+ 	(BEA Systems, Inc.).</p>
+ <p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/www-ws-desc/">discussions
+       on www-ws-desc@w3.org</a> are also gratefully
+       acknowledged.</p>
+ </div>
+ 
+ 
+     <div class="div1">
+ 	
+ <h2><a name="wsdl-uri-references"></a>C. URI References for WSDL Components (Non-Normative)</h2>
+ 
+ 	<p>
+ 		This appendix provides a syntax for URI references for all
+ 		components found in a WSDL document. The URI references are easy
+ 		to understand and compare, while imposing no burden on the WSDL
+ 		author.
+ 	</p>
  
  	<div class="div2">
  	
! <h3><a name="wsdl-uris"></a>C.1 WSDL URIs</h3>
! 	<p>There are two main cases for WSDL URIs:</p>
! 	<ul>
! 	<li><p>the URI of a WSDL document</p></li>
! 	<li><p>the URI of a WSDL namespace</p></li>
! 	</ul>
  	<p>
! 		The URI of a WSDL document can be dereferenced to give a
! 		resource representation that contributes component definitions
! 		to a single WSDL namespace. If the media type is set to the WSDL
! 		media type, then the fragment identifiers can be used to
! 		identify the main components that are defined in the document.
  	</p>
! 
! 	<p>
! 		However, in keeping with the recommendation in
! 		<a href="#Description_details"><b>2.1.1 The Description Component</b></a>
! 		that the namespace URI be dereferencible to a WSDL document,
! 		this appendix specifies the use of the namespace URI with the
! 		WSDL fragment identifiers to form a URI-reference.
  	</p>
+ 
  	<p>
! 		The URI in a URI-reference for a WSDL component is the namespace
! 		name of the {name} property of either the component itself, in
! 		the case of Interface, Binding, and Service components, or the
! 		{name} property of the ancestor component. The URI provided by
! 		the namespace name of the {name} property is combined with a
! 		fragment identifier as defined in <a href="#frag-ids"><b>A.2 Fragment Identifiers</b></a>.
  	</p>
  
+ 	</div>
  	<div class="div2">
  	
! <h3><a name="Uri-ref-ex"></a>C.2 Example</h3>
  	<p>Consider the following WSDL located at
  	http://example.org/TicketAgent.wsdl:
***************
*** 7257,7261 ****
  </div>
  <p>
! Its conceptual elements have the following URI-references:</p>
  
  <div class="exampleOuter">
--- 7272,7276 ----
  </div>
  <p>
! Its components have the following URI-references:</p>
  
  <div class="exampleOuter">
***************
*** 7542,7547 ****
--- 7557,7575 ----
        <th rowspan="1" colspan="1">Description</th>
      </tr>
+     
+     <tr>
+     	<td rowspan="1" colspan="1">20050416</td>
+     	<td rowspan="1" colspan="1">AGR</td>
+     	<td rowspan="1" colspan="1">Moved the <a href="#frag-ids">fragment identifer</a> definition into the media registration appendix.</td>
+     </tr>
  
      <tr>
+     	<td rowspan="1" colspan="1">20050414</td>
+     	<td rowspan="1" colspan="1">JJM</td>
+     	<td rowspan="1" colspan="1">
+     		Fixed XML Schema P1/P2 version listed in the bibliograpy section.
+     	</td>
+     </tr>
+     <tr>
      	<td rowspan="1" colspan="1">20050413</td>
      	<td rowspan="1" colspan="1">AGR</td>

Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** wsdl20-primer.html	16 Apr 2005 17:23:43 -0000	1.29
--- wsdl20-primer.html	16 Apr 2005 23:40:23 -0000	1.30
***************
*** 1,14 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
!     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
! <html lang="en" xmlns="http://www.w3.org/1999/xhtml">
! <head>
! <meta name="generator"
! content="HTML Tidy for Windows (vers 1st January 2002), see www.w3.org" />
! <meta content="text/html; charset=utf-8"
! http-equiv="Content-Type" />
! <title>Web Services Description Language (WSDL) Version 2.0 Part 0:
! Primer</title>
[...7237 lines suppressed...]
+ 	  </dd>
+ 					<dt class="label"><a name="XPTR"></a>[XPointer Framework] </dt><dd>
+ 						<cite><a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer Framework</a></cite>,Paul Grosso, Eve
+ 	    Maler, Jonathan Marsh, Norman Walsh, Editors. World Wide Web
+ 	    Consortium, 22 November 2002.  This version of the XPointer
+ 	    Framework Proposed Recommendation is
+ 	    http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The
+ 	    <a href="http://www.w3.org/TR/xptr-framework/">latest
+ 	    version of XPointer Framework</a> is available at
+ 	    http://www.w3.org/TR/xptr-framework/.
+ 	  </dd>
+ 					
+ 				</dl>
+ 			</div>
+ 		</div>
+ 		
+ 		
+ 	</div>
+ </body></html>
\ No newline at end of file
Received on Saturday, 16 April 2005 23:40:29 UTC

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