- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 19 Jan 2010 23:14:51 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv22450
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml
wsfrag.html wsfrag.xml wst.html wst.xml
Log Message:
8283
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -d -r1.95 -r1.96
--- wst.xml 19 Jan 2010 22:54:17 -0000 1.95
+++ wst.xml 19 Jan 2010 23:14:49 -0000 1.96
@@ -397,6 +397,16 @@
serializable in XML 1.0, hence the use of XML 1.0.
</p>
+ <p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
+ </p>
+
</div2>
<div2 id="extensions">
@@ -1419,9 +1429,11 @@
<div2 id="InvalidRepresentation">
<head>InvalidRepresentation</head>
- <p>This fault is generated when an incorrect representation is sent in a
- wst:Put or wst:Create message. </p>
- <table id="Table2" border="1" cellpadding="5">
+ <p>
+ This fault MUST be generated when an incorrect representation is
+ sent in a wst:Put or wst:Create message.
+ </p>
+ <table border="1">
<tbody>
<tr>
<th align="left"><kw>[Code]</kw></th>
@@ -1446,10 +1458,10 @@
<div2 id="UnknownDialect">
<head>UnknownDialect</head>
<p>
- This fault is generated when a service detects an unknown Dialect
- IRI in a request message.
+ This fault MUST be generated when a service detects an unknown
+ Dialect IRI in a request message.
</p>
- <table id="Table3" border="1" cellpadding="5">
+ <table border="1">
<tbody>
<tr>
<th align="left"><kw>[Code]</kw></th>
@@ -1476,10 +1488,10 @@
<div2 id="PutDenied">
<head>PutDenied</head>
<p>
- This fault is generated when a Put request message attempts
+ This fault MUST be generated when a Put request message attempts
to modify a portion of a resource but is not allowed to do so.
</p>
- <table id="Table4" border="1" cellpadding="5">
+ <table border="1">
<tbody>
<tr>
<th align="left"><kw>[Code]</kw></th>
@@ -1507,10 +1519,10 @@
<div2 id="UnknownResource">
<head>UnknownResource</head>
<p>
- This fault is generated when a request specifies a resource that
- is not known.
+ This fault MUST be generated when a request specifies a resource
+ that is not known.
</p>
- <table id="Table4" border="1" cellpadding="5">
+ <table border="1">
<tbody>
<tr>
<th align="left"><kw>[Code]</kw></th>
@@ -2730,6 +2742,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8301">8301</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/19 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -d -r1.149 -r1.150
--- wseventing.html 19 Jan 2010 22:38:48 -0000 1.149
+++ wseventing.html 19 Jan 2010 23:14:49 -0000 1.150
@@ -76,22 +76,22 @@
7.2 <a href="#AccessControl">Access Control</a><br/>
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_2164">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2237">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2166">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2239">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2308">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2442">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2310">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2444">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3_1_2644">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2665">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2670">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2688">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2646">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2667">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2672">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2690">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2715">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2736">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2717">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2738">Multiple Event Information Metadata Sections</a><br/>
B <a href="#Schema">XML Schema</a><br/>
C <a href="#WSDL">WSDL</a><br/>
D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -349,6 +349,14 @@
<a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
+ </p><p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
</p></div><div class="div2">
<h3><a name="extensions" id="extensions"/>3.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
@@ -1316,25 +1324,25 @@
likely to succeed.
</p></dd></dl></div><div class="div2">
<h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>6.2 InvalidExpirationTime</h3><p>
- This fault is generated when a request specifies an
+ This fault MUST be generated when a request specifies an
expiration that is malformed.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidExpirationTime</td></tr><tr><td><b>[Reason]</b></td><td>The expiration time requested is invalid.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="ExpirationTimeExceeded" id="ExpirationTimeExceeded"/>6.3 ExpirationTimeExceeded</h3><p>
- This fault is generated when a request specifies an
+ This fault MUST be generated when a request specifies an
expiration that is not within the min/max range.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:ExpirationTimeExceeded</td></tr><tr><td><b>[Reason]</b></td><td>The expiration time requested is not within the min/max range.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="UnsupportedExpirationType" id="UnsupportedExpirationType"/>6.4 UnsupportedExpirationType</h3><p>
- This fault is generated when a Subscribe request specifies an
+ This fault MUST be generated when a Subscribe request specifies an
expiration time and the event source is only capable of accepting
expiration durations; for instance, if the event source does not
have access to absolute time.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnsupportedExpirationType</td></tr><tr><td><b>[Reason]</b></td><td>Only expiration durations are supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="FilteringNotSupported" id="FilteringNotSupported"/>6.5 FilteringNotSupported</h3><p>
- This fault is generated when a Subscribe request contains a filter
+ This fault MUST be generated when a Subscribe request contains a filter
and the event source does not support filtering.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>Filtering is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="FilteringRequestedUnavailable" id="FilteringRequestedUnavailable"/>6.6 FilteringRequestedUnavailable</h3><p>
- This fault is generated when a Subscribe request specifies a filter
+ This fault MUST be 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 IRIs in the
Detail property.
@@ -1343,7 +1351,7 @@
<br/><em>OPTIONAL; one per filter dialect supported by the
receiver</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.7 DeliveryFormatRequestUnavailable</h3><p>
- This fault is generated when a Subscribe request specifies a delivery
+ This fault MUST be 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 IRIs in the
Detail property.
@@ -1351,20 +1359,20 @@
<wse:SupportedDeliveryFormat> +
<br/><em> OPTIONAL, one per delivery format supported by the receiver.</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="EmptyFilter" id="EmptyFilter"/>6.8 EmptyFilter</h3><p>
- This fault MAY be generated when an event source detects a
+ This fault MUST 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 class="div2">
<h3><a name="UnusableEPR" id="UnusableEPR"/>6.9 UnusableEPR</h3><p>
- This fault MAY be generated when an event source detects
+ This fault MUST 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 class="div2">
<h3><a name="UnknownSubscription" id="UnknownSubscription"/>6.10 UnknownSubscription</h3><p>
- This fault is generated when a request specifies a subscription
+ This fault MUST be generated when a request specifies a subscription
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 class="div2">
<h3><a name="EndToNotSupported" id="EndToNotSupported"/>6.11 EndToNotSupported</h3><p>
- This fault is generated by an event source that does not support
+ This fault MUST be generated by an event source that does not support
/wse:Subscribe/wse:EndTo semantics, in response to a subscription
request that contains a wse:EndTo element.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EndToNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>wse:EndTo semantics is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
@@ -1492,7 +1500,7 @@
that indicate a particular security mechanism used to protect
the WS-Eventing operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2164" id="iddiv2_1_2164"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2166" id="iddiv2_1_2166"/>9.1 EventSource Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Eventing specification's definition of an event source
is through the use of the Web Services
@@ -1558,7 +1566,7 @@
will be sent to the EPR contained in the wse:EndTo element, if
the subscription terminates unexpectedly.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2237" id="iddiv2_1_2237"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2239" id="iddiv2_1_2239"/>9.2 SubscriptionManager Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Eventing specification's definition of a subscription manager
is through the use of the Web Services
@@ -1643,7 +1651,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2308" id="iddiv2_1_2308"/>11.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_2310" id="iddiv2_1_2310"/>11.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.
@@ -1695,7 +1703,7 @@
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2442" id="iddiv2_1_2442"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2_1_2444" id="iddiv2_1_2444"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1799,7 +1807,7 @@
serve as a description of the Event Type used in
<a href="#Table1">Example 2-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2634" id="idexample_1_2634"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2636" id="idexample_1_2636"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wse="http://www.w3.org/2009/09/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1819,7 +1827,7 @@
GED for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p><div class="div3">
-<h4><a name="iddiv3_1_2644" id="iddiv3_1_2644"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2646" id="iddiv3_1_2646"/>A.1.1 Retrieving Event Descriptions</h4><p>
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>.
@@ -1830,7 +1838,7 @@
be equal to the value of its wse:EventDescriptions/@targetNamespace. An
event source MUST NOT have more than one EventDescriptions document.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2665" id="iddiv3_1_2665"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2667" id="iddiv3_1_2667"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it SHOULD be possible to determine how a
given wse:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
@@ -1842,7 +1850,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4_1_2670" id="iddiv4_1_2670"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2672" id="iddiv4_1_2672"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
The information about an Event Type contained in the wse:eventType
element binds to a Unwrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1856,7 +1864,7 @@
of the wse:eventType element corresponding to the type of the
event being transmitted.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2688" id="iddiv4_1_2688"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2690" id="iddiv4_1_2690"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
The information about an Event Type contained in the eventType element
binds to a Wrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1880,7 +1888,7 @@
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_2709" id="idexample_1_2709"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2711" id="idexample_1_2711"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:xs="http://www.w3.org/2001/XMLSchema"
(04) xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1915,7 +1923,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2715" id="iddiv3_1_2715"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2717" id="iddiv3_1_2717"/>A.2.1 Retrieving Notification WSDLs</h4><p>
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>.
@@ -1931,7 +1939,7 @@
Format IRI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2736" id="iddiv2_1_2736"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2738" id="iddiv2_1_2738"/>A.3 Multiple Event Information Metadata Sections</h3><p>
When WS-MetadataExchange is used to retrieve metadata about an event
source, recipients of mex:Metadata elements that contain Metadata
Sections with both the
@@ -2499,4 +2507,5 @@
<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><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</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=8286">8286</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</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.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- wsfrag.xml 19 Jan 2010 22:12:26 -0000 1.43
+++ wsfrag.xml 19 Jan 2010 23:14:49 -0000 1.44
@@ -403,6 +403,16 @@
</p>
<p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
+ </p>
+
+ <p>
In the outlines, <kw>bold</kw> text is used to indicate those parts
of the message that are defined as part of this specification and
are extensions to the WS-Transfer messages.
@@ -1499,7 +1509,7 @@
<div2 id="UnsupportedLanguage">
<head>UnsupportedLanguage</head>
<p>
- This fault is generated when a service detects an unknown or
+ This fault MUST be generated when a service detects an unknown or
unsupported Language
IRI in a request message.
</p>
@@ -1530,7 +1540,7 @@
<div2 id="InvalidExpression">
<head>InvalidExpression</head>
<p>
- This fault is generated when a service determines that the Language
+ This fault MUST be generated when a service determines that the Language
expression specified in a request does not conform to the syntax
of the language specified in the Language attribute or is semantically
invalid.
@@ -1562,7 +1572,7 @@
<div2 id="UnsupportedMode">
<head>UnsupportedMode</head>
<p>
- This fault is generated when a service detects a Mode in a Put
+ This fault MUST be generated when a service detects a Mode in a Put
request that is not supported.
</p>
<table id="Table6" border="1" cellpadding="5">
@@ -2076,6 +2086,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8192">8192</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/19 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- wsfrag.html 19 Jan 2010 22:12:26 -0000 1.41
+++ wsfrag.html 19 Jan 2010 23:14:49 -0000 1.42
@@ -53,8 +53,8 @@
3.2 <a href="#Put">Put</a><br/>
3.3 <a href="#Delete">Delete</a><br/>
3.4 <a href="#Create">Create</a><br/>
-4 <a href="#iddiv1_1_776">Examples</a><br/>
- 4.1 <a href="#iddiv2_1_779">Examples</a><br/>
+4 <a href="#iddiv1_1_778">Examples</a><br/>
+ 4.1 <a href="#iddiv2_1_781">Examples</a><br/>
5 <a href="#QName">QName Expression Language</a><br/>
6 <a href="#XPathL1">XPath Level 1 Expression Language</a><br/>
7 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
@@ -63,10 +63,10 @@
8.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
8.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
9 <a href="#metadata">WS-Fragment Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_1396">Fragment Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_1398">Fragment Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_1449">Normative References</a><br/>
+ 11.1 <a href="#iddiv2_1_1451">Normative 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="#changelog">Change Log</a><br/>
@@ -191,6 +191,14 @@
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
</p><p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
+ </p><p>
In the outlines, <b>bold</b> text is used to indicate those parts
of the message that are defined as part of this specification and
are extensions to the WS-Transfer messages.
@@ -417,8 +425,8 @@
This specification does not extend the Create operation defined in
WS-Transfer.
</p></div></div><div class="div1">
-<h2><a name="iddiv1_1_776" id="iddiv1_1_776"/>4 Examples</h2><div class="div2">
-<h3><a name="iddiv2_1_779" id="iddiv2_1_779"/>4.1 Examples</h3><p>
+<h2><a name="iddiv1_1_778" id="iddiv1_1_778"/>4 Examples</h2><div class="div2">
+<h3><a name="iddiv2_1_781" id="iddiv2_1_781"/>4.1 Examples</h3><p>
In the following examples, and Expression Language definitions,
the following representation of a resource is used for
informational purposes:
@@ -805,14 +813,14 @@
</s11:Body>
</s11:Envelope></pre></div></div><div class="div2">
<h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>8.1 UnsupportedLanguage</h3><p>
- This fault is generated when a service detects an unknown or
+ This fault MUST be generated when a service detects an unknown or
unsupported Language
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 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="InvalidExpression" id="InvalidExpression"/>8.2 InvalidExpression</h3><p>
- This fault is generated when a service determines that the Language
+ This fault MUST be generated when a service determines that the Language
expression specified in a request does not conform to the syntax
of the language specified in the Language attribute or is semantically
invalid.
@@ -820,7 +828,7 @@
The specified Language expression is invalid.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The invalid language expression.</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="UnsupportedMode" id="UnsupportedMode"/>8.3 UnsupportedMode</h3><p>
- This fault is generated when a service detects a Mode in a Put
+ This fault MUST be generated when a service detects a Mode in a Put
request that is not supported.
</p><a name="Table6" id="Table6"/><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:UnsupportedMode</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
The specified mode is not supported.
@@ -831,7 +839,7 @@
doing so the endpoint is indicating that the corresponding WS-Fragment
features are supported by that endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1396" id="iddiv2_1_1396"/>9.1 Fragment Assertion</h3><p>
+<h3><a name="iddiv2_1_1398" id="iddiv2_1_1398"/>9.1 Fragment Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Fragment specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -899,7 +907,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1449" id="iddiv2_1_1449"/>11.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_1451" id="iddiv2_1_1451"/>11.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.
@@ -1057,4 +1065,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8194">8194</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8195">8195</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=8192">8192</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=8192">8192</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</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.96
retrieving revision 1.97
diff -u -d -r1.96 -r1.97
--- wst.html 19 Jan 2010 22:54:17 -0000 1.96
+++ wst.html 19 Jan 2010 23:14:49 -0000 1.97
@@ -59,12 +59,12 @@
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_1395">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1465">TransferResourceFactory Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_1389">TransferResource Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1459">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">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/>
+ 9.1 <a href="#iddiv2_1_1512">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1685">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/>
@@ -194,6 +194,14 @@
<a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
+ </p><p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
</p></div><div class="div2">
<h3><a name="extensions" id="extensions"/>2.4 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
@@ -853,25 +861,27 @@
</s11:Fault>
</s11:Body>
</s11:Envelope></pre></div></div><div class="div2">
-<h3><a name="InvalidRepresentation" id="InvalidRepresentation"/>5.1 InvalidRepresentation</h3><p>This fault is generated when an incorrect representation is sent in a
- 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="InvalidRepresentation" id="InvalidRepresentation"/>5.1 InvalidRepresentation</h3><p>
+ This fault MUST be generated when an incorrect representation is
+ sent in a wst:Put or wst:Create message.
+ </p><table border="1"><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
- 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>
+ This fault MUST be generated when a service detects an unknown
+ Dialect IRI in a request message.
+ </p><table border="1"><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 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
+ This fault MUST be generated when a Put request message attempts
to modify a portion of a resource but is not allowed to do so.
- </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>
+ </p><table border="1"><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 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>
+ This fault MUST be generated when a request specifies a resource
+ that is not known.
+ </p><table border="1"><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
@@ -940,7 +950,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_1395" id="iddiv2_1_1395"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1389" id="iddiv2_1_1389"/>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
@@ -1008,7 +1018,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_1465" id="iddiv2_1_1465"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1459" id="iddiv2_1_1459"/>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
@@ -1080,7 +1090,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_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>
+<h3><a name="iddiv2_1_1512" id="iddiv2_1_1512"/>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.
@@ -1148,7 +1158,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_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>
+<h3><a name="iddiv2_1_1685" id="iddiv2_1_1685"/>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.
@@ -1474,4 +1484,5 @@
<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><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><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8301">8301</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=8301">8301</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</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.102
retrieving revision 1.103
diff -u -d -r1.102 -r1.103
--- wsenum.html 19 Jan 2010 22:38:48 -0000 1.102
+++ wsenum.html 19 Jan 2010 23:14:49 -0000 1.103
@@ -68,11 +68,11 @@
4.10 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
5 <a href="#Security">Security Considerations</a><br/>
6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 6.1 <a href="#iddiv2_1_1955">Enumeration Assertion</a><br/>
+ 6.1 <a href="#iddiv2_1_1957">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2050">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2236">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2052">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2238">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/>
@@ -210,6 +210,14 @@
<a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
+ </p><p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
</p></div><div class="div2">
<h3><a name="extensions" id="extensions"/>2.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
@@ -1111,31 +1119,30 @@
</s11:Body>
</s11:Envelope></pre></div></div><div class="div2">
<h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>4.1 InvalidExpirationTime</h3><p>
- This fault is generated when a request specifies an
- expiration that is malformed.
+ This fault MUST be generated when a request specified an expiration that
+ is malformed.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:InvalidExpirationTime </td></tr><tr><td><b>[Reason]</b></td><td>
Invalid expiration time.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="ExpirationTimeExceeded" id="ExpirationTimeExceeded"/>4.2 ExpirationTimeExceeded</h3><p>
- This fault is generated when a request specifies an
+ This fault MUST be generated when a request specifies an
expiration that is not within the min/max range.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:ExpirationTimeExceeded </td></tr><tr><td><b>[Reason]</b></td><td>
The expiration time requested is not within the min/max range.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="UnsupportedExpirationTime" id="UnsupportedExpirationTime"/>4.3 UnsupportedExpirationTime</h3><p>
- This fault is generated if the Enumerate expiration time is
- specified not as a duration.
+ This fault MUST be generated when the Enumerate expiration time that is
+ specified is not a duration.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:UnsupportedExpirationTime </td></tr><tr><td><b>[Reason]</b></td><td>
Unsupported expiration time.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="FilteringNotSupported" id="FilteringNotSupported"/>4.4 FilteringNotSupported</h3><p>
- This fault is generated if the data source does not support
- filters.
+ This fault MUST generated when the data source does not support filters.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:FilteringNotSupported </td></tr><tr><td><b>[Reason]</b></td><td>
Filtering not supported.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="FilterDialectRequestedUnavailable" id="FilterDialectRequestedUnavailable"/>4.5 FilterDialectRequestedUnavailable</h3><p>
- This fault is generated if the data source does not support
+ This fault MUST be generated when the data source does not support
the requested filter dialect.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:FilterDialectRequestedUnavailable </td></tr><tr><td><b>[Reason]</b></td><td>
Filer dialect requested unavailable.
@@ -1144,13 +1151,13 @@
<br/><em>OPTIONAL; repeating; one per filter dialect supported by the
receiver</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="CannotProcessFilter" id="CannotProcessFilter"/>4.6 CannotProcessFilter</h3><p>
- This fault is generated if the data source can not process the
+ This fault MUST be generated when the data source can not process the
filter content.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:CannotProcessFilter </td></tr><tr><td><b>[Reason]</b></td><td>
Cannot filter as requested.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="InvalidEnumerationContext" id="InvalidEnumerationContext"/>4.7 InvalidEnumerationContext</h3><p>
- This fault is generated if the enumeration context is invalid.
+ This fault MUST be generated when the enumeration context is invalid.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Receiver </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:InvalidEnumerationContext </td></tr><tr><td><b>[Reason]</b></td><td><em>
Text explaining why the enumeration context is no longer valid, or
</em>
@@ -1159,15 +1166,15 @@
if no additional information is available.
</em></td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="TimedOut" id="TimedOut"/>4.8 TimedOut</h3><p>
- This fault is generated if the data source times out during the
+ This fault MUST be generated when the data source times out during the
processing of a Pull operation, if the wsen:MaxTime is reached.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Receiver </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:TimedOut </td></tr><tr><td><b>[Reason]</b></td><td> Timeout. </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
+ This fault MUST 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 class="div2">
<h3><a name="EndToNotSupported" id="EndToNotSupported"/>4.10 EndToNotSupported</h3><p>
- This fault is generated by an event source that does not support
+ This fault MUST be generated by an event source that does not support
/wsen:Enumerate/wsen:EndTo semantics, in response to a enumerate
request that contains a wsen:EndTo element.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:EndToNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>wsen:EndTo semantics is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
@@ -1279,7 +1286,7 @@
that indicate a particular security mechanism used to protect
the WS-Enumeration operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1955" id="iddiv2_1_1955"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1957" id="iddiv2_1_1957"/>6.1 Enumeration Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Enumeration specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1382,7 +1389,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2050" id="iddiv2_1_2050"/>8.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_2052" id="iddiv2_1_2052"/>8.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.
@@ -1454,7 +1461,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_2236" id="iddiv2_1_2236"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2_1_2238" id="iddiv2_1_2238"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
@@ -1961,4 +1968,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8305">8305</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8159">8159</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8161">8161</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</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=8286">8286</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</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.95
retrieving revision 1.96
diff -u -d -r1.95 -r1.96
--- wsenum.xml 19 Jan 2010 22:38:48 -0000 1.95
+++ wsenum.xml 19 Jan 2010 23:14:49 -0000 1.96
@@ -321,6 +321,16 @@
serializable in XML 1.0, hence the use of XML 1.0.
</p>
+ <p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
+ </p>
+
</div2>
<div2 id="extensions">
@@ -1856,8 +1866,8 @@
<head>InvalidExpirationTime</head>
<p>
- This fault is generated when a request specifies an
- expiration that is malformed.
+ This fault MUST be generated when a request specified an expiration that
+ is malformed.
</p>
<table border="1">
@@ -1888,7 +1898,7 @@
<head>ExpirationTimeExceeded</head>
<p>
- This fault is generated when a request specifies an
+ This fault MUST be generated when a request specifies an
expiration that is not within the min/max range.
</p>
@@ -1920,8 +1930,8 @@
<head>UnsupportedExpirationTime</head>
<p>
- This fault is generated if the Enumerate expiration time is
- specified not as a duration.
+ This fault MUST be generated when the Enumerate expiration time that is
+ specified is not a duration.
</p>
<table border="1">
@@ -1952,8 +1962,7 @@
<head>FilteringNotSupported</head>
<p>
- This fault is generated if the data source does not support
- filters.
+ This fault MUST generated when the data source does not support filters.
</p>
<table border="1">
@@ -1984,7 +1993,7 @@
<head>FilterDialectRequestedUnavailable</head>
<p>
- This fault is generated if the data source does not support
+ This fault MUST be generated when the data source does not support
the requested filter dialect.
</p>
@@ -2021,7 +2030,7 @@
<head>CannotProcessFilter</head>
<p>
- This fault is generated if the data source can not process the
+ This fault MUST be generated when the data source can not process the
filter content.
</p>
@@ -2053,7 +2062,7 @@
<head>InvalidEnumerationContext</head>
<p>
- This fault is generated if the enumeration context is invalid.
+ This fault MUST be generated when the enumeration context is invalid.
</p>
<table border="1">
@@ -2090,7 +2099,7 @@
<head>TimedOut</head>
<p>
- This fault is generated if the data source times out during the
+ This fault MUST be generated when the data source times out during the
processing of a Pull operation, if the wsen:MaxTime is reached.
</p>
@@ -2120,7 +2129,7 @@
<head>UnusableEPR</head>
<p>
- This fault MAY be generated when a data source detects
+ This fault MUST be generated when a data source detects
that the wsen:EndTo EPR is unusable.
</p>
@@ -2155,7 +2164,7 @@
<head>EndToNotSupported</head>
<p>
- This fault is generated by an event source that does not support
+ This fault MUST be generated by an event source that does not support
/wsen:Enumerate/wsen:EndTo semantics, in response to a enumerate
request that contains a wsen:EndTo element.
</p>
@@ -3589,6 +3598,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/19 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -d -r1.143 -r1.144
--- wseventing.xml 19 Jan 2010 22:38:48 -0000 1.143
+++ wseventing.xml 19 Jan 2010 23:14:49 -0000 1.144
@@ -530,6 +530,16 @@
serializable in XML 1.0, hence the use of XML 1.0.
</p>
+ <p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ futher processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the fault MAY NOT
+ be transmitted.
+ </p>
+
</div2>
<div2 id="extensions">
@@ -2112,7 +2122,7 @@
<head>InvalidExpirationTime</head>
<p>
- This fault is generated when a request specifies an
+ This fault MUST be generated when a request specifies an
expiration that is malformed.
</p>
@@ -2145,7 +2155,7 @@
<head>ExpirationTimeExceeded</head>
<p>
- This fault is generated when a request specifies an
+ This fault MUST be generated when a request specifies an
expiration that is not within the min/max range.
</p>
@@ -2178,7 +2188,7 @@
<head>UnsupportedExpirationType</head>
<p>
- This fault is generated when a Subscribe request specifies an
+ This fault MUST be generated when a Subscribe request specifies an
expiration time and the event source is only capable of accepting
expiration durations; for instance, if the event source does not
have access to absolute time.
@@ -2213,7 +2223,7 @@
<head>FilteringNotSupported</head>
<p>
- This fault is generated when a Subscribe request contains a filter
+ This fault MUST be generated when a Subscribe request contains a filter
and the event source does not support filtering.
</p>
@@ -2246,7 +2256,7 @@
<head>FilteringRequestedUnavailable</head>
<p>
- This fault is generated when a Subscribe request specifies a filter
+ This fault MUST be 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 IRIs in the
Detail property.
@@ -2286,7 +2296,7 @@
<head>DeliveryFormatRequestUnavailable</head>
<p>
- This fault is generated when a Subscribe request specifies a delivery
+ This fault MUST be 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 IRIs in the
Detail property.
@@ -2325,7 +2335,7 @@
<head>EmptyFilter</head>
<p>
- This fault MAY be generated when an event source detects a
+ This fault MUST be generated when an event source detects a
wse:Subscribe request containing a filter that, for whatever
reason, will never evaluate to true.
</p>
@@ -2361,7 +2371,7 @@
<head>UnusableEPR</head>
<p>
- This fault MAY be generated when an event source detects
+ This fault MUST be generated when an event source detects
that the wse:NotifyTo or wse:EndTo EPR is unusable.
</p>
@@ -2396,7 +2406,7 @@
<head>UnknownSubscription</head>
<p>
- This fault is generated when a request specifies a subscription
+ This fault MUST be generated when a request specifies a subscription
that is not known.
</p>
@@ -2429,7 +2439,7 @@
<head>EndToNotSupported</head>
<p>
- This fault is generated by an event source that does not support
+ This fault MUST be generated by an event source that does not support
/wse:Subscribe/wse:EndTo semantics, in response to a subscription
request that contains a wse:EndTo element.
</p>
@@ -4570,6 +4580,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/19 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 19 January 2010 23:14:55 UTC