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

Timestamp:

Oct 19, 2010, 2:44:09 AM (9 years ago)

Author:

julian.reschke@…

Message:

Source reformat, update Changes section (see #229 and [1035])

File:

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

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

@@ -658 +658 @@
 </t>
 
-<section title="Considerations for New Status Codes">
-  
-   <t>When it is necessary to express new semantics for a HTTP response that
-  aren't specific to a single application or media type, and currently defined
-  status codes are inadequate, a new status code can be registered.</t>
-  
-   <t>New HTTP status codes &MUST; be defined in one of the categories defined
+<section title="Considerations for New Status Codes" anchor="considerations.for.new.status.codes">
+<t>
+   When it is necessary to express new semantics for a HTTP response that
+   aren't specific to a single application or media type, and currently defined
+   status codes are inadequate, a new status code can be registered.
+</t>
+<t>
+   New HTTP status codes &MUST; be defined in one of the categories defined
    in <xref target="status.codes"/>. They &MUST-NOT; disallow a response body,
    although they &MAY; mandate a zero-length response body. They &MAY; require
-   the presence of one or more particular HTTP response header(s).</t>
-  
-   <t>Likewise, their definitions &MAY; specify that caches are allowed to use
+   the presence of one or more particular HTTP response header(s).
+</t>
+<t>
+   Likewise, their definitions &MAY; specify that caches are allowed to use
    heuristics to determine their freshness (see &caching;; by default, it is
    not allowed), and &MAY; define how to determine the resource which they
    carry a representation for (see <xref
    target="identifying.response.associated.with.representation"/>; by default,
-   it is anonymous).</t>
-  
-   <t>If there are particular request conditions that produce a response
-  containing the status code (e.g., request headers and/or method(s)), they
-  &SHOULD; be described in detail.</t>
-  
-   <t>New HTTP status codes &SHOULD; be registered in a document that isn't
-  specific to a single application or other use of HTTP, so that it's clear that
-  they are not specific to that application or extension.</t>
-  
+   it is anonymous).
+</t>
+<t>
+   If there are particular request conditions that produce a response
+   containing the status code (e.g., request headers and/or method(s)), they
+   &SHOULD; be described in detail.
+</t>
+<t>
+   New HTTP status codes &SHOULD; be registered in a document that isn't
+   specific to a single application or other use of HTTP, so that it's clear that
+   they are not specific to that application or extension.
+</t>
 </section>
 
@@ -3886 +3890 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/229"/>:
+      "Considerations for new status codes"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/230"/>:
       "Considerations for new methods"