- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 05 Jan 2010 22:17:57 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv5085
Modified Files:
wst.html wst.xml
Log Message:
8183
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- wst.xml 9 Dec 2009 00:42:20 -0000 1.89
+++ wst.xml 5 Jan 2010 22:17:55 -0000 1.90
@@ -738,13 +738,13 @@
</p>
<p>
- Implementations MAY use the fault code wst:InvalidRepresentation if
- the presented representation is invalid for the target resource. The
- replacement representation could be considered to be invalid if it
- does not conform to the schema(s) for the target resource or otherwise
- violates some cardinality or type constraint. If an implementation
- detects that the presented representation is invalid it MUST generate
+ If an implementation that performs schema validation on a presented
+ representation detects that the presented representation is invalid
+ for the target resource, then the implementation MUST generate
a wst:InvalidRepresentation fault.
+ The replacement representation could be considered to be invalid if it
+ does not conform to the schema(s) for the target resource or otherwise
+ violates some cardinality or type constraint.
</p>
<p>
@@ -940,16 +940,24 @@
</gitem>
</glist>
- <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>Implementations MAY respond with a fault message using the standard fault
-codes defined in WS-Addressing (e.g., <code>wsa:ActionNotSupported</code>).
-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:</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:
+ </p>
+
<example>
<eg><kw>[Action]</kw>
http://www.w3.org/&wstra.nsprefix;/ws-tra/DeleteResponse
@@ -1116,18 +1124,27 @@
</glist>
- <p>A Create request MUST be targeted at a resource factory capable of
- creating the desired new resource. This factory is distinct from the resource
- being created (which by definition does not exist prior to the successful
- processing of the Create request message).</p>
- <p>In addition to the standard fault codes defined in WS-Addressing,
- implementations MAY use the fault code wst:InvalidRepresentation if the
- presented representation is invalid for the target resource.
- See <specref ref="Faults"/>.</p>
- <p>Other components of the outline above are not further constrained by this
- specification.</p>
- <p>If the resource factory accepts a Create request, it MUST reply with a
- response of the following form:</p>
+ <p>
+ A Create request MUST be targeted at a resource factory capable of
+ creating the desired new resource. This factory is distinct from the
+ resource being created (which by definition does not exist prior to
+ the successful processing of the Create request message).
+ </p>
+ <p>
+ If an implementation that performs schema validation on a presented
+ representation detects that the presented representation is invalid
+ for the target resource, then the implementation MUST generate
+ a wst:InvalidRepresentation fault.
+ </p>
+ <p>
+ Other components of the outline above are not further constrained by
+ this specification.
+ </p>
+ <p>
+ If the resource factory accepts a Create request, it MUST reply with
+ a response of the following form:
+ </p>
+
<example>
<eg><kw>[Action]</kw>
http://www.w3.org/&wstra.nsprefix;/ws-tra/CreateResponse
@@ -2610,6 +2627,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8183">8183</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -d -r1.90 -r1.91
--- wst.html 9 Dec 2009 00:42:20 -0000 1.90
+++ wst.html 5 Jan 2010 22:17:55 -0000 1.91
@@ -58,12 +58,12 @@
5.3 <a href="#PutDenied">PutDenied</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_1341">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1411">TransferResourceFactory Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_1335">TransferResource Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1405">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1464">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1637">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1458">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1631">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/>
@@ -406,13 +406,13 @@
desired to be replaced, as described in
<a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of this specification.
</p><p>
- Implementations MAY use the fault code wst:InvalidRepresentation if
- the presented representation is invalid for the target resource. The
- replacement representation could be considered to be invalid if it
- does not conform to the schema(s) for the target resource or otherwise
- violates some cardinality or type constraint. If an implementation
- detects that the presented representation is invalid it MUST generate
+ If an implementation that performs schema validation on a presented
+ representation detects that the presented representation is invalid
+ for the target resource, then the implementation MUST generate
a wst:InvalidRepresentation fault.
+ The replacement representation could be considered to be invalid if it
+ does not conform to the schema(s) for the target resource or otherwise
+ violates some cardinality or type constraint.
</p><p>
The replacement representation could contain within it element or
attribute values that are different than their corresponding values in
@@ -542,13 +542,19 @@
this dialect IRI. Use of this IRI indicates that the contents
of the Delete element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
- </p></dd></dl><p>A Delete request MUST be targeted at the resource to be deleted as
- described in <a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of this
-specification.</p><p>Implementations MAY respond with a fault message using the standard fault
-codes defined in WS-Addressing (e.g., <code>wsa:ActionNotSupported</code>).
-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:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
+ </p></dd></dl><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.
+ </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:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2009/09/ws-tra/DeleteResponse
<b>[Body]</b>
@@ -657,15 +663,23 @@
this dialect IRI. Use of this IRI indicates that the contents
of the Create element MUST be processed as specified by the
WS-Fragment <a href="#WsFrag">[WS-Fragment]</a> specification.
- </p></dd></dl><p>A Create request MUST be targeted at a resource factory capable of
- creating the desired new resource. This factory is distinct from the resource
- being created (which by definition does not exist prior to the successful
- processing of the Create request message).</p><p>In addition to the standard fault codes defined in WS-Addressing,
- implementations MAY use the fault code wst:InvalidRepresentation if the
- presented representation is invalid for the target resource.
- See <a href="#Faults"><b>5 Faults</b></a>.</p><p>Other components of the outline above are not further constrained by this
- specification.</p><p>If the resource factory accepts a Create request, it MUST reply with a
- response of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
+ </p></dd></dl><p>
+ A Create request MUST be targeted at a resource factory capable of
+ creating the desired new resource. This factory is distinct from the
+ resource being created (which by definition does not exist prior to
+ the successful processing of the Create request message).
+ </p><p>
+ If an implementation that performs schema validation on a presented
+ representation detects that the presented representation is invalid
+ for the target resource, then the implementation MUST generate
+ a wst:InvalidRepresentation fault.
+ </p><p>
+ Other components of the outline above are not further constrained by
+ this specification.
+ </p><p>
+ If the resource factory accepts a Create request, it MUST reply with
+ a response of the following form:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2009/09/ws-tra/CreateResponse
<b>[Body]</b>
@@ -900,7 +914,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_1341" id="iddiv2_1_1341"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1335" id="iddiv2_1_1335"/>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
@@ -968,7 +982,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_1411" id="iddiv2_1_1411"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1405" id="iddiv2_1_1405"/>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
@@ -1040,7 +1054,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_1464" id="iddiv2_1_1464"/>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_1458" id="iddiv2_1_1458"/>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.
@@ -1108,7 +1122,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_1637" id="iddiv2_1_1637"/>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_1631" id="iddiv2_1_1631"/>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.
@@ -1429,4 +1443,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8179">8179</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</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=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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 5 January 2010 22:18:00 UTC