- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 10 Feb 2010 00:49:48 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv23711
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml
wsfrag.html wsfrag.xml wsmex.html wsmex.xml wst.html wst.xml
Log Message:
8160
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -d -r1.102 -r1.103
--- wst.xml 3 Feb 2010 12:55:50 -0000 1.102
+++ wst.xml 10 Feb 2010 00:49:45 -0000 1.103
@@ -139,7 +139,7 @@
are advised to code defensively.</p>
<p>There is no requirement for uniformity in resource representations between
the messages defined in this specification. For example, the
- representations required by Create or Put can differ from the representation
+ representations used by Create or Put can differ from the representation
returned by Get, depending on the semantic requirements of the service.
Additionally, there is no requirement that the resource content is fixed for
any given endpoint reference. The resource content can vary based on
@@ -1115,7 +1115,7 @@
In some cases, the initial representation MAY constitute the
representation of a logical constructor for the resource and can
thus differ structurally from the representation returned by Get or
- the one required by Put. This is because
+ the one used by Put. This is because
the parameterization requirement for creating a resource is
often distinct from the steady-state representation of the resource.
Implementations SHOULD provide metadata which describes the use of
@@ -1218,7 +1218,7 @@
<label> <kw>[Body]</kw>/wst:CreateResponse/wst:ResourceCreated </label>
<def>
<p>
- This required element MUST be an endpoint reference for the
+ This REQUIRED element MUST be an endpoint reference for the
newly created resource. This endpoint reference MUST
identify the resource for future Get, Put, and Delete
operations.
@@ -1609,7 +1609,7 @@
<emph>Accountability</emph> - Accountability is a function of the
type of and string of the key and algorithms being used. In many cases, a
strong symmetric key provides sufficient accountability. However, in some
- environments, strong PKI signatures are required.</p>
+ environments, strong PKI signatures are needed.</p>
</item>
<item>
<p>
@@ -1675,7 +1675,7 @@
<p>
The wst: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
+ alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p>
@@ -1814,7 +1814,7 @@
The wst: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
+ alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource Factory.
</p>
@@ -2757,6 +2757,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299">8299</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.160
retrieving revision 1.161
diff -u -d -r1.160 -r1.161
--- wseventing.html 9 Feb 2010 19:44:41 -0000 1.160
+++ wseventing.html 10 Feb 2010 00:47:43 -0000 1.161
@@ -523,7 +523,7 @@
</p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Delivery </dt><dd><p>
This element contains the information necessary to convey
notification messages to the event sink in
- a manner required by the subscriber. This element MUST contain
+ a manner REQUIRED by the subscriber. This element MUST contain
at least one child element.
</p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Delivery/wse:NotifyTo </dt><dd><p>
This is an OPTIONAL element. When present, this element indicates
@@ -1438,7 +1438,7 @@
a function of the type of and string of the key and
algorithms being used. In many cases, a strong symmetric key
provides sufficient accountability. However, in some
- environments, strong PKI signatures are required.
+ environments, strong PKI signatures are needed.
</p></li><li><p>
Availability - All reliable
messaging services are subject to a variety of availability
@@ -1526,7 +1526,7 @@
</p><p>
The wse:EventSource policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Eventing is required to communicate with the
+ alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing event source.
</p><p>
In order to indicate that the subject supports WS-Eventing
@@ -1609,7 +1609,7 @@
</p><p>
The wse:SubscriptionManager policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Eventing is required to communicate with the
+ alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing subscription manager.
</p><p>
In order to indicate that the subject supports WS-Eventing
@@ -1906,7 +1906,7 @@
SOAP messages called "Notifications". These notifications MAY be
described via a Web Services Description Language <a href="#WSDL11">[WSDL11]</a>
definitions element termed a "Notification WSDL". A Notification WSDL
- describes the interface that the event sink is required to implement to
+ describes the interface that the event sink is REQUIRED to implement to
receive and process the notifications that might result from a
successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
@@ -2631,4 +2631,6 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</a></td></tr><tr><td> 2010/01/27 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986">7986</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a></td></tr><tr><td> 2010/02/05 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435">6435</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=6435">6435</a></td></tr><tr><td> 2010/02/08 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</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.50
retrieving revision 1.51
diff -u -d -r1.50 -r1.51
--- wsfrag.xml 29 Jan 2010 04:25:32 -0000 1.50
+++ wsfrag.xml 10 Feb 2010 00:49:34 -0000 1.51
@@ -1163,7 +1163,7 @@
<p>
If accessed, attributes MUST be the final token in the path
- and they MAY be namespace-qualified or unqualified names, as required:
+ and they MAY be namespace-qualified or unqualified names, as needed:
</p>
<example>
@@ -1660,7 +1660,7 @@
<p>
The wsf:FragmentAssertion policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Fragment is required to communicate with the
+ alternative, is that WS-Fragment is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p>
@@ -2159,6 +2159,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/10 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -d -r1.50 -r1.51
--- wsfrag.html 9 Feb 2010 19:44:41 -0000 1.50
+++ wsfrag.html 10 Feb 2010 00:49:26 -0000 1.51
@@ -643,7 +643,7 @@
node would then be serialized into the following XML representation:
</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) <wsf:TextNode>20</wsf:TextNode></pre></div></div><p>
If accessed, attributes MUST be the final token in the path
- and they MAY be namespace-qualified or unqualified names, as required:
+ and they MAY be namespace-qualified or unqualified names, as needed:
</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b/c/@d</pre></div></div><p>
The above expression would return a node-set containing a
single attribute node with the value <em>d="30"</em> as its result.
@@ -878,7 +878,7 @@
</p><p>
The wsf:FragmentAssertion policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Fragment is required to communicate with the
+ alternative, is that WS-Fragment is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p><p>
In order to indicate that the subject supports WS-Fragment
@@ -1095,4 +1095,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180">8180</a>,
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299">8299</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191">8191</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</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=8196">8196</a></td></tr><tr><td> 2010/02/10 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</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.104
retrieving revision 1.105
diff -u -d -r1.104 -r1.105
--- wst.html 9 Feb 2010 19:44:42 -0000 1.104
+++ wst.html 10 Feb 2010 00:49:39 -0000 1.105
@@ -107,7 +107,7 @@
resources are long-lived and stable, there are no guarantees, and clients
are advised to code defensively.</p><p>There is no requirement for uniformity in resource representations between
the messages defined in this specification. For example, the
- representations required by Create or Put can differ from the representation
+ representations used by Create or Put can differ from the representation
returned by Get, depending on the semantic requirements of the service.
Additionally, there is no requirement that the resource content is fixed for
any given endpoint reference. The resource content can vary based on
@@ -668,7 +668,7 @@
In some cases, the initial representation MAY constitute the
representation of a logical constructor for the resource and can
thus differ structurally from the representation returned by Get or
- the one required by Put. This is because
+ the one used by Put. This is because
the parameterization requirement for creating a resource is
often distinct from the steady-state representation of the resource.
Implementations SHOULD provide metadata which describes the use of
@@ -735,7 +735,7 @@
</wst:Representation>?
<em>xs:any</em>*
</wst:CreateResponse></pre></div></div><dl><dt class="label"><b>[Body]</b>/wst:CreateResponse/wst:ResourceCreated </dt><dd><p>
- This required element MUST be an endpoint reference for the
+ This REQUIRED element MUST be an endpoint reference for the
newly created resource. This endpoint reference MUST
identify the resource for future Get, Put, and Delete
operations.
@@ -924,7 +924,7 @@
authenticated using the mechanisms described in WS-Security.</p></li><li><p><em>Accountability</em> - Accountability is a function of the
type of and string of the key and algorithms being used. In many cases, a
strong symmetric key provides sufficient accountability. However, in some
- environments, strong PKI signatures are required.</p></li><li><p><em>Availability</em> - All reliable messaging services are
+ environments, strong PKI signatures are needed.</p></li><li><p><em>Availability</em> - All reliable messaging services are
subject to a variety of availability attacks. Replay detection is a
common attack and it is RECOMMENDED that this be addressed by the
mechanisms described in WS-Security. Other attacks, such as network-level
@@ -966,7 +966,7 @@
</p><p>
The wst: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
+ alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p><p>
In order to indicate that the subject supports WS-Transfer
@@ -1037,7 +1037,7 @@
The wst: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
+ alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource Factory.
</p><p>
In order to indicate that the subject supports WS-Transfer
@@ -1498,4 +1498,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7774">7774</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issues
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8302">8302</a>,
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8180">8180</a>,
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299">8299</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=8299">8299</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -d -r1.91 -r1.92
--- wsmex.xml 29 Jan 2010 04:19:48 -0000 1.91
+++ wsmex.xml 10 Feb 2010 00:49:37 -0000 1.92
@@ -1663,7 +1663,7 @@
<kw>Accountability</kw> - Accountability is a function of the type
of and strength of the key and algorithms being used. In many
cases, a strong symmetric key provides sufficient accountability.
- However, in some environments, strong PKI signatures are required.
+ However, in some environments, strong PKI signatures are needed.
</p>
</item>
<item>
@@ -1758,7 +1758,7 @@
<p>
The mex:MetadataExchange policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-MetadataExchange is required to communicate with
+ alternative, is that WS-MetadataExchange is REQUIRED to communicate with
the subject and that the subject supports WS-MetadataExchange.
</p>
@@ -2626,6 +2626,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728">7728</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -d -r1.112 -r1.113
--- wsenum.html 9 Feb 2010 19:44:41 -0000 1.112
+++ wsenum.html 10 Feb 2010 00:46:56 -0000 1.113
@@ -585,9 +585,9 @@
shut-down.
</p></dd><dt class="label"><b>[Body]</b>/wsen:EnumerateResponse/wsen:EnumerationContext
</dt><dd><p>
- The required EnumerationContext element
+ The REQUIRED EnumerationContext element
contains the XML representation of the new enumeration context. The
- consumer is required to pass this XML data in Pull requests for
+ consumer is REQUIRED to pass this XML data in Pull requests for
this enumeration context, until and unless a PullResponse or
RenewResponse message updates the enumeration context.
</p></dd></dl><p><a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
@@ -676,13 +676,13 @@
The following describes additional, normative
constraints on the outline listed above:
</p><dl><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:EnumerationContext </dt><dd><p>
- This required element contains the XML data
+ This REQUIRED element contains the XML data
that represents the current enumeration context.
</p></dd><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:MaxTime </dt><dd><p>
This OPTIONAL element (of type xs:duration)
indicates the maximum amount of time the initiator is willing to
allow the data source to assemble the Pull response. When this
- element is absent, the data source is not required to limit the
+ element is absent, the data source is NOT REQUIRED to limit the
amount of time it takes to assemble the Pull
response. The data source MUST recognize the wsen:MaxTime
element and return a wsen:TimedOut fault if no elements
@@ -704,7 +704,7 @@
This OPTIONAL element (of type xs:long)
indicates the maximum size of the returned elements, in Unicode
characters, that the initiator is willing to accept. When this
- element is absent, the data source is not required to limit the
+ element is absent, the data source is NOT REQUIRED to limit the
number of characters in the Pull response.
Implementations MUST NOT
return a Pull response message whose wsen:Items element, and
@@ -887,7 +887,7 @@
(see <a href="#Enumerate"><b>3.1 Enumerate</b></a>) with the following
addition(s):
</p><dl><dt class="label"><b>[Body]</b>/wsen:Renew/wsen:EnumerationContext </dt><dd><p>
- This required element contains the XML data
+ This REQUIRED element contains the XML data
that represents the current enumeration context.
</p></dd></dl><p>
Other components of the outline above are not
@@ -979,7 +979,7 @@
constraints on the outline listed above:
</p><dl><dt class="label"><b>[Body]</b>/wsen:Release/wsen:EnumerationContext
</dt><dd><p>
- This required element contains the XML data
+ This REQUIRED element contains the XML data
that represents the enumeration context being
abandoned.
</p></dd></dl><p>
@@ -1287,7 +1287,7 @@
a function of the type of and string of the key and algorithms
being used. In many cases, a strong symmetric key
provides sufficient accountability. However, in some
- environments, strong PKI signatures are required.
+ environments, strong PKI signatures are needed.
</p></li><li><p><em>Availability</em>
- All reliable
messaging services are subject to a variety of availability
@@ -1336,7 +1336,7 @@
The wsenu:DataSource policy assertion is a nested policy
container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Enumeration is required to communicate with the
+ alternative, is that WS-Enumeration is REQUIRED to communicate with the
subject and that the subject is a WS-Enumeration data source.
</p><p>
In order to indicate that the subject supports WS-Enumeration
@@ -2091,4 +2091,6 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157">8157</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a></td></tr><tr><td> 2010/02/05 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6436">6436</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=6436">6436</a></td></tr><tr><td> 2010/02/08 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</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.104
retrieving revision 1.105
diff -u -d -r1.104 -r1.105
--- wsenum.xml 8 Feb 2010 18:11:29 -0000 1.104
+++ wsenum.xml 10 Feb 2010 00:46:58 -0000 1.105
@@ -1001,9 +1001,9 @@
</label>
<def>
<p>
- The required EnumerationContext element
+ The REQUIRED EnumerationContext element
contains the XML representation of the new enumeration context. The
- consumer is required to pass this XML data in Pull requests for
+ consumer is REQUIRED to pass this XML data in Pull requests for
this enumeration context, until and unless a PullResponse or
RenewResponse message updates the enumeration context.
</p>
@@ -1131,7 +1131,7 @@
<label> <kw>[Body]</kw>/wsen:Pull/wsen:EnumerationContext </label>
<def>
<p>
- This required element contains the XML data
+ This REQUIRED element contains the XML data
that represents the current enumeration context.
</p>
</def>
@@ -1144,7 +1144,7 @@
This OPTIONAL element (of type xs:duration)
indicates the maximum amount of time the initiator is willing to
allow the data source to assemble the Pull response. When this
- element is absent, the data source is not required to limit the
+ element is absent, the data source is NOT REQUIRED to limit the
amount of time it takes to assemble the Pull
response. The data source MUST recognize the wsen:MaxTime
element and return a wsen:TimedOut fault if no elements
@@ -1181,7 +1181,7 @@
This OPTIONAL element (of type xs:long)
indicates the maximum size of the returned elements, in Unicode
characters, that the initiator is willing to accept. When this
- element is absent, the data source is not required to limit the
+ element is absent, the data source is NOT REQUIRED to limit the
number of characters in the Pull response.
Implementations MUST NOT
return a Pull response message whose wsen:Items element, and
@@ -1447,7 +1447,7 @@
<label> <kw>[Body]</kw>/wsen:Renew/wsen:EnumerationContext </label>
<def>
<p>
- This required element contains the XML data
+ This REQUIRED element contains the XML data
that represents the current enumeration context.
</p>
</def>
@@ -1605,7 +1605,7 @@
</label>
<def>
<p>
- This required element contains the XML data
+ This REQUIRED element contains the XML data
that represents the enumeration context being
abandoned.
</p>
@@ -2394,7 +2394,7 @@
a function of the type of and string of the key and algorithms
being used. In many cases, a strong symmetric key
provides sufficient accountability. However, in some
- environments, strong PKI signatures are required.
+ environments, strong PKI signatures are needed.
</p>
</item>
@@ -2467,7 +2467,7 @@
The wsenu:DataSource policy assertion is a nested policy
container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Enumeration is required to communicate with the
+ alternative, is that WS-Enumeration is REQUIRED to communicate with the
subject and that the subject is a WS-Enumeration data source.
</p>
@@ -3917,6 +3917,20 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6436">6436</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/08 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</loc>
+ </td>
+ </tr>
+ <tr>
+ <td> 2010/02/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.103
retrieving revision 1.104
diff -u -d -r1.103 -r1.104
--- wsmex.html 9 Feb 2010 19:44:42 -0000 1.103
+++ wsmex.html 10 Feb 2010 00:49:37 -0000 1.104
@@ -1007,7 +1007,7 @@
</p></li><li><p><b>Accountability</b> - Accountability is a function of the type
of and strength of the key and algorithms being used. In many
cases, a strong symmetric key provides sufficient accountability.
- However, in some environments, strong PKI signatures are required.
+ However, in some environments, strong PKI signatures are needed.
</p></li><li><p><b>Availability</b> - Metadata services are subject to a variety
of availability attacks such as application-level denial of
service. It is RECOMMENDED that the mechanisms described in
@@ -1060,7 +1060,7 @@
</p><p>
The mex:MetadataExchange policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-MetadataExchange is required to communicate with
+ alternative, is that WS-MetadataExchange is REQUIRED to communicate with
the subject and that the subject supports WS-MetadataExchange.
</p><p>
In order to indicate that the subject supports WS-MetadataExchange
@@ -1422,4 +1422,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8292">8292</a></td></tr><tr><td> 2010/01/27 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8290">8290</a></td></tr><tr><td> 2010/01/27 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8205">8205</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728">7728</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=7728">7728</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -d -r1.153 -r1.154
--- wseventing.xml 9 Feb 2010 19:41:44 -0000 1.153
+++ wseventing.xml 10 Feb 2010 00:48:11 -0000 1.154
@@ -883,7 +883,7 @@
<p>
This element contains the information necessary to convey
notification messages to the event sink in
- a manner required by the subscriber. This element MUST contain
+ a manner REQUIRED by the subscriber. This element MUST contain
at least one child element.
</p>
</def>
@@ -2565,7 +2565,7 @@
a function of the type of and string of the key and
algorithms being used. In many cases, a strong symmetric key
provides sufficient accountability. However, in some
- environments, strong PKI signatures are required.
+ environments, strong PKI signatures are needed.
</p>
</item>
@@ -2706,7 +2706,7 @@
<p>
The wse:EventSource policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Eventing is required to communicate with the
+ alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing event source.
</p>
@@ -2863,7 +2863,7 @@
<p>
The wse:SubscriptionManager policy assertion is a nested policy container
assertion. The meaning of this assertion, when present in a policy
- alternative, is that WS-Eventing is required to communicate with the
+ alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing subscription manager.
</p>
@@ -3387,7 +3387,7 @@
SOAP messages called "Notifications". These notifications MAY be
described via a Web Services Description Language <bibref ref="WSDL11"/>
definitions element termed a "Notification WSDL". A Notification WSDL
- describes the interface that the event sink is required to implement to
+ describes the interface that the event sink is REQUIRED to implement to
receive and process the notifications that might result from a
successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
@@ -4879,6 +4879,20 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435">6435</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/08 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</loc>
+ </td>
+ </tr>
+ <tr>
+ <td> 2010/02/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Wednesday, 10 February 2010 00:49:51 UTC