Changeset 1750 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

Jul 9, 2012, 12:06:58 PM (7 years ago)

Author:

fielding@…

Message:

We do not want broad cross-references to the semantics spec within
the parsing algorithm -- it just makes it harder to understand.
Parsing needs to be independent of semantics, so we only need
the xref in one section.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1103 +1103 @@
   <x:anchor-alias value="response"/>
   <x:anchor-alias value="status-line"/>
+  <x:anchor-alias value="status-code"/>
+  <x:anchor-alias value="reason-phrase"/>
 <t>
    The first line of a response message is the status-line, consisting
@@ -1116 +1118 @@
    with a status-line and matches the ABNF rule for HTTP-message.
 </t>
-
-<t anchor="status-code">
-   The status-code element is a 3-digit integer result code of the attempt to
-   understand and satisfy the request. See &status-codes; for
-   further information, such as the list of status codes defined by this
-   specification, the IANA registry, and considerations for new status codes.
+<t>
+   The status-code element is a 3-digit integer code describing the
+   result of the server's attempt to understand and satisfy the client's
+   corresponding request. The rest of the response message is to be
+   interpreted in light of the semantics defined for that status code.
+   See &status-codes; for information about the semantics of status codes,
+   including the classes of status code (indicated by the first digit),
+   the status codes defined by this specification, considerations for the
+   definition of new status codes, and the IANA registry.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/>
   <x:ref>status-code</x:ref>    = 3<x:ref>DIGIT</x:ref>
 </artwork></figure>
-
-<t anchor="reason-phrase">   
+<t>   
    The reason-phrase element exists for the sole purpose of providing a
    textual description associated with the numeric status code, mostly
@@ -1498 +1502 @@
    The presence of a message body in a response depends on both
    the request method to which it is responding and the response
-   status code (<xref target="status-code"/>).
+   status code (<xref target="status.line"/>).
    Responses to the HEAD request method never include a message body
    because the associated response header fields (e.g.,
@@ -1508 +1512 @@
    <x:ref>304 (Not Modified)</x:ref> responses &MUST-NOT; include a message body.
    All other responses do include a message body, although the body
-   &MAY; be of zero length. (See &status-codes; and &status-304;.)
+   &MAY; be of zero length.
 </t>