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

Timestamp:

11/01/13 08:14:43 (10 years ago)

Author:

fielding@…

Message:

(editorial) move definition of selected representtation to top and change name of selected representation header fields to validator header fields for consistency with p4

File:

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

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

@@ -286 +286 @@
 
 <section title="Representations" anchor="representations">
-<iref item="representation"/>
+   <iref primary="true" item="representation"/>
+   <iref primary="true" item="selected representation"/>
+   <x:anchor-alias value="representation"/>
+   <x:anchor-alias value="selected representation"/>
 <t>
    If we consider that a resource could be anything, and that the uniform
@@ -302 +305 @@
    and that consists of a set of representation metadata and a potentially
    unbounded stream of representation data.
+</t>
+<t>
+   We use the term "<x:dfn>selected representation</x:dfn>" to refer to the
+   representation of the <x:ref>target resource</x:ref> in a
+   <x:ref>200 (OK)</x:ref> response to <x:ref>GET</x:ref>, or the
+   representation that would have been selected in a successful response if
+   the request had used the method <x:ref>GET</x:ref> and excluded any
+   conditional request header fields.
 </t>
 
@@ -2768 +2779 @@
 <t>
    The 201 response payload typically describes and links to the resource(s)
-   created. See <xref target="selected.representation"/> for discussion of the
-   meaning and purpose of selected representation header fields, such as
+   created. See <xref target="response.validator"/> for a discussion of the
+   meaning and purpose of validator header fields, such as
    <x:ref>ETag</x:ref> and <x:ref>Last-Modified</x:ref>, in a 201 response.
 </t>
@@ -3941 +3952 @@
 </section>
 
-<section title="Selected Representation Header Fields" anchor="selected.representation">
-   <iref primary="true" item="selected representation"/>
-   <x:anchor-alias value="selected representation"/>
-<t>
-   We use the term "<x:dfn>selected representation</x:dfn>" to refer to the
-   representation of the <x:ref>target resource</x:ref> in a
-   <x:ref>200 (OK)</x:ref> response to <x:ref>GET</x:ref>, or the
-   representation that would have been selected in a successful response if
-   the request had used the method <x:ref>GET</x:ref> and excluded any
-   conditional request header fields.
-</t>
-<t>
-   The following header fields define metadata about the selected
-   representation at the conclusion of handling the request. In other words,
-   for a successful response to a state-changing method, these fields describe
-   the new representation that has replaced the prior selected representation.
+<section title="Validator Header Fields" anchor="response.validator">
+   <iref item="selected representation"/>
+<t>
+   Validator header fields convey metadata about the
+   <x:ref>selected representation</x:ref> (<xref target="representations"/>).
+   In responses to safe requests, validator fields describe the selected
+   representation chosen by the origin server while handling the response.
+   Note that, depending on the status code semantics, the
+   <x:ref>selected representation</x:ref> for a given response is not
+   necessarily the same as the representation enclosed as response payload.
+</t>
+<t>
+   In a successful response to a state-changing request, validator fields
+   describe the new representation that has replaced the prior
+   <x:ref>selected representation</x:ref> as a result of processing the
+   request.
+</t>
+<t>
    For example, an ETag header field in a 201 response communicates the
    entity-tag of the newly created resource's representation, so that it can