- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 18 Aug 2009 21:40:10 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv31461
Modified Files:
wsrt.html wsrt.xml
Log Message:
7196
Index: wsrt.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- wsrt.html 18 Aug 2009 20:54:31 -0000 1.41
+++ wsrt.html 18 Aug 2009 21:40:07 -0000 1.42
@@ -271,7 +271,7 @@
</p></dd><dt class="label">Metadata resource</dt><dd><p>
A resource whose XML representation describes some aspect of the
metadata of another resource, such as its WSDL or lifecycle metadata.
- Each resource may have zero or more metadata resources associated with
+ Each resource MAY have zero or more metadata resources associated with
it.
</p></dd><dt class="label">Fragment</dt><dd><p>
The term "fragment" is used in this specification to mean a
@@ -372,8 +372,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>
@@ -415,17 +415,17 @@
The dialects defined below are used to form an expression
that can be evaluated with respect to the XML document that represents the
resource. The de-referenced value of the expression is the part of the XML
- that is of interest. The expression may form a logical "pointer" to
- the fragment of XML that is of interest or, depending on the dialect, may
+ that is of interest. The expression MAY form a logical "pointer" to
+ the fragment of XML that is of interest or, depending on the dialect, MAY
form a query that can be applied to the XML document to produce an
evaluated result. It is important to understand that these expression
dialects simply identify the appropriate fragment of the resource
representation and that the <b>[Action]</b>
itself defines what will happen to the referenced fragment.
</p><p>
- The definition of each dialect must clearly specify how the
+ The definition of each dialect MUST clearly specify how the
result of evaluating an expression against a resource representation is
- serialized to XML and should specify any dialect-specific behavior for
+ serialized to XML and SHOULD specify any dialect-specific behavior for
operations that access the resource representation.
</p><div class="div3">
<h4><a name="qname" id="qname"/>4.2.1 QName Dialect</h4><p>
@@ -528,7 +528,7 @@
Implementations that support the full XPath 1.0 dialect MUST
support the XPath Level 1 dialect.
</p><p>
- Note that the expression may evaluate to one of four
+ Note that the expression MAY evaluate to one of four
possible types: a node-set, a Boolean, a number or a string. The
latter three types are the results of evaluating a computed expression.
They are serialized
@@ -584,7 +584,7 @@
used as the wrapper element when serializing these node-sets outside of
a WS-RT result.
</p><p>
- An XPath 1.0 expression may evaluate to multiple nodes;
+ An XPath 1.0 expression MAY evaluate to multiple nodes;
because of this the XPath 1.0 dialect MUST NOT be used with a "Put" or
"Create" operation.
</p></div></div><div class="div2">
@@ -949,7 +949,7 @@
representation MUST be omitted in the response. Otherwise the response
MUST be as described in WS-Transfer. The absence of the resource
representation in the response is in recognition of the potentially
- large amount of data that may be returned, which may have been the
+ large amount of data that can be returned, which could have been the
reason a fragment Put was used instead of
sending the entire resource representation.
</p></dd></dl><p>
@@ -979,9 +979,9 @@
(20) </wsrt:Fragment>
(21) </wsrt:Put>
(22) </s:Body></pre></div></div><p>
- Line (04) indicates that a fragment should be removed and is targeted
+ Line (04) indicates that a fragment SHOULD be removed and is targeted
at the 1<sup>st</sup> Volume element, identified by the wsrt:Expression
- contents on line (05). Line (09) indicates that a fragment should be
+ contents on line (05). Line (09) indicates that a fragment SHOULD be
inserted into the representation that results from applying the first
fragment update.
The insertion location is identified by the wsrt:Expression contents on
@@ -1063,7 +1063,7 @@
contents on line (06). Lines (08) - (19) show the new value for this
set of elements to use to replace the old set.
</p><p>
- Lines (21) - (32) indicates that a fragment should be inserted into the
+ Lines (21) - (32) indicates that a fragment SHOULD be inserted into the
representation that results from applying the first fragment update.
Lines (25) - (31) show the content of the new Volume which is added at
the end.
@@ -1108,7 +1108,7 @@
presented representation. The new resource will be assigned a
factory-service-determined
endpoint reference that is returned in the response message. In many cases, the
- information required to create a resource may markedly differ from the initial
+ information required to create a resource can markedly differ from the initial
representation (the value as realized by a subsequent "Get"
operation), and supplying the initial representation is not viable.
</p><p>
@@ -1295,7 +1295,7 @@
</s11:Envelope></pre></div></div><div class="div2">
<h3><a name="unreachable" id="unreachable"/>5.1 wsa:DestinationUnreachable</h3><p>
This fault is generated in response to a message that is targeted at a
- resource that cannot be found and is deemed not to exist. This may be
+ resource that cannot be found and is deemed not to exist. This can be
because the resource was never created or because the resource has
been destroyed - there is no distinction between these cases.
</p><p>
@@ -1305,7 +1305,7 @@
<h3><a name="unavailable" id="unavailable"/>5.2 wsa:EndpointUnavailable</h3><p>
The resource is unable to process the message at this time due to
some transient issue. The endpoint MAY optionally include a wsa:RetryAfter
- parameter in the detail. The source should not retransmit the message until
+ parameter in the detail. The source SHOULD not retransmit the message until
this duration has passed.
</p><p>
The SOAP bindings for this fault are defined in
@@ -1379,7 +1379,7 @@
The fault detail SHOULD include a wsrt:SideAffects element
in the fault detail to indicate whether any changes occurred. A value of
"true" indicates some changes occurred; a value of "false" indicates no
- changes occurred. Absence of the element indicates that changes may
+ changes occurred. Absence of the element indicates that changes might
have occurred.
</p><a name="tab_putfault" id="tab_putfault"/><table border="1"><tbody><tr><th align="left"><b>[Action]</b></th><th align="left">
http://www.w3.org/2009/02/ws-rst/fault
@@ -1420,7 +1420,7 @@
http://www.w3.org/2009/02/ws-rst/fault
</th></tr><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsrt:InvalidRemoveSyntaxFault </td></tr><tr><td><b>[Reason]</b></td><td> Invalid syntax used for Put request </td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div></div><div class="div1">
<h2><a name="security" id="security"/>6 Security</h2><p>
- It is strongly recommended that the communication between services be
+ It is strongly RECOMMENDED that the communication between services be
secured using the mechanisms described in <a href="#WSSec">[WS-Security]</a>.
</p><p>
In order to properly secure messages, the
@@ -1430,9 +1430,9 @@
them together and prevent certain types of attacks.
</p><p>
If a requestor is issuing multiple messages
- to a resource reference, then it is recommended that a security context be
+ to a resource reference, then it is RECOMMENDED that a security context be
established using the mechanisms described in <a href="#WSTrust">[WS-Trust]</a> and
- <a href="#WSSecConv">[WS-SecureConversation]</a>. It is further recommended that if shared
+ <a href="#WSSecConv">[WS-SecureConversation]</a>. It is further RECOMMENDED that if shared
secrets are used, message-specific derived keys also be used to protect
the secret from crypto attacks.
</p><p>
@@ -1582,13 +1582,13 @@
The context and document root node need
clarification. XPath Level 1 assumes that the root is the root
node of the resource document, not the SOAP envelope or any other wrapper
- element which may contain the resource.
+ element which might contain the resource.
</p><p>
Further, the default context is the root element and the
context position is 1.
</p><p>
In view of this, the / operator selects the containing root,
- and the only valid operand which may follow it is the outermost element
+ and the only valid operand which can follow it is the outermost element
of the resource:
</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a</pre></div></div><p>The following paths are equivalent:</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b
(02) b</pre></div></div><p>
@@ -1619,13 +1619,13 @@
bindings that are in effect, including default bindings. This allows
implementations to simply match element names in the majority of cases.
If namespace bindings are significant for all elements, then qualified names
- must be used.
+ MUST be used.
</p><p>
The <follower> production allows for special-casing of
the final tokens of the XPath allowing it to end in either an attribute
or text.
</p><p>
- The text() NodeTest may be applied as a final token to the
+ The text() NodeTest MAY be applied as a final token to the
selected element. This NodeTest selects any text nodes that are
children of the selected element. If the element only contains text
content, the
@@ -1635,8 +1635,8 @@
single text node with the value <em>20 </em>as its result. This text
node would then be serialized into the following XML representation:
</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) <wsrt:TextNode>20</wsrt: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:
+ If accessed, attributes MUST be the final token in the path
+ and they MAY be namespace-qualified or unqualified names, as required:
</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. This
@@ -1658,9 +1658,9 @@
</p></div><div class="div1">
<h2><a name="rt_metadata" id="rt_metadata"/>B Resource Metadata Content</h2><p>
A resource can have associated metadata that MAY be
- specified when the resource is created. A resource may provide access to
+ specified when the resource is created. A resource MAY provide access to
that metadata after it has been created and some aspects of a resource's
- metadata may be mutable.
+ metadata MAY be mutable.
</p><p>The form of the resource metadata is shown below.</p><p><b>Resource metadata:</b></p><div class="exampleOuter"><div class="exampleInner"><pre>(01) <wsrt:Metadata>
(02) <wsrt:Lifetime><em>lifetime metadata</em></wsrt:Lifetime> ?
(03) <wsrt:SupportedDialect>
@@ -1683,8 +1683,8 @@
dialects as described in the following sub-sections.
</p><div class="div2">
<h3><a name="lifemeta" id="lifemeta"/>B.1 Lifecycle metadata</h3><p>
- Resources have a distinct lifecycle in that they may be
- created and they may be destroyed. There is no distinction between
+ Resources have a distinct lifecycle in that they can be
+ created and they can be destroyed. There is no distinction between
a resource that has been destroyed and a resource that has not been
created.
</p><p>
@@ -2126,4 +2126,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</a></td></tr><tr><td> 2009/07/01 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6699">6699</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</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=7196">7196</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsrt.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- wsrt.xml 18 Aug 2009 21:10:01 -0000 1.31
+++ wsrt.xml 18 Aug 2009 21:40:08 -0000 1.32
@@ -382,7 +382,7 @@
<p>
A resource whose XML representation describes some aspect of the
metadata of another resource, such as its WSDL or lifecycle metadata.
- Each resource may have zero or more metadata resources associated with
+ Each resource MAY have zero or more metadata resources associated with
it.
</p>
</def>
@@ -726,8 +726,8 @@
The dialects defined below are used to form an expression
that can be evaluated with respect to the XML document that represents the
resource. The de-referenced value of the expression is the part of the XML
- that is of interest. The expression may form a logical "pointer" to
- the fragment of XML that is of interest or, depending on the dialect, may
+ that is of interest. The expression MAY form a logical "pointer" to
+ the fragment of XML that is of interest or, depending on the dialect, MAY
form a query that can be applied to the XML document to produce an
evaluated result. It is important to understand that these expression
dialects simply identify the appropriate fragment of the resource
@@ -736,9 +736,9 @@
</p>
<p>
- The definition of each dialect must clearly specify how the
+ The definition of each dialect MUST clearly specify how the
result of evaluating an expression against a resource representation is
- serialized to XML and should specify any dialect-specific behavior for
+ serialized to XML and SHOULD specify any dialect-specific behavior for
operations that access the resource representation.
</p>
@@ -930,7 +930,7 @@
</p>
<p>
- Note that the expression may evaluate to one of four
+ Note that the expression MAY evaluate to one of four
possible types: a node-set, a Boolean, a number or a string. The
latter three types are the results of evaluating a computed expression.
They are serialized
@@ -1053,7 +1053,7 @@
</p>
<p>
- An XPath 1.0 expression may evaluate to multiple nodes;
+ An XPath 1.0 expression MAY evaluate to multiple nodes;
because of this the XPath 1.0 dialect MUST NOT be used with a "Put" or
"Create" operation.
</p>
@@ -1619,7 +1619,7 @@
representation MUST be omitted in the response. Otherwise the response
MUST be as described in WS-Transfer. The absence of the resource
representation in the response is in recognition of the potentially
- large amount of data that may be returned, which may have been the
+ large amount of data that can be returned, which could have been the
reason a fragment Put was used instead of
sending the entire resource representation.
</p>
@@ -1660,9 +1660,9 @@
</example>
<p>
- Line (04) indicates that a fragment should be removed and is targeted
+ Line (04) indicates that a fragment SHOULD be removed and is targeted
at the 1<sup>st</sup> Volume element, identified by the wsrt:Expression
- contents on line (05). Line (09) indicates that a fragment should be
+ contents on line (05). Line (09) indicates that a fragment SHOULD be
inserted into the representation that results from applying the first
fragment update.
The insertion location is identified by the wsrt:Expression contents on
@@ -1760,7 +1760,7 @@
</p>
<p>
- Lines (21) - (32) indicates that a fragment should be inserted into the
+ Lines (21) - (32) indicates that a fragment SHOULD be inserted into the
representation that results from applying the first fragment update.
Lines (25) - (31) show the content of the new Volume which is added at
the end.
@@ -1818,7 +1818,7 @@
presented representation. The new resource will be assigned a
factory-service-determined
endpoint reference that is returned in the response message. In many cases, the
- information required to create a resource may markedly differ from the initial
+ information required to create a resource can markedly differ from the initial
representation (the value as realized by a subsequent "Get"
operation), and supplying the initial representation is not viable.
</p>
@@ -2149,7 +2149,7 @@
<p>
This fault is generated in response to a message that is targeted at a
- resource that cannot be found and is deemed not to exist. This may be
+ resource that cannot be found and is deemed not to exist. This can be
because the resource was never created or because the resource has
been destroyed - there is no distinction between these cases.
</p>
@@ -2166,7 +2166,7 @@
<p>
The resource is unable to process the message at this time due to
some transient issue. The endpoint MAY optionally include a wsa:RetryAfter
- parameter in the detail. The source should not retransmit the message until
+ parameter in the detail. The source SHOULD not retransmit the message until
this duration has passed.
</p>
@@ -2433,7 +2433,7 @@
The fault detail SHOULD include a wsrt:SideAffects element
in the fault detail to indicate whether any changes occurred. A value of
"true" indicates some changes occurred; a value of "false" indicates no
- changes occurred. Absence of the element indicates that changes may
+ changes occurred. Absence of the element indicates that changes might
have occurred.
</p>
@@ -2629,7 +2629,7 @@
<head>Security</head>
<p>
- It is strongly recommended that the communication between services be
+ It is strongly RECOMMENDED that the communication between services be
secured using the mechanisms described in <bibref ref="WSSec"/>.
</p>
@@ -2643,9 +2643,9 @@
<p>
If a requestor is issuing multiple messages
- to a resource reference, then it is recommended that a security context be
+ to a resource reference, then it is RECOMMENDED that a security context be
established using the mechanisms described in <bibref ref="WSTrust"/> and
- <bibref ref="WSSecConv"/>. It is further recommended that if shared
+ <bibref ref="WSSecConv"/>. It is further RECOMMENDED that if shared
secrets are used, message-specific derived keys also be used to protect
the secret from crypto attacks.
</p>
@@ -2896,7 +2896,7 @@
The context and document root node need
clarification. XPath Level 1 assumes that the root is the root
node of the resource document, not the SOAP envelope or any other wrapper
- element which may contain the resource.
+ element which might contain the resource.
</p>
<p>
@@ -2906,7 +2906,7 @@
<p>
In view of this, the / operator selects the containing root,
- and the only valid operand which may follow it is the outermost element
+ and the only valid operand which can follow it is the outermost element
of the resource:
</p>
@@ -2973,7 +2973,7 @@
bindings that are in effect, including default bindings. This allows
implementations to simply match element names in the majority of cases.
If namespace bindings are significant for all elements, then qualified names
- must be used.
+ MUST be used.
</p>
<p>
@@ -2983,7 +2983,7 @@
</p>
<p>
- The text() NodeTest may be applied as a final token to the
+ The text() NodeTest MAY be applied as a final token to the
selected element. This NodeTest selects any text nodes that are
children of the selected element. If the element only contains text
content, the
@@ -3005,8 +3005,8 @@
</example>
<p>
- If accessed, attributes must be the final token in the path
- and they may be namespace-qualified or unqualified names, as required:
+ If accessed, attributes MUST be the final token in the path
+ and they MAY be namespace-qualified or unqualified names, as required:
</p>
<example>
@@ -3053,9 +3053,9 @@
<p>
A resource can have associated metadata that MAY be
- specified when the resource is created. A resource may provide access to
+ specified when the resource is created. A resource MAY provide access to
that metadata after it has been created and some aspects of a resource's
- metadata may be mutable.
+ metadata MAY be mutable.
</p>
<p>The form of the resource metadata is shown below.</p>
@@ -3100,8 +3100,8 @@
<head>Lifecycle metadata</head>
<p>
- Resources have a distinct lifecycle in that they may be
- created and they may be destroyed. There is no distinction between
+ Resources have a distinct lifecycle in that they can be
+ created and they can be destroyed. There is no distinction between
a resource that has been destroyed and a resource that has not been
created.
</p>
@@ -3777,6 +3777,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=7196">7196</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 18 August 2009 21:40:20 UTC