- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 13 Jan 2010 01:54:38 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv32141
Modified Files:
wseventing.html wseventing.xml wst.html wst.xml
Log Message:
8176
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -d -r1.92 -r1.93
--- wst.xml 12 Jan 2010 21:38:21 -0000 1.92
+++ wst.xml 13 Jan 2010 01:54:35 -0000 1.93
@@ -488,8 +488,12 @@
<emph>xs:any</emph>*
</wst:Get></eg>
</example>
- <p>The following describes additional, normative constraints on the outline
-listed above:</p>
+
+ <p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p>
+
<glist>
<gitem>
<label> <kw>[Body]</kw>/wst:Get </label>
@@ -529,11 +533,24 @@
</gitem>
</glist>
- <p>A Get request MUST be targeted at the resource whose representation is
- desired as described in <specref ref="Notations_and_Terminology"/> of
-this specification.</p>
- <p>If the resource accepts a Get request, it MUST reply with a response of
-the following form:</p>
+
+ <p>
+ If the request message reaches a conformant implementation of
+ WS-Transfer and the message refers to an unknown resource, then the
+ implementation MUST generate a wst:UnknownResource fault.
+ </p>
+
+ <p>
+ A Get request MUST be targeted at the resource whose representation is
+ desired as described in <specref ref="Notations_and_Terminology"/> of
+ this specification.
+ </p>
+
+ <p>
+ If the resource accepts a Get request, it MUST reply with a response
+ of the following form:
+ </p>
+
<example>
<eg><kw>[Action]</kw>
http://www.w3.org/&wstra.nsprefix;/ws-tra/GetResponse
@@ -651,6 +668,7 @@
</xxx:Customer></eg>
</example>
</div2>
+
<div2 id="Put">
<head>Put</head>
<p>
@@ -682,6 +700,7 @@
<emph>xs:any</emph>*
</wst:Put></eg>
</example>
+
<p>
The following describes additional, normative constraints on the
outline listed above:
@@ -727,6 +746,13 @@
</gitem>
</glist>
+
+ <p>
+ If the request message reaches a conformant implementation of
+ WS-Transfer and the message refers to an unknown resource, then the
+ implementation MUST generate a wst:UnknownResource fault.
+ </p>
+
<p>
A Put request MUST be targeted at the resource whose representation is
desired to be replaced, as described in
@@ -876,6 +902,7 @@
</s:Envelope> </eg>
</example>
</div2>
+
<div2 id="Delete">
<head>Delete</head>
<p>
@@ -893,8 +920,12 @@
<emph>xs:any</emph>*
</wst:Delete></eg>
</example>
- <p>The following describes additional, normative constraints on the outline
-listed above:</p>
+
+ <p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p>
+
<glist>
<gitem>
<label> <kw>[Body]</kw>/wst:Delete </label>
@@ -937,17 +968,26 @@
</glist>
<p>
+ If the request message reaches a conformant implementation of
+ WS-Transfer and the message refers to an unknown resource, then the
+ implementation MUST generate a wst:UnknownResource fault.
+ </p>
+
+ <p>
A Delete request MUST be targeted at the resource to be deleted as
described in <specref ref="Notations_and_Terminology"/> of this
specification.
</p>
+
<p>
Other components of the outline above are not further constrained by
this specification.
</p>
+
<p>
A successful Delete operation deletes the targeted resource.
</p>
+
<p>
If the resource accepts a Delete request, it MUST reply with a
response of the following form:
@@ -978,8 +1018,11 @@
by this specification.
</p>
- <p>The following shows a sample SOAP envelope containing a Delete
-request:</p>
+ <p>
+ The following shows a sample SOAP envelope containing a Delete
+ request:
+ </p>
+
<example>
<eg><s:Envelope
xmlns:s="http://www.w3.org/2003/05/soap-envelope"
@@ -1045,20 +1088,24 @@
creating a resource and providing its initial representation.
This operation MAY be supported by compliant WS-Transfer resource
factories.
- In some cases, the
- initial representation MAY constitute the representation of a logical
- constructor for the resource and can thus differ structurally from the
- representation returned by Get or the one required by Put. This is because
- the parameterization requirement for creating a resource is often distinct
- from the steady-state representation of the resource. Implementations
- SHOULD provide metadata which describes the use of the representation and how
- it relates to the resource which is created, but such mechanisms are beyond
- the scope of this specification. The resource factory that receives a
- Create request will allocate a new resource that is initialized from the
- 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>
+ In some cases, the initial representation MAY constitute the
+ representation of a logical constructor for the resource and can
+ thus differ structurally from the representation returned by Get or
+ the one required by Put. This is because
+ the parameterization requirement for creating a resource is
+ often distinct from the steady-state representation of the resource.
+ Implementations SHOULD provide metadata which describes the use of
+ the representation and how it relates to the resource which is
+ created, but such mechanisms are beyond the scope of this
+ specification. The resource factory that receives a
+ Create request will allocate a new resource that is initialized
+ from the 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>
<example>
<eg><kw>[Action]</kw>
http://www.w3.org/&wstra.nsprefix;/ws-tra/Create
@@ -1456,6 +1503,36 @@
</table>
</div2>
+ <div2 id="UnknownResource">
+ <head>UnknownResource</head>
+ <p>
+ This fault is generated when a request specifies a resource that
+ is not known.
+ </p>
+ <table id="Table4" border="1" cellpadding="5">
+ <tbody>
+ <tr>
+ <th align="left"><kw>[Code]</kw></th>
+ <td>s:Sender</td>
+ </tr>
+ <tr>
+ <th align="left"><kw>[Subcode]</kw></th>
+ <td>wst:UnknownResource</td>
+ </tr>
+ <tr>
+ <th align="left"><kw>[Reason]</kw></th>
+ <td>
+ The resource is not known.
+ </td>
+ </tr>
+ <tr>
+ <th align="left"><kw>[Detail]</kw></th>
+ <td><emph>none</emph></td>
+ </tr>
+ </tbody>
+ </table>
+ </div2>
+
</div1>
<div1 id="Security_Considerations">
<head>Security Considerations</head>
@@ -2638,6 +2715,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8303">8303</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/12 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.140
retrieving revision 1.141
diff -u -d -r1.140 -r1.141
--- wseventing.xml 12 Jan 2010 21:15:01 -0000 1.140
+++ wseventing.xml 13 Jan 2010 01:54:35 -0000 1.141
@@ -1394,8 +1394,9 @@
</p>
<p>
- If the subscription is not active, the request MUST fail and the
- subscription manager MAY generate a wse:UnknownSubscription fault.
+ If the request message reaches a conformant implementation of
+ WS-Eventing and the message refers to an unknown subscription, then the
+ implemention MUST generate a wse:UnknownSubscription fault.
</p>
<p>
@@ -1562,11 +1563,6 @@
</example>
<p>
- If the subscription is not active, the request MUST fail and the
- subscription manager MAY generate a wse:UnknownSubscription fault.
- </p>
-
- <p>
Components of the outline listed above are constrained as for
a response to a renew request (see <specref ref="Renew"/>).
Other components of the outline above are not further
@@ -1574,6 +1570,12 @@
</p>
<p>
+ If the request message reaches a conformant implementation of
+ WS-Eventing and the message refers to an unknown subscription, then the
+ implemention MUST generate a wse:UnknownSubscription fault.
+ </p>
+
+ <p>
This operation is safe; it will not result in any side effect
imputable to the requester. This means that in case of an underlying
protocol error that might get unnoticed, resending the same request
@@ -1709,13 +1711,14 @@
</example>
<p>
- If the subscription is not active, the request MUST fail and the
- subscription manager MAY generate a wse:UnknownSubscription fault.
+ Components of the outline listed above are not further
+ constrained by this specification.
</p>
<p>
- Components of the outline listed above are not further
- constrained by this specification.
+ If the request message reaches a conformant implementation of
+ WS-Eventing and the message refers to an unknown subscription, then the
+ implemention MUST generate a wse:UnknownSubscription fault.
</p>
<p>
@@ -2393,7 +2396,7 @@
<p>
This fault is generated when a request specifies a subscription
- that is not active.
+ that is not known.
</p>
<table border="1">
@@ -2410,7 +2413,7 @@
<tr>
<td><kw>[Reason]</kw></td>
- <td>the subscription is not active.</td>
+ <td>The subscription is not known.</td>
</tr>
<tr>
@@ -4688,6 +4691,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8281">8281</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/12 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -d -r1.93 -r1.94
--- wst.html 12 Jan 2010 21:38:21 -0000 1.93
+++ wst.html 13 Jan 2010 01:54:35 -0000 1.94
@@ -56,14 +56,15 @@
5.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br/>
5.2 <a href="#UnknownDialect">UnknownDialect</a><br/>
5.3 <a href="#PutDenied">PutDenied</a><br/>
+ 5.4 <a href="#UnknownResource">UnknownResource</a><br/>
6 <a href="#Security_Considerations">Security Considerations</a><br/>
7 <a href="#metadata">WS-Transfer Metadata</a><br/>
- 7.1 <a href="#iddiv2_1_1333">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1403">TransferResourceFactory Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_1395">TransferResource Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1465">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1456">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1629">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1518">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1691">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="#WSDL">WSDL</a><br/>
@@ -250,8 +251,10 @@
<b>[Body]</b>
<wst:Get Dialect="<em>xs:anyURI</em>"? ...>
<em>xs:any</em>*
- </wst:Get></pre></div></div><p>The following describes additional, normative constraints on the outline
-listed above:</p><dl><dt class="label"><b>[Body]</b>/wst:Get </dt><dd><p>
+ </wst:Get></pre></div></div><p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p><dl><dt class="label"><b>[Body]</b>/wst:Get </dt><dd><p>
This is a REQUIRED element that has no defined child element
content.
</p></dd><dt class="label"><b>[Body]</b>/wst:Get@Dialect </dt><dd><p>
@@ -267,10 +270,18 @@
this dialect IRI. Use of this IRI 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>
+ </p></dd></dl><p>
+ If the request message reaches a conformant implementation of
+ WS-Transfer and the message refers to an unknown resource, then the
+ implementation MUST generate a wst:UnknownResource fault.
+ </p><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/09/ws-tra/GetResponse
<b>[Body]</b>
@@ -398,6 +409,10 @@
of the Put element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
</p></dd></dl><p>
+ If the request message reaches a conformant implementation of
+ WS-Transfer and the message refers to an unknown resource, then the
+ implementation MUST generate a wst:UnknownResource fault.
+ </p><p>
A Put request MUST be targeted at the resource whose representation is
desired to be replaced, as described in
<a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of this specification.
@@ -519,8 +534,10 @@
<b>[Body]</b>
<wst:Delete Dialect="<em>xs:anyURI</em>"? ...>
<em>xs:any</em>*
- </wst:Delete></pre></div></div><p>The following describes additional, normative constraints on the outline
-listed above:</p><dl><dt class="label"><b>[Body]</b>/wst:Delete </dt><dd><p>
+ </wst:Delete></pre></div></div><p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p><dl><dt class="label"><b>[Body]</b>/wst:Delete </dt><dd><p>
This is a REQUIRED element that has no defined child element
content. However, it MAY include child element content as
defined by an extension(s).
@@ -538,6 +555,10 @@
of the Delete element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
</p></dd></dl><p>
+ If the request message reaches a conformant implementation of
+ WS-Transfer and the message refers to an unknown resource, then the
+ implementation MUST generate a wst:UnknownResource fault.
+ </p><p>
A Delete request MUST be targeted at the resource to be deleted as
described in <a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of this
specification.
@@ -560,8 +581,10 @@
</p></dd></dl><p>
Other components of the outline above are not further constrained
by this specification.
- </p><p>The following shows a sample SOAP envelope containing a Delete
-request:</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope
+ </p><p>
+ The following shows a sample SOAP envelope containing a Delete
+ request:
+ </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:xxx="http://fabrikam123.example.com/resource-model" >
@@ -615,19 +638,23 @@
creating a resource and providing its initial representation.
This operation MAY be supported by compliant WS-Transfer resource
factories.
- In some cases, the
- initial representation MAY constitute the representation of a logical
- constructor for the resource and can thus differ structurally from the
- representation returned by Get or the one required by Put. This is because
- the parameterization requirement for creating a resource is often distinct
- from the steady-state representation of the resource. Implementations
- SHOULD provide metadata which describes the use of the representation and how
- it relates to the resource which is created, but such mechanisms are beyond
- the scope of this specification. The resource factory that receives a
- Create request will allocate a new resource that is initialized from the
- 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>
+ In some cases, the initial representation MAY constitute the
+ representation of a logical constructor for the resource and can
+ thus differ structurally from the representation returned by Get or
+ the one required by Put. This is because
+ the parameterization requirement for creating a resource is
+ often distinct from the steady-state representation of the resource.
+ Implementations SHOULD provide metadata which describes the use of
+ the representation and how it relates to the resource which is
+ created, but such mechanisms are beyond the scope of this
+ specification. The resource factory that receives a
+ Create request will allocate a new resource that is initialized
+ from the 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/09/ws-tra/Create
<b>[Body]</b>
@@ -839,7 +866,13 @@
</p><a name="Table4" id="Table4"/><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:UpdateDenied</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
One or more elements or attributes cannot be updated.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>An OPTIONAL list of the QNames of the elements or
- attributes that are not allowed to be updated.</em></td></tr></tbody></table></div></div><div class="div1">
+ attributes that are not allowed to be updated.</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="UnknownResource" id="UnknownResource"/>5.4 UnknownResource</h3><p>
+ This fault is generated when a request specifies a resource that
+ is not known.
+ </p><a name="Table4" id="Table4"/><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:UnknownResource</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
+ The resource is not known.
+ </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="Security_Considerations" id="Security_Considerations"/>6 Security Considerations</h2><p>It is strongly RECOMMENDED that the communication between services be
secured using the mechanisms described in <a href="#WSSecurity">[WS-Security]</a>.</p><p>In order to properly secure messages, the body (even if empty) and all
relevant headers need to be included in the signature. Specifically, the
@@ -906,7 +939,7 @@
that indicate a particular security mechanism used to protect
the WS-Transfer operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1333" id="iddiv2_1_1333"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1395" id="iddiv2_1_1395"/>7.1 TransferResource Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Transfer specification's definition of a Transfer Resource
is through the use of the Web Services
@@ -974,7 +1007,7 @@
the Global Element Declaration (GED) or type of this resource. This
QName can be used in order to retrieve the schema of the resource.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1403" id="iddiv2_1_1403"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1465" id="iddiv2_1_1465"/>7.2 TransferResourceFactory Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Transfer specification's definition of a Transfer Resource Factory
is through the use of the Web Services
@@ -1046,7 +1079,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_1456" id="iddiv2_1_1456"/>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_1518" id="iddiv2_1_1518"/>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.
@@ -1114,7 +1147,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_1629" id="iddiv2_1_1629"/>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_1691" id="iddiv2_1_1691"/>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.
@@ -1438,4 +1471,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a></td></tr><tr><td> 2010/01/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8183">8183</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8300">8300</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8303">8303</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=8303">8303</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.146
retrieving revision 1.147
diff -u -d -r1.146 -r1.147
--- wseventing.html 12 Jan 2010 21:15:01 -0000 1.146
+++ wseventing.html 13 Jan 2010 01:54:35 -0000 1.147
@@ -841,8 +841,9 @@
of the outline above are not further constrained by this
specification.
</p><p>
- If the subscription is not active, the request MUST fail and the
- subscription manager MAY generate a wse:UnknownSubscription fault.
+ If the request message reaches a conformant implementation of
+ WS-Eventing and the message refers to an unknown subscription, then the
+ implemention MUST generate a wse:UnknownSubscription fault.
</p><p>
If the subscription manager chooses not to renew this
subscription, the request MUST fail, and the subscription manager
@@ -962,14 +963,15 @@
</wse:GrantedExpires> ?
<em>xs:any</em>*
</wse:GetStatusResponse></pre></div></div><p>
- If the subscription is not active, the request MUST fail and the
- subscription manager MAY generate a wse:UnknownSubscription fault.
- </p><p>
Components of the outline listed above are constrained as for
a response to a renew request (see <a href="#Renew"><b>4.2 Renew</b></a>).
Other components of the outline above are not further
constrained by this specification.
</p><p>
+ If the request message reaches a conformant implementation of
+ WS-Eventing and the message refers to an unknown subscription, then the
+ implemention MUST generate a wse:UnknownSubscription fault.
+ </p><p>
This operation is safe; it will not result in any side effect
imputable to the requester. This means that in case of an underlying
protocol error that might get unnoticed, resending the same request
@@ -1066,11 +1068,12 @@
<wse:UnsubscribeResponse ...>
<em>xs:any</em>*
</wse:UnsubscribeResponse></pre></div></div><p>
- If the subscription is not active, the request MUST fail and the
- subscription manager MAY generate a wse:UnknownSubscription fault.
- </p><p>
Components of the outline listed above are not further
constrained by this specification.
+ </p><p>
+ If the request message reaches a conformant implementation of
+ WS-Eventing and the message refers to an unknown subscription, then the
+ implemention MUST generate a wse:UnknownSubscription fault.
</p><p><a href="#Table10">Example 4-7</a> lists a hypothetical request to delete the
subscription created in <a href="#Table5">Example 4-2</a>.
</p><div class="exampleOuter">
@@ -1359,8 +1362,8 @@
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>An EPR in the Subscribe request message is unusable.</td></tr><tr><td><b>[Detail]</b></td><td><em> The specific EPR that generated the error and why. </em></td></tr></tbody></table></div><div class="div2">
<h3><a name="UnknownSubscription" id="UnknownSubscription"/>6.10 UnknownSubscription</h3><p>
This fault is generated when a request specifies a subscription
- that is not active.
- </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnknownSubscription</td></tr><tr><td><b>[Reason]</b></td><td>the subscription is not active.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
+ that is not known.
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnknownSubscription</td></tr><tr><td><b>[Reason]</b></td><td>The subscription is not known.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="Security" id="Security"/>7 Security Considerations</h2><div class="div2">
<h3><a name="MessageSecurity" id="MessageSecurity"/>7.1 Message Security</h3><p>
It is strongly RECOMMENDED that the communication between
@@ -2605,4 +2608,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8287">8287</a></td></tr><tr><td> 2010/01/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8165">8165</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164">8164</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8281">8281</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=8281">8281</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 13 January 2010 01:54:40 UTC