- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 18 Aug 2009 21:32:47 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv30985
Modified Files:
wsmex.html wsmex.xml
Log Message:
7195
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- wsmex.xml 18 Aug 2009 21:10:01 -0000 1.38
+++ wsmex.xml 18 Aug 2009 21:32:44 -0000 1.39
@@ -123,11 +123,11 @@
endpoint references, and how Web service endpoints can optionally
support a request-response interaction for the retrieval of metadata.
When the type of metadata sought is clearly known, e.g.,
- <bibref ref='WS-Policy'/>, a requester may indicate that only that
- type should be returned; where additional types of metadata are being
+ <bibref ref='WS-Policy'/>, a requester MAY indicate that only that
+ type is to be returned; where additional types of metadata are being
used, or are expected, or when a requester needs to retrieve all of
the metadata relevant to subsequent interactions with an endpoint, a
- requester may indicate that all available metadata, regardless of their
+ requester MAY indicate that all available metadata, regardless of their
types, are expected.
</p>
@@ -240,7 +240,7 @@
resource's representation. In this case, the requested representation
is the WS-Metadata Exchange Metadata element about a Web service
endpoint. The fact that the resource's representation is a
- mex:Metadata element may be known to the requestor but is not
+ mex:Metadata element might be known to the requestor but is not
explicitly encoded in the request message.
</p>
@@ -359,7 +359,7 @@
a WS-Transfer GET request directed to the endpoint identified by the
mex:MetadataReference element in lines 72-76 of
<specref ref="GetResponse"/>,
- some endpoints may choose to support explicit request for metadata.
+ some endpoints MAY choose to support explicit request for metadata.
<specref ref="GetMexReq"/> illustrates a sample GetMetadata request
for the <bibref ref ='WS-Policy'/>.
</p>
@@ -777,8 +777,8 @@
<p>
To facilitate processing, Metadata Sections are tagged with a
@Dialect and (optionally) @Identifier of the metadata unit. To ensure
- scalability, a unit of metadata may be included in-line within its
- Metadata Section or may be included by reference, either an endpoint
+ scalability, a unit of metadata MAY be included in-line within its
+ Metadata Section or MAY be included by reference, either an endpoint
reference <bibref ref='AddrCore'/>
(Metadata Reference) or a URL (Location).
</p>
@@ -853,7 +853,7 @@
<p>
This specification defines the following values for Dialect;
- other specifications should define values for Dialect for their
+ other specifications SHOULD define values for Dialect for their
metadata format(s).
</p>
@@ -1040,7 +1040,7 @@
MAY send a <bibref ref='WS-Transfer'/> Get request message to the
metadata resource's endpoint. The WS-Transfer Get request fetches a
one-time snapshot of the metadata. The metadata associated with a
- service endpoint may be available as multiple metadata resources.
+ service endpoint MAY be available as multiple metadata resources.
</p>
<p>
@@ -1457,11 +1457,11 @@
</p>
<p>
- When that information is not available, however, requesters must
+ When that information is not available, however, requesters will
rely on contextual or out-of-band information in order to choose
the protocol binding most appropriate to use in retrieving Web
service metadata. Furthermore, specific protocol bindings for
- metadata retrieval may be defined by communities within the
+ metadata retrieval MAY be defined by communities within the
context of particular application domains.
</p>
</div1>
@@ -1481,13 +1481,13 @@
</p>
<p>
- Different security mechanisms may be desired depending on the
+ Different security mechanisms might be desired depending on the
frequency of messages. For example, for infrequent messages, public key
- technologies may be adequate for integrity and confidentiality.
- However, for high-frequency events, it may be more performant to
+ technologies might be adequate for integrity and confidentiality.
+ However, for high-frequency events, it might be more performant to
establish a security context for the events using the mechanisms
described in <bibref ref='WS-Trust'/> and
- <bibref ref='WS-SecureConversation'/>. It should be noted that if
+ <bibref ref='WS-SecureConversation'/>. Note that if
a shared secret is used it is RECOMMENDED that derived keys be used
to strengthen the secret as described in WS-SecureConversation.
</p>
@@ -1511,7 +1511,7 @@
<p>
Additionally, some metadata formats, such as policies
- <bibref ref='WS-Policy'/>, may have embedded security
+ <bibref ref='WS-Policy'/>, can have embedded security
semantics. These SHOULD be verified using the same considerations
outlined in this section.
</p>
@@ -1562,7 +1562,7 @@
<p>
<kw>Availability</kw> - 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
+ service. It is RECOMMENDED that the mechanisms described in
WS-Security be considered as mitigations for some forms of
attacks. Other attacks, such as network-level denial of service
are harder to avoid. Note that both of these classes of attack
@@ -1571,8 +1571,8 @@
</item>
<item>
<p>
- <kw>Replay</kw> - Messages may be replayed for a variety of
- reasons. To detect and eliminate this attack, mechanisms should
+ <kw>Replay</kw> - Messages can be replayed for a variety of
+ reasons. To detect and eliminate this attack, mechanisms SHOULD
be used to identify replayed messages such as the timestamp/nonce
outlined in WS-Security. Alternatively, and optionally, other
technologies, such as sequencing, can also be used to prevent
@@ -1742,7 +1742,7 @@
<p>
A normative copy of the XML Schema <bibref ref='Schema1'/>,
- <bibref ref='Schema2'/> description for this specification may be
+ <bibref ref='Schema2'/> description for this specification can be
retrieved from the following address:
</p>
@@ -1839,7 +1839,7 @@
<p>
A normative copy of the WSDL <bibref ref='WSDL11'/> description for
- this specification may be retrieved from the following address:
+ this specification can be retrieved from the following address:
</p>
<example>
@@ -2060,6 +2060,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/08/18 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7195">7195</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- wsmex.html 18 Aug 2009 20:54:31 -0000 1.48
+++ wsmex.html 18 Aug 2009 21:32:44 -0000 1.49
@@ -89,11 +89,11 @@
endpoint references, and how Web service endpoints can optionally
support a request-response interaction for the retrieval of metadata.
When the type of metadata sought is clearly known, e.g.,
- <a href="#WS-Policy">[WS-Policy]</a>, a requester may indicate that only that
- type should be returned; where additional types of metadata are being
+ <a href="#WS-Policy">[WS-Policy]</a>, a requester MAY indicate that only that
+ type is to be returned; where additional types of metadata are being
used, or are expected, or when a requester needs to retrieve all of
the metadata relevant to subsequent interactions with an endpoint, a
- requester may indicate that all available metadata, regardless of their
+ requester MAY indicate that all available metadata, regardless of their
types, are expected.
</p><p>
The mechanisms defined herein are intended for the retrieval of
@@ -153,7 +153,7 @@
resource's representation. In this case, the requested representation
is the WS-Metadata Exchange Metadata element about a Web service
endpoint. The fact that the resource's representation is a
- mex:Metadata element may be known to the requestor but is not
+ mex:Metadata element might be known to the requestor but is not
explicitly encoded in the request message.
</p><p><a href="#GetResponse">Example 2-2</a> illustrates a sample response to the
request of <a href="#GetRequest">Example 2-1</a>.
@@ -260,7 +260,7 @@
a WS-Transfer GET request directed to the endpoint identified by the
mex:MetadataReference element in lines 72-76 of
<a href="#GetResponse">Example 2-2</a>,
- some endpoints may choose to support explicit request for metadata.
+ some endpoints MAY choose to support explicit request for metadata.
<a href="#GetMexReq">Example 2-3</a> illustrates a sample GetMetadata request
for the <a href="#WS-Policy">[WS-Policy]</a>.
</p><div class="exampleOuter">
@@ -410,8 +410,8 @@
In cases where it is either desirable or necessary for the receiver
of a request that has been extended to indicate that it has
recognized and accepted the semantics associated with that extension,
- it is recommended that the receiver add a corresponding extension
- to the response message. The definition of an extension should clearly
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD clearly
specify how the extension that appears in the response correlates
with that in the corresponding request.
</p><p>
@@ -478,8 +478,8 @@
</p><p>
To facilitate processing, Metadata Sections are tagged with a
@Dialect and (optionally) @Identifier of the metadata unit. To ensure
- scalability, a unit of metadata may be included in-line within its
- Metadata Section or may be included by reference, either an endpoint
+ scalability, a unit of metadata MAY be included in-line within its
+ Metadata Section or MAY be included by reference, either an endpoint
reference <a href="#AddrCore">[WS-Addressing]</a>
(Metadata Reference) or a URL (Location).
</p><p>
@@ -521,7 +521,7 @@
<a href="#RFC3986">[RFC 3986]</a> section 6.2.1.
</p></dd></dl><p>
This specification defines the following values for Dialect;
- other specifications should define values for Dialect for their
+ other specifications SHOULD define values for Dialect for their
metadata format(s).
</p><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#Schema1">[XML Schema: Structures]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL 1.1]</a></td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#WS-Policy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all </td><td> None. [Defined in this specification for use in GetMetadata requests. See <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
If there is more than one metadata unit with the same Dialect, e.g.,
@@ -592,7 +592,7 @@
MAY send a <a href="#WS-Transfer">[WS-Transfer]</a> Get request message to the
metadata resource's endpoint. The WS-Transfer Get request fetches a
one-time snapshot of the metadata. The metadata associated with a
- service endpoint may be available as multiple metadata resources.
+ service endpoint MAY be available as multiple metadata resources.
</p><p>
The representation of a metadata resource MAY be a mex:Metadata
element which MAY contain one or more mex:MetadataSection children.
@@ -854,11 +854,11 @@
resource, or a GetMetadata request against a service endpoint, in
order to retrieve all the information needed to use the service.
</p><p>
- When that information is not available, however, requesters must
+ When that information is not available, however, requesters will
rely on contextual or out-of-band information in order to choose
the protocol binding most appropriate to use in retrieving Web
service metadata. Furthermore, specific protocol bindings for
- metadata retrieval may be defined by communities within the
+ metadata retrieval MAY be defined by communities within the
context of particular application domains.
</p></div><div class="div1">
<h2><a name="Security" id="Security"/>9 Security</h2><p>
@@ -871,13 +871,13 @@
<a href="#AddrCore">[WS-Addressing]</a>, need to be signed with the body in
order to "bind" the two together.
</p><p>
- Different security mechanisms may be desired depending on the
+ Different security mechanisms might be desired depending on the
frequency of messages. For example, for infrequent messages, public key
- technologies may be adequate for integrity and confidentiality.
- However, for high-frequency events, it may be more performant to
+ technologies might be adequate for integrity and confidentiality.
+ However, for high-frequency events, it might be more performant to
establish a security context for the events using the mechanisms
described in <a href="#WS-Trust">[WS-Trust]</a> and
- <a href="#WS-SecureConversation">[WS-SecureConversation]</a>. It should be noted that if
+ <a href="#WS-SecureConversation">[WS-SecureConversation]</a>. Note that if
a shared secret is used it is RECOMMENDED that derived keys be used
to strengthen the secret as described in WS-SecureConversation.
</p><p>
@@ -895,7 +895,7 @@
of the sender.
</p><p>
Additionally, some metadata formats, such as policies
- <a href="#WS-Policy">[WS-Policy]</a>, may have embedded security
+ <a href="#WS-Policy">[WS-Policy]</a>, can have embedded security
semantics. These SHOULD be verified using the same considerations
outlined in this section.
</p><p>
@@ -919,13 +919,13 @@
However, in some environments, strong PKI signatures are required.
</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
+ service. It is RECOMMENDED that the mechanisms described in
WS-Security be considered as mitigations for some forms of
attacks. Other attacks, such as network-level denial of service
are harder to avoid. Note that both of these classes of attack
are outside the scope of this specification.
- </p></li><li><p><b>Replay</b> - Messages may be replayed for a variety of
- reasons. To detect and eliminate this attack, mechanisms should
+ </p></li><li><p><b>Replay</b> - Messages can be replayed for a variety of
+ reasons. To detect and eliminate this attack, mechanisms SHOULD
be used to identify replayed messages such as the timestamp/nonce
outlined in WS-Security. Alternatively, and optionally, other
technologies, such as sequencing, can also be used to prevent
@@ -1016,7 +1016,7 @@
(See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd></dl></div></div><div class="back"><div class="div1">
<h2><a name="Appendix-A" id="Appendix-A"/>A XML Schema</h2><p>
A normative copy of the XML Schema <a href="#Schema1">[XML Schema: Structures]</a>,
- <a href="#Schema2">[XML Schema: Datatypes]</a> description for this specification may be
+ <a href="#Schema2">[XML Schema: Datatypes]</a> description for this specification can be
retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd">http://www.w3.org/2009/02/ws-mex/MetadataExchange.xsd</a></pre></div></div><p>
A non-normative copy of the XML Schema description is listed below for
@@ -1098,7 +1098,7 @@
</xs:schema></pre></div></div></div><div class="div1">
<h2><a name="Appendix-B" id="Appendix-B"/>B WSDL</h2><p>
A normative copy of the WSDL <a href="#WSDL11">[WSDL 1.1]</a> description for
- this specification may be retrieved from the following address:
+ this specification can be retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl">http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl</a></pre></div></div><p>
A non-normative copy of the WSDL description is listed below for
convenience.
@@ -1160,4 +1160,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6720">6720</a></td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7194">7194</a></td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679">6679</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</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=7206">7206</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7195">7195</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 18 August 2009 21:32:55 UTC