W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > September 2009

WWW/2002/ws/ra/edcopies wsfrag.xml,1.13,1.14 wsfrag.html,1.13,1.14

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 23 Sep 2009 17:36:27 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MqVlT-0007RI-A6@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv28492

Modified Files:
	wsfrag.xml wsfrag.html 
Log Message:
proposal


Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- wsfrag.html	15 Sep 2009 19:43:09 -0000	1.13
+++ wsfrag.html	23 Sep 2009 17:36:25 -0000	1.14
@@ -33,7 +33,7 @@
 <h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-fragment">http://www.w3.org/TR/ws-fragment
    </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-fragment-20090317">http://www.w3.org/TR/2009/WD-ws-fragment-20090317</a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
 <h2><a name="abstract" id="abstract"/>Abstract</h2><p>
-    This specification extends the <a href="#WsTransfer">[WS-Transfer]</a>
+    This specification extends the WS-Transfer <a href="#WsTransfer">[WS-Transfer]</a>
     specification to enable clients to retrieve and manipulate parts or
     fragments of a WS-Transfer enabled resource without needing to include 
     the entire XML representation in a message exchange.
@@ -53,8 +53,8 @@
 &nbsp;&nbsp;&nbsp;3.2 <a href="#Put">Put</a><br/>
 &nbsp;&nbsp;&nbsp;3.3 <a href="#Delete">Delete</a><br/>
 &nbsp;&nbsp;&nbsp;3.4 <a href="#Create">Create</a><br/>
-4 <a href="#iddiv1_1_901">Examples</a><br/>
-&nbsp;&nbsp;&nbsp;4.1 <a href="#iddiv2_1_904">Examples</a><br/>
+4 <a href="#iddiv1_1_714">Examples</a><br/>
+&nbsp;&nbsp;&nbsp;4.1 <a href="#iddiv2_1_717">Examples</a><br/>
 5 <a href="#QName">QName Expression Language</a><br/>
 6 <a href="#XPathL1">XPath Level 1 Expression Language</a><br/>
 7 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
@@ -62,9 +62,11 @@
 &nbsp;&nbsp;&nbsp;8.1 <a href="#UnsupportedLanguage">UnsupportedLanguage</a><br/>
 &nbsp;&nbsp;&nbsp;8.2 <a href="#InvalidFragment">InvalidFragment</a><br/>
 &nbsp;&nbsp;&nbsp;8.3 <a href="#InvalidExpression">InvalidExpression</a><br/>
+&nbsp;&nbsp;&nbsp;8.4 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
 9 <a href="#policy">WS-Fragment Policy Assertion(s)</a><br/>
 10 <a href="#acks">Acknowledgements</a><br/>
 11 <a href="#refs">References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_1373">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="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -85,7 +87,7 @@
     The fragment transfer mechanism is defined as an extension to 
     WS-Transfer.  This
     involves defining a WS-Transfer Dialect and corresponding XML elements
-    that go into the SOAP Body of the Get, Put, Delete and Create  
+    that go into the SOAP Body of the Get and Put
     WS-Transfer operations. 
     This fragment transfer mechanism is designed so that it can be used 
     with any number of
@@ -100,14 +102,14 @@
        Provide an extension mechanism to WS-Transfer that allows for
        subsets (parts or fragments) of a resource to be retrieved or modified.
       </p></li><li><p>
-       Provide an extenson framework for defining expression languages.
+       Provide an extension framework for defining expression languages.
       </p></li><li><p>
        Provide a set of expression languages that implementations
        can leverage.
       </p></li></ul></div></div><div class="div1">
 <h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"/>2 Terminology and Notation</h2><div class="div2">
 <h3><a name="terminology" id="terminology"/>2.1 Terminology</h3><dl><dt class="label">Expression</dt><dd><p>
-        A Language specific set of tokens that resolve to a location
+        A Language specific set of tokens that resolves to a location
         in a resource that contains a subset of the resource.
        </p></dd><dt class="label">Fragment</dt><dd><p>
         A subset of a resource.
@@ -123,8 +125,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> wsf </td><td><a href="http://www.w3.org/2009/02/ws-fra">http://www.w3.org/2009/02/ws-fra</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">[SOAP 1.1]</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="#Soap12">[SOAP 1.2]</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">[WSDL 1.1]</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="#XmlSchemaPart1">[XML Schema, Part 1]</a>, <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a></td></tr><tr><td> wst </td><td><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></td><td><a href="#WsTransfer">[WS-Transfer]</a></td></tr></tbody></table><p>
+       </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><tr><td> wst </td><td><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></td><td><a href="#WsTransfer">[WS-Transfer]</a></td></tr></tbody></table><p>
      The working group intends to update the value of the Web Services
      Fragment namespace URI each time a new version of this document is
      published until such time that the document reaches Candidate
@@ -147,7 +149,7 @@
      "SHOULD", "SHOULD NOT", "RECOMMENDED",
      "MAY", and "OPTIONAL" in this document are to be
      interpreted as described in RFC 2119 
-     <a href="#Rfc2119">[RFC 2119]</a>.
+     <a href="#RFC2119">[RFC 2119]</a>.
     </p><p>
      This specification uses the following syntax to define outlines for 
      messages:
@@ -187,7 +189,7 @@
   &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt;
 &lt;/s:Envelope&gt;</pre></div></div><p>
      This specification can be used in terms of XML Information Set (Infoset)
-     <a href="#">[XMLInfoset]</a>, even though the specification uses XML 1.0
+     <a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
      terminology. Valid Infoset for this specification is the one
      serializable in XML 1.0, hence the use of XML 1.0.
     </p></div><div class="div2">
@@ -236,12 +238,6 @@
     The following sections define the expected behavior when the WS-Fragment
     Dialect is used in each of the WS-Transfer operations.
    </p><p>
-    Each Expression language that uses this transfer fragment mechanism 
-    MUST fully define how it behaves for each operation and for the
-    language specific expression constructs it supports.  For example,
-    an <a href="#">[XPath]</a> language will need to explain how a new XML 
-    element is inserted into an existing resource.
-   </p><p>
     WS-Transfer defines what the expected behavior of a resource is 
     with respect to modifications of the resource that might result in
     an invalid state or if the client does not have the authority to
@@ -257,7 +253,7 @@
   http://www.w3.org/2009/02/ws-tra/Get
 
 <b>[Body]</b>
-  &lt;wst:Get Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
+  &lt;wst:Get Dialect="http://www.w3.org/2009/02/ws-fra" ...&gt;
     &lt;wsf:Expression Language="<em>xs:anyURI</em>" ...&gt;
       <em>xs:any</em> *
     &lt;/wsf:Expression&gt;
@@ -266,13 +262,13 @@
      The following describes additional, normative constraints on the outline
      listed above:
     </p><dl><dt class="label"><b>[Body]</b>/wst:Get@Dialect </dt><dd><p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
+        This attribute MUST be set to http://www.w3.org/2009/02/ws-fra.
        </p></dd><dt class="label"><b>[Body]</b>/wst:Get/wsf:Expression </dt><dd><p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language 
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
+        This element identifies which fragment in the resource this 
+        operation applies to. If the value of this element does not 
+        conform to the syntax of the language specified in the Language 
+        attribute, or is semantically invalid, a wsf:InvalidExpression 
+        fault MUST be generated.
        </p></dd><dt class="label"><b>[Body]</b>/wst:Get/wsf:Expression@Language </dt><dd><p>
         This URI indicates which expression language will be
         used to identify the subset of the resource this operation applies
@@ -311,7 +307,7 @@
   http://www.w3.org/2009/02/ws-tra/Put
 
 <b>[Body]</b>
-  &lt;wst:Put Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
+  &lt;wst:Put Dialect="http://www.w3.org/2009/02/ws-fra" ...&gt;
     &lt;wsf:Fragment ...&gt;
       &lt;wsf:Expression Language="<em>xs:anyURI</em>" Mode="<em>xs:anyURI</em>"? ...&gt;
         <em>xs:any</em> *
