- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 13 Oct 2009 19:50:30 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv18669
Modified Files:
wst.html wst.xml
Log Message:
7812
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -d -r1.69 -r1.70
--- wst.xml 12 Oct 2009 11:53:13 -0000 1.69
+++ wst.xml 13 Oct 2009 19:50:28 -0000 1.70
@@ -129,12 +129,6 @@
any given endpoint reference. The resource content can vary based on
environmental factors, such as the security context, time of day,
configuration, or the dynamic state of the service.</p>
- <p>As per the SOAP processing model, other specifications MAY define SOAP
- headers which can be optionally added to request messages to require the
- transfer of subsets or the application of transformations of the resource
- associated with the endpoint reference. When the Action IRIs defined by
- this specification are used, such extension specifications MUST also allow
- the basic processing models defined herein.</p>
<div2 id="reqs">
<head>Requirements</head>
<p>This specification intends to meet the following requirements:</p>
@@ -2542,6 +2536,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/13 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7812">7812</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -d -r1.71 -r1.72
--- wst.html 12 Oct 2009 11:53:13 -0000 1.71
+++ wst.html 13 Oct 2009 19:50:28 -0000 1.72
@@ -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_1379">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1440">TransferResourceFactory Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_1377">TransferResource Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1438">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1493">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1666">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1491">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1664">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -102,12 +102,7 @@
Additionally, there is no requirement that the resource content is fixed for
any given endpoint reference. The resource content can vary based on
environmental factors, such as the security context, time of day,
- configuration, or the dynamic state of the service.</p><p>As per the SOAP processing model, other specifications MAY define SOAP
- headers which can be optionally added to request messages to require the
- transfer of subsets or the application of transformations of the resource
- associated with the endpoint reference. When the Action IRIs defined by
- this specification are used, such extension specifications MUST also allow
- the basic processing models defined herein.</p><div class="div2">
+ configuration, or the dynamic state of the service.</p><div class="div2">
<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>Provide a SOAP-based protocol for managing resources and their
representations.
</p></li><li><p>Minimize additional mechanism beyond the current Web Services
@@ -898,7 +893,7 @@
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_1379" id="iddiv2_1_1379"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1377" id="iddiv2_1_1377"/>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
@@ -961,7 +956,7 @@
When present, this parameter indicates support for the specified
Dialect IRI.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1440" id="iddiv2_1_1440"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1438" id="iddiv2_1_1438"/>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
@@ -1033,7 +1028,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_1493" id="iddiv2_1_1493"/>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_1491" id="iddiv2_1_1491"/>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.
@@ -1101,7 +1096,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_1666" id="iddiv2_1_1666"/>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_1664" id="iddiv2_1_1664"/>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.
@@ -1416,4 +1411,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6572">6572</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a></td></tr><tr><td> 2009/10/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7731">7731</a>,
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</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=6721">6721</a></td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7812">7812</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 13 October 2009 19:50:32 UTC