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

WWW/2002/ws/ra/edcopies wsenum.html,1.44,1.45 wsenum.xml,1.35,1.36 wst.html,1.42,1.43 wst.xml,1.38,1.39

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 12 Jun 2009 03:24:11 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MExND-00033h-Fy@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv11632

Modified Files:
	wsenum.html wsenum.xml wst.html wst.xml 
Log Message:
6924 - for wst
fix typo for wsenum


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- wst.xml	10 Jun 2009 22:51:00 -0000	1.38
+++ wst.xml	12 Jun 2009 03:24:09 -0000	1.39
@@ -635,15 +635,41 @@
         </p>
 
         <p>
-         Implementations MAY use the fault code wst:InvalidRepresentation 
-         if the presented representation is invalid for the target resource. 
-         See <specref ref="Faults"/>. Other components of the outline above are not 
+         Implementations MAY use the fault code wst:InvalidRepresentation if 
+         the presented representation is invalid for the target resource. The 
+         replacement representation may be considered to be invalid if it does 
+         not conform to the schema(s) for the target resource or otherwise 
+         violates some cardinality or type constraint. If an implementation 
+         detects that the presented representation is invalid it MUST generate 
+         a wst:InvalidRepresentation fault.
+        </p>
+
+        <p>
+         The replacement representation may contain within it element or 
+         attribute values that are different than their corresponding values in 
+         the current representation. Such changes may affect elements or 
+         attributes that, for whatever reason, the implementation does wish to 
+         allow the client to change. An implementation MAY choose to ignore 
+         such elements or attributes, or it MAY generate a wst:PutDenied 
+         fault. See <specref ref="Faults"/>.
+        </p>
+
+        <p>
+         Other components of the outline above are not 
          further constrained by this specification.
         </p>
-        <p>A successful Put operation updates the current representation associated
-with the targeted resource.</p>
-        <p>If the resource accepts a Put request and performs the requested update,
-it MUST reply with a response of the following form:</p>
+
+        <p>
+         A successful Put operation updates the current representation 
+         associated with the targeted resource. An unsuccessful Put operation 
+         does not affect the resource.
+        </p>
+
+        <p>
+         If the resource accepts a Put request and performs the requested 
+         update, it MUST reply with a response of the following form:
+        </p>
+
         <example>
           <eg><kw>[Action]</kw>
   http://www.w3.org/2009/02/ws-tra/PutResponse
@@ -1167,6 +1193,38 @@
           </tbody>
         </table>
       </div2>
+
+      <div2 id="PutDenied">
+        <head>PutDenied</head>
+        <p>
+         This fault is generated when a Put request message attempts
+         to modify a portion of a resource but is not allowed to do so.
+        </p>
+        <table id="Table4" 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:UpdateDenied</td>
+            </tr>
+            <tr>
+              <th align="left"><kw>[Reason]</kw></th>
+              <td>
+                One or more elements or attributes cannot be updated.
+              </td>
+            </tr>
+            <tr>
+              <th align="left"><kw>[Detail]</kw></th>
+              <td><emph>An optional list of the QNames of the elements or 
+              attributes that are not allowed to be updated.</emph></td>
+            </tr>
+          </tbody>
+        </table>
+      </div2>
+
     </div1>
     <div1 id="Security_Considerations">
       <head>Security Considerations</head>
@@ -1720,6 +1778,13 @@
             <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6712">6712</loc>
           </td>
         </tr>
+        <tr>
+          <td> 2009/06/10 </td>
+          <td> DD </td>
+          <td> Added resolution of issue 
+            <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6924">6924</loc>
+          </td>
+        </tr>
       </tbody>
      </table>
     </div1>

Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- wst.html	10 Jun 2009 22:51:00 -0000	1.42
+++ wst.html	12 Jun 2009 03:24:09 -0000	1.43
@@ -55,6 +55,7 @@
 5 <a href="#Faults">Faults</a><br/>
 &nbsp;&nbsp;&nbsp;5.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br/>
 &nbsp;&nbsp;&nbsp;5.2 <a href="#InvalidContentDescription">InvalidContentDescription</a><br/>
+&nbsp;&nbsp;&nbsp;5.3 <a href="#PutDenied">PutDenied</a><br/>
 6 <a href="#Security_Considerations">Security Considerations</a><br/>
 7 <a href="#acks">Acknowledgements</a><br/>
 8 <a href="#refs">References</a><br/>
@@ -338,13 +339,32 @@
          desired to be replaced, as described in 
          <a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of this specification.
         </p><p>