@@ -325,45 +321,41 @@
      The following describes additional, normative constraints on the outline
      listed above:
     </p><dl><dt class="label"><b>[Body]</b>/wst:Put@Dialect </dt><dd><p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
+        This attribute MUST be set to http://www.w3.org/2009/02/ws-fra.
        </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment </dt><dd><p>
         This element contains an expression that identifies the location of
         a fragment in the resource and a value for the fragment. If the
         contents of this element are invalid a wsf:InvalidFragment
         fault MUST be generated.
        </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression </dt><dd><p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
+        This element identifies which fragment in the resource this operation 
+        applies to. If the value of this element does not conform to the 
+        syntax of the language specified in the Language attribute, or is 
+        semantically invalid, a wsf:InvalidExpression fault MUST be generated.
        </p><p>
         This element identifies the fragment in the resource as it appears
-        after successful processing the Put request.
+        after successfully processing the Put request.
        </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Language </dt><dd><p>
         This URI indicates which expression language will be 
         used to identify the subset of the resource this operation applies
-        to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it 
+        to. A resource MUST generate a wsf:UnsupportedLanguage fault if it 
         does not support the specified Language.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode </dt><dd><p><b>OPTION 1:</b>
-        This OPTIONAL URI indicates what action should be taken in the event 
-        that there is data already present at the specified location within 
-        the resource. The implied value for this attribute is 
-        "http://www.w3.org/2009/02/ws-frag/Modes/Replace". This attribute will 
-        have no effect on the processing of the message if the Expression 
-        refers to non-existing data.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-frag/Modes/Replace" </dt><dd><p><b>OPTION 1:</b>
+       </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode </dt><dd><p>
+        This OPTIONAL attribute indicates the type of update to be 
+        performed on this fragment.
+        The implied value for this attribute is 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Replace". 
+        A resource MUST generate a wsf:UnsupportedMode fault if the specified 
+        Mode is not supported.
+       </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-fra/Modes/Replace" </dt><dd><p>
         When the Mode attribute is set to a value of 
-        "http://www.w3.org/2009/02/ws-frag/Modes/Replace" the resource 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Replace" the resource 
         representation specified within the Value element MUST replace the 
         entire resource representation referenced by the children of the 
         Expression element, if it exists.
-       </p><p>
-        Note: to delete the portion of the resource referenced by this 
-        fragment the Value element MUST be absent from the message.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-frag/Modes/Insert" </dt><dd><p><b>OPTION 1:</b>
+       </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-fra/Modes/Insert" </dt><dd><p>
         When the Mode attribute is set to a value of 
-        "http://www.w3.org/2009/02/ws-frag/Modes/Insert" the resource 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Insert" the resource 
         representation specified within the Value element MUST be added to 
         the resource representation. If the expression targets a repeated 
         element (maxOccurs &gt; 1), the fragment MUST be added at the end. If 
@@ -372,33 +364,26 @@
         wst:InvalidRepresentation fault. If the expression targets an 
         existing item of a repeated element, the fragment MUST be added 
         before the existing item. 
+       </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-fra/Modes/Remove" </dt><dd><p>
+        When the Mode attribute is set to a value of 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Remove" the resource 
+        representation referenced by the children of the Expression element
+        MUST be deleted from the resource representation. 
+       </p><p>
+        Note: the Value element MUST NOT be present if this attribute
+        has a value of "http://www.w3.org/2009/02/ws-fra/Modes/Remove".
        </p></dd><dt class="label"><b>[Body]</b>/wst:Put/wsf:Fragment/wsf:Value </dt><dd><p>
         This OPTIONAL element contains the fragment resource representation
         corresponding to the
         subset of the resource identified by the wsf:Expression element.
-       </p><p><b>OPTION 1:</b>
-        The absence of this element is used to indicate that the portion 
-        of the resource referenced by this Fragment is to be deleted. It 
-        is important to note that there is a difference between a missing 
-        Value element and an empty Value element (e.g. &lt;Value/&gt; ).  An 
-        empty Value element is used in cases where an empty value set is 
-        needed - for example, a missing Value element can be used to delete 
-        an attribute, while an empty Value element might be used to set 
-        the attribute to an empty string (i.e. "").
-       </p></dd></dl><p><b>OPTION 2:</b>
-     This operation MUST be performed by removing any data that corresponds
-     to the Expression element of the request and inserting the specified
-     Fragment data in its place.
-     If the Expression identifies non-existent data
-     then this operation will not have any impact on the resource.
-     In other words, to insert new information into a resource the
-     wst:Create operation is to be used.
-    </p><p>
-        Note: do we really want this?  Should the client really be forced
-        to know whether or not there's data there just to add something?
-        What if, instead, we just allowed it to replace the existing
-        data (if any)?
        </p><p>
+        This element MUST NOT be present if the Mode attribute has a value 
+        of "http://www.w3.org/2009/02/ws-fra/Modes/Remove". This element 
+        MUST be present if the Mode attribute has a value of either
+        "http://www.w3.org/2009/02/ws-fra/Modes/Replace" or 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Insert". When present, 
+        this element can either be empty or non-empty.
+       </p></dd></dl><p>
      If the resource accepts a Put request, it MUST reply with a response of
      the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
@@ -410,138 +395,16 @@
   &lt;/wst:PutResponse&gt;</pre></div></div><p>
      There are no additional constraints beyond what WS-Transfer defines.
     </p></div><div class="div2">
-<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p><b>OPTION 1:</b>
-     This specification makes no modification to the Delete
-     operation.
-    </p><p><b>OPTION 2:</b>
-     To delete a subset of a resource a client MUST specify the WS-Fragment
-     URI in the wst:Delete request.
-    </p><p><b>OPTION 2:</b>
-     The remaining part of this section is all for OPTION 2.
-    </p><p>
-     The Delete request message MUST be of the following form:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
-  http://www.w3.org/2009/02/ws-tra/Delete
-
-<b>[Body]</b>
-  &lt;wst:Delete Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
-    &lt;wsf:Expression Language="<em>xs:anyURI</em>" ...&gt;
-      <em>xs:any</em> *
-    &lt;/wsf:Expression&gt;
-    <em>xs:any</em> *
-  &lt;/wst:Delete&gt;</pre></div></div><p>
-     The following describes additional, normative constraints on the outline
-     listed above:
-    </p><dl><dt class="label"><b>[Body]</b>/wst:Delete@Dialect </dt><dd><p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Delete/wsf:Expression </dt><dd><p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Delete/wsf:Expression@Language </dt><dd><p>
-        This URI indicates which expression language will be
-        used to identify the subset of the resource this operation applies
-        to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it
-        does not support the specified Language.
-       </p></dd></dl><p>
-     This operation MUST be performed by removing any data that corresponds
-     to the Expression element of the request.
-     If the Expression identifies non-existent data
-     then this operation will not have any impact on the resource and
-     no fault is generated.
-    </p><p>
-     If the resource accepts a Delete request, it MUST reply with a response of
-     the following form:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
-  http://www.w3.org/2009/02/ws-tra/DeleteResponse
-
-<b>[Body]</b>
-  &lt;wst:DeleteResponse ...&gt;
-    <em>xs:any</em> *
-  &lt;/wst:DeleteResponse&gt;</pre></div></div><p>
-     There are no additional constraints beyond what WS-Transfer defines.
+<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p>
+     This specification does not extend the Delete operation defined in
+     WS-Transfer.
     </p></div><div class="div2">
