- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 13 May 2009 13:44:55 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv15963
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml
Log Message:
6696
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- wseventing.xml 13 May 2009 13:26:20 -0000 1.41
+++ wseventing.xml 13 May 2009 13:44:53 -0000 1.42
@@ -1100,6 +1100,20 @@
</p>
<p>
+ If included within the Subscribe request message, the wse:NotifyTo
+ and wse:EndTo SHOULD have some cursory validity checking performed before
+ the Subscribe response is returned. While not all errors can be detected
+ prior to sending a message to those EPRs, some obvious ones can be
+ detected. For example, an unsupported transport specified within the
+ wsa:Address IRI.
+ Detecting these errors during Subscribe processing will lessen the chances
+ of the subscriber creating an unusable subscription. If this check is
+ performed and a problem is detected then the event source MAY generate
+ a wse:UnusableEPR fault rather than returning the SubscribeResponse
+ message.
+ </p>
+
+ <p>
If the event source accepts a request to create a
subscription, it MUST reply with a response of the following
form:
@@ -2444,6 +2458,41 @@
</table>
</div2>
+ <div2 id="UnusableEPR">
+ <head>UnusableEPR</head>
+
+ <p>
+ This fault MAY be generated when an Event Source detects
+ that the wse:NotifyTo or wse:EndTo EPR is unusable.
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <td><kw>[Code]</kw></td>
+ <td>s12:Sender</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Subcode]</kw></td>
+ <td>wse:UnusableEPR</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Reason]</kw></td>
+ <td>An EPR in the Subscribe request message is unusable.</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Detail]</kw></td>
+ <td>
+ <emph> The specific EPR that generated the error and why. </emph>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div2>
+
</div1>
<div1 id="Security">
@@ -3487,6 +3536,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6850">6850</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/05/13 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6696">6696</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- wseventing.html 13 May 2009 13:26:20 -0000 1.49
+++ wseventing.html 13 May 2009 13:44:53 -0000 1.50
@@ -70,6 +70,7 @@
6.9 <a href="#InvalidMessage">InvalidMessage</a><br/>
6.10 <a href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestUnavailable</a><br/>
6.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
+ 6.12 <a href="#UnusableEPR">UnusableEPR</a><br/>
7 <a href="#Security">Security Considerations</a><br/>
7.1 <a href="#MessageSecurity">Message Security</a><br/>
7.2 <a href="#AccessControl">Access Control</a><br/>
@@ -614,6 +615,18 @@
Other components of the outline above are not further
constrained by this specification.
</p><p>
+ If included within the Subscribe request message, the wse:NotifyTo
+ and wse:EndTo SHOULD have some cursory validity checking performed before
+ the Subscribe response is returned. While not all errors can be detected
+ prior to sending a message to those EPRs, some obvious ones can be
+ detected. For example, an unsupported transport specified within the
+ wsa:Address IRI.
+ Detecting these errors during Subscribe processing will lessen the chances
+ of the subscriber creating an unusable subscription. If this check is
+ performed and a problem is detected then the event source MAY generate
+ a wse:UnusableEPR fault rather than returning the SubscribeResponse
+ message.
+ </p><p>
If the event source accepts a request to create a
subscription, it MUST reply with a response of the following
form:
@@ -1334,7 +1347,11 @@
This fault MAY be generated when an Event Source detects a
wse:Subscribe request containing a filter that, for whatever
reason, will never evaluate to true.
- </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EmptyFilter</td></tr><tr><td><b>[Reason]</b></td><td>The wse:Filter would result in zero Notifications.</td></tr><tr><td><b>[Detail]</b></td><td><em> The wse:Filter value. </em></td></tr></tbody></table></div></div><div class="div1">
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EmptyFilter</td></tr><tr><td><b>[Reason]</b></td><td>The wse:Filter would result in zero Notifications.</td></tr><tr><td><b>[Detail]</b></td><td><em> The wse:Filter value. </em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="UnusableEPR" id="UnusableEPR"/>6.12 UnusableEPR</h3><p>
+ This fault MAY be generated when an Event Source detects
+ that the wse:NotifyTo or wse:EndTo EPR is unusable.
+ </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><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
@@ -1993,4 +2010,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6787">6787</a></td></tr><tr><td> 2009/04/28 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6788">6788</a></td></tr><tr><td> 2009/05/13 </td><td> KW </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6472">6472</a></td></tr><tr><td> 2009/05/13 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6850">6850</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=6850">6850</a></td></tr><tr><td> 2009/05/13 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6696">6696</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- wsenum.html 13 May 2009 00:34:06 -0000 1.36
+++ wsenum.html 13 May 2009 13:44:53 -0000 1.37
@@ -64,6 +64,7 @@
4.6 <a href="#InvalidEnumerationContext">InvalidEnumerationContext</a><br/>
4.7 <a href="#TimedOut">TimedOut</a><br/>
4.8 <a href="#UnableToRenew">UnableToRenew</a><br/>
+ 4.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
5 <a href="#Security">Security Considerations</a><br/>
6 <a href="#acks">Acknowledgements</a><br/>
7 <a href="#refs">References</a><br/>
@@ -435,6 +436,18 @@
Other components of the outline above are not
further constrained by this specification.
</p><p>
+ If included within the Enumerate request message, the
+ wsen:EndTo SHOULD have some cursory validity checking performed before
+ the Enumerate response is returned. While not all errors can be detected
+ prior to sending a message to that EPR, some obvious ones can be
+ detected. For example, an unsupported transport specified within the
+ wsa:Address IRI.
+ Detecting these errors during Enumerate processing will lessen the chances
+ of the consumer creating an unusable enumeration. If this check is
+ performed and a problem is detected then the event source MAY generate
+ a wsen:UnusableEPR fault rather than returning the EnumerateResponse.
+ message.
+ </p><p>
Upon successful processing of an Enumerate
request message, a data source is expected to create an enumeration
context and return that context in an Enumerate response message,
@@ -1097,7 +1110,11 @@
"data source unable to renew"
<em>
if no additional information is available.
- </em></td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div></div><div class="div1">
+ </em></td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
+<h3><a name="UnusableEPR" id="UnusableEPR"/>4.9 UnusableEPR</h3><p>
+ This fault MAY be generated when a Data Source detects
+ that the wsen:EndTo EPR is unusable.
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>The wsen:EndTo EPR is unusable.</td></tr><tr><td><b>[Detail]</b></td><td><em> Details as to why the EPR is unusable. </em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="Security" id="Security"/>5 Security Considerations</h2><p>
It is strongly recommended that the
communication between services be secured using the mechanisms
@@ -1636,4 +1653,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6726">6726</a></td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a></td></tr><tr><td> 2009/04/28 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6787">6787</a></td></tr><tr><td> 2009/05/12 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6860">6860</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=6860">6860</a></td></tr><tr><td> 2009/05/13 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6696">6696</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.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- wsenum.xml 13 May 2009 00:34:06 -0000 1.27
+++ wsenum.xml 13 May 2009 13:44:53 -0000 1.28
@@ -761,6 +761,20 @@
Other components of the outline above are not
further constrained by this specification.
</p>
+
+ <p>
+ If included within the Enumerate request message, the
+ wsen:EndTo SHOULD have some cursory validity checking performed before
+ the Enumerate response is returned. While not all errors can be detected
+ prior to sending a message to that EPR, some obvious ones can be
+ detected. For example, an unsupported transport specified within the
+ wsa:Address IRI.
+ Detecting these errors during Enumerate processing will lessen the chances
+ of the consumer creating an unusable enumeration. If this check is
+ performed and a problem is detected then the event source MAY generate
+ a wsen:UnusableEPR fault rather than returning the EnumerateResponse.
+ message.
+ </p>
<p>
Upon successful processing of an Enumerate
@@ -2015,6 +2029,41 @@
</table>
</div2>
+ <div2 id="UnusableEPR">
+ <head>UnusableEPR</head>
+
+ <p>
+ This fault MAY be generated when a Data Source detects
+ that the wsen:EndTo EPR is unusable.
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <td><kw>[Code]</kw></td>
+ <td>s12:Sender</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Subcode]</kw></td>
+ <td>wsen:UnusableEPR</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Reason]</kw></td>
+ <td>The wsen:EndTo EPR is unusable.</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Detail]</kw></td>
+ <td>
+ <emph> Details as to why the EPR is unusable. </emph>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div2>
+
</div1>
<div1 id="Security">
@@ -2800,6 +2849,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6860">6860</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/05/13 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6696">6696</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Wednesday, 13 May 2009 13:45:05 UTC