- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 05 Oct 2009 14:04:00 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv8523
Modified Files:
wst.html wst.xml
Log Message:
7731, 6721
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- wst.xml 2 Oct 2009 15:50:33 -0000 1.63
+++ wst.xml 5 Oct 2009 14:03:58 -0000 1.64
@@ -212,6 +212,15 @@
</td>
</tr>
<tr>
+ <td> wstrp </td>
+ <td>
+ <loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra">http://www.w3.org/&wstra.nsprefix;/ws-trp</loc>
+ </td>
+ <td>
+ This specification
+ </td>
+ </tr>
+ <tr>
<td> s </td>
<td> Either SOAP 1.1 or 1.2 </td>
<td> SOAP </td>
@@ -1541,23 +1550,268 @@
</ulist>
</div1>
- <div1 id="policy">
- <head>WS-Transfer Policy Assertion(s)</head>
+ <div1 id="metadata">
- <p>
- An endpoint MAY indicate that it supports WS-Transfer, or its features,
- by including the WS-Transfer Policy assertion(s) within its WSDL. By
- doing so the endpoint is indicating that the corresponding WS-Transfer
- operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL.
- </p>
- </div1>
+ <head>WS-Transfer Metadata</head>
- <div1 id="acks">
- <head>Acknowledgements</head>
- <p>
- This specification has been developed as a result of joint
- work with many individuals and teams, including:
+ <p>
+ An endpoint MAY indicate that it supports WS-Transfer, or its features,
+ by including the WS-Transfer Policy assertion within its WSDL. By
+ doing so the endpoint is indicating that the corresponding WS-Transfer
+ operations are supported by that endpoint even though they do not
+ explicitly appear in its WSDL (i.e. retrievable by using a
+ WS-MetadataExchange GetMetadata with a Dialect IRI of
+ http://schemas.xmlsoap.org/wsdl/).
+ </p>
+
+ <p>
+ An endpoint MAY choose to expose the WS-Transfer WSDL by using the
+ following WS-MetadataExchange Dialect:
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <th align="left"> Dialect IRI </th>
+ <th> @Identifier value </th>
+ </tr>
+ <tr>
+ <td> http://www.w3.org/2009/02/ws-tra/TransferWSDL </td>
+ <td> Not defined </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ The WS-Transfer WSDL can be annotated to indicate any endpoint
+ specific metadata that might be needed by clients interacting with
+ this service. For example, the WSDL MAY have policy assertions that
+ indicate a particular security mechanism used to protect the
+ WS-Transfer operations supported by this endpoint.
+ </p>
+
+ <div2>
+ <head>TransferResource Assertion</head>
+
+ <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
+ Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
+ Attachment <bibref ref="wspolicyattach"/> specifications.
+ </p>
+
+ <p>
+ This specification defines a policy assertion (wstrp:TransferResource).
+ The wstrp:TransferResource policy assertion applies to the endpoint
+ policy subject.
+ </p>
+
+ <p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the wstrp:TransferResource
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p>
+
+ <p>
+ The wstrp:TransferResource policy assertion is a nested policy container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Transfer is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Transfer
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wstrp:TransferResource assertion. This indicates two policy
+ alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p>
+
+ <p>
+ The inclusion of this assertion implies support for the WS-Transfer
+ specification and that the subject is a WS-Transfer resource.
+ </p>
+
+ <p>
+ The normative outline of this assertion is:
+ </p>
+
+ <example>
+ <eg><wstrp:TransferResource [wsp:Optional="<emph>xs:boolean</emph>"]? ...>
+ <wstrp:PutOperationSupported .../> ?
+ <wstrp:DeleteOperationSupported .../> ?
+ <wstrp:FaultOnPutDenied.../> ?
+ <wstrp:Dialect ...> <emph>xs:anyURI</emph> </wstrp:Dialect> *
+ ...
+</wstrp:TransferResource></eg>
+ </example>
+
+ <p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p>
+
+ <glist>
+
+ <gitem>
+ <label> /wstrp:TransferResource </label>
+ <def>
+ <p>
+ This policy assertion specifies that WS-Transfer protocol MUST be
+ used when communicating with this endpoint and that the subject is a
+ Transfer Resource. This assertion has Endpoint Policy Subject. Unless
+ support for optional operations is explicitly indicated by either
+ the PutOperationSupported or DeleteOperationSupported parameters only
+ the Get operation is supported.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wstrp:TransferResource/wstrp:PutOperationSupported </label>
+ <def>
+ <p>
+ When present, this parameter indicates that the Put operation is
+ supported by this endpoint.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wstrp:TransferResource/wstrp:DeleteOperationSupported </label>
+ <def>
+ <p>
+ When present, this parameter indicates that the Delete operation is
+ supported by this endpoint.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wstrp:TransferResource/wstrp:FaultOnPutDenied </label>
+ <def>
+ <p>
+ When present, this parameter indicates that attempts to change
+ portions of the representation that are read-only will generate a
+ wst:PutDenied fault. If this parameter is not present, attempts
+ to modify read-only portions of the resource representation will
+ be ignored without any fault being generated.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wstrp:TransferResource/wstrp:Dialect </label>
+ <def>
+ <p>
+ When present, this parameter indicates support for the specified
+ Dialect IRI.
+ </p>
+ </def>
+ </gitem>
+
+ </glist>
+
+ </div2>
+
+ <div2>
+ <head>TransferResourceFactory Assertion</head>
+
+ <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
+ Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
+ Attachment <bibref ref="wspolicyattach"/> specifications.
+ </p>
+
+ <p>
+ This specification defines a policy assertion
+ (wstrp:TransferResourceFactory).
+ The wstrp:TransferResourceFactory policy assertion applies to the endpoint
+ policy subject.
+ </p>
+
+ <p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the
+ wstrp:TransferResourceFactory
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p>
+
+ <p>
+ The wstrp:TransferResourceFactory policy assertion is a nested policy
+ container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Transfer is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Transfer
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wstrp:TransferResourceFactory assertion. This indicates two
+ policy alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p>
+
+ <p>
+ The inclusion of this assertion implies support for the WS-Transfer
+ specification and that the subject is a Resource Factory.
+ </p>
+
+ <p>
+ The normative outline of this assertion is:
+ </p>
+
+ <example>
+ <eg><wstrp:TransferResourceFactory [wsp:Optional="<emph>xs:boolean</emph>"]? ...>
+ <wstrp:Dialect ...> <emph>xs :anyURI</emph> </wstrp:Dialect> *
+ ...
+</wstrp:TransferResourceFactory></eg>
+ </example>
+
+ <p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p>
+
+ <glist>
+
+ <gitem>
+ <label> /wstrp:TransferResourceFactory </label>
+ <def>
+ <p>
+ This policy assertion specifies that WS-Transfer Create operation
+ MUST be used when communicating with this endpoint. This assertion
+ has Endpoint Policy Subject.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wstrp:TransferResourceFactory/wstrp:Dialect </label>
+ <def>
+ <p>
+ When present, this parameter indicates support for the specified
+ Dialect IRI.
+ </p>
+ </def>
+ </gitem>
+
+ </glist>
+
+ </div2>
+ </div1>
+
+ <div1 id="acks">
+ <head>Acknowledgements</head>
+ <p>
+ This specification has been developed as a result of joint
+ work with many individuals and teams, including:
Ashok Malhotra (Oracle Corp.),
Asir Vedamuthu (Microsoft Corp.),
Bob Freund (Hitachi, Ltd.),
@@ -1660,6 +1914,16 @@
World Wide Web Consortium (W3C), 4 September 2007.
</bibl>
+ <bibl key="WS-Policy Attachment" id="wspolicyattach"
+ href="http://www.w3.org/TR/ws-policy-attach">
+ <titleref>
+ W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
+
+ </titleref>
+ , A. Vedamuthu, et al., Editors.
+ World Wide Web Consortium (W3C), 4 September 2007.
+ </bibl>
+
<bibl key="WSDL11" id="WSDL11"
href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
<titleref>
@@ -2200,6 +2464,14 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7731">7731</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -d -r1.65 -r1.66
--- wst.html 2 Oct 2009 15:50:32 -0000 1.65
+++ wst.html 5 Oct 2009 14:03:58 -0000 1.66
@@ -57,11 +57,13 @@
5.2 <a href="#UnknownDialect">UnknownDialect</a><br/>
5.3 <a href="#PutDenied">PutDenied</a><br/>
6 <a href="#Security_Considerations">Security Considerations</a><br/>
-7 <a href="#policy">WS-Transfer Policy Assertion(s)</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_1443">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1343">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1503">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1499">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1672">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/>
@@ -129,6 +131,8 @@
Prefixes and XML Namespaces used in this specification.
</caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wst </td><td><a href="http://www.w3.org/2009/09/ws-tra">http://www.w3.org/2009/09/ws-tra</a></td><td>
This specification
+ </td></tr><tr><td> wstrp </td><td><a href="http://www.w3.org/2009/09/ws-tra">http://www.w3.org/2009/09/ws-trp</a></td><td>
+ This specification
</td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a></td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a></td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a></td><td>
XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
@@ -875,16 +879,142 @@
denial of service attacks are harder to avoid and are outside the scope
of this specification. That said, care SHOULD be taken to ensure that
minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
-<h2><a name="policy" id="policy"/>7 WS-Transfer Policy Assertion(s)</h2><p>
- An endpoint MAY indicate that it supports WS-Transfer, or its features,
- by including the WS-Transfer Policy assertion(s) within its WSDL. By
- doing so the endpoint is indicating that the corresponding WS-Transfer
- operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL.
- </p></div><div class="div1">
+<h2><a name="metadata" id="metadata"/>7 WS-Transfer Metadata</h2><p>
+ An endpoint MAY indicate that it supports WS-Transfer, or its features,
+ by including the WS-Transfer Policy assertion within its WSDL. By
+ doing so the endpoint is indicating that the corresponding WS-Transfer
+ operations are supported by that endpoint even though they do not
+ explicitly appear in its WSDL (i.e. retrievable by using a
+ WS-MetadataExchange GetMetadata with a Dialect IRI of
+ http://schemas.xmlsoap.org/wsdl/).
+ </p><p>
+ An endpoint MAY choose to expose the WS-Transfer WSDL by using the
+ following WS-MetadataExchange Dialect:
+ </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th> @Identifier value </th></tr><tr><td> http://www.w3.org/2009/02/ws-tra/TransferWSDL </td><td> Not defined </td></tr></tbody></table><p>
+ The WS-Transfer WSDL can be annotated to indicate any endpoint
+ specific metadata that might be needed by clients interacting with
+ this service. For example, the WSDL MAY have policy assertions 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_1379" id="iddiv2_1_1379"/>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
+ Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
+ Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
+ </p><p>
+ This specification defines a policy assertion (wstrp:TransferResource).
+ The wstrp:TransferResource policy assertion applies to the endpoint
+ policy subject.
+ </p><p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the wstrp:TransferResource
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p><p>
+ The wstrp:TransferResource policy assertion is a nested policy container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Transfer is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Transfer
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wstrp:TransferResource assertion. This indicates two policy
+ alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p><p>
+ The inclusion of this assertion implies support for the WS-Transfer
+ specification and that the subject is a WS-Transfer resource.
+ </p><p>
+ The normative outline of this assertion is:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><wstrp:TransferResource [wsp:Optional="<em>xs:boolean</em>"]? ...>
+ <wstrp:PutOperationSupported .../> ?
+ <wstrp:DeleteOperationSupported .../> ?
+ <wstrp:FaultOnPutDenied.../> ?
+ <wstrp:Dialect ...> <em>xs:anyURI</em> </wstrp:Dialect> *
+ ...
+</wstrp:TransferResource></pre></div></div><p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p><dl><dt class="label"> /wstrp:TransferResource </dt><dd><p>
+ This policy assertion specifies that WS-Transfer protocol MUST be
+ used when communicating with this endpoint and that the subject is a
+ Transfer Resource. This assertion has Endpoint Policy Subject. Unless
+ support for optional operations is explicitly indicated by either
+ the PutOperationSupported or DeleteOperationSupported parameters only
+ the Get operation is supported.
+ </p></dd><dt class="label"> /wstrp:TransferResource/wstrp:PutOperationSupported </dt><dd><p>
+ When present, this parameter indicates that the Put operation is
+ supported by this endpoint.
+ </p></dd><dt class="label"> /wstrp:TransferResource/wstrp:DeleteOperationSupported </dt><dd><p>
+ When present, this parameter indicates that the Delete operation is
+ supported by this endpoint.
+ </p></dd><dt class="label"> /wstrp:TransferResource/wstrp:FaultOnPutDenied </dt><dd><p>
+ When present, this parameter indicates that attempts to change
+ portions of the representation that are read-only will generate a
+ wst:PutDenied fault. If this parameter is not present, attempts
+ to modify read-only portions of the resource representation will
+ be ignored without any fault being generated.
+ </p></dd><dt class="label"> /wstrp:TransferResource/wstrp:Dialect </dt><dd><p>
+ When present, this parameter indicates support for the specified
+ Dialect IRI.
+ </p></dd></dl></div><div class="div2">
+<h3><a name="iddiv2_1_1443" id="iddiv2_1_1443"/>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
+ Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
+ Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
+ </p><p>
+ This specification defines a policy assertion
+ (wstrp:TransferResourceFactory).
+ The wstrp:TransferResourceFactory policy assertion applies to the endpoint
+ policy subject.
+ </p><p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the
+ wstrp:TransferResourceFactory
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p><p>
+ The wstrp:TransferResourceFactory policy assertion is a nested policy
+ container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Transfer is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Transfer
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wstrp:TransferResourceFactory assertion. This indicates two
+ policy alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p><p>
+ The inclusion of this assertion implies support for the WS-Transfer
+ specification and that the subject is a Resource Factory.
+ </p><p>
+ The normative outline of this assertion is:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><wstrp:TransferResourceFactory [wsp:Optional="<em>xs:boolean</em>"]? ...>
+ <wstrp:Dialect ...> <em>xs :anyURI</em> </wstrp:Dialect> *
+ ...
+</wstrp:TransferResourceFactory></pre></div></div><p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p><dl><dt class="label"> /wstrp:TransferResourceFactory </dt><dd><p>
+ This policy assertion specifies that WS-Transfer Create operation
+ MUST be used when communicating with this endpoint. This assertion
+ has Endpoint Policy Subject.
+ </p></dd><dt class="label"> /wstrp:TransferResourceFactory/wstrp:Dialect </dt><dd><p>
+ When present, this parameter indicates support for the specified
+ Dialect IRI.
+ </p></dd></dl></div></div><div class="div1">
<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
- This specification has been developed as a result of joint
- work with many individuals and teams, including:
+ This specification has been developed as a result of joint
+ work with many individuals and teams, including:
Ashok Malhotra (Oracle Corp.),
Asir Vedamuthu (Microsoft Corp.),
Bob Freund (Hitachi, Ltd.),
@@ -906,7 +1036,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_1343" id="iddiv2_1_1343"/>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_1499" id="iddiv2_1_1499"/>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.
@@ -947,7 +1077,13 @@
</cite></a>
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
- Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+ Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="wspolicyattach" id="wspolicyattach"/>WS-Policy Attachment</dt><dd><a href="http://www.w3.org/TR/ws-policy-attach"><cite>
+ W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
+
+ </cite></a>
+ , 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><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
W3C Note, "Web Services Description Language (WSDL) 1.1"
</cite></a>
, E. Christensen, et al., Editors.
@@ -968,7 +1104,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_1503" id="iddiv2_1_1503"/>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_1672" id="iddiv2_1_1672"/>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.
@@ -1223,4 +1359,6 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr><tr><td> 2009/09/16 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7486">7486</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
<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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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
Received on Monday, 5 October 2009 14:04:06 UTC