-<h3><a name="Create" id="Create"/>3.4 Create</h3><p><b>OPTION 1:</b>
-     The wst:Create operation can be used to create a new resource. This 
-     specification extends the wst:Create request by allowing a client to 
-     specify just a portion of the new resource's initial representation.
-    </p><p><b>OPTION 2:</b>
-     To insert data into an existing resource a client MUST specify the
-     WS-Fragment URI in the wst:Delete request.
-    </p><p>
-     The Create request message MUST be of the following form:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
-  http://www.w3.org/2009/02/ws-tra/Create
-
-<b>[Body]</b>
-  &lt;wst:Create Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
-    &lt;wsf:Fragment ...&gt;
-      &lt;wsf:Expression Language="<em>xs:anyURI</em>" ...&gt;
-        <em>xs:any</em> *
-      &lt;/wsf:Expression&gt; 
-      &lt;wsf:Value ...&gt;
-        <em>xs:any</em> *
-      &lt;/wsf:Value&gt; 
-    &lt;/wsf:Fragment&gt;
-    <em>xs:any</em> *
-  &lt;/wst:Create&gt;</pre></div></div><p>
-     The following describes additional, normative constraints on the outline
-     listed above:
-    </p><dl><dt class="label"><b>[Body]</b>/wst:Create@Dialect </dt><dd><p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Create@Fragment </dt><dd><p>
-        This element contains an expression that identifies the location 
-        of a fragment in  the resource and a value for the fragment. If 
-        the contents of this element are invalid a wsf:InvalidFragment 
-        fault MUST be generated.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Create/wsf:Fragment/wsf:Expression </dt><dd><p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
-       </p><p>
-        This element identifies the fragment in the resource as it
-        appears after successful processing of the Create request.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Create/wsf:Fragment/wsf:Expression@Language </dt><dd><p>
-        This URI indicates which expression language will be
-        used to identify the subset of the resource this operation applies
-        to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it
-        does not support the specified Language.
-       </p></dd><dt class="label"><b>[Body]</b>/wst:Create/wsf:Fragment/wsf:Value </dt><dd><p>
-        This element contains the fragment resource representation 
-        corresponding to the
-        subset of the resource indentified by the wsf:Expression element.
-       </p></dd></dl><p><b>OPTION 1:</b>
-     This operation MUST be performed by creating a new resource using 
-     the specified subset of the resource. Other values within the resource 
-     will use the appropriate default values. Note: this operation has the 
-     same net effect as creating a new resource that is populated with 
-     default values, followed by a wst.Put request with this specified 
-     Fragment.
-    </p><p><b>OPTION 2:</b>
-     This operation MUST be performed by inserting new data within the
-     Fragment element into the resource as specified by the Expression
-     element. If data is already present and would result in the resource
-     being left in an invalid state then a wst:InvalidRepresentation
-     fault MUST be generated.
-    </p><p>
-     If the resource accepts a Create request, it MUST reply with a response of
-     the following form:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
-  http://www.w3.org/2009/02/ws-tra/CreateResponse
-
-<b>[Body]</b>
-  &lt;wst:CreateResponse ...&gt;
-    &lt;wst:ResourceCreated&gt; <em>endpoint-reference</em> &lt;/wst:ResourceCreated&gt;
-    <em>xs:any</em> *
-  &lt;/wst:CreateResponse&gt;</pre></div></div><p>
-     There are no additional constraints beyond what WS-Transfer defines.
+<h3><a name="Create" id="Create"/>3.4 Create</h3><p>
+     This specification does not extend the Create operation defined in
+     WS-Transfer.
     </p></div></div><div class="div1">
-<h2><a name="iddiv1_1_901" id="iddiv1_1_901"/>4 Examples</h2><div class="div2">
-<h3><a name="iddiv2_1_904" id="iddiv2_1_904"/>4.1 Examples</h3><p>
+<h2><a name="iddiv1_1_714" id="iddiv1_1_714"/>4 Examples</h2><div class="div2">
+<h3><a name="iddiv2_1_717" id="iddiv2_1_717"/>4.1 Examples</h3><p>
      In the following examples, and Expression Language definitions,
      the following representation of a resource is used for
      informational purposes:
@@ -582,7 +445,7 @@
   &lt;/s:Header&gt;
   &lt;s:Body&gt;
     &lt;wst:Get&gt;
-      &lt;wsf:Expression Language=".../ws-frag/QName"&gt;
+      &lt;wsf:Expression Language="http://www.w3.org/2009/02/ws-fra/QName"&gt;
         ab:contact
       &lt;/wsf:Expression&gt;
     &lt;/wst:Get&gt;
@@ -634,7 +497,8 @@
     the resource representation.  The expression MUST evaluate to zero or 
     more elements, each including the element name, any attributes 
     and its entire content.
-    This language can be implemented as a precise subset of the XPath language.
+    This language can be implemented as a precise subset of the 
+    XPath 1.0 <a href="#XPath1">[XPath1.0]</a> language.
    </p><p>
     The QName language MUST be indicated by using the URI:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-fra/QName">http://www.w3.org/2009/02/ws-fra/QName</a></pre></div></div></div><div class="div1">
@@ -650,7 +514,8 @@
     their resource representation.
    </p><p>
     XPath Level 1 is a subset of the abbreviated relative syntax