-         Implementations MAY use the fault code wst:InvalidRepresentation 
-         if the presented representation is invalid for the target resource. 
-         See <a href="#Faults"><b>5 Faults</b></a>. Other components of the outline above are not 
+         Implementations MAY use the fault code wst:InvalidRepresentation if 
+         the presented representation is invalid for the target resource. The 
+         replacement representation may be considered to be invalid if it does 
+         not conform to the schema(s) for the target resource or otherwise 
+         violates some cardinality or type constraint. If an implementation 
+         detects that the presented representation is invalid it MUST generate 
+         a wst:InvalidRepresentation fault.
+        </p><p>
+         The replacement representation may contain within it element or 
+         attribute values that are different than their corresponding values in 
+         the current representation. Such changes may affect elements or 
+         attributes that, for whatever reason, the implementation does wish to 
+         allow the client to change. An implementation MAY choose to ignore 
+         such elements or attributes, or it MAY generate a wst:PutDenied 
+         fault. See <a href="#Faults"><b>5 Faults</b></a>.
+        </p><p>
+         Other components of the outline above are not 
          further constrained by this specification.
-        </p><p>A successful Put operation updates the current representation associated
-with the targeted resource.</p><p>If the resource accepts a Put request and performs the requested update,
-it MUST reply with a response of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
+        </p><p>
+         A successful Put operation updates the current representation 
+         associated with the targeted resource. An unsuccessful Put operation 
+         does not affect the resource.
+        </p><p>
+         If the resource accepts a Put request and performs the requested 
+         update, 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/PutResponse
 
 <b>[Body]</b>
@@ -678,7 +698,14 @@
         </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:InvalidContentDescription</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
                 The service requires a ContentDescription URI, or the 
                 value specified is not known
-              </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown URI if specified</em></td></tr></tbody></table></div></div><div class="div1">
+              </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown URI if specified</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="PutDenied" id="PutDenied"/>5.3 PutDenied</h3><p>
+         This fault is generated when a Put request message attempts
+         to modify a portion of a resource but is not allowed to do so.
+        </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:UpdateDenied</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
+                One or more elements or attributes cannot be updated.
+              </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>An optional list of the QNames of the elements or 
+              attributes that are not allowed to be updated.</em></td></tr></tbody></table></div></div><div class="div1">
 <h2><a name="Security_Considerations" id="Security_Considerations"/>6 Security Considerations</h2><p>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 body (even if empty) and all
     relevant headers need to be included in the signature. Specifically, the
@@ -1006,4 +1033,5 @@
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6907">6907</a></td></tr><tr><td> 2009/05/21 </td><td> DD </td><td> Added resolution of issue 
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6674">6674</a></td></tr><tr><td> 2009/05/27 </td><td> DD </td><td> Added resolution of issue 
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</a></td></tr><tr><td> 2009/06/10 </td><td> DD </td><td> Added resolution of issue 
-            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6712">6712</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=6712">6712</a></td></tr><tr><td> 2009/06/10 </td><td> DD </td><td> Added resolution of issue 
+            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6924">6924</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- wsenum.html	12 Jun 2009 03:05:10 -0000	1.44
+++ wsenum.html	12 Jun 2009 03:24:09 -0000	1.45
@@ -578,16 +578,16 @@
         wsen:InvalidEnumerationContext fault if the data source is able to 
         determine that the enumeration context is invalid for any reason 
         including:
-        <ol class="enumar"><li>
-          Context replaced in the response to another Pull request
-         </li><li>
-          Context completed (i.e. an EndOfSequence has been returned in
-          a Pull response)
-         </li><li>
-          Context released
-         </li><li>
-          Context expired
-         </li></ol></p><p>
+        <ol class="enumar"><li><p>
+           Context replaced in the response to another Pull request
+          </p></li><li><p>
+           Context completed (i.e. an EndOfSequence has been returned in
+           a Pull response)
+          </p></li><li><p>
+           Context released
+          </p></li><li><p>
+           Context expired
+          </p></li></ol></p><p>
         Note that the data source may not be able to
         determine that an enumeration context is not valid, especially if
         all of the state associated with the enumeration is kept in the

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- wsenum.xml	12 Jun 2009 03:05:10 -0000	1.35
+++ wsenum.xml	12 Jun 2009 03:24:09 -0000	1.36
@@ -973,17 +973,25 @@
         including:
         <olist>
          <item>
-          Context replaced in the response to another Pull request
+          <p>
+           Context replaced in the response to another Pull request
+          </p>
          </item>
          <item>
-          Context completed (i.e. an EndOfSequence has been returned in
-          a Pull response)
+          <p>
+           Context completed (i.e. an EndOfSequence has been returned in
+           a Pull response)
+          </p>
          </item>
          <item>
-          Context released
+          <p>
+           Context released
+          </p>
          </item>
          <item>
-          Context expired
+          <p>
+           Context expired
+          </p>
          </item>
         </olist>
        </p>
Received on Friday, 12 June 2009 03:24:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 12 June 2009 03:24:19 GMT