Changeset 1594 for draft-ietf-httpbis/19

Timestamp:

12/03/12 10:28:12 (10 years ago)

Author:

julian.reschke@…

Message:

regen -19 draft (see #338)

Location:

draft-ietf-httpbis/19

Files:

• draft-ietf-httpbis-p3-payload-19.txt (modified) (5 diffs)
• draft-ietf-httpbis-p3-payload-19.xml (modified) (2 diffs)

draft-ietf-httpbis/19/draft-ietf-httpbis-p3-payload-19.txt

@@ -1322 +1322 @@
    If Content-Location is included in a response message and its value
    is the same as the effective request URI, then the response payload
-   SHOULD be considered the current representation of that resource.
-   For a GET or HEAD request, this is the same as the default semantics
-   when no Content-Location is provided by the server.  For a state-
-   changing request like PUT or POST, it implies that the server's
-   response contains the new representation of that resource, thereby
+   SHOULD be considered a current representation of that resource.  For
+   a GET or HEAD request, this is the same as the default semantics when
+   no Content-Location is provided by the server.  For a state-changing
+   request like PUT or POST, it implies that the server's response
+   contains the new representation of that resource, thereby
    distinguishing it from representations that might only report about
    the action (e.g., "It worked!").  This allows authoring applications
@@ -2310 +2310 @@
       representation header field?"
 
+   o  <http://tools.ietf.org/wg/httpbis/trac/ticket/338>: "Content-
+      Location doesn't constrain the cardinality of representations"
+
    o  <http://tools.ietf.org/wg/httpbis/trac/ticket/346>: "make IANA
       policy definitions consistent"
@@ -2327 +2330 @@
          gzip  8
       compress (Coding Format)  7
+
+
+
+Fielding, et al.       Expires September 13, 2012              [Page 41]
+
+
+Internet-Draft              HTTP/1.1, Part 3                  March 2012
+
+
       content negotiation  5
       Content-Encoding header field  22
       Content-Language header field  23
-
-
-
-Fielding, et al.       Expires September 13, 2012              [Page 41]
-
-
-Internet-Draft              HTTP/1.1, Part 3                  March 2012
-
-
       Content-Location header field  23
       Content-Transfer-Encoding header field  32
@@ -2384 +2387 @@
          Content-Transfer-Encoding  32
          Content-Type  25
+
+
+
+Fielding, et al.       Expires September 13, 2012              [Page 42]
+
+
+Internet-Draft              HTTP/1.1, Part 3                  March 2012
+
+
          MIME-Version  30
 
    M
-
-
-
-Fielding, et al.       Expires September 13, 2012              [Page 42]
-
-
-Internet-Draft              HTTP/1.1, Part 3                  March 2012
-
-
       MIME-Version header field  30
 
@@ -2444 +2447 @@
 
 
-
-
-
 Fielding, et al.       Expires September 13, 2012              [Page 43]
 

draft-ietf-httpbis/19/draft-ietf-httpbis-p3-payload-19.xml

@@ -1279 +1279 @@
    If Content-Location is included in a response message and its value
    is the same as the effective request URI, then the response payload
-   SHOULD be considered the current representation of that resource.
+   SHOULD be considered a current representation of that resource.
    For a GET or HEAD request, this is the same as the default semantics
    when no Content-Location is provided by the server.  For a state-changing
@@ -2866 +2866 @@
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/338"/>:
+      "Content-Location doesn't constrain the cardinality of representations"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>:
       "make IANA policy definitions consistent"