-    of XPath 1.0, and is used to identify or select a node (element, attribute
+    of XPath 1.0 <a href="#XPath1">[XPath1.0]</a>, and is used to identify or select 
+    a node (element, attribute
     or value) within a resource
     representation or fragment. It is identified by the following URI:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/02/ws-fra/XPath-Level-1</pre></div></div><p>
@@ -876,7 +741,7 @@
 (05) &lt;/wsf:Value&gt;</pre></div></div><p>The nodes in the node-set MAY be serialized in any order.</p><p>
     The WS-Fragment global element definition wsf:NodeSet can also be
     used as the wrapper element when serializing these node-sets outside of
-    a WS-Fragmen result.
+    a WS-Fragment result.
    </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
@@ -932,7 +797,7 @@
 &lt;/s11:Envelope&gt;</pre></div></div><div class="div2">
 <h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>8.1 UnsupportedLanguage</h3><p>
      This fault is generated when a service detects an unknown or
-     unsupprted Language 
+     unsupported Language 
      URI in a request message. 
     </p><a name="Table3" id="Table3"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnsupportedLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
         The specified Language URI is not supported.
@@ -940,15 +805,23 @@
 <h3><a name="InvalidFragment" id="InvalidFragment"/>8.2 InvalidFragment</h3><p>
      This fault is generated when a service determines that the fragment 
      (contents of the wsf:Fragment element) specified in a request is invalid. 
-    </p><a name="Table3" id="Table3"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidFragment</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
+    </p><a name="Table4" id="Table4"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidFragment</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
         The specific fragment is invalid.
        </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The invalid fragment.</em></td></tr></tbody></table></div><div class="div2">
 <h3><a name="InvalidExpression" id="InvalidExpression"/>8.3 InvalidExpression</h3><p>
-     This fault is generated when a service determines that the language
-     expression specified in a request is invalid.
-    </p><a name="Table3" id="Table3"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidExpression</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
+     This fault is generated when a service determines that the Language
+     expression specified in a request does not conform to the syntax
+     of the language specified in the Language attribute or is semantically
+     invalid.
+    </p><a name="Table5" id="Table5"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidExpression</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
         The specified Language expression is invalid.
-       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The invalid language expression.</em></td></tr></tbody></table></div></div><div class="div1">
+       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The invalid language expression.</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="UnsupportedMode" id="UnsupportedMode"/>8.4 UnsupportedMode</h3><p>
+     This fault is generated when a service detects a Mode in a Put
+     request that is not supported.
+    </p><a name="Table6" id="Table6"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnsupportedMode</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
+        The specified mode is not supported.
+       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Mode.</em></td></tr></tbody></table></div></div><div class="div1">
 <h2><a name="policy" id="policy"/>9 WS-Fragment Policy Assertion(s)</h2><p>
     An endpoint MAY indicate that it supports WS-Fragment, or its features,
     by including the WS-Fragment Policy assertion(s) within its WSDL. By
@@ -977,64 +850,79 @@
      Sumeet Vij (Software AG),
      Vikas Varma (Software AG),
      Wu Chou (Avaya Communications),
-     Yves Lafon (W3C)
+     Yves Lafon (W3C).
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"/>11 References</h2><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, Harvard University, March 1997.
-      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="RFC3986" id="RFC3986"/>RFC 3986</dt><dd><a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>
-      Uniform Resource Identifier (URI): Generic Syntax
-     </cite></a>
-     , T. Berners-Lee, W3C/MIT, January 2005.
-      (See http://www.ietf.org/rfc/rfc3986.txt.)</dd><dt class="label"><a name="Soap11" id="Soap11"/>SOAP 1.1</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
-      Simple Object Access Protocol (SOAP) 1.1
-     </cite></a>
-     , D. Box, et al, May 2000.
-      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="Soap12" id="Soap12"/>SOAP 1.2</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
-      SOAP Version 1.2 Part 1: Messaging Framework
-     </cite></a>
-     , M. Gudgin, et al, June 2003.
-      (See http://www.w3.org/TR/soap12-part1/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/2005/08/addressing/"><cite>
-      W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
-     </cite></a>
-     , May 2006.
-      (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="WSABinding" id="WSABinding"/>WS-Addressing 1.0 SOAP Binding</dt><dd><a href="http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509"><cite>
-      W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
-     </cite></a>
-     , May 2006.
-      (See http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509.)</dd><dt class="label"><a name="WsPolicy" id="WsPolicy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
-      W3C Recommendation, "Web Services Policy 1.5 - Framework"
-     </cite></a>
-     , September 2007.
-      (See http://www.w3.org/TR/ws-policy/.)</dd><dt class="label"><a name="WsTransfer" id="WsTransfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/2009/02/ws-tra"><cite>
-      W3C Working Group Draft, "Web Services Transfer"
-     </cite></a>
-     , July 2009.
-      (See http://www.w3.org/2009/02/ws-tra.)</dd><dt class="label"><a name="Wsdl11" id="Wsdl11"/>WSDL 1.1</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
-      Web Services Description Language (WSDL) 1.1
-     </cite></a>
-     , E. Christensen, et al, March 2001.
-      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoSet" id="XMLInfoSet"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
-      J. Cowan, et al, "XML Information Set"
-     </cite></a>
-     , February 2004.
-      (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XmlSchemaPart1" id="XmlSchemaPart1"/>XML Schema, Part 1</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
-      XML Schema Part 1: Structures
-     </cite></a>
-     , H. Thompson, et al, October 2004.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XmlSchemaPart2" id="XmlSchemaPart2"/>XML Schema, Part 2</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
-      XML Schema Part 2: Datatypes
-     </cite></a>
-     , James Clark, et al, November 1999.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="xpath" id="xpath"/>XPath 1.0</dt><dd><a href="http://www.w3.org/TR/xpath"><cite>
-      XML Path Language (XPath) Version 1.0
-     </cite></a>
-     , James Clark, et al, November 1999.
-      (See http://www.w3.org/TR/xpath.)</dd></dl></div></div><div class="back"><div class="div1">
+<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
+<h3><a name="iddiv2_1_1373" id="iddiv2_1_1373"/>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.
+       Internet Engineering Task Force, March 1997.
+      Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="RFC3986" id="RFC3986"/>RFC 3986</dt><dd><a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>
+        Uniform Resource Identifier (URI): Generic Syntax
+       </cite></a>
+       , T. Berners-Lee, R. Fields and L. Masinter, Authors.
+       Network Working Group, January 2005.
+      Available at <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+        W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
+       </cite></a>
+       , D. Box, et al, Editors.
+       World Wide Web Consortium (W3C), 8 May 2000.
+      Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+        W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
+       </cite></a>
+       , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
+        Editors.
+       World Wide Web Consortium (W3C), 27 April 2007.
+      Available at <a href="http://www.w3.org/TR/soap12-part1/">http://www.w3.org/TR/soap12-part1/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/TR/ws-addr-core"><cite>
+        W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+       </cite></a>
+       , M. Gudgin, M. Hadley, T. Rogers, Editors.
+       World Wide Web Consortium (W3C), 9 May 2006.
+      Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="WSABinding" id="WSABinding"/>WS-Addressing 1.0 SOAP Binding</dt><dd><a href="http://www.w3.org/TR/ws-addr-soap"><cite>
+        W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
+       </cite></a>
+       , M. Gudgin, M. Hadley, T. Rogers, Editors.
+       World Wide Web Consortium (W3C), 9 May 2006.
+      Available at <a href="http://www.w3.org/TR/ws-addr-soap">http://www.w3.org/TR/ws-addr-soap</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
+        W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
+       </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="WsTransfer" id="WsTransfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/TR/ws-transfer"><cite>
+       W3C Working Group Draft, "Web Services Transfer (WS-Transfer)1.1"
+      </cite></a>
+      , D. Davis, et al., Editors.
+      World Wide Web Consortium (W3C), 15 September 2009.
+      Available at <a href="http://www.w3.org/TR/ws-transfer">http://www.w3.org/TR/ws-transfer</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.
+       World Wide Web Consortium (W3C), 15 March 2001
+      Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
+        W3C Recommendation, "XML Information Set (Second Edition)"
+       </cite></a>
+       , J. Cowan, R. Tobin, Editors.
+       World Wide Web Consortium (W3C), 4 February 2004.
+      Available at <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd><a href="http://www.w3.org/TR/xmlschema-1/"><cite>
+        W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
+       </cite></a>
+       , H. Thompson, et al., Editors.
+       World Wide Web Consortium (W3C), 28 October 2004.
+      Available at <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd><a href="http://www.w3.org/TR/xmlschema-2/"><cite>
+        W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
+       </cite></a>
+       , 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><dt class="label"><a name="XPath1" id="XPath1"/>XPath1.0</dt><dd><a href="http://www.w3.org/TR/xpath"><cite>
+        W3C Recommendation, "XML Path Language (XPath) Version 1.0"
+       </cite></a>
+       , J. Clark, S. DeRose, Editors.
+       World Wide Web Consortium (W3C), 16 November 1999.
+      Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
 <h2><a name="Appendix_I__E2_80_93_XSD" id="Appendix_I__E2_80_93_XSD"/>A XML Schema</h2><p>
-    A normative copy of the XML Schema <a href="#XmlSchemaPart1">[XML Schema, Part 1]</a>,
-    <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a> description for this specification can be
+    A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
+    <a href="#XMLSchema2">[XMLSchema - Part 2]</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-fra/fragment.xsd">http://www.w3.org/2009/02/ws-fra/fragment.xsd</a></pre></div></div><p>
     A non-normative copy of the XML schema is listed below for convenience.
@@ -1048,7 +936,7 @@
  
 &lt;/xs:schema&gt;  </pre></div></div></div><div class="div1">
 <h2><a name="Appendix_II__E2_80_93_WSDL" id="Appendix_II__E2_80_93_WSDL"/>B WSDL</h2><p>
-    A normative copy of the WSDL <a href="#Wsdl11">[WSDL 1.1]</a> description
+    A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</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-fra/fragment.wsdl">http://www.w3.org/2009/02/ws-fra/fragment.wsdl</a></pre></div></div><p>
     A non-normative copy of the WSDL description is listed below for
@@ -1069,20 +957,6 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr></tbody></table></div><div class="div1">
 <h2><a name="Questions" id="Questions"/>D Open Questions and Actions</h2><p>
-    Ram - If the expression resolves to a non-existent node should it fault
-      or do nothing?
-   </p><p>
-    Ram - should we allow for the creation with default value? This is, 
-      allow 0 or 1 value elements on the Create.
-   </p><p>
-    Ram - add a NonExistentNode fault.
-   </p><p>
-    Ram - add a general fault to indicate that a fragment message is invalid.
-   </p><p>
-    Dug - on put - Should the client really be forced to know whether or not 
-    there's data there just to add something? What if, instead, we just 
-    allowed it to replace the existing data (if any)? 
-   </p><p>
     Ram - should we make the new bits <b>bold</b> so that people
     can see what's new from base Transfer?
    </p><p> Ram - update the wsdl/xsd </p><p> Ram - add a generic wsf:FragmentOperationFailed fault? </p></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.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- wsfrag.xml	15 Sep 2009 19:43:09 -0000	1.13
+++ wsfrag.xml	23 Sep 2009 17:36:25 -0000	1.14
@@ -70,7 +70,7 @@
 
   <abstract>
    <p>
-    This specification extends the <bibref ref="WsTransfer"/>
+    This specification extends the WS-Transfer <bibref ref="WsTransfer"/>
     specification to enable clients to retrieve and manipulate parts or
     fragments of a WS-Transfer enabled resource without needing to include 
     the entire XML representation in a message exchange.
@@ -107,7 +107,7 @@
     The fragment transfer mechanism is defined as an extension to 
     WS-Transfer.  This
     involves defining a WS-Transfer Dialect and corresponding XML elements
-    that go into the SOAP Body of the Get, Put, Delete and Create  
+    that go into the SOAP Body of the Get and Put
     WS-Transfer operations. 
     This fragment transfer mechanism is designed so that it can be used 
     with any number of
@@ -134,7 +134,7 @@
 
      <item>
       <p>
-       Provide an extenson framework for defining expression languages.
+       Provide an extension framework for defining expression languages.
       </p>
      </item>
 
@@ -158,7 +158,7 @@
       <label>Expression</label>
       <def>
        <p>
-        A Language specific set of tokens that resolve to a location
+        A Language specific set of tokens that resolves to a location
         in a resource that contains a subset of the resource.
        </p>
       </def>
@@ -223,7 +223,7 @@
         <loc href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</loc>
        </td>
        <td>
-        <bibref ref="Soap11"/>
+        <bibref ref="SOAP11"/>
        </td>
       </tr>
       <tr>
@@ -232,7 +232,7 @@
         <loc href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</loc>
        </td>
        <td>
-        <bibref ref="Soap12"/>
+        <bibref ref="SOAP121"/>
        </td>
       </tr>
       <tr>
@@ -250,7 +250,7 @@
         <loc href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</loc>
        </td>
        <td>
-        <bibref ref="Wsdl11"/>
+        <bibref ref="WSDL11"/>
        </td>
       </tr>
       <tr>
@@ -259,7 +259,7 @@
         <loc href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</loc>
        </td>
        <td> 
-        XML Schema <bibref ref="XmlSchemaPart1"/>, <bibref ref="XmlSchemaPart2"/>
+        XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
        </td>
       </tr>
       <tr>
@@ -301,7 +301,7 @@
      "SHOULD", "SHOULD NOT", "RECOMMENDED",
      "MAY", and "OPTIONAL" in this document are to be
      interpreted as described in RFC 2119 
-     <bibref ref="Rfc2119"/>.
+     <bibref ref="RFC2119"/>.
     </p>
     <p>
      This specification uses the following syntax to define outlines for 
@@ -488,14 +488,6 @@
    </p>
 
    <p>
-    Each Expression language that uses this transfer fragment mechanism 
-    MUST fully define how it behaves for each operation and for the
-    language specific expression constructs it supports.  For example,
-    an <bibref ref="XPath"/> language will need to explain how a new XML 
-    element is inserted into an existing resource.
-   </p>
-
-   <p>
     WS-Transfer defines what the expected behavior of a resource is 
     with respect to modifications of the resource that might result in
     an invalid state or if the client does not have the authority to
@@ -517,7 +509,7 @@
   http://www.w3.org/2009/02/ws-tra/Get
 
 <kw>[Body]</kw>
-  &lt;wst:Get Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
+  &lt;wst:Get Dialect="http://www.w3.org/2009/02/ws-fra" ...&gt;
     &lt;wsf:Expression Language="<emph>xs:anyURI</emph>" ...&gt;
       <emph>xs:any</emph> *
     &lt;/wsf:Expression&gt;
@@ -533,7 +525,7 @@
       <label> <kw>[Body]</kw>/wst:Get@Dialect </label>
       <def>
        <p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
+        This attribute MUST be set to http://www.w3.org/2009/02/ws-fra.
        </p>
       </def>
      </gitem>
@@ -542,11 +534,11 @@
       <label> <kw>[Body]</kw>/wst:Get/wsf:Expression </label>
       <def>
        <p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language 
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
+        This element identifies which fragment in the resource this 
+        operation applies to. If the value of this element does not 
+        conform to the syntax of the language specified in the Language 
+        attribute, or is semantically invalid, a wsf:InvalidExpression 
+        fault MUST be generated.
        </p>
       </def>
      </gitem>
@@ -620,7 +612,7 @@
   http://www.w3.org/2009/02/ws-tra/Put
 
 <kw>[Body]</kw>
-  &lt;wst:Put Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
+  &lt;wst:Put Dialect="http://www.w3.org/2009/02/ws-fra" ...&gt;
     &lt;wsf:Fragment ...&gt;
       &lt;wsf:Expression Language="<emph>xs:anyURI</emph>" Mode="<emph>xs:anyURI</emph>"? ...&gt;
         <emph>xs:any</emph> *
@@ -641,7 +633,7 @@
       <label> <kw>[Body]</kw>/wst:Put@Dialect </label>
       <def>
        <p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
+        This attribute MUST be set to http://www.w3.org/2009/02/ws-fra.
        </p>
       </def>
      </gitem>
@@ -662,16 +654,15 @@
       <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression </label>
       <def>
        <p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
+        This element identifies which fragment in the resource this operation 
+        applies to. If the value of this element does not conform to the 
+        syntax of the language specified in the Language attribute, or is 
+        semantically invalid, a wsf:InvalidExpression fault MUST be generated.
        </p>
 
        <p>
         This element identifies the fragment in the resource as it appears
-        after successful processing the Put request.
+        after successfully processing the Put request.
        </p>
       </def>
      </gitem>
@@ -682,7 +673,7 @@
        <p>
         This URI indicates which expression language will be 
         used to identify the subset of the resource this operation applies
-        to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it 
+        to. A resource MUST generate a wsf:UnsupportedLanguage fault if it 
         does not support the specified Language.
        </p>
       </def>
@@ -692,42 +683,35 @@
       <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression@Mode </label>
       <def>
        <p>
-        <kw>OPTION 1:</kw>
-        This OPTIONAL URI indicates what action should be taken in the event 
-        that there is data already present at the specified location within 
-        the resource. The implied value for this attribute is 
-        "http://www.w3.org/2009/02/ws-frag/Modes/Replace". This attribute will 
-        have no effect on the processing of the message if the Expression 
-        refers to non-existing data.
+        This OPTIONAL attribute indicates the type of update to be 
+        performed on this fragment.
+        The implied value for this attribute is 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Replace". 
+        A resource MUST generate a wsf:UnsupportedMode fault if the specified 
+        Mode is not supported.
        </p>
       </def>
      </gitem>
 
      <gitem>
-      <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-frag/Modes/Replace" </label>
+      <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-fra/Modes/Replace" </label>
       <def>
        <p>
-        <kw>OPTION 1:</kw>
         When the Mode attribute is set to a value of 
-        "http://www.w3.org/2009/02/ws-frag/Modes/Replace" the resource 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Replace" the resource 
         representation specified within the Value element MUST replace the 
         entire resource representation referenced by the children of the 
         Expression element, if it exists.
        </p>
-       <p>
-        Note: to delete the portion of the resource referenced by this 
-        fragment the Value element MUST be absent from the message.
-       </p>
       </def>
      </gitem>
 
      <gitem>
-      <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-frag/Modes/Insert" </label>
+      <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-fra/Modes/Insert" </label>
       <def>
        <p>
-        <kw>OPTION 1:</kw>
         When the Mode attribute is set to a value of 
-        "http://www.w3.org/2009/02/ws-frag/Modes/Insert" the resource 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Insert" the resource 
         representation specified within the Value element MUST be added to 
         the resource representation. If the expression targets a repeated 
         element (maxOccurs > 1), the fragment MUST be added at the end. If 
@@ -741,6 +725,22 @@
      </gitem>
 
      <gitem>
+      <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Expression@Mode="http://www.w3.org/2009/02/ws-fra/Modes/Remove" </label>
+      <def>
+       <p>
+        When the Mode attribute is set to a value of 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Remove" the resource 
+        representation referenced by the children of the Expression element
+        MUST be deleted from the resource representation. 
+       </p>
+       <p>
+        Note: the Value element MUST NOT be present if this attribute
+        has a value of "http://www.w3.org/2009/02/ws-fra/Modes/Remove".
+       </p>
+      </def>
+     </gitem>
+
+     <gitem>
       <label> <kw>[Body]</kw>/wst:Put/wsf:Fragment/wsf:Value </label>
       <def>
        <p>
@@ -749,39 +749,18 @@
         subset of the resource identified by the wsf:Expression element.
        </p>
        <p>
-        <kw>OPTION 1:</kw>
-        The absence of this element is used to indicate that the portion 
-        of the resource referenced by this Fragment is to be deleted. It 
-        is important to note that there is a difference between a missing 
-        Value element and an empty Value element (e.g. &lt;Value/> ).  An 
-        empty Value element is used in cases where an empty value set is 
-        needed - for example, a missing Value element can be used to delete 
-        an attribute, while an empty Value element might be used to set 
-        the attribute to an empty string (i.e. "").
+        This element MUST NOT be present if the Mode attribute has a value 
+        of "http://www.w3.org/2009/02/ws-fra/Modes/Remove". This element 
+        MUST be present if the Mode attribute has a value of either
+        "http://www.w3.org/2009/02/ws-fra/Modes/Replace" or 
+        "http://www.w3.org/2009/02/ws-fra/Modes/Insert". When present, 
+        this element can either be empty or non-empty.
        </p>
       </def>
      </gitem>
     </glist>
 
     <p>
-     <kw>OPTION 2:</kw>
-     This operation MUST be performed by removing any data that corresponds
-     to the Expression element of the request and inserting the specified
-     Fragment data in its place.
-     If the Expression identifies non-existent data
-     then this operation will not have any impact on the resource.
-     In other words, to insert new information into a resource the
-     wst:Create operation is to be used.
-    </p>
-
-       <p>
-        Note: do we really want this?  Should the client really be forced
-        to know whether or not there's data there just to add something?
-        What if, instead, we just allowed it to replace the existing
-        data (if any)?
-       </p>
-
-    <p>
      If the resource accepts a Put request, it MUST reply with a response of
      the following form:
     </p>
@@ -803,240 +782,19 @@
    <div2 id="Delete">
     <head>Delete</head>
     <p>
-     <kw>OPTION 1:</kw>
-     This specification makes no modification to the Delete
-     operation.
-    </p>
-
-    <p>
-     <kw>OPTION 2:</kw>
-     To delete a subset of a resource a client MUST specify the WS-Fragment
-     URI in the wst:Delete request.
-    </p>
-    <p>
-     <kw>OPTION 2:</kw>
-     The remaining part of this section is all for OPTION 2.
-    </p>
-    <p>
-     The Delete request message MUST be of the following form:
-    </p>
-    <example>
-     <eg><kw>[Action]</kw>
-  http://www.w3.org/2009/02/ws-tra/Delete
-
-<kw>[Body]</kw>
-  &lt;wst:Delete Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
-    &lt;wsf:Expression Language="<emph>xs:anyURI</emph>" ...&gt;
-      <emph>xs:any</emph> *
-    &lt;/wsf:Expression&gt;
-    <emph>xs:any</emph> *
-  &lt;/wst:Delete&gt;</eg>
-    </example>
-    <p>
-     The following describes additional, normative constraints on the outline
-     listed above:
-    </p>
-    <glist>
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Delete@Dialect </label>
-      <def>
-       <p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
-       </p>
-      </def>
-     </gitem>
-
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Delete/wsf:Expression </label>
-      <def>
-       <p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
-       </p>
-      </def>
-     </gitem>
-
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Delete/wsf:Expression@Language </label>
-      <def>
-       <p>
-        This URI indicates which expression language will be
-        used to identify the subset of the resource this operation applies
-        to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it
-        does not support the specified Language.
-       </p>
-      </def>
-     </gitem>
-    </glist>
-
-    <p>
-     This operation MUST be performed by removing any data that corresponds
-     to the Expression element of the request.
-     If the Expression identifies non-existent data
-     then this operation will not have any impact on the resource and
-     no fault is generated.
-    </p>
-
-    <p>
-     If the resource accepts a Delete request, it MUST reply with a response of
-     the following form:
+     This specification does not extend the Delete operation defined in
+     WS-Transfer.
     </p>
-    <example>
-     <eg><kw>[Action]</kw>
-  http://www.w3.org/2009/02/ws-tra/DeleteResponse
-
-<kw>[Body]</kw>
-  &lt;wst:DeleteResponse ...&gt;
-    <emph>xs:any</emph> *
-  &lt;/wst:DeleteResponse&gt;</eg>
-    </example>
 
-    <p>
-     There are no additional constraints beyond what WS-Transfer defines.
-    </p>
    </div2>
 
    <div2 id="Create">
     <head>Create</head>
     <p>
-     <kw>OPTION 1:</kw>
-     The wst:Create operation can be used to create a new resource. This 
-     specification extends the wst:Create request by allowing a client to 
-     specify just a portion of the new resource's initial representation.
-    </p>
-
-    <p>
-     <kw>OPTION 2:</kw>
-     To insert data into an existing resource a client MUST specify the
-     WS-Fragment URI in the wst:Delete request.
-    </p>
-    <p>
-     The Create request message MUST be of the following form:
-    </p>
-    <example>
-     <eg><kw>[Action]</kw>
-  http://www.w3.org/2009/02/ws-tra/Create
-
-<kw>[Body]</kw>
-  &lt;wst:Create Dialect="http://www.w3.org/2009/02/ws-frag" ...&gt;
-    &lt;wsf:Fragment ...&gt;
-      &lt;wsf:Expression Language="<emph>xs:anyURI</emph>" ...&gt;
-        <emph>xs:any</emph> *
-      &lt;/wsf:Expression&gt; 
-      &lt;wsf:Value ...&gt;
-        <emph>xs:any</emph> *
-      &lt;/wsf:Value&gt; 
-    &lt;/wsf:Fragment&gt;
-    <emph>xs:any</emph> *
-  &lt;/wst:Create&gt;</eg>
-    </example>
-    <p>
-     The following describes additional, normative constraints on the outline
-     listed above:
-    </p>
-    <glist>
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Create@Dialect </label>
-      <def>
-       <p>
-        This attribute MUST be set to http://www.w3.org/2009/02/ws-frag.
-       </p>
-      </def>
-     </gitem>
-
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Create@Fragment </label>
-      <def>
-       <p>
-        This element contains an expression that identifies the location 
-        of a fragment in  the resource and a value for the fragment. If 
-        the contents of this element are invalid a wsf:InvalidFragment 
-        fault MUST be generated.
-       </p>
-      </def>
-     </gitem>
-
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Create/wsf:Fragment/wsf:Expression </label>
-      <def>
-       <p>
-        This element identifies which fragment in the resource this
-        operation applies to.
-        The value of this element MUST conform to the syntax of the language
-        specified in Language attribute, otherwise a
-        wsf:InvalidExpression fault MUST be generated.
-       </p>
-       <p>
-        This element identifies the fragment in the resource as it
-        appears after successful processing of the Create request.
-       </p>
-      </def>
-     </gitem>
-
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Create/wsf:Fragment/wsf:Expression@Language </label>
-      <def>
-       <p>
-        This URI indicates which expression language will be
-        used to identify the subset of the resource this operation applies
-        to. A resource MUST generate a wsf:UnsupportedLanguage Fault if it
-        does not support the specified Language.
-       </p>
-      </def>
-     </gitem>
-
-     <gitem>
-      <label> <kw>[Body]</kw>/wst:Create/wsf:Fragment/wsf:Value </label>
-      <def>
-       <p>
-        This element contains the fragment resource representation 
-        corresponding to the
-        subset of the resource indentified by the wsf:Expression element.
-       </p>
-      </def>
-     </gitem>
-    </glist>
-
-    <p>
-     <kw>OPTION 1:</kw>
-     This operation MUST be performed by creating a new resource using 
-     the specified subset of the resource. Other values within the resource 
-     will use the appropriate default values. Note: this operation has the 
-     same net effect as creating a new resource that is populated with 
-     default values, followed by a wst.Put request with this specified 
-     Fragment.
-    </p>
-
-    <p>
-     <kw>OPTION 2:</kw>
-     This operation MUST be performed by inserting new data within the
-     Fragment element into the resource as specified by the Expression
-     element. If data is already present and would result in the resource
-     being left in an invalid state then a wst:InvalidRepresentation
-     fault MUST be generated.
-    </p>
-
-    <p>
-     If the resource accepts a Create request, it MUST reply with a response of
-     the following form:
+     This specification does not extend the Create operation defined in
+     WS-Transfer.
     </p>
-    <example>
-     <eg><kw>[Action]</kw>
-  http://www.w3.org/2009/02/ws-tra/CreateResponse
-
-<kw>[Body]</kw>
-  &lt;wst:CreateResponse ...&gt;
-    &lt;wst:ResourceCreated> <emph>endpoint-reference</emph> &lt;/wst:ResourceCreated>
-    <emph>xs:any</emph> *
-  &lt;/wst:CreateResponse&gt;</eg>
-    </example>
 
-    <p>
-     There are no additional constraints beyond what WS-Transfer defines.
-    </p>
    </div2>
 
   </div1>
@@ -1096,7 +854,7 @@
   &lt;/s:Header&gt;
   &lt;s:Body&gt;
     &lt;wst:Get&gt;
-      &lt;wsf:Expression Language=".../ws-frag/QName"&gt;
+      &lt;wsf:Expression Language="http://www.w3.org/2009/02/ws-fra/QName"&gt;
         ab:contact
       &lt;/wsf:Expression&gt;
     &lt;/wst:Get&gt;
@@ -1160,7 +918,8 @@
     the resource representation.  The expression MUST evaluate to zero or 
     more elements, each including the element name, any attributes 
     and its entire content.
-    This language can be implemented as a precise subset of the XPath language.
+    This language can be implemented as a precise subset of the 
+    XPath 1.0 <bibref ref="XPath1"/> language.
    </p>
 
    <p>
@@ -1189,7 +948,8 @@
 
    <p>
     XPath Level 1 is a subset of the abbreviated relative syntax
-    of XPath 1.0, and is used to identify or select a node (element, attribute
+    of XPath 1.0 <bibref ref="XPath1"/>, and is used to identify or select 
+    a node (element, attribute
     or value) within a resource
     representation or fragment. It is identified by the following URI:
    </p>
@@ -1626,7 +1386,7 @@
    <p>
     The WS-Fragment global element definition wsf:NodeSet can also be
     used as the wrapper element when serializing these node-sets outside of
-    a WS-Fragmen result.
+    a WS-Fragment result.
    </p>
     
    <p>
@@ -1731,7 +1491,7 @@
     <head>UnsupportedLanguage</head>
     <p>
      This fault is generated when a service detects an unknown or
-     unsupprted Language 
+     unsupported Language 
      URI in a request message. 
     </p>
     <table id="Table3" border="1" cellpadding="5">
@@ -1764,7 +1524,7 @@
      This fault is generated when a service determines that the fragment 
      (contents of the wsf:Fragment element) specified in a request is invalid. 
     </p>
-    <table id="Table3" border="1" cellpadding="5">
+    <table id="Table4" border="1" cellpadding="5">
      <tbody>
       <tr>
        <th align="left"><kw>[Code]</kw></th>
@@ -1791,10 +1551,12 @@
    <div2 id="InvalidExpression">
     <head>InvalidExpression</head>
     <p>
-     This fault is generated when a service determines that the language
-     expression specified in a request is invalid.
+     This fault is generated when a service determines that the Language
+     expression specified in a request does not conform to the syntax
+     of the language specified in the Language attribute or is semantically
+     invalid.
     </p>
-    <table id="Table3" border="1" cellpadding="5">
+    <table id="Table5" border="1" cellpadding="5">
      <tbody>
       <tr>
        <th align="left"><kw>[Code]</kw></th>
@@ -1818,6 +1580,36 @@
     </table>
    </div2>
 
+   <div2 id="UnsupportedMode">
+    <head>UnsupportedMode</head>
+    <p>
+     This fault is generated when a service detects a Mode in a Put
+     request that is not supported.
+    </p>
+    <table id="Table6" border="1" cellpadding="5">
+     <tbody>
+      <tr>
+       <th align="left"><kw>[Code]</kw></th>
+       <td>s:Sender</td>
+      </tr>
+      <tr>
+       <th align="left"><kw>[Subcode]</kw></th>
+       <td>wst:UnsupportedMode</td>
+      </tr>
+      <tr>
+       <th align="left"><kw>[Reason]</kw></th>
+       <td>
+        The specified mode is not supported.
+       </td>
+      </tr>
+      <tr>
+       <th align="left"><kw>[Detail]</kw></th>
+       <td><emph>The unsupported Mode.</emph></td>
+      </tr>
+     </tbody>
+    </table>
+   </div2>
+
   </div1>
 
   <div1 id="policy">
@@ -1855,116 +1647,138 @@
      Sumeet Vij (Software AG),
      Vikas Varma (Software AG),
      Wu Chou (Avaya Communications),
-     Yves Lafon (W3C)
+     Yves Lafon (W3C).
    </p>
   </div1>
 
   <div1 id="refs">
    <head>References</head>
-   <blist>
-    <bibl key="RFC 2119" id="Rfc2119" 
-          href="http://www.ietf.org/rfc/rfc2119.txt">
-     <titleref>
-      Key words for use in RFCs to Indicate Requirement Levels
-     </titleref>
-     , S. Bradner, Harvard University, March 1997.
-    </bibl>
 
-    <bibl id="RFC3986" key="RFC 3986"
-          href="http://www.ietf.org/rfc/rfc3986.txt">
-     <titleref>
-      Uniform Resource Identifier (URI): Generic Syntax
-     </titleref>
-     , T. Berners-Lee, W3C/MIT, January 2005.
-    </bibl>
+   <div2>
+    <head>Normative References</head>
 
-    <bibl key="SOAP 1.1" id="Soap11" 
-          href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
-     <titleref>
-      Simple Object Access Protocol (SOAP) 1.1
-     </titleref>
-     , D. Box, et al, May 2000.
-    </bibl>
+    <blist>
+     <bibl key="RFC 2119" id="RFC2119"
+      href="http://www.ietf.org/rfc/rfc2119.txt">
+       <titleref>
+        Key words for use in RFCs to Indicate Requirement Levels
+       </titleref>
+       , S. Bradner, Author.
+       Internet Engineering Task Force, March 1997.
+     </bibl>
 
-    <bibl key="SOAP 1.2" id="Soap12" href="http://www.w3.org/TR/soap12-part1/">
-     <titleref>
-      SOAP Version 1.2 Part 1: Messaging Framework
-     </titleref>
-     , M. Gudgin, et al, June 2003.
-    </bibl>
+     <bibl key="RFC 3986" id="RFC3986"
+      href="http://www.ietf.org/rfc/rfc3986.txt">
+       <titleref>
+        Uniform Resource Identifier (URI): Generic Syntax
+       </titleref>
+       , T. Berners-Lee, R. Fields and L. Masinter, Authors.
+       Network Working Group, January 2005.
+     </bibl>
 
-    <bibl key="WS-Addressing" id="AddrCore"
-          href="http://www.w3.org/2005/08/addressing/">
-     <titleref>
-      W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
-     </titleref>
-     , May 2006.
-    </bibl>
+     <bibl key="SOAP11" id="SOAP11"
+      href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
+       <titleref>
+        W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
+       </titleref>
+       , D. Box, et al, Editors.
+       World Wide Web Consortium (W3C), 8 May 2000.
+     </bibl>
 
-    <bibl key="WS-Addressing 1.0 SOAP Binding" id="WSABinding"
-          href="http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509">
-     <titleref>
-      W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
-     </titleref>
-     , May 2006.
-    </bibl>
+     <bibl key="SOAP12" id="SOAP121"
+      href="http://www.w3.org/TR/soap12-part1/">
+       <titleref>
+        W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
+       </titleref>
+       , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
+        Editors.
+       World Wide Web Consortium (W3C), 27 April 2007.
+     </bibl>
 
-    <bibl key="WS-Policy" id="WsPolicy" href="http://www.w3.org/TR/ws-policy/">
-     <titleref>
-      W3C Recommendation, "Web Services Policy 1.5 - Framework"
-     </titleref>
-     , September 2007.
-    </bibl>
+     <bibl key="WS-Addressing" id="AddrCore"
+      href="http://www.w3.org/TR/ws-addr-core">
+       <titleref>
+        W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+       </titleref>
+       , M. Gudgin, M. Hadley, T. Rogers, Editors.
+       World Wide Web Consortium (W3C), 9 May 2006.
+     </bibl>
 
-    <bibl key="WS-Transfer" id="WsTransfer" 
-          href="http://www.w3.org/2009/02/ws-tra">
-     <titleref>
-      W3C Working Group Draft, "Web Services Transfer"
-     </titleref>
-     , July 2009.
-    </bibl>
+     <bibl key="WS-Addressing 1.0 SOAP Binding" id="WSABinding"
+      href="http://www.w3.org/TR/ws-addr-soap">
+       <titleref>
+        W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
+       </titleref>
+       , M. Gudgin, M. Hadley, T. Rogers, Editors.
+       World Wide Web Consortium (W3C), 9 May 2006.
+     </bibl>
 
-    <bibl key="WSDL 1.1" id="Wsdl11" 
-          href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
-     <titleref>
-      Web Services Description Language (WSDL) 1.1
-     </titleref>
-     , E. Christensen, et al, March 2001.
-    </bibl>
+     <bibl key="WS-Policy" id="wspolicy"
+      href="http://www.w3.org/TR/ws-policy/">
+       <titleref>
+        W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
+       </titleref>
+       , A. Vedamuthu, et al., Editors.
+       World Wide Web Consortium (W3C), 4 September 2007.
+     </bibl>
 
-    <bibl key="XML Infoset" id="XMLInfoSet" 
-          href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">
-     <titleref>
-      J. Cowan, et al, "XML Information Set"
-     </titleref>
-     , February 2004.
-    </bibl>
+     <bibl key="WS-Transfer" id="WsTransfer" 
+           href="http://www.w3.org/TR/ws-transfer">
+      <titleref>
+       W3C Working Group Draft, "Web Services Transfer (WS-Transfer)1.1"
+      </titleref>
+      , D. Davis, et al., Editors.
+      World Wide Web Consortium (W3C), 15 September 2009.
+     </bibl>
 
-    <bibl key="XML Schema, Part 1" id="XmlSchemaPart1" 
-          href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
-     <titleref>
-      XML Schema Part 1: Structures
-     </titleref>
-     , H. Thompson, et al, October 2004.
-    </bibl>
+     <bibl key="WSDL11" id="WSDL11"
+      href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
+       <titleref>
+        W3C Note, "Web Services Description Language (WSDL) 1.1"
+       </titleref>
+       , E. Christensen, et al., Editors.
+       World Wide Web Consortium (W3C), 15 March 2001
+     </bibl>
 
-    <bibl key="XML Schema, Part 2" id="XmlSchemaPart2" 
-          href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
-     <titleref>
-      XML Schema Part 2: Datatypes
-     </titleref>
-     , James Clark, et al, November 1999.
-    </bibl>
+     <bibl key="XML Infoset" id="XMLInfoset"
+      href="http://www.w3.org/TR/xml-infoset">
+       <titleref>
+        W3C Recommendation, "XML Information Set (Second Edition)"
+       </titleref>
+       , J. Cowan, R. Tobin, Editors.
+       World Wide Web Consortium (W3C), 4 February 2004.
+     </bibl>
 
-    <bibl key="XPath 1.0" id="xpath"
-          href="http://www.w3.org/TR/xpath">
-     <titleref>
-      XML Path Language (XPath) Version 1.0
-     </titleref>
-     , James Clark, et al, November 1999.
-    </bibl>
+     <bibl key="XMLSchema - Part 1" id="XMLSchema1"
+      href="http://www.w3.org/TR/xmlschema-1/">
+       <titleref>
+        W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
+       </titleref>
+       , H. Thompson, et al., Editors.
+       World Wide Web Consortium (W3C), 28 October 2004.
+     </bibl>
+
+     <bibl key="XMLSchema - Part 2" id="XMLSchema2"
+      href="http://www.w3.org/TR/xmlschema-2/">
+       <titleref>
+        W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
+       </titleref>
+       , P. Biron, A. Malhotra, Editors.
+       World Wide Web Consortium (W3C), 28 October 2004.
+     </bibl>
+
+     <bibl key="XPath1.0" id="XPath1"
+      href="http://www.w3.org/TR/xpath">
+       <titleref>
+        W3C Recommendation, "XML Path Language (XPath) Version 1.0"
+       </titleref>
+       , J. Clark, S. DeRose, Editors.
+       World Wide Web Consortium (W3C), 16 November 1999.
+     </bibl>
+
+    </blist>
+   </div2>
 
-   </blist>
   </div1>
  </body>
 
@@ -1973,8 +1787,8 @@
    <head>XML Schema</head>
 
    <p>
-    A normative copy of the XML Schema <bibref ref='XmlSchemaPart1'/>,
-    <bibref ref='XmlSchemaPart2'/> description for this specification can be
+    A normative copy of the XML Schema <bibref ref='XMLSchema1'/>,
+    <bibref ref='XMLSchema2'/> description for this specification can be
     retrieved from the following address:
    </p>
     
@@ -2002,7 +1816,7 @@
   <div1 id="Appendix_II__E2_80_93_WSDL">
    <head>WSDL</head>
    <p>
-    A normative copy of the WSDL <bibref ref="Wsdl11"/> description
+    A normative copy of the WSDL <bibref ref="WSDL11"/> description
     for this specification can be retrieved from the following address:
    </p>
    <example>
@@ -2083,28 +1897,6 @@
   <div1 id="Questions">
    <head>Open Questions and Actions</head>
    <p>
-    Ram - If the expression resolves to a non-existent node should it fault
-      or do nothing?
-   </p>
-   <p>
-    Ram - should we allow for the creation with default value? This is, 
-      allow 0 or 1 value elements on the Create.
-   </p>
-   <p>
-    Ram - add a NonExistentNode fault.
-   </p>
-
-   <p>
-    Ram - add a general fault to indicate that a fragment message is invalid.
-   </p>
-
-   <p>
-    Dug - on put - Should the client really be forced to know whether or not 
-    there's data there just to add something? What if, instead, we just 
-    allowed it to replace the existing data (if any)? 
-   </p>
-
-   <p>
     Ram - should we make the new bits <kw>bold</kw> so that people
     can see what's new from base Transfer?
    </p>
Received on Wednesday, 23 September 2009 17:36:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 September 2009 17:36:39 GMT