- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 02 Oct 2009 15:50:35 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv19878
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml
wsfrag.html wsfrag.xml wsmex.html wsmex.xml wst.html wst.xml
Log Message:
7426
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -d -r1.62 -r1.63
--- wst.xml 28 Sep 2009 12:20:34 -0000 1.62
+++ wst.xml 2 Oct 2009 15:50:33 -0000 1.63
@@ -132,7 +132,7 @@
<p>As per the SOAP processing model, other specifications MAY define SOAP
headers which can be optionally added to request messages to require the
transfer of subsets or the application of transformations of the resource
- associated with the endpoint reference. When the Action URIs defined by
+ associated with the endpoint reference. When the Action IRIs defined by
this specification are used, such extension specifications MUST also allow
the basic processing models defined herein.</p>
<div2 id="reqs">
@@ -369,7 +369,7 @@
<gitem>
<label> <kw>[Action]</kw> </label>
<def>
- <p> The value to be used for the wsa:Action URI. </p>
+ <p> The value to be used for the wsa:Action IRI. </p>
</def>
</gitem>
@@ -459,8 +459,8 @@
</p>
<p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <bibref ref="RFC3986"/> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
</p>
<p>
@@ -507,10 +507,10 @@
<label> <kw>[Body]</kw>/wst:Get@Dialect </label>
<def>
<p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
@@ -523,7 +523,7 @@
<def>
<p>
The WS-Fragment <bibref ref="WsFrag"/> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this URI indicates that the contents
of the Get element MUST be processed as specified by the
WS-Fragment <bibref ref="WsFrag"/> specification.
</p>
@@ -706,10 +706,10 @@
<label> <kw>[Body]</kw>/wst:Put@Dialect </label>
<def>
<p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
@@ -722,7 +722,7 @@
<def>
<p>
The WS-Fragment <bibref ref="WsFrag"/> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this IRI indicates that the contents
of the Put element MUST be processed as specified by the
WS-Fragment <bibref ref="WsFrag"/> specification.
</p>
@@ -912,10 +912,10 @@
<label> <kw>[Body]</kw>/wst:Delete@Dialect </label>
<def>
<p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
@@ -928,7 +928,7 @@
<def>
<p>
The WS-Fragment <bibref ref="WsFrag"/> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this IRI indicates that the contents
of the Delete element MUST be processed as specified by the
WS-Fragment <bibref ref="WsFrag"/> specification.
</p>
@@ -1084,10 +1084,10 @@
<label> <kw>[Body]</kw>/wst:Create@Dialect </label>
<def>
<p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
@@ -1100,7 +1100,7 @@
<def>
<p>
The WS-Fragment <bibref ref="WsFrag"/> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this IRI indicates that the contents
of the Create element MUST be processed as specified by the
WS-Fragment <bibref ref="WsFrag"/> specification.
</p>
@@ -1386,7 +1386,7 @@
<head>UnknownDialect</head>
<p>
This fault is generated when a service detects an unknown Dialect
- URI in a request message.
+ IRI in a request message.
</p>
<table id="Table3" border="1" cellpadding="5">
<tbody>
@@ -1401,12 +1401,12 @@
<tr>
<th align="left"><kw>[Reason]</kw></th>
<td>
- The specified Dialect URI is not known.
+ The specified Dialect IRI is not known.
</td>
</tr>
<tr>
<th align="left"><kw>[Detail]</kw></th>
- <td><emph>The unknown URI if specified</emph></td>
+ <td><emph>The unknown IRI if specified</emph></td>
</tr>
</tbody>
</table>
@@ -1605,6 +1605,15 @@
Network Working Group, January 2005.
</bibl>
+ <bibl key="RFC 3987" id="RFC3987"
+ href="http://www.ietf.org/rfc/rfc3987.txt">
+ <titleref>
+ Internationalized Resource Identifiers (IRIs)
+ </titleref>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ </bibl>
+
<bibl key="SOAP11" id="SOAP11"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
<titleref>
@@ -2184,6 +2193,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6572">6572</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/02 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -d -r1.91 -r1.92
--- wseventing.html 2 Oct 2009 14:40:13 -0000 1.91
+++ wseventing.html 2 Oct 2009 15:50:32 -0000 1.92
@@ -339,7 +339,7 @@
In addition to Message Information Header properties
<a href="#AddrCore">[WS-Addressing]</a>,
this specification uses the following properties to define messages:
- </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+ </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
These properties bind to a SOAP Envelope as follows:
</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
<s:Header>
@@ -441,8 +441,8 @@
All messages defined by this specification MUST be sent to a Web service
that is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
</p><p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <a href="#RFC3986">[RFC 3986]</a> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
</p></div></div><div class="div1">
<h2><a name="SubMsgs" id="SubMsgs"/>4 Subscription Messages</h2><p>
To create, renew, and delete subscriptions, subscribers send
@@ -1169,7 +1169,7 @@
(21) </wse:SubscriptionEnd>
(22) </s12:Body>
(23) </s12:Envelope></pre></div></div><p>
- Line (08) is the action URI for Subscription End. Lines
+ Line (08) is the action IRI for Subscription End. Lines
(10-13) indicate the message is sent to the EndTo of the
subscribe request (lines (23-30) in <a href="#Table4">Example 4-1</a>).
Line (17) indicates the event source is shutting down, and
@@ -1308,7 +1308,7 @@
<h3><a name="FilteringRequestedUnavailable" id="FilteringRequestedUnavailable"/>6.5 FilteringRequestedUnavailable</h3><p>
This fault is generated when a Subscribe request specifies a filter
dialect that the event source does not support. Optionally, this
- fault MAY contain a list of supported filter dialect URIs in the
+ fault MAY contain a list of supported filter dialect IRIs in the
Detail property.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested filter dialect is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
<wse:SupportedDialect> +
@@ -1344,7 +1344,7 @@
<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.10 DeliveryFormatRequestUnavailable</h3><p>
This fault is generated when a Subscribe request specifies a delivery
format that is not supported by the event source. Optionally, this
- fault MAY contain a list of supported delivery format URIs in the
+ fault MAY contain a list of supported delivery format IRIs in the
Detail property.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:DeliveryFormatRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested delivery format is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
<wse:SupportedDeliveryFormat> +
@@ -1760,8 +1760,8 @@
Although there are many ways in which an Event Source can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
- This specification defines the following URI to serve as the Dialect
- URI for the wse:EventDescriptions element.
+ This specification defines the following IRI to serve as the Dialect
+ IRI for the wse:EventDescriptions element.
</p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-evt/EventDescriptions</pre></div></div><p>
The value of the @Identifier attribute for this Metadata Section MUST
be equal to the value of its wse:EventDescriptions/@targetNamespace. An
@@ -1814,7 +1814,7 @@
definitions element termed a "Notification WSDL". A Notification WSDL
describes the interface that the Event Sink is required to implement to
receive and process the Notifications that might result from a
- successful Subscribe request that used a particular Format URI. The
+ successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="idexample_1_2706" id="idexample_1_2706"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
@@ -1856,16 +1856,16 @@
Although there are many ways in which an Event Source can make
Notification WSDLs available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
- This specification defines the following URI to serve as the Dialect
- URI for the Notification WSDL.
+ This specification defines the following IRI to serve as the Dialect
+ IRI for the Notification WSDL.
</p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-evt/NotificationWSDL</pre></div></div><p>
Because the Notification Format specified in a Subscribe request can
affect various aspects of the Notification WSDL, it is necessary to
correlate Notification WSDLs with their corresponding Notification
Formats. When using WS-MetadataExchange to transfer Notification WSDLs,
- the corresponding Format URI for that Notification WSDL MUST be
+ the corresponding Format IRI for that Notification WSDL MUST be
represented via the @Identifier attribute. For any particular
- Format URI/@Identifier, there MUST NOT exist more than one
+ Format IRI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p></div></div><div class="div2">
<h3><a name="iddiv2_1_2728" id="iddiv2_1_2728"/>A.3 Multiple Event Information Metadata Sections</h3><p>
@@ -2370,4 +2370,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr><tr><td> 2009/09/22 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7698">7698</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6569">6569</a></td></tr><tr><td> 2009/10/01 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7589">7589</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7589">7589</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- wsfrag.xml 2 Oct 2009 15:28:28 -0000 1.18
+++ wsfrag.xml 2 Oct 2009 15:50:32 -0000 1.19
@@ -368,7 +368,7 @@
<gitem>
<label> <kw>[Action]</kw> </label>
<def>
- <p> The value to be used for the wsa:Action URI. </p>
+ <p> The value to be used for the wsa:Action IRI. </p>
</def>
</gitem>
@@ -464,8 +464,8 @@
</p>
<p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <bibref ref="RFC3986"/> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
</p>
</div2>
@@ -493,7 +493,7 @@
<head>Get</head>
<p>
To retrieve a subset of a resource
- a client MUST specify the WS-Fragment Dialect URI in the wst:Get request.
+ a client MUST specify the WS-Fragment Dialect IRI in the wst:Get request.
</p>
<p>
The Get request message MUST be of the following form:
@@ -542,7 +542,7 @@
<label> <kw>[Body]</kw>/wst:Get/wsf:Expression@Language </label>
<def>
<p>
- This URI indicates which expression language will be
+ This IRI indicates which expression language will be
used to identify the subset of the resource this operation applies
to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it
does not support the specified Language.
@@ -598,7 +598,7 @@
<head>Put</head>
<p>
To update a subset of a resource a client MUST specify the WS-Fragment
- URI in the wst:Put request.
+ IRI in the wst:Put request.
</p>
<p>
The Put request message MUST be of the following form:
@@ -668,7 +668,7 @@
<label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression@Language </label>
<def>
<p>
- This URI indicates which expression language will be
+ This IRI indicates which expression language will be
used to identify the subset of the resource this operation applies
to. A resource MUST generate a wsf:UnsupportedLanguage fault if it
does not support the specified Language.
@@ -920,7 +920,7 @@
</p>
<p>
- The QName language MUST be indicated by using the URI:
+ The QName language MUST be indicated by using the IRI:
</p>
<example>
<eg><loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra/QName">http://www.w3.org/&wsfra.nsprefix;/ws-fra/QName</loc></eg>
@@ -948,7 +948,7 @@
of XPath 1.0 <bibref ref="XPath1"/>, and is used to identify or select
a node (element, attribute
or value) within a resource
- representation or fragment. It is identified by the following URI:
+ representation or fragment. It is identified by the following IRI:
</p>
<example>
@@ -1251,7 +1251,7 @@
representation.
</p>
- <p>The XPath 1.0 language MUST be indicated by using the URI:</p>
+ <p>The XPath 1.0 language MUST be indicated by using the IRI:</p>
<example>
<eg><loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath">http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath</loc></eg>
</example>
@@ -1489,7 +1489,7 @@
<p>
This fault is generated when a service detects an unknown or
unsupported Language
- URI in a request message.
+ IRI in a request message.
</p>
<table id="Table3" border="1" cellpadding="5">
<tbody>
@@ -1504,12 +1504,12 @@
<tr>
<th align="left"><kw>[Reason]</kw></th>
<td>
- The specified Language URI is not supported.
+ The specified Language IRI is not supported.
</td>
</tr>
<tr>
<th align="left"><kw>[Detail]</kw></th>
- <td><emph>The unsupported Language URI.</emph></td>
+ <td><emph>The unsupported Language IRI.</emph></td>
</tr>
</tbody>
</table>
@@ -1673,6 +1673,15 @@
Network Working Group, January 2005.
</bibl>
+ <bibl key="RFC 3987" id="RFC3987"
+ href="http://www.ietf.org/rfc/rfc3987.txt">
+ <titleref>
+ Internationalized Resource Identifiers (IRIs)
+ </titleref>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ </bibl>
+
<bibl key="SOAP11" id="SOAP11"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
<titleref>
@@ -1901,6 +1910,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7770">7770</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/02 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- wsfrag.html 2 Oct 2009 15:28:28 -0000 1.17
+++ wsfrag.html 2 Oct 2009 15:50:32 -0000 1.18
@@ -176,7 +176,7 @@
In addition to Message Information Header properties
<a href="#AddrCore">[WS-Addressing]</a>,
this specification uses the following properties to define messages:
- </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+ </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
These properties bind to a SOAP Envelope as follows:
</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
<s:Header>
@@ -231,8 +231,8 @@
All messages defined by this specification MUST be sent to a Web service
that is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
</p><p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <a href="#RFC3986">[RFC 3986]</a> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
</p></div></div><div class="div1">
<h2><a name="fragments" id="fragments"/>3 Fragment WS-Transfer Dialect</h2><p>
This section defines the fragment transfer mechanism that the expression
@@ -248,7 +248,7 @@
</p><div class="div2">
<h3><a name="Get" id="Get"/>3.1 Get</h3><p>
To retrieve a subset of a resource
- a client MUST specify the WS-Fragment Dialect URI in the wst:Get request.
+ a client MUST specify the WS-Fragment Dialect IRI in the wst:Get request.
</p><p>
The Get request message MUST be of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
@@ -272,7 +272,7 @@
attribute, or is semantically invalid, a wsf:InvalidExpression
fault MUST be generated.
</p></dd><dt class="label"><b>[Body]</b>/wst:Get/wsf:Expression@Language </dt><dd><p>
- This URI indicates which expression language will be
+ This IRI indicates which expression language will be
used to identify the subset of the resource this operation applies
to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it
does not support the specified Language.
@@ -302,7 +302,7 @@
</p></div><div class="div2">
<h3><a name="Put" id="Put"/>3.2 Put</h3><p>
To update a subset of a resource a client MUST specify the WS-Fragment
- URI in the wst:Put request.
+ IRI in the wst:Put request.
</p><p>
The Put request message MUST be of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
@@ -338,7 +338,7 @@
This element identifies the fragment in the resource as it appears
after successfully processing the Put request.
</p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Language </dt><dd><p>
- This URI indicates which expression language will be
+ This IRI indicates which expression language will be
used to identify the subset of the resource this operation applies
to. A resource MUST generate a wsf:UnsupportedLanguage fault if it
does not support the specified Language.
@@ -502,7 +502,7 @@
This language can be implemented as a precise subset of the
XPath 1.0 <a href="#XPath1">[XPath1.0]</a> language.
</p><p>
- The QName language MUST be indicated by using the URI:
+ The QName language MUST be indicated by using the IRI:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-fra/QName">http://www.w3.org/2009/09/ws-fra/QName</a></pre></div></div></div><div class="div1">
<h2><a name="XPathL1" id="XPathL1"/>6 XPath Level 1 Expression Language</h2><p>
The XPath Level 1 expression language uses an XPath to
@@ -519,7 +519,7 @@
of XPath 1.0 <a href="#XPath1">[XPath1.0]</a>, and is used to identify or select
a node (element, attribute
or value) within a resource
- representation or fragment. It is identified by the following URI:
+ representation or fragment. It is identified by the following IRI:
</p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-fra/XPath-Level-1</pre></div></div><p>
An XPath Level 1 expression is an expression whose context is:
</p><ul><li><p>
@@ -683,7 +683,7 @@
define references to any element, attribute or value in the resource
representation and can also be used to compute values from the resource
representation.
- </p><p>The XPath 1.0 language MUST be indicated by using the URI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-fra/XPath">http://www.w3.org/2009/09/ws-fra/XPath</a></pre></div></div><p>
+ </p><p>The XPath 1.0 language MUST be indicated by using the IRI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-fra/XPath">http://www.w3.org/2009/09/ws-fra/XPath</a></pre></div></div><p>
Implementations that support the full XPath 1.0 language MUST
support the XPath Level 1 language.
</p><p>
@@ -800,10 +800,10 @@
<h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>8.1 UnsupportedLanguage</h3><p>
This fault is generated when a service detects an unknown or
unsupported Language
- URI in a request message.
+ IRI in a request message.
</p><a name="Table3" id="Table3"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnsupportedLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
- The specified Language URI is not supported.
- </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Language URI.</em></td></tr></tbody></table></div><div class="div2">
+ The specified Language IRI is not supported.
+ </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Language IRI.</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="InvalidFragment" id="InvalidFragment"/>8.2 InvalidFragment</h3><p>
This fault is generated when a service determines that the fragment
(contents of the wsf:Fragment element) specified in a request is invalid.
@@ -865,7 +865,12 @@
</cite></a>
, T. Berners-Lee, R. Fields and L. Masinter, Authors.
Network Working Group, January 2005.
- Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+ Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="RFC3987" id="RFC3987"/>RFC 3987</dt><dd><a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
+ Internationalized Resource Identifiers (IRIs)
+ </cite></a>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
@@ -971,4 +976,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/30 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7088">7088</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7770">7770</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7770">7770</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -d -r1.64 -r1.65
--- wst.html 23 Sep 2009 20:06:57 -0000 1.64
+++ wst.html 2 Oct 2009 15:50:32 -0000 1.65
@@ -60,8 +60,8 @@
7 <a href="#policy">WS-Transfer Policy Assertion(s)</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1295">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1442">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1343">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1503">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -102,7 +102,7 @@
configuration, or the dynamic state of the service.</p><p>As per the SOAP processing model, other specifications MAY define SOAP
headers which can be optionally added to request messages to require the
transfer of subsets or the application of transformations of the resource
- associated with the endpoint reference. When the Action URIs defined by
+ associated with the endpoint reference. When the Action IRIs defined by
this specification are used, such extension specifications MUST also allow
the basic processing models defined herein.</p><div class="div2">
<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>Provide a SOAP-based protocol for managing resources and their
@@ -121,13 +121,13 @@
<h3><a name="namespaces" id="namespaces"/>2.2 XML Namespaces</h3><p>
The XML Namespace URI that MUST be used by implementations of this
specification is:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></pre></div></div><p><a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-tra">http://www.w3.org/2009/09/ws-tra</a></pre></div></div><p><a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are
used in this specification. The
choice of any namespace prefix is arbitrary and not semantically
significant.
</p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1" cellpadding="5"><caption>Table 2-1:
Prefixes and XML Namespaces used in this specification.
- </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wst </td><td><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></td><td>
+ </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wst </td><td><a href="http://www.w3.org/2009/09/ws-tra">http://www.w3.org/2009/09/ws-tra</a></td><td>
This specification
</td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a></td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a></td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a></td><td>
XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr></tbody></table><p>
@@ -182,7 +182,7 @@
In addition to Message Information Header properties
<a href="#AddrCore">[WS-Addressing]</a>,
this specification uses the following properties to define messages:
- </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+ </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
These properties bind to a SOAP Envelope as follows:
</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
<s:Header>
@@ -233,8 +233,8 @@
All messages defined by this specification MUST be sent to a Web service
that is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
</p><p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <a href="#RFC3986">[RFC 3986]</a> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
</p><p>
A compliant SOAP Node that implements a resource MUST
provide the Get operation as defined in this specification, and MAY provide
@@ -243,7 +243,7 @@
<h2><a name="resourceOperations" id="resourceOperations"/>3 Resource Operations</h2><div class="div2">
<h3><a name="Get" id="Get"/>3.1 Get</h3><p>This specification defines one Web service operation (Get) for fetching a
one-time snapshot of the representation of a resource.</p><p>The Get request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/Get
+ http://www.w3.org/2009/09/ws-tra/Get
<b>[Body]</b>
<wst:Get Dialect="<em>xs:anyURI</em>"? ...>
@@ -254,23 +254,23 @@
content. However, it MAY include child element content as
defined by an extension(s).
</p></dd><dt class="label"><b>[Body]</b>/wst:Get@Dialect </dt><dd><p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
- </p></dd><dt class="label"><b>[Body]</b>/wst:Get@Dialect="http://www.w3.org/2009/02/ws-fra" </dt><dd><p>
+ </p></dd><dt class="label"><b>[Body]</b>/wst:Get@Dialect="http://www.w3.org/2009/09/ws-fra" </dt><dd><p>
The WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this URI indicates that the contents
of the Get element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
</p></dd></dl><p>A Get request MUST be targeted at the resource whose representation is
desired as described in <a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of
this specification.</p><p>If the resource accepts a Get request, it MUST reply with a response of
the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/GetResponse
+ http://www.w3.org/2009/09/ws-tra/GetResponse
<b>[Body]</b>
<wst:GetResponse ...>
@@ -312,7 +312,7 @@
EMEA
</xxx:Region>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/Get
+ http://www.w3.org/2009/09/ws-tra/Get
</wsa:Action>
<wsa:MessageID>
uuid:00000000-0000-0000-C000-000000000046
@@ -328,7 +328,7 @@
<s:Header>
<wsa:To>http://www.fabrikam123.example.org/pullport</wsa:Address>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/GetResponse
+ http://www.w3.org/2009/09/ws-tra/GetResponse
</wsa:Action>
<wsa:MessageID>
uuid:0000010e-0000-0000-C000-000000000046
@@ -371,7 +371,7 @@
</p><p>
The Put request message MUST be of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/Put
+ http://www.w3.org/2009/09/ws-tra/Put
<b>[Body]</b>
<wst:Put Dialect="<em>xs:anyURI</em>"? ...>
@@ -385,16 +385,16 @@
that is to be replaced. Additional extension elements MAY
be included after the element representing the resource.
</p></dd><dt class="label"><b>[Body]</b>/wst:Put@Dialect </dt><dd><p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
- </p></dd><dt class="label"><b>[Body]</b>/wst:Put@Dialect="http://www.w3.org/2009/02/ws-fra" </dt><dd><p>
+ </p></dd><dt class="label"><b>[Body]</b>/wst:Put@Dialect="http://www.w3.org/2009/09/ws-fra" </dt><dd><p>
The WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this IRI indicates that the contents
of the Put element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
</p></dd></dl><p>
@@ -428,7 +428,7 @@
If the resource accepts a Put request and performs the requested
update, it MUST reply with a response of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/PutResponse
+ http://www.w3.org/2009/09/ws-tra/PutResponse
<b>[Body]</b>
<wst:PutResponse ...>
@@ -472,7 +472,7 @@
EMEA
</xxx:Region>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/Put
+ http://www.w3.org/2009/09/ws-tra/Put
</wsa:Action>
<wsa:MessageID>
uuid:00000000-0000-0000-C000-000000000047
@@ -497,7 +497,7 @@
<s:Header>
<wsa:To>http://www.fabrikam123.example.org/sender</wsa:Address>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/PutResponse
+ http://www.w3.org/2009/09/ws-tra/PutResponse
</wsa:Action>
<wsa:MessageID>
uuid:0000010e-0000-0000-C000-000000000047
@@ -512,7 +512,7 @@
</s:Envelope> </pre></div></div></div><div class="div2">
<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p>This specification defines one Web service operation (Delete) for deleting
a resource in its entirety.</p><p>The Delete request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/Delete
+ http://www.w3.org/2009/09/ws-tra/Delete
<b>[Body]</b>
<wst:Delete Dialect="<em>xs:anyURI</em>"? ...>
@@ -523,16 +523,16 @@
content. However, it MAY include child element content as
defined by an extension(s).
</p></dd><dt class="label"><b>[Body]</b>/wst:Delete@Dialect </dt><dd><p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
- </p></dd><dt class="label"><b>[Body]</b>/wst:Delete@Dialect="http://www.w3.org/2009/02/ws-fra" </dt><dd><p>
+ </p></dd><dt class="label"><b>[Body]</b>/wst:Delete@Dialect="http://www.w3.org/2009/09/ws-fra" </dt><dd><p>
The WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this IRI indicates that the contents
of the Delete element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
</p></dd></dl><p>A Delete request MUST be targeted at the resource to be deleted as
@@ -543,7 +543,7 @@
specification.</p><p>A successful Delete operation invalidates the current representation
associated with the targeted resource.</p><p>If the resource accepts a Delete request, it MUST reply with a response of
the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/DeleteResponse
+ http://www.w3.org/2009/09/ws-tra/DeleteResponse
<b>[Body]</b>
<wst:DeleteResponse ...>
@@ -572,7 +572,7 @@
EMEA
</xxx:Region>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/Delete
+ http://www.w3.org/2009/09/ws-tra/Delete
</wsa:Action>
<wsa:MessageID>
uuid:00000000-0000-0000-C000-000000000049
@@ -589,7 +589,7 @@
<s:Header>
<wsa:To>http://www.fabrikam123.example.org/sender</wsa:Address>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/DeleteResponse
+ http://www.w3.org/2009/09/ws-tra/DeleteResponse
</wsa:Action>
<wsa:MessageID>
uuid:0000010e-0000-0000-C000-000000000049
@@ -617,7 +617,7 @@
presented representation. The new resource will be assigned a
service-determined endpoint reference that is returned in the response
message.</p><p>The Create request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/Create
+ http://www.w3.org/2009/09/ws-tra/Create
<b>[Body]</b>
<wst:Create Dialect="<em>xs:anyURI</em>"? ...>
@@ -635,16 +635,16 @@
Additional extension elements MAY be included only after
the mandated first child element.
</p></dd><dt class="label"><b>[Body]</b>/wst:Create@Dialect </dt><dd><p>
- When this OPTIONAL attribute is present it contains a URI that
+ When this OPTIONAL attribute is present it contains a IRI that
refers to additional information for the service on how to
process this element. If the attribute is present but the
- dialect URI is not known then the service MUST generate an
+ dialect IRI is not known then the service MUST generate an
UnknownDialect fault. There is no default value for the
attribute. If the attribute is absent, then the base
behavior is used.
- </p></dd><dt class="label"><b>[Body]</b>/wst:Create@Dialect="http://www.w3.org/2009/02/ws-fra" </dt><dd><p>
+ </p></dd><dt class="label"><b>[Body]</b>/wst:Create@Dialect="http://www.w3.org/2009/09/ws-fra" </dt><dd><p>
The WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification defines
- this dialect URI. Use of this URI indicates that the contents
+ this dialect IRI. Use of this IRI indicates that the contents
of the Create element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
</p></dd></dl><p>A Create request MUST be targeted at a resource factory capable of
@@ -656,7 +656,7 @@
See <a href="#Faults"><b>5 Faults</b></a>.</p><p>Other components of the outline above are not further constrained by this
specification.</p><p>If the resource factory accepts a Create request, it MUST reply with a
response of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-tra/CreateResponse
+ http://www.w3.org/2009/09/ws-tra/CreateResponse
<b>[Body]</b>
<wst:CreateResponse ...>
@@ -715,7 +715,7 @@
</wsa:ReplyTo>
<wsa:To>http://www.example.org/pushport/CustomerSpace</wsa:To>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/Create
+ http://www.w3.org/2009/09/ws-tra/Create
</wsa:Action>
<wsa:MessageID>
uuid:00000000-0000-0000-C000-000000000048
@@ -736,12 +736,12 @@
success:</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope
xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
- xmlns:wst="http://www.w3.org/2009/02/ws-tra"
+ xmlns:wst="http://www.w3.org/2009/09/ws-tra"
xmlns:xxx="http://fabrikam123.example.com/resource-model" >
<s:Header>
<wsa:To>http://www.fabrikam123.example.org/sender</wsa:Address>
<wsa:Action>
- http://www.w3.org/2009/02/ws-tra/CreateResponse
+ http://www.w3.org/2009/09/ws-tra/CreateResponse
</wsa:Action>
<wsa:MessageID>
uuid:0000010e-0000-0000-C000-000000000048
@@ -769,7 +769,7 @@
Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
The <b>[Action]</b> property below MUST be used for faults
defined in this specification:
- </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/02/ws-tra/fault</pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-tra/fault</pre></div></div><p>
The definitions of faults in this section use the following properties:
</p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element
is defined for the fault.<br/></p><p>
@@ -814,10 +814,10 @@
wst:Put or wst:Create message. </p><a name="Table2" id="Table2"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidRepresentation</td></tr><tr><th align="left"><b>[Reason]</b></th><td>The supplied representation is invalid</td></tr><tr><th align="left"><b>[Detail]</b></th><td>none</td></tr></tbody></table></div><div class="div2">
<h3><a name="UnknownDialect" id="UnknownDialect"/>5.2 UnknownDialect</h3><p>
This fault is generated when a service detects an unknown Dialect
- URI in a request message.
+ IRI in a request message.
</p><a name="Table3" id="Table3"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnknownDialect</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
- The specified Dialect URI is not known.
- </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown URI if specified</em></td></tr></tbody></table></div><div class="div2">
+ The specified Dialect IRI is not known.
+ </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown IRI if specified</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="PutDenied" id="PutDenied"/>5.3 PutDenied</h3><p>
This fault is generated when a Put request message attempts
to modify a portion of a resource but is not allowed to do so.
@@ -906,7 +906,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1295" id="iddiv2_1_1295"/>9.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1343" id="iddiv2_1_1343"/>9.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -916,7 +916,12 @@
</cite></a>
, T. Berners-Lee, R. Fields and L. Masinter, Authors.
Network Working Group, January 2005.
- Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+ Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="RFC3987" id="RFC3987"/>RFC 3987</dt><dd><a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
+ Internationalized Resource Identifiers (IRIs)
+ </cite></a>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
@@ -963,7 +968,7 @@
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1442" id="iddiv2_1_1442"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
+<h3><a name="iddiv2_1_1503" id="iddiv2_1_1503"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
</cite></a>
, D. Davis, et al., Editors.
@@ -993,12 +998,12 @@
A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra/transfer.xsd">http://www.w3.org/2009/02/ws-tra/transfer.xsd</a></pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-tra/transfer.xsd">http://www.w3.org/2009/09/ws-tra/transfer.xsd</a></pre></div></div><p>
A non-normative copy of the XML schema is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
- targetNamespace="http://www.w3.org/2009/02/ws-tra"
- xmlns:tns="http://www.w3.org/2009/02/ws-tra"
+ targetNamespace="http://www.w3.org/2009/09/ws-tra"
+ xmlns:tns="http://www.w3.org/2009/09/ws-tra"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
elementFormDefault="qualified"
@@ -1089,12 +1094,12 @@
<h2><a name="Appendix_II__E2_80_93_WSDL" id="Appendix_II__E2_80_93_WSDL"/>B WSDL</h2><p>
A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a> description
for this specification can be retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra/transfer.wsdl">http://www.w3.org/2009/02/ws-tra/transfer.wsdl</a></pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-tra/transfer.wsdl">http://www.w3.org/2009/09/ws-tra/transfer.wsdl</a></pre></div></div><p>
A non-normative copy of the WSDL description is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsdl:definitions
- targetNamespace="http://www.w3.org/2009/02/ws-tra"
- xmlns:tns="http://www.w3.org/2009/02/ws-tra"
+ targetNamespace="http://www.w3.org/2009/09/ws-tra"
+ xmlns:tns="http://www.w3.org/2009/09/ws-tra"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
@@ -1103,8 +1108,8 @@
<wsdl:types>
<xs:schema>
<xs:import
- namespace="http://www.w3.org/2009/02/ws-tra"
- schemaLocation="http://www.w3.org/2009/02/ws-tra/transfer.xsd"
+ namespace="http://www.w3.org/2009/09/ws-tra"
+ schemaLocation="http://www.w3.org/2009/09/ws-tra/transfer.xsd"
/>
</xs:schema>
</wsdl:types>
@@ -1145,26 +1150,26 @@
<wsdl:operation name="Get">
<wsdl:input
message="tns:GetMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/Get"/>
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/Get"/>
<wsdl:output
message="tns:GetResponseMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/GetResponse" />
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/GetResponse" />
</wsdl:operation>
<wsdl:operation name="Put">
<wsdl:input
message="tns:PutMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/Put" />
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/Put" />
<wsdl:output
message="tns:PutResponseMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/PutResponse" />
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/PutResponse" />
</wsdl:operation>
<wsdl:operation name="Delete">
<wsdl:input
message="tns:DeleteMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/Delete" />
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/Delete" />
<wsdl:output
message="tns:DeleteResponseMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/DeleteResponse" />
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/DeleteResponse" />
</wsdl:operation>
</wsdl:portType>
@@ -1176,10 +1181,10 @@
<wsdl:operation name="Create">
<wsdl:input
message="tns:CreateMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/Create" />
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/Create" />
<wsdl:output
message="tns:CreateResponseMessage"
- wsam:Action="http://www.w3.org/2009/02/ws-tra/CreateResponse" />
+ wsam:Action="http://www.w3.org/2009/09/ws-tra/CreateResponse" />
</wsdl:operation>
</wsdl:portType>
@@ -1217,4 +1222,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr><tr><td> 2009/09/16 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7486">7486</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6572">6572</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6572">6572</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -d -r1.52 -r1.53
--- wsmex.xml 28 Sep 2009 12:20:34 -0000 1.52
+++ wsmex.xml 2 Oct 2009 15:50:32 -0000 1.53
@@ -627,7 +627,7 @@
<gitem>
<label> <kw>[Action]</kw> </label>
<def>
- <p> The value to be used for the wsa:Action URI. </p>
+ <p> The value to be used for the wsa:Action IRI. </p>
</def>
</gitem>
@@ -717,8 +717,8 @@
</p>
<p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <bibref ref="RFC3986"/> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
</p>
<p>
@@ -856,7 +856,7 @@
<p>
This indicates the format and version of the metadata unit
contained in this Metadata Section (e.g., WSDL version 1.1). Dialect
- is an absolute URI.
+ is an absolute IRI.
</p>
</def>
</gitem>
@@ -871,7 +871,7 @@
<table border ='1'>
<tbody>
<tr>
- <th align="left"> Dialect URI </th>
+ <th align="left"> Dialect IRI </th>
<th align="left"> Metadata Format </th>
</tr>
<tr>
@@ -930,7 +930,7 @@
<def>
<p>
This indicates the Identifier for the metadata unit in this
- Metadata Section. Identifier is an absolute URI.
+ Metadata Section. Identifier is an absolute IRI.
If omitted, there is no implied value.
</p>
@@ -959,7 +959,7 @@
<table border ='1'>
<tbody>
<tr>
- <th align="left"> Dialect URI </th>
+ <th align="left"> Dialect IRI </th>
<th align="left"> @Identifier value </th>
</tr>
<tr>
@@ -1108,7 +1108,7 @@
<p>
When this repeating OPTIONAL element is present,the response
MUST include only Metadata Sections corresponding to the
- dialect specified by the URI attribute; if the receiver does
+ dialect specified by the IRI attribute; if the receiver does
not have any Metadata Sections of the indicated dialect, the
response MUST include zero Metadata Sections. </p>
@@ -1121,7 +1121,11 @@
<label> <kw>[Body]</kw>/mex:GetMetadata/mex:Dialect@URI </label>
<def>
<p>
- This REQUIRED attribute specifies the Metadata dialect. The response MUST only include Metadata Sections corresponding to the dialect specified by this URI. If the receiver does not have any Metadata Sections of this indicated dialect, the response MUST include zero Metadata Sections for this URI.
+ This REQUIRED attribute specifies the Metadata dialect. The response
+ MUST only include Metadata Sections corresponding to the dialect
+ specified by this IRI. If the receiver does not have any Metadata
+ Sections of this indicated dialect, the response MUST include zero
+ Metadata Sections for this IRI.
</p>
</def>
</gitem>
@@ -1149,7 +1153,7 @@
Metadata Sections with the indicated identifier; if the receiver
does not have any Metadata Sections of the indicated identifier,
the response MUST include zero Metadata Sections for this
- URI/Identifier pair.
+ IRI/Identifier pair.
When this attribute is not present, the implied value is any
identifier.
If multiple Metadata Sections have the indicated Dialect
@@ -1166,13 +1170,13 @@
Metadata Sections of this specified content form. If the specified
content form is not available, or not known,
then the response MUST include zero
- Metadata Sections of the specified form for this URI/Identifier pair.
- This specification defines the following content form URIs:
+ Metadata Sections of the specified form for this IRI/Identifier pair.
+ This specification defines the following content form IRIs:
</p>
<table border ='1'>
<tbody>
<tr>
- <th align="left"> Content Form URI </th>
+ <th align="left"> Content Form IRI </th>
<th align="left"> Form </th>
</tr>
<tr>
@@ -1520,7 +1524,7 @@
to authenticate and verify the integrity of the data. Specifically,
recipients SHOULD verify that the sender has the right to "speak" for
the metadata. This is important because some metadata, such as
- schemas, have embedded target URIs that might be outside the scope
+ schemas, have embedded target IRIs that might be outside the scope
of the sender.
</p>
@@ -1662,6 +1666,15 @@
Network Working Group, January 2005.
</bibl>
+ <bibl key="RFC 3987" id="RFC3987"
+ href="http://www.ietf.org/rfc/rfc3987.txt">
+ <titleref>
+ Internationalized Resource Identifiers (IRIs)
+ </titleref>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ </bibl>
+
<bibl key="SOAP11" id="SOAP11"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
<titleref>
@@ -2187,6 +2200,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6570">6570</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/02 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- wsenum.html 30 Sep 2009 09:11:55 -0000 1.63
+++ wsenum.html 2 Oct 2009 15:50:32 -0000 1.64
@@ -70,7 +70,7 @@
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
8.1 <a href="#iddiv2_1_1879">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2039">Informative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2052">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -193,7 +193,7 @@
In addition to Message Information Header properties
<a href="#AddrCore">[WS-Addressing]</a>,
this specification uses the following properties to define messages:
- </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+ </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
These properties bind to a SOAP Envelope as follows:
</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
<s:Header>
@@ -297,8 +297,8 @@
All messages defined by this specification MUST be sent to a Web service
that is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
</p><p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <a href="#RFC3986">[RFC 3986]</a> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
</p></div></div><div class="div1">
<h2><a name="EnumMsgs" id="EnumMsgs"/>3 Enumeration Messages</h2><p>
Enumeration contexts represent a specific
@@ -1281,7 +1281,12 @@
</cite></a>
, T. Berners-Lee, R. Fields and L. Masinter, Authors.
Network Working Group, January 2005.
- Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+ Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="RFC3987" id="RFC3987"/>RFC 3987</dt><dd><a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
+ Internationalized Resource Identifiers (IRIs)
+ </cite></a>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
@@ -1333,7 +1338,7 @@
, J. Clark, S. DeRose, Editors.
World Wide Web Consortium (W3C), 16 November 1999.
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2039" id="iddiv2_1_2039"/>8.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_2052" id="iddiv2_1_2052"/>8.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
OASIS Standard, "Web Services Secure Conversation
(WS-SecureConversation) 1.4"
</cite></a>
@@ -1746,4 +1751,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6568">6568</a></td></tr><tr><td> 2009/09/30 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7716">7716</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7716">7716</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- wsenum.xml 30 Sep 2009 09:11:55 -0000 1.56
+++ wsenum.xml 2 Oct 2009 15:50:32 -0000 1.57
@@ -286,7 +286,7 @@
<gitem>
<label> <kw>[Action]</kw> </label>
<def>
- <p> The value to be used for the wsa:Action URI. </p>
+ <p> The value to be used for the wsa:Action IRI. </p>
</def>
</gitem>
@@ -532,8 +532,8 @@
</p>
<p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <bibref ref="RFC3986"/> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
</p>
</div2>
@@ -2335,6 +2335,15 @@
, T. Berners-Lee, R. Fields and L. Masinter, Authors.
Network Working Group, January 2005.
</bibl>
+
+ <bibl key="RFC 3987" id="RFC3987"
+ href="http://www.ietf.org/rfc/rfc3987.txt">
+ <titleref>
+ Internationalized Resource Identifiers (IRIs)
+ </titleref>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ </bibl>
<bibl key="SOAP11" id="SOAP11"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
@@ -3109,6 +3118,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7716">7716</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/02 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -d -r1.62 -r1.63
--- wsmex.html 23 Sep 2009 19:37:15 -0000 1.62
+++ wsmex.html 2 Oct 2009 15:50:32 -0000 1.63
@@ -62,8 +62,8 @@
10 <a href="#policy">WS-MetadataExchange Policy Assertion(s)</a><br/>
11 <a href="#Acknowledgements">Acknowledgements</a><br/>
12 <a href="#References">References</a><br/>
- 12.1 <a href="#iddiv2_1_1331">Normative References</a><br/>
- 12.2 <a href="#iddiv2_1_1491">Informative References</a><br/>
+ 12.1 <a href="#iddiv2_1_1387">Normative References</a><br/>
+ 12.2 <a href="#iddiv2_1_1560">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
B <a href="#Appendix-B">WSDL</a><br/>
@@ -139,7 +139,7 @@
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'>
(04) <s11:Header>
(05) <wsa:Action>
-(06) http://www.w3.org/2009/02/ws-tra/Get
+(06) http://www.w3.org/2009/09/ws-tra/Get
(07) </wsa:Action>
(08) <wsa:To>http://services.example.org/stockquote/metadata</wsa:To>
(09) <wsa:ReplyTo>
@@ -164,12 +164,12 @@
<div class="exampleHeader"><a name="GetResponse" id="GetResponse"/>Example 2-2: Sample response message with metadata</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
-(04) xmlns:mex='http://www.w3.org/2009/02/ws-mex'
+(04) xmlns:mex='http://www.w3.org/2009/09/ws-mex'
(05) xmlns:wsp='http://www.w3.org/ns/ws-policy'
(06) xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>
(07) <s11:Header>
(08) <wsa:Action>
-(09) http://www.w3.org/2009/02/ws-tra/GetResponse
+(09) http://www.w3.org/2009/09/ws-tra/GetResponse
(10) </wsa:Action>
(11) <wsa:To>http://client.example.org</wsa:To>
(12) <wsa:RelatesTo>
@@ -270,11 +270,11 @@
<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"/>Example 2-3: Sample GetMetadata request message</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
-(04) xmlns:mex='http://www.w3.org/2009/02/ws-mex' >
+(04) xmlns:mex='http://www.w3.org/2009/09/ws-mex' >
(05) <s11:Header>
(06) <wsa:To>http://services.example.org/stockquote</wsa:To>
(07) <wsa:Action>
-(08) http://www.w3.org/2009/02/ws-mex/GetMetadata
+(08) http://www.w3.org/2009/09/ws-mex/GetMetadata
(09) </wsa:Action>
(10) <wsa:MessageID>
(11) urn:uuid:73d7edfc-5c3c-49b9-ba46-2480caee43e9
@@ -300,11 +300,11 @@
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
(04) xmlns:wsp='http://www.w3.org/ns/ws-policy'
-(05) xmlns:mex='http://www.w3.org/2009/02/ws-mex'>
+(05) xmlns:mex='http://www.w3.org/2009/09/ws-mex'>
(06) <s11:Header>
(07) <wsa:To>http://client.example.org</wsa:To>
(08) <wsa:Action>
-(09) http://www.w3.org/2009/02/ws-mex/GetMetadataResponse
+(09) http://www.w3.org/2009/09/ws-mex/GetMetadataResponse
(10) </wsa:Action>
(11) <wsa:RelatesTo>
(12) urn:uuid:73d7edfc-5c3c-49b9-ba46-2480caee43e9
@@ -338,10 +338,10 @@
<h3><a name="namespaces" id="namespaces"/>3.1 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of this
specification is:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex">http://www.w3.org/2009/02/ws-mex</a></pre></div></div><p><a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-mex">http://www.w3.org/2009/09/ws-mex</a></pre></div></div><p><a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this
specification. The choice of any namespace prefix is arbitrary and
not semantically significant.
- </p><a name="XMLNS" id="XMLNS"/><table border="1"><caption>Table 3-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td><a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2009/02/ws-mex </td><td> This specification </td></tr><tr><td> xs /td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> wst </td><td> http://www.w3.org/2009/02/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</a></td></tr></tbody></table><p>
+ </p><a name="XMLNS" id="XMLNS"/><table border="1"><caption>Table 3-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td><a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2009/09/ws-mex </td><td> This specification </td></tr><tr><td> xs /td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> wst </td><td> http://www.w3.org/2009/09/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</a></td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
Metadata Exchange namespace URI each time a new version of this document is
published until such time that the document reaches Candidate
@@ -389,7 +389,7 @@
In addition to Message Information Header properties
<a href="#AddrCore">[WS-Addressing]</a>,
this specification uses the following properties to define messages:
- </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+ </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
These properties bind to a SOAP Envelope as follows:
</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
<s:Header>
@@ -440,8 +440,8 @@
All messages defined by this specification MUST be sent to a Web service
that is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
</p><p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <a href="#RFC3986">[RFC 3986]</a> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
</p><p>
Support for the GetMetadata operation by a Web service is
optional. If metadata about a Web service endpoint is referenced by
@@ -528,17 +528,17 @@
</p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/@Dialect</dt><dd><p>
This indicates the format and version of the metadata unit
contained in this Metadata Section (e.g., WSDL version 1.1). Dialect
- is an absolute URI.
+ is an absolute IRI.
</p></dd></dl><p>
This specification defines the following values for Dialect;
other specifications SHOULD define values for Dialect for their
metadata format(s).
- </p><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all </td><td> None. [Defined in this specification for use in GetMetadata requests. See <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
+ </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all </td><td> None. [Defined in this specification for use in GetMetadata requests. See <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
If there is more than one metadata unit with the same Dialect, e.g.,
more than one XML Schema document, including them all, one per
Metadata Section, is explicitly encouraged.
</p><dl><dt class="label">
- /mex:Metadata/mex:MetadataSection/@Dialect ="http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex"
+ /mex:Metadata/mex:MetadataSection/@Dialect ="http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex"
</dt><dd><p>
This dialect value indicates that the type of the metadata contained
within the Metadata Section is itself a mex:Metadata element.
@@ -549,7 +549,7 @@
<a href="#EPRMD">Example 7-2</a> illustrates the use of this dialect.
</p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/@Identifier</dt><dd><p>
This indicates the Identifier for the metadata unit in this
- Metadata Section. Identifier is an absolute URI.
+ Metadata Section. Identifier is an absolute IRI.
If omitted, there is no implied value.
</p><p>
The interpretation of Identifier is Dialect-specific. While the
@@ -568,7 +568,7 @@
same. For well-known metadata formats, it is RECOMMENDED
that the value of the Identifier comes from the metadata when
that is possible, as the table below shows.
- </p></dd></dl><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> @Identifier value </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions/@targetNamespace </td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy/@Name </td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> Not defined </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex </td><td> Not defined </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all </td><td> Not defined </td></tr></tbody></table><p>
+ </p></dd></dl><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th align="left"> @Identifier value </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions/@targetNamespace </td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy/@Name </td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> Not defined </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex </td><td> Not defined </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all </td><td> Not defined </td></tr></tbody></table><p>
If there is more than one metadata section with the same
identifier, e.g., more than one XML Schema in the same target
namespace, including them all, one per metadata section, is
@@ -624,7 +624,7 @@
retrieve that endpoint's metadata. The normative outline for a
GetMetadata request is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-mex/GetMetadata
+ http://www.w3.org/2009/09/ws-mex/GetMetadata
<b>[Body]</b>
<mex:GetMetadata ... >
@@ -638,22 +638,26 @@
</p><dl><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect </dt><dd><p>
When this repeating OPTIONAL element is present,the response
MUST include only Metadata Sections corresponding to the
- dialect specified by the URI attribute; if the receiver does
+ dialect specified by the IRI attribute; if the receiver does
not have any Metadata Sections of the indicated dialect, the
response MUST include zero Metadata Sections. </p><p>When this element
is not present, the endpoint SHOULD return all the types of metadata that it deems necessary to communicate with it.
</p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI </dt><dd><p>
- This REQUIRED attribute specifies the Metadata dialect. The response MUST only include Metadata Sections corresponding to the dialect specified by this URI. If the receiver does not have any Metadata Sections of this indicated dialect, the response MUST include zero Metadata Sections for this URI.
- </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all" </dt><dd><p>
+ This REQUIRED attribute specifies the Metadata dialect. The response
+ MUST only include Metadata Sections corresponding to the dialect
+ specified by this IRI. If the receiver does not have any Metadata
+ Sections of this indicated dialect, the response MUST include zero
+ Metadata Sections for this IRI.
+ </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all" </dt><dd><p>
This value returns all known metadata. The endpoint has the option to optimize the format in which it returns the data.
- </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex"</dt><dd><p>
+ </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex"</dt><dd><p>
This value returns no metadata sections.
</p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Identifier </dt><dd><p>
When this OPTIONAL attribute is present, the response MUST include only
Metadata Sections with the indicated identifier; if the receiver
does not have any Metadata Sections of the indicated identifier,
the response MUST include zero Metadata Sections for this
- URI/Identifier pair.
+ IRI/Identifier pair.
When this attribute is not present, the implied value is any
identifier.
If multiple Metadata Sections have the indicated Dialect
@@ -663,11 +667,11 @@
Metadata Sections of this specified content form. If the specified
content form is not available, or not known,
then the response MUST include zero
- Metadata Sections of the specified form for this URI/Identifier pair.
- This specification defines the following content form URIs:
- </p><table border="1"><tbody><tr><th align="left"> Content Form URI </th><th align="left"> Form </th></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Content/EPR </td><td> A MetadataReference element is returned </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Content/URI </td><td> A Location element is returned </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Content/Metadata </td><td> The metadata is inlined </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Content/Any </td><td> The service is free to chose any content form </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Content/All </td><td> The service MUST return all available content forms </td></tr></tbody></table><p>
+ Metadata Sections of the specified form for this IRI/Identifier pair.
+ This specification defines the following content form IRIs:
+ </p><table border="1"><tbody><tr><th align="left"> Content Form IRI </th><th align="left"> Form </th></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Content/EPR </td><td> A MetadataReference element is returned </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Content/URI </td><td> A Location element is returned </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Content/Metadata </td><td> The metadata is inlined </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Content/Any </td><td> The service is free to chose any content form </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Content/All </td><td> The service MUST return all available content forms </td></tr></tbody></table><p>
When not present the default value is
- "http://www.w3.org/2009/02/ws-mex/Content/Any".
+ "http://www.w3.org/2009/09/ws-mex/Content/Any".
</p></dd></dl><p>
Other message information headers defined by WS-Addressing
<a href="#AddrCore">[WS-Addressing]</a> MAY be included
@@ -682,7 +686,7 @@
a GetMetadataResponse message. The normative outline for a
GetMetadataResponse is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
- http://www.w3.org/2009/02/ws-mex/GetMetadataResponse
+ http://www.w3.org/2009/09/ws-mex/GetMetadataResponse
<b>[Body]</b>
<mex:GetMetadataResponse>
@@ -738,7 +742,7 @@
(02) xmlns:wsa='http://www.w3.org/2005/08/addressing'>
(03) <wsa:Address>http://services.example.org/stockquote</wsa:Address>
(04) <wsa:Metadata>
-(05) <mex:Metadata xmlns:mex='http://www.w3.org/2009/02/ws-mex'>
+(05) <mex:Metadata xmlns:mex='http://www.w3.org/2009/09/ws-mex'>
(06) <mex:MetadataSection Dialect='http://schemas.xmlsoap.org/wsdl/'>
(07) <wsdl:definitions
(08) name='StockQuote'
@@ -822,9 +826,9 @@
(02) xmlns:wsa='http://www.w3.org/2005/08/addressing'>
(03) <wsa:Address>http://services.example.org/stockquote</wsa:Address>
(04) <wsa:Metadata>
-(05) <mex:Metadata xmlns:mex='http://www.w3.org/2009/02/ws-mex'>
+(05) <mex:Metadata xmlns:mex='http://www.w3.org/2009/09/ws-mex'>
(06) <mex:MetadataSection
-(07) Dialect='http://www.w3.org/2009/02/ws-mex'>
+(07) Dialect='http://www.w3.org/2009/09/ws-mex'>
(08) <mex:MetadataReference>
(09) <wsa:Address>
(10) http://services.example.org/stockquote/metadata
@@ -902,7 +906,7 @@
to authenticate and verify the integrity of the data. Specifically,
recipients SHOULD verify that the sender has the right to "speak" for
the metadata. This is important because some metadata, such as
- schemas, have embedded target URIs that might be outside the scope
+ schemas, have embedded target IRIs that might be outside the scope
of the sender.
</p><p>
Additionally, some metadata formats, such as policies
@@ -973,7 +977,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1331" id="iddiv2_1_1331"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1387" id="iddiv2_1_1387"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -983,7 +987,12 @@
</cite></a>
, T. Berners-Lee, R. Fields and L. Masinter, Authors.
Network Working Group, January 2005.
- Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+ Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="RFC3987" id="RFC3987"/>RFC 3987</dt><dd><a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
+ Internationalized Resource Identifiers (IRIs)
+ </cite></a>
+ , M. Duerst and M. Suignard, Authors.
+ Internet Engineering Task Force, January 2005.
+ Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
@@ -1035,7 +1044,7 @@
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1491" id="iddiv2_1_1491"/>12.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1560" id="iddiv2_1_1560"/>12.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
OASIS Standard, "Web Services Secure Conversation
(WS-SecureConversation) 1.4"
</cite></a>
@@ -1066,12 +1075,12 @@
A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd">http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd</a></pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-mex/MetadataExchange.xsd">http://www.w3.org/2009/09/ws-mex/MetadataExchange.xsd</a></pre></div></div><p>
A non-normative copy of the XML Schema description is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
- targetNamespace='http://www.w3.org/2009/02/ws-mex'
- xmlns:tns='http://www.w3.org/2009/02/ws-mex'
+ targetNamespace='http://www.w3.org/2009/09/ws-mex'
+ xmlns:tns='http://www.w3.org/2009/09/ws-mex'
xmlns:wsa='http://www.w3.org/2005/08/addressing'
xmlns:xs='http://www.w3.org/2001/XMLSchema'
elementFormDefault='qualified'
@@ -1147,12 +1156,12 @@
<h2><a name="Appendix-B" id="Appendix-B"/>B WSDL</h2><p>
A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a> description for
this specification can be retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl">http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl</a></pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-mex/metadataexchange.wsdl">http://www.w3.org/2009/09/ws-mex/metadataexchange.wsdl</a></pre></div></div><p>
A non-normative copy of the WSDL description is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsdl:definitions
- targetNamespace='http://www.w3.org/2009/02/ws-mex'
- xmlns:tns='http://www.w3.org/2009/02/ws-mex'
+ targetNamespace='http://www.w3.org/2009/09/ws-mex'
+ xmlns:tns='http://www.w3.org/2009/09/ws-mex'
xmlns:wsa='http://www.w3.org/2005/08/addressing'
xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
@@ -1160,7 +1169,7 @@
<wsdl:types>
<xs:schema
- targetNamespace='http://www.w3.org/2009/02/ws-mex'>
+ targetNamespace='http://www.w3.org/2009/09/ws-mex'>
<xs:include schemaLocation='metadataexchange.xsd'/>
</xs:schema>
</wsdl:types>
@@ -1176,11 +1185,11 @@
<wsdl:input
message='tns:GetMetadataMsg'
wsam:Action=
- 'http://www.w3.org/2009/02/ws-mex/GetMetadata'/>
+ 'http://www.w3.org/2009/09/ws-mex/GetMetadata'/>
<wsdl:output
message='tns:GetMetadataResponseMsg'
wsam:Action=
- 'http://www.w3.org/2009/02/ws-mex/GetMetadataResponse'/>
+ 'http://www.w3.org/2009/09/ws-mex/GetMetadataResponse'/>
</wsdl:operation>
</wsdl:portType>
@@ -1216,4 +1225,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6702">6702</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6570">6570</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6570">6570</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -d -r1.83 -r1.84
--- wseventing.xml 2 Oct 2009 14:40:13 -0000 1.83
+++ wseventing.xml 2 Oct 2009 15:50:32 -0000 1.84
@@ -499,7 +499,7 @@
<gitem>
<label> <kw>[Action]</kw> </label>
<def>
- <p> The value to be used for the wsa:Action URI. </p>
+ <p> The value to be used for the wsa:Action IRI. </p>
</def>
</gitem>
@@ -754,8 +754,8 @@
</p>
<p>
- Unless otherwise noted, all URIs are absolute URIs and URI comparison
- MUST be performed according to <bibref ref="RFC3986"/> section 6.2.1.
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
</p>
</div2>
@@ -1866,7 +1866,7 @@
</example>
<p>
- Line (08) is the action URI for Subscription End. Lines
+ Line (08) is the action IRI for Subscription End. Lines
(10-13) indicate the message is sent to the EndTo of the
subscribe request (lines (23-30) in <specref ref="Table4"/>).
Line (17) indicates the event source is shutting down, and
@@ -2178,7 +2178,7 @@
<p>
This fault is generated when a Subscribe request specifies a filter
dialect that the event source does not support. Optionally, this
- fault MAY contain a list of supported filter dialect URIs in the
+ fault MAY contain a list of supported filter dialect IRIs in the
Detail property.
</p>
@@ -2368,7 +2368,7 @@
<p>
This fault is generated when a Subscribe request specifies a delivery
format that is not supported by the event source. Optionally, this
- fault MAY contain a list of supported delivery format URIs in the
+ fault MAY contain a list of supported delivery format IRIs in the
Detail property.
</p>
@@ -3161,8 +3161,8 @@
Although there are many ways in which an Event Source can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <bibref ref="MEX"/>.
- This specification defines the following URI to serve as the Dialect
- URI for the wse:EventDescriptions element.
+ This specification defines the following IRI to serve as the Dialect
+ IRI for the wse:EventDescriptions element.
</p>
<example>
@@ -3258,7 +3258,7 @@
definitions element termed a "Notification WSDL". A Notification WSDL
describes the interface that the Event Sink is required to implement to
receive and process the Notifications that might result from a
- successful Subscribe request that used a particular Format URI. The
+ successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
</p>
@@ -3307,8 +3307,8 @@
Although there are many ways in which an Event Source can make
Notification WSDLs available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <bibref ref="MEX"/>.
- This specification defines the following URI to serve as the Dialect
- URI for the Notification WSDL.
+ This specification defines the following IRI to serve as the Dialect
+ IRI for the Notification WSDL.
</p>
<example>
@@ -3320,9 +3320,9 @@
affect various aspects of the Notification WSDL, it is necessary to
correlate Notification WSDLs with their corresponding Notification
Formats. When using WS-MetadataExchange to transfer Notification WSDLs,
- the corresponding Format URI for that Notification WSDL MUST be
+ the corresponding Format IRI for that Notification WSDL MUST be
represented via the @Identifier attribute. For any particular
- Format URI/@Identifier, there MUST NOT exist more than one
+ Format IRI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p>
</div3>
@@ -4219,6 +4219,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7589">7589</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/02 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Friday, 2 October 2009 15:50:45 UTC