W3C home > Mailing lists > Public > public-ws-policy-eds@w3.org > November 2006

2006/ws/policy wsdl11elementidentifiers.html,NONE,1.1 wsdl11elementidentifiers.xml,NONE,1.1

From: David Orchard via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 08 Nov 2006 22:17:45 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1Ghvjt-00077X-DK@lionel-hutz.w3.org>

Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv27334

Added Files:
	wsdl11elementidentifiers.html wsdl11elementidentifiers.xml 
Log Message:
initial rev

--- NEW FILE: wsdl11elementidentifiers.html ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html xmlns:saxon="http://icl.com/saxon" lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>WSDL 1.1 Element Identifiers</title><style type="text/css">
code           { font-family: monospace; }

div.constraint,
div.issue,
div.note,
div.notice     { margin-left: 2em; }

ol.enumar      { list-style-type: decimal; }
ol.enumla      { list-style-type: lower-alpha; }
ol.enumlr      { list-style-type: lower-roman; }
ol.enumua      { list-style-type: upper-alpha; }
ol.enumur      { list-style-type: upper-roman; }


div.exampleInner pre { margin-left: 1em;
                       margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
                  margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
                   border-top-width: 4px;
                   border-top-style: double;
                   border-top-color: #d3d3d3;
                   border-bottom-width: 4px;
                   border-bottom-style: double;
                   border-bottom-color: #d3d3d3;
                   padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
                    margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p>
<h1><a name="title" id="title"></a>WSDL 1.1 Element Identifiers</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Note 08 November 2006</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/wsdl11-elementidentifier">http://www.w3.org/TR/wsdl11-elementidentifier</a></dd><dt xmlns:fo="http://www.w3.org/1999/XSL/Format">Latest version:</dt><dd xmlns:fo="http://www.w3.org/1999/XSL/Format"><a href="http://www.w3.org/TR/2006/Note-wsdl11-elementidentifier-20061108.html">http://www.w3.org/TR/2006/Note-wsdl11-elementidentifier-20061108.html</a></dd><dt>Previous version:</dt><dd>

		</dd><dt>Editor:</dt><dd>David Orchard, BEA Systems</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2006 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>WSDL 2.0 provides a element identifer for WSDL 2.0 elements.  This, the WSDL 1.1 element identifier, provides an element identifier for WSDL 1.1 .</p></div><div>
<h2><a name="status" id="status"></a>Status of this Document</h2><p>
This section describes the status of this document at the time of its 
publication. Other documents may supersede this document. A list of 
current W3C publications and the latest revision of this technical report 
can be found in the W3C technical reports index at <a href="http://www.w3.org/TR/">http://www.w3.org/TR</a>.
(say about version) It has been produced by the WS-Policy Working Group 
which is part of the Web Services Activity.
The current intention of the Working Groups is to issue the final version 
of this specification as a Working Group Note.</p><p>
Comments on this document are welcome. Please send them to the public 
mailing-list <a href="mailto:ws-policy-comments@w3.org">ws-policy-comments@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/ws-policy-comments/">archive</a>). It is inappropriate to send 
discussion email to this address. 
Publication as a Note does not imply endorsement by the W3C 
Membership. This is a draft document and may be updated, replaced or 
obsoleted by other documents at any time. It is inappropriate to cite this 
document as other than work in progress.
</p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br>
    1.1 <a href="#notcon">Notational Conventions</a><br>
2 <a href="#wsdl-iri-references">IRI-References for WSDL 1.1 Elements</a><br>
    2.1 <a href="#wsdl-iris">WSDL 1.1 IRIs</a><br>
    2.2 <a href="#Iri-ref-ex">Example</a><br>
3 <a href="#refs">References</a><br>
    3.1 <a href="#refs-norm">Normative References</a><br>
    3.2 <a href="#refs-inform">Informative References</a><br>
</p>
<h3><a name="appendices" id="appendices"></a>Appendix</h3><p class="toc">A <a href="#changelog">Change Log</a> (Non-Normative)<br>
</p></div><hr><div class="body"><div class="div1">
<h2><a name="intro" id="intro"></a>1 Introduction</h2><p>This document provides an element identifier for WSDL 1.1 identifiers.
			</p><div class="div2">
<h3><a name="notcon" id="notcon"></a>1.1 Notational Conventions</h3><p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL",
	  "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
	  and "OPTIONAL" in this document are to be interpreted as
	  described in RFC 2119 <a href="#RFC2119">[RFC 2119]</a>.</p><p>With the exception of examples and sections explicitly marked
    	as "Non-Normative", all parts of this specification are
    	normative.</p></div></div><div class="div1">
<h2><a name="wsdl-iri-references" id="wsdl-iri-references"></a>2 IRI-References for WSDL 1.1 Elements</h2><p>
		This appendix provides a syntax for IRI-references for all
		elements found in a WSDL 1.1 document. The IRI-references are easy
		to understand and compare, while imposing no burden on the WSDL 1.1
		author.
	</p><div class="div2">
<h3><a name="wsdl-iris" id="wsdl-iris"></a>2.1 WSDL 1.1 IRIs</h3><p>There are two main cases for WSDL 1.1 IRIs:</p><ul><li><p>the IRI of a WSDL 1.1 document</p></li><li><p>the IRI of a WSDL 1.1 namespace</p></li></ul><p>
		The IRI of a WSDL 1.1 document can be dereferenced to give a
		resource representation that contributes elements
		to a single WSDL 1.1 namespace. If the media type is set to the WSDL 1.1
		media type, then the fragment identifiers can be used to
		identify the main elements that are defined in the document.
	</p><p>
		In keeping with the WSDL 2.0, which has a recommendation that 
		that the namespace URI be dereferencible to a WSDL 1.1 document,
		this appendix specifies the use of the namespace IRI with the
		WSDL 1.1 fragment identifiers to form an IRI-reference.
	</p><p>
		The IRI in an IRI-reference for a WSDL 1.1 element is the
		namespace name of the
		<code>name</code>
		property of either the element itself, in the case of
		<code>portType</code>
		,
		<code>Binding</code>
		, and
		<code>Service</code>
		elements, or the
		<code>name</code>
		property of the ancestor top-level element. The IRI provided
		by the namespace name of the
		<code>name</code>
		property is combined with a zero or more
		<code>xmlns</code>
		pointer parts (see
		<em>3.4 Namespace Binding Context</em>
		in
		<a href="#XPTR">[XPointer Framework]</a>
		) followed by a single WSDL 1.1 pointer part, following the same rules as defined for WSDL 2.0 fragment ids
		<b><a href="#WSDL-PART1">???</a></b>
		.
	</p></div><div class="div2">
<h3><a name="Iri-ref-ex" id="Iri-ref-ex"></a>2.2 Example</h3><p>Consider the following WSDL 1.1 document located at
	http://example.org/TicketAgent.wsdl:
	</p><div class="exampleOuter">
<div class="exampleHeader"><a name="iri-ref-example-wsdl" id="iri-ref-example-wsdl"></a>Example: IRI-References - Example WSDL 1.1 Document</div><div class="exampleInner"><pre>

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;wsdl:definitions 
    targetNamespace="http://example.org/TicketAgent.wsdl11" 
    xmlns:wsdl="http://www.w3.org/TR/2001/NOTE-wsdl-20010315" 
    xmlns:xs="http://www.w3.org/2001/XMLSchema" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="http://www.w3.org/TR/2001/NOTE-wsdl-20010315 http://www.w3.org/TR/2001/NOTE-wsdl-20010315/wsdl11.xsd"&gt;
	
    &lt;wsdl:types&gt;
      &lt;xs:schema xmlns:xsTicketAgent="http://example.org/TicketAgent.xsd"
      targetNamespace="http://example.org/TicketAgent.xsd" 
      xmlns:xs="http://www.w3.org/2000/10/XMLSchema"&gt;
    
      &lt;xs:element name="listFlightsRequest" type="tListFlights"/&gt;   
       
      &lt;xs:complexType name="tListFlights"&gt;     
        &lt;xs:sequence&gt;      
          &lt;xs:element  name="travelDate" type="xs:date"/&gt;      
          &lt;xs:element  name="startCity" type="xs:string"/&gt;
          &lt;xs:element  name="endCity" type="xs:string"/&gt;      
        &lt;/xs:sequence&gt;     
      &lt;/xs:complexType&gt;   
            
    &lt;xs:element name="listFlightsResponse" type="tFlights"/&gt;    
     
     &lt;xs:complexType name="tFlightsResponse"&gt;     
        &lt;xs:sequence&gt;      
          &lt;xs:element  name="flightNumber" type="xs:integer" minOccurs="0" maxOccurs="unbounded"/&gt;      
        &lt;/xs:sequence&gt;     
      &lt;/xs:complexType&gt;
           
      &lt;/wsdl:types&gt;
	
    &lt;message name="listFlightsRequest"&gt;
	   &lt;part name="body" element="xsTicketAgent:listFlightRequest"/&gt;
    &lt;/message&gt;

    &lt;message name="listFlightsResponse"&gt;
        &lt;part name="body" element="xsTicketagent:listFlightsResponse"/&gt;
    &lt;/message&gt;

    &lt;wsdl:portType name="TicketAgent"&gt;

        &lt;wsdl:operation name="listFlights"&gt;
            &lt;wsdl:input message="xsTicketAgent:listFlightsRequest"/&gt;
            &lt;wsdl:output message="xsTicketAgent:listFlightsResponse"/&gt;
        &lt;/wsdl:operation&gt;

    &lt;/wsdl:portType&gt;
&lt;/wsdl:definitions&gt;

</pre></div></div><p>
Its elements have the following IRI-references which follow the above canonicalization rules except for the presence of
optional whitespace that has been added in order to improve the formatting:</p><div class="exampleOuter">
<div class="exampleHeader"><a name="iri-ref-example-iris" id="iri-ref-example-iris"></a>Example: IRI-References - Example IRIs</div><div class="exampleInner"><pre>
http://example.org/TicketAgent.wsdl11#
  wsd11.definitions() 

http://example.org/TicketAgent.wsdl11#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsd11.elementDeclaration(ns1:listFlightsRequest) 

http://example.org/TicketAgent.wsdl11#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsd11.elementDeclaration(ns1:listFlightsResponse) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portType(TicketAgent) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portTypeOperation(TicketAgent/listFlights) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portTypeMessageReference(TicketAgent/listFlights/In) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portTypeMessageReference(TicketAgent/listFlights/Out) 
  
http://example.org/TicketAgent.wsdl11#
  wsd11.MessageReference(TicketAgent/listFlightsRequest) 

http://example.org/TicketAgent.wsdl11#
  wsd11.MessageReference(TicketAgent/listFlightsResponse)

</pre></div></div></div></div><div class="div1">
<h2><a name="refs" id="refs"></a>3 References</h2><div class="div2">
<h3><a name="refs-norm" id="refs-norm"></a>3.1 Normative References</h3><dl><dt xmlns:fo="http://www.w3.org/1999/XSL/Format" class="label"><a name="RFC3023" id="RFC3023"></a>RFC 3023</dt><dd xmlns:fo="http://www.w3.org/1999/XSL/Format">IETF
	  "RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D. Kohn, July
	  1998.
        (See <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>)
      </dd><dt xmlns:fo="http://www.w3.org/1999/XSL/Format" class="label"><a name="WSDL-PART1" id="WSDL-PART1"></a>WSDL 2.0 Core</dt><dd xmlns:fo="http://www.w3.org/1999/XSL/Format"><a href="http://www.w3.org/TR/wsdl20 "><cite>
		 Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language
	  	</cite></a>, R. Chinnici, J-J.
	  	Moreau, A. Ryman, S. Weerawarana, Editors.  World
	  	Wide Web Consortium, 27 March 2006.  This version of the "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"
	  	Specification is available at
	  	http://www.w3.org/TR/wsdl20. The
	  	<a href="http://www.w3.org/TR/wsdl20 ">
	  		latest version of "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"
	  	</a>
	  	is available at
	  	http://www.w3.org/TR/wsdl20.
	  
        (See <a href="http://www.w3.org/TR/wsdl20 ">http://www.w3.org/TR/wsdl20 </a>)
      </dd><dt xmlns:fo="http://www.w3.org/1999/XSL/Format" class="label"><a name="WSDL11" id="WSDL11"></a>WSDL 1.1</dt><dd xmlns:fo="http://www.w3.org/1999/XSL/Format"><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>Web Services Description Language (WSDL)
	  1.1</cite></a>, E. Christensen, F. Curbera, G. Meredith, and
	  S. Weerawarana, Authors. World Wide Web Consortium, 15 March
	  2002. This version of the Web Services Description Language
          1.1 Note is http://www.w3.org/TR/2001/NOTE-wsdl-20010315. The <a href="http://www.w3.org/TR/wsdl">latest version of Web
	  Services Description Language 1.1</a> is available at
	  http://www.w3.org/TR/wsdl.
	
        (See <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>)
      </dd><dt xmlns:fo="http://www.w3.org/1999/XSL/Format" class="label"><a name="XPTR" id="XPTR"></a>XPointer Framework</dt><dd xmlns:fo="http://www.w3.org/1999/XSL/Format"><a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/"><cite>XPointer Framework</cite></a>,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/.
	  
        (See <a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">http://www.w3.org/TR/2003/REC-xptr-framework-20030325/</a>)
      </dd><dt xmlns:fo="http://www.w3.org/1999/XSL/Format" class="label"><a name="RFC2119" id="RFC2119"></a>RFC 2119</dt><dd xmlns:fo="http://www.w3.org/1999/XSL/Format">IETF "RFC 2119:
	  Key words for use in RFCs to Indicate Requirement Levels",
	  S. Bradner, March 1997.
        (See <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>)
      </dd><dt xmlns:fo="http://www.w3.org/1999/XSL/Format" class="label"><a name="RFC3986" id="RFC3986"></a>RFC 3986</dt><dd xmlns:fo="http://www.w3.org/1999/XSL/Format">IETF "RFC 3986:
	  Uniform Resource Identifiers (URI): Generic Syntax",
	  T. Berners-Lee, R. Fielding, L. Masinter, January 2005. 
        (See <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>)
      </dd></dl></div><div class="div2">
<h3><a name="refs-inform" id="refs-inform"></a>3.2 Informative References</h3></div></div></div><div class="back"><div class="div1">
<h2><a name="changelog" id="changelog"></a>A Change Log (Non-Normative)</h2><table border="1"><caption>Changes</caption><thead><tr><th>Who</th><th>When</th><th>What</th></tr></thead><tbody><tr><td>DBO</td><td>20061108</td><td>Initial Revision</td></tr></tbody></table></div></div></body></html>
--- NEW FILE: wsdl11elementidentifiers.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='UpdatedBibl.xsl'?>
<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.2//EN" "xmlspec.dtd" [
	<!ENTITY % entities SYSTEM "wsdl11eientitieswd.dtd">
	%entities;
	<!ENTITY status "Editors Copy $Date$">
	<!ENTITY wsdl-ns "http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
]>
<spec w3c-doctype="wd" role="Note">
	<header>
		<title>WSDL 1.1 Element Identifiers</title>
		<w3c-designation>&w3c-designation;</w3c-designation>
		<w3c-doctype>&status;</w3c-doctype>
		<pubdate>
			<day>&draft.day;</day>
			<month>&draft.month;</month>
			<year>&draft.year;</year>
		</pubdate>
		<publoc>
			<loc href="&wsdl11ei.latest;">&wsdl11ei.latest;</loc>
		</publoc>
		<latestloc>
			<loc href="&w3c-designation;.html">&w3c-designation;.html</loc>
		</latestloc>
		<prevlocs>

		</prevlocs>
		<authlist>
			<author>
				<name>David Orchard</name>
				<affiliation>BEA Systems</affiliation>
			</author>
		</authlist>
		<abstract>
			<p>WSDL 2.0 provides a element identifer for WSDL 2.0 elements.  This, the WSDL 1.1 element identifier, provides an element identifier for WSDL 1.1 .</p>
		</abstract>
		<status>
		<p>
This section describes the status of this document at the time of its 
publication. Other documents may supersede this document. A list of 
current W3C publications and the latest revision of this technical report 
can be found in the W3C technical reports index at <loc href="http://www.w3.org/TR/">http://www.w3.org/TR</loc>.
(say about version) It has been produced by the WS-Policy Working Group 
which is part of the Web Services Activity.
The current intention of the Working Groups is to issue the final version 
of this specification as a Working Group Note.</p>
<p>
Comments on this document are welcome. Please send them to the public 
mailing-list <loc href="mailto:ws-policy-comments@w3.org">ws-policy-comments@w3.org</loc> (<loc href="http://lists.w3.org/Archives/Public/ws-policy-comments/">archive</loc>). It is inappropriate to send 
discussion email to this address. 
Publication as a Note does not imply endorsement by the W3C 
Membership. This is a draft document and may be updated, replaced or 
obsoleted by other documents at any time. It is inappropriate to cite this 
document as other than work in progress.
</p>
</status>
		<langusage>
			<language id="en">English</language>
		</langusage>
		<revisiondesc>
			<p>Last Modified: $Date$ CET</p>
		</revisiondesc>
	</header>
	<body>
		<div1 id="intro">
			<head>Introduction</head>
			<p>This document provides an element identifier for WSDL 1.1 identifiers.
			</p>
			<div2 id="notcon">
				<head>Notational Conventions</head>
				<p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL",
	  "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
	  and "OPTIONAL" in this document are to be interpreted as
	  described in RFC 2119 <bibref ref="RFC2119"/>.</p>
				<p>With the exception of examples and sections explicitly marked
    	as "Non-Normative", all parts of this specification are
    	normative.</p>
			</div2>
		</div1>
		
<div1 id="wsdl-iri-references">
	<head>IRI-References for WSDL 1.1 Elements</head>

	<p>
		This appendix provides a syntax for IRI-references for all
		elements found in a WSDL 1.1 document. The IRI-references are easy
		to understand and compare, while imposing no burden on the WSDL 1.1
		author.
	</p>

	<div2 id="wsdl-iris">
	<head>WSDL 1.1 IRIs</head>
	<p>There are two main cases for WSDL 1.1 IRIs:</p>
	<ulist>
	<item><p>the IRI of a WSDL 1.1 document</p></item>
	<item><p>the IRI of a WSDL 1.1 namespace</p></item>
	</ulist>
	<p>
		The IRI of a WSDL 1.1 document can be dereferenced to give a
		resource representation that contributes elements
		to a single WSDL 1.1 namespace. If the media type is set to the WSDL 1.1
		media type, then the fragment identifiers can be used to
		identify the main elements that are defined in the document.
	</p>

	<p>
		In keeping with the WSDL 2.0, which has a recommendation that 
		that the namespace URI be dereferencible to a WSDL 1.1 document,
		this appendix specifies the use of the namespace IRI with the
		WSDL 1.1 fragment identifiers to form an IRI-reference.
	</p>

	<p>
		The IRI in an IRI-reference for a WSDL 1.1 element is the
		namespace name of the
		<code>name</code>
		property of either the element itself, in the case of
		<code>portType</code>
		,
		<code>Binding</code>
		, and
		<code>Service</code>
		elements, or the
		<code>name</code>
		property of the ancestor top-level element. The IRI provided
		by the namespace name of the
		<code>name</code>
		property is combined with a zero or more
		<code>xmlns</code>
		pointer parts (see
		<emph>3.4 Namespace Binding Context</emph>
		in
		<bibref ref="XPTR" />
		) followed by a single WSDL 1.1 pointer part, following the same rules as defined for WSDL 2.0 fragment ids
		<specref ref="WSDL-PART1" />
		.
	</p>

	</div2>
	<!--
	<div2 id="element-designator-canonical-form">
		<head>Canonical Form for WSDL 1.1 element Designators</head>
		<p>
			The IRI-references described above MAY be used as WSDL 1.1
			element designators. For ease of comparison, the fragment
			identifier of WSDL 1.1 element designators SHOULD conform
			to the following canonicalization rules:
		</p>
		<ulist>
			<item>
				<p>
					<assert class="element"
						id="CanonFragId-1900002" required="false">
						The fragment identifier consists of a sequence
						zero or more
						<code>xmlns()</code>
						pointer parts followed by exactly one
						<code>wsd11.*()</code>
						pointer part.
					</assert>
				</p>
			</item>
			<item>
				<p>
					<assert class="element"
						id="CanonFragId-1900003" required="false">
						Each
						<code>xmlns()</code>
						pointer part that appears in the fragment
						identifier defines a namespace that is
						referenced by the
						<code>wsd11.*()</code>
						pointer part.
					</assert>
				</p>
			</item>
			<item>
				<p>
					<assert class="element"
						id="CanonFragId-1900004" required="false">
						Each
						<code>xmlns()</code>
						pointer part defines a unique namespace.
					</assert>
				</p>
			</item>
			<item>
				<p>
					<assert class="element"
						id="CanonFragId-1900005" required="false">
						The
						<code>xmlns()</code>
						pointer parts define namespaces in the same
						order as they are referenced in the
						<code>wsd11.*()</code>
						pointer part.
					</assert>
				</p>
			</item>
			<item>
				<p>
					<assert class="element"
						id="CanonFragId-1900006" required="false">
						The namespace prefixes defined by the
						<code>xmlns()</code>
						pointer parts are named
						<code>ns1</code>
						,
						<code>ns2</code>
						, etc., in the order of their appearance.
					</assert>
				</p>
			</item>
			<item>
				<p>
					<assert class="element"
						id="CanonFragId-1900007" required="false">
						The fragment identifier contains no optional
						whitespace.
					</assert>
				</p>
			</item>
		</ulist>
	</div2>
-->
	<div2 id="Iri-ref-ex">
	<head>Example</head>
	<p>Consider the following WSDL 1.1 document located at
	http://example.org/TicketAgent.wsdl:
	</p>
	<example id="iri-ref-example-wsdl">
	<head>IRI-References - Example WSDL 1.1 Document</head>
	<eg xml:space="preserve">

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;wsdl:definitions 
    targetNamespace="http://example.org/TicketAgent.wsdl11" 
    xmlns:wsdl="&wsdl-ns;" 
    xmlns:xs="http://www.w3.org/2001/XMLSchema" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="&wsdl-ns; &wsdl-ns;/wsdl11.xsd"&gt;
	
    &lt;wsdl:types&gt;
      &lt;xs:schema xmlns:xsTicketAgent="http://example.org/TicketAgent.xsd"
      targetNamespace="http://example.org/TicketAgent.xsd" 
      xmlns:xs="http://www.w3.org/2000/10/XMLSchema"&gt;
    
      &lt;xs:element name="listFlightsRequest" type="tListFlights"/&gt;   
       
      &lt;xs:complexType name="tListFlights"&gt;     
        &lt;xs:sequence&gt;      
          &lt;xs:element  name="travelDate" type="xs:date"/&gt;      
          &lt;xs:element  name="startCity" type="xs:string"/&gt;
          &lt;xs:element  name="endCity" type="xs:string"/&gt;      
        &lt;/xs:sequence&gt;     
      &lt;/xs:complexType&gt;   
            
    &lt;xs:element name="listFlightsResponse" type="tFlights"/&gt;    
     
     &lt;xs:complexType name="tFlightsResponse"&gt;     
        &lt;xs:sequence&gt;      
          &lt;xs:element  name="flightNumber" type="xs:integer" minOccurs="0" maxOccurs="unbounded"/&gt;      
        &lt;/xs:sequence&gt;     
      &lt;/xs:complexType&gt;
           
      &lt;/wsdl:types&gt;
	
    &lt;message name="listFlightsRequest"&gt;
	   &lt;part name="body" element="xsTicketAgent:listFlightRequest"/&gt;
    &lt;/message&gt;

    &lt;message name="listFlightsResponse"&gt;
        &lt;part name="body" element="xsTicketagent:listFlightsResponse"/&gt;
    &lt;/message&gt;

    &lt;wsdl:portType name="TicketAgent"&gt;

        &lt;wsdl:operation name="listFlights"&gt;
            &lt;wsdl:input message="xsTicketAgent:listFlightsRequest"/&gt;
            &lt;wsdl:output message="xsTicketAgent:listFlightsResponse"/&gt;
        &lt;/wsdl:operation&gt;

    &lt;/wsdl:portType&gt;
&lt;/wsdl:definitions&gt;

</eg>
</example>
<p>
Its elements have the following IRI-references which follow the above canonicalization rules except for the presence of
optional whitespace that has been added in order to improve the formatting:</p>

<example id="iri-ref-example-iris">
<head>IRI-References - Example IRIs</head>
<eg xml:space="preserve">
http://example.org/TicketAgent.wsdl11#
  wsd11.definitions() 

http://example.org/TicketAgent.wsdl11#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsd11.elementDeclaration(ns1:listFlightsRequest) 

http://example.org/TicketAgent.wsdl11#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsd11.elementDeclaration(ns1:listFlightsResponse) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portType(TicketAgent) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portTypeOperation(TicketAgent/listFlights) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portTypeMessageReference(TicketAgent/listFlights/In) 

http://example.org/TicketAgent.wsdl11#
  wsd11.portTypeMessageReference(TicketAgent/listFlights/Out) 
  
http://example.org/TicketAgent.wsdl11#
  wsd11.MessageReference(TicketAgent/listFlightsRequest) 

http://example.org/TicketAgent.wsdl11#
  wsd11.MessageReference(TicketAgent/listFlightsResponse)

</eg>
</example>

	</div2>
    </div1>		
		
		<div1 id="refs">
			<head>References</head>
			<div2 id="refs-norm">
				<head>Normative References</head>
				<blist>

<bibl key="RFC 3023"	 
	  href="http://www.ietf.org/rfc/rfc3023.txt" id="RFC3023">IETF
	  "RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D. Kohn, July
	  1998.</bibl>
	  
	  <bibl key="WSDL 2.0 Core" href="http://www.w3.org/TR/wsdl20 "
	  	id="WSDL-PART1">
	  	<titleref>
		 Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language
	  	</titleref>, R. Chinnici, J-J.
	  	Moreau, A. Ryman, S. Weerawarana, Editors.  World
	  	Wide Web Consortium, 27 March 2006.  This version of the "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"
	  	Specification is available at
	  	http://www.w3.org/TR/wsdl20. The
	  	<loc href="http://www.w3.org/TR/wsdl20 ">
	  		latest version of "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"
	  	</loc>
	  	is available at
	  	http://www.w3.org/TR/wsdl20.
	  </bibl>


	  <bibl
	   
	    key="WSDL 1.1"
	    href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"
	    id="WSDL11">
	  <titleref>Web Services Description Language (WSDL)
	  1.1</titleref>, E. Christensen, F. Curbera, G. Meredith, and
	  S. Weerawarana, Authors. World Wide Web Consortium, 15 March
	  2002. This version of the Web Services Description Language
          1.1 Note is http://www.w3.org/TR/2001/NOTE-wsdl-20010315. The <loc
	  href="http://www.w3.org/TR/wsdl">latest version of Web
	  Services Description Language 1.1</loc> is available at
	  http://www.w3.org/TR/wsdl.
	</bibl>
	
<bibl key="XPointer Framework"
	    href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/"
	    id="XPTR">
	    <titleref>XPointer Framework</titleref>,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
	    <loc href='http://www.w3.org/TR/xptr-framework/'>latest
	    version of XPointer Framework</loc> is available at
	    http://www.w3.org/TR/xptr-framework/.
	  </bibl>
					<bibl key="RFC 2119" id="RFC2119" href="http://www.ietf.org/rfc/rfc2119.txt">IETF "RFC 2119:
	  Key words for use in RFCs to Indicate Requirement Levels",
	  S. Bradner, March 1997.</bibl>
					<bibl key="RFC 3986" id="RFC3986" href="http://www.ietf.org/rfc/rfc3986.txt">IETF "RFC 3986:
	  Uniform Resource Identifiers (URI): Generic Syntax",
	  T. Berners-Lee, R. Fielding, L. Masinter, January 2005. </bibl>
				</blist>
			</div2>
			<div2 id="refs-inform">
				<head>Informative References</head>

			</div2>
		</div1>
	</body>
	<back>
		<inform-div1 id="changelog">
			<head>Change Log</head>
			<table border="1">
				<caption>Changes</caption>
				<thead>
					<tr>
						<th>Who</th>
						<th>When</th>
						<th>What</th>
					</tr>
				</thead>
				<tbody>
					<tr>
						<td>DBO</td>
						<td>20061108</td>
						<td>Initial Revision</td>
					</tr>
					
				</tbody>
			</table>
		</inform-div1>
	</back>
</spec>
Received on Wednesday, 8 November 2006 22:18:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:58 GMT