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

Timestamp:

02/09/12 06:46:39 (9 years ago)

Author:

fielding@…

Message:

(editorial) separate discussions of request and response fields

File:

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

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

@@ -224 +224 @@
    intentions defined by each request method (<xref target="methods"/>),
    extensions to those semantics that might be described in request header
-   fields (<xref target="request.fields"/>),
+   fields (<xref target="request.header.fields"/>),
    the meaning of status codes to indicate a machine-readable response
    (<xref target="status.codes"/>), and other control data
-   and resource metadata that might be given in response header fields.
+   and resource metadata that might be given in response header fields
+   (<xref target="response.header.fields"/>).
 </t>
 <t><iref item="content negotiation"/>
@@ -280 +281 @@
    request semantics, which is made possible by vesting the request
    semantics in the request method (<xref target="methods"/>) and a few
-   request-modifying header fields (<xref target="request.fields"/>).
+   request-modifying header fields (<xref target="request.header.fields"/>).
    Resource owners &SHOULD-NOT; include request semantics within a URI,
    such as by specifying an action to invoke within the path or query
@@ -471 +472 @@
    and what is expected by the client as a successful result.  The request
    semantics &MAY; be further specialized by the semantics of some header
-   fields when present in a request (<xref target="request.fields"/>) if
-   those additional semantics do not conflict with the method.
+   fields when present in a request (<xref target="request.header.fields"/>)
+   if those additional semantics do not conflict with the method.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
@@ -1131 +1132 @@
 </section>
 
-<section title="Header Fields" anchor="header.fields">
-
-<section title="Request-modifier Header Fields" anchor="request.fields">
-</section>
-
-<section title="Status-modifier Header Fields" anchor="response.fields">
-</section>
-
-<section title="Resource Metadata Fields" anchor="resource.fields">
-</section>
-
-<section title="Payload Metadata Fields" anchor="payload.fields">
-</section>
-
 <section title="Request Header Fields" anchor="request.header.fields">
   <x:anchor-alias value="request-header"/>
@@ -1178 +1165 @@
   <c>User-Agent</c> <c><xref target="header.user-agent"/></c>
 </texttable>
-</section>
-
-<section title="Response Header Fields" anchor="response.header.fields">
-  <x:anchor-alias value="response-header"/>
-<t>
-   The response header fields allow the server to pass additional
-   information about the response which cannot be placed in the status-line.
-   These header fields give information about the server and about
-   further access to the target resource (&effective-request-uri;).
-</t>
-<texttable align="left">
-  <ttcol>Header Field Name</ttcol><ttcol>Defined in...</ttcol>
-
-  <c>Accept-Ranges</c> <c>&header-accept-ranges;</c>
-  <c>Age</c> <c>&header-age;</c>
-  <c>Allow</c> <c><xref target="header.allow"/></c>
-  <c>Date</c> <c><xref target="header.date"/></c>
-  <c>ETag</c> <c>&header-etag;</c>
-  <c>Location</c> <c><xref target="header.location"/></c>
-  <c>Proxy-Authenticate</c> <c>&header-proxy-authenticate;</c>
-  <c>Retry-After</c> <c><xref target="header.retry-after"/></c>
-  <c>Server</c> <c><xref target="header.server"/></c>
-  <c>Vary</c> <c>&header-vary;</c>
-  <c>WWW-Authenticate</c> <c>&header-www-authenticate;</c>
-</texttable>
-</section>
-
+
+<section title="Controls" anchor="request.controls">
+</section>
+
+<section title="Conditionals" anchor="request.conditionals">
+</section>
+
+<section title="Content Negotiation" anchor="request.conneg">
+</section>
+
+<section title="Information" anchor="request.inform">
+</section>
 </section>
 
@@ -2207 +2179 @@
 </section>
 </section>
+</section>
+
+<section title="Response Header Fields" anchor="response.header.fields">
+  <x:anchor-alias value="response-header"/>
+<t>
+   The response header fields allow the server to pass additional
+   information about the response which cannot be placed in the status-line.
+   These header fields give information about the server and about
+   further access to the target resource (&effective-request-uri;).
+</t>
+<texttable align="left">
+  <ttcol>Header Field Name</ttcol><ttcol>Defined in...</ttcol>
+
+  <c>Accept-Ranges</c> <c>&header-accept-ranges;</c>
+  <c>Age</c> <c>&header-age;</c>
+  <c>Allow</c> <c><xref target="header.allow"/></c>
+  <c>Date</c> <c><xref target="header.date"/></c>
+  <c>ETag</c> <c>&header-etag;</c>
+  <c>Location</c> <c><xref target="header.location"/></c>
+  <c>Proxy-Authenticate</c> <c>&header-proxy-authenticate;</c>
+  <c>Retry-After</c> <c><xref target="header.retry-after"/></c>
+  <c>Server</c> <c><xref target="header.server"/></c>
+  <c>Vary</c> <c>&header-vary;</c>
+  <c>WWW-Authenticate</c> <c>&header-www-authenticate;</c>
+</texttable>
 </section>