Changeset 1842 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

01/09/12 05:32:48 (8 years ago)

Author:

fielding@…

Message:

(editorial) wordsmithing and sectioning

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (8 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -289 +289 @@
 
 <section title="Request Methods" anchor="methods">
+
+<section title="Overview" anchor="method.overview">
   <x:anchor-alias value="method"/>
 <t>
@@ -322 +324 @@
    standardized methods are defined in all-uppercase ASCII letters.
 </t>
-<texttable align="left" suppress-title="true" anchor="method.overview">
+<texttable align="left" suppress-title="true" anchor="table.of.methods">
    <ttcol>Method</ttcol>
    <ttcol>Description</ttcol>
@@ -375 +377 @@
    with the <x:ref>405 (Method Not Allowed)</x:ref> status code.
 </t>
+</section>
+
 <section title="Common Method Properties" anchor="method.properties">
 
@@ -451 +455 @@
    able to read the server's response.  For example, if a client sends a PUT
    request and the underlying connection is closed before any response is
-   received, then it can establish a new connection and retry the request
-   because it knows that repeating the request will have the same effect
-   even if the original request succeeded.  Note, however, that repeated
-   failures would indicate a problem within the server.
+   received, then it can establish a new connection and retry the idempotent
+   request because it knows that repeating the request will have the same
+   effect even if the original request succeeded.  Note, however, that
+   repeated failures would indicate a problem within the server.
 </t>
 </section>
@@ -466 +470 @@
    request.  GET and HEAD are defined to be cacheable.  In general, safe
    methods that do not depend on a current or authoritative response are
-   also cacheable, though the overwhelming majority of caches only support
+   cacheable, though the overwhelming majority of caches only support
    GET and HEAD. HTTP requirements for cache behavior and cacheable responses
    are defined in &caching;.
@@ -1784 +1788 @@
     that it does not allow rewriting the request method from POST to GET. This
     specification defines no equivalent counterpart for <x:ref>301 (Moved
-    Permanently)</x:ref> (<xref target="draft-reschke-http-status-308"/>,
+    Permanently)</x:ref> (<xref target="status-308"/>,
     however, defines the status code 308 (Permanent Redirect) for this purpose). 
   </t>
@@ -5025 +5029 @@
 <references title="Informative References">
 
-<reference anchor="REST" target="http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm">
+<reference anchor="REST" target="http://roy.gbiv.com/pubs/dissertation/top.htm">
   <front>
     <title>Architectural Styles and the Design of Network-based Software Architectures</title>
     <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
-      <organization>Doctoral Dissertation, University of California, Irvine</organization>
-    </author>
-    <date month="Sep" year="2000"/>
+    </author>
+    <date month="September" year="2000"/>
   </front>
+  <seriesInfo name='Doctoral Dissertation, University of California, Irvine' value=''/>
 </reference>
 
@@ -5383 +5387 @@
 </reference>
 
-<reference anchor="draft-reschke-http-status-308">
+<reference anchor="status-308">
         <front>
     <title abbrev="HTTP Status Code 308">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</title>