- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 29 Jan 2010 04:11:00 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv25005
Modified Files:
wsfrag.html wsfrag.xml
Log Message:
8191
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -d -r1.46 -r1.47
--- wsfrag.html 29 Jan 2010 04:00:59 -0000 1.46
+++ wsfrag.html 29 Jan 2010 04:10:58 -0000 1.47
@@ -63,10 +63,10 @@
8.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
8.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
9 <a href="#metadata">WS-Fragment Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_1397">Fragment Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_1399">Fragment Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_1450">Normative References</a><br/>
+ 11.1 <a href="#iddiv2_1_1452">Normative 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="#changelog">Change Log</a><br/>
@@ -659,17 +659,18 @@
returns a
node-set containing a single element node which serializes directly:
</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) <b> <c d="30"> 20 </c> </b></pre></div></div><p>
- In the event that there is more than one node which would
- match the XPath, the implementation MUST select or return the first node
- only. This allows simple implementations to avoid the overhead of
+ In the case of a Put operation, if the XPath expression selects more
+ than one node, the implementation MUST process only the first selected
+ node. This allows simple implementations to avoid the overhead of
checking the remainder of the resource document for a possible match.
</p><p>
Conformant implementations MAY supply additional functions
and capabilities, but MUST adhere to the minimum behavior described above.
</p><p>
The XPath Level 1 language does not support computed values.
- Text and attribute nodes MUST be serialized using the same serialization
- as for the XPath 1.0 language.
+ Text and attribute nodes MUST be serialized in the GetResponse
+ message using the same serialization as for the XPath 1.0 language.
+ This serialization mechanism MUST NOT be used in the PutRequest message.
</p></div><div class="div1">
<h2><a name="XPath10" id="XPath10"/>7 XPath 1.0 Expression Language</h2><p>
The XPath 1.0 expression language uses an XPath to reference specific
@@ -698,10 +699,20 @@
Implementations that support the full XPath 1.0 language MUST
support the XPath Level 1 language.
</p><p>
- Note that the expression MAY evaluate to one of four
+ In the case of a Put operation if the XPath expression selects more
+ than one node, the implementation MUST process only the first selected
+ node. This allows simple implementations to avoid the overhead of
+ checking the remainder of the resource document for a possible match.
+ </p><p>
+ The remainder of this section defines an XML serialization mechanism
+ that MUST be used when constructing a GetResponse message. Since the
+ PutRequest message MUST NOT be used to modify more than one target,
+ these serialization rules MUST NOT be used in a PutRequest message.
+ </p><p>
+ Expressions MUST 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
+ When they appear in a GetResponse message they are serialized
by performing the following conversion and then wrapping the result in
the wsf:Value element:
</p><ul><li><p>Boolean - converted to an xs:boolean</p></li><li><p>string - convert to an xs:string</p></li><li><p>number - convert to an xs:double</p></li></ul><p>
@@ -751,11 +762,7 @@
(02) <b>1</b>
(03) <wsf:TextNode>1</wsf:TextNode>
(04) <wsf:AttributeNode name="x">y</wsf:AttributeNode>
-(05) </wsf:Value></pre></div></div><p>The nodes in the node-set MAY be serialized in any order.</p><p>
- An XPath 1.0 expression MAY evaluate to multiple nodes;
- because of this the XPath 1.0 language MUST NOT be used with a "Put" or
- "Create" operation.
- </p></div><div class="div1">
+(05) </wsf:Value></pre></div></div><p>The nodes in the node-set MAY be serialized in any order.</p></div><div class="div1">
<h2><a name="Faults" id="Faults"/>8 Faults</h2><p>
All fault messages defined in this specification MUST be sent
according to the rules and usage described in
@@ -831,7 +838,7 @@
doing so the endpoint is indicating that the corresponding WS-Fragment
features are supported by that endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1397" id="iddiv2_1_1397"/>9.1 Fragment Assertion</h3><p>
+<h3><a name="iddiv2_1_1399" id="iddiv2_1_1399"/>9.1 Fragment Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Fragment specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -899,7 +906,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1450" id="iddiv2_1_1450"/>11.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_1452" id="iddiv2_1_1452"/>11.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.
@@ -1061,7 +1068,8 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8181">8181</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8257">8257</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=8229">8229</a></td></tr><tr><td> 2010/01/27 </td><td> DD </td><td> Added resolution of issues
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8229">8229</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/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></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.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- wsfrag.xml 29 Jan 2010 04:00:59 -0000 1.48
+++ wsfrag.xml 29 Jan 2010 04:10:58 -0000 1.49
@@ -1199,9 +1199,9 @@
</example>
<p>
- In the event that there is more than one node which would
- match the XPath, the implementation MUST select or return the first node
- only. This allows simple implementations to avoid the overhead of
+ In the case of a Put operation, if the XPath expression selects more
+ than one node, the implementation MUST process only the first selected
+ node. This allows simple implementations to avoid the overhead of
checking the remainder of the resource document for a possible match.
</p>
@@ -1212,8 +1212,9 @@
<p>
The XPath Level 1 language does not support computed values.
- Text and attribute nodes MUST be serialized using the same serialization
- as for the XPath 1.0 language.
+ Text and attribute nodes MUST be serialized in the GetResponse
+ message using the same serialization as for the XPath 1.0 language.
+ This serialization mechanism MUST NOT be used in the PutRequest message.
</p>
</div1>
@@ -1271,12 +1272,26 @@
Implementations that support the full XPath 1.0 language MUST
support the XPath Level 1 language.
</p>
+
+ <p>
+ In the case of a Put operation if the XPath expression selects more
+ than one node, the implementation MUST process only the first selected
+ node. This allows simple implementations to avoid the overhead of
+ checking the remainder of the resource document for a possible match.
+ </p>
+
+ <p>
+ The remainder of this section defines an XML serialization mechanism
+ that MUST be used when constructing a GetResponse message. Since the
+ PutRequest message MUST NOT be used to modify more than one target,
+ these serialization rules MUST NOT be used in a PutRequest message.
+ </p>
<p>
- Note that the expression MAY evaluate to one of four
+ Expressions MUST 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
+ When they appear in a GetResponse message they are serialized
by performing the following conversion and then wrapping the result in
the wsf:Value element:
</p>
@@ -1396,11 +1411,6 @@
<p>The nodes in the node-set MAY be serialized in any order.</p>
- <p>
- An XPath 1.0 expression MAY evaluate to multiple nodes;
- because of this the XPath 1.0 language MUST NOT be used with a "Put" or
- "Create" operation.
- </p>
</div1>
<div1 id="Faults">
@@ -2103,7 +2113,7 @@
</td>
</tr>
<tr>
- <td> 2010/01/27 </td>
+ <td> 2010/01/28 </td>
<td> DD </td>
<td> Added resolution of issues
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8302">8302</loc>,
@@ -2111,6 +2121,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299">8299</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/28 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191">8191</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Friday, 29 January 2010 04:11:02 UTC