Changeset 1593 for draft-ietf-httpbis/19

Timestamp:

12/03/12 10:22:53 (10 years ago)

Author:

julian.reschke@…

Message:

Content-Location doesn't constrain the cardinality of representations (see #338)

Location:

draft-ietf-httpbis/19

Files:

• p3-payload.html (modified) (2 diffs)
• p3-payload.xml (modified) (2 diffs)

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

@@ -1375 +1375 @@
       </p>
       <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
-         payload <em class="bcp14">SHOULD</em> be considered the current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
+         payload <em class="bcp14">SHOULD</em> 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
@@ -2125 +2125 @@
       <ul>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>&gt;: "is ETag a representation header field?"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/338">http://tools.ietf.org/wg/httpbis/trac/ticket/338</a>&gt;: "Content-Location doesn't constrain the cardinality of representations"
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>&gt;: "make IANA policy definitions consistent"

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

@@ -1321 +1321 @@
    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
@@ -2908 +2908 @@
     </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"