Changeset 1037 for draft-ietf-httpbis/latest

Timestamp:

19/10/10 09:37:34 (10 years ago)

Author:

julian.reschke@…

Message:

Source reformat, update Changes section (see #230 and [1034])

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (3 diffs)
• p2-semantics.xml (modified) (2 diffs)

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

@@ -543 +543 @@
          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul class="toc">
-                     <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.1.1">Considerations for New Methods</a></li>
+                     <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
                   </ul>
                </li>
@@ -792 +792 @@
       <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
       </p>
-      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;Considerations for New Methods
-      </h3>
+      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
       <p id="rfc.section.2.1.1.p.1">When it is necessary to express new semantics for a HTTP request that aren't specific to a single application or media type,
          and currently defined methods are inadequate, it may be appropriate to register a new method.
@@ -2621 +2620 @@
       <p id="rfc.section.C.13.p.1">Closed issues: </p>
       <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/230">http://tools.ietf.org/wg/httpbis/trac/ticket/230</a>&gt;: "Considerations for new methods"
+         </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/232">http://tools.ietf.org/wg/httpbis/trac/ticket/232</a>&gt;: "User-Agent guidelines" (relating to the 'User-Agent' header field)
          </li>

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

@@ -482 +482 @@
 </t>
 
-<section title="Considerations for New Methods">
-
-  <t>When it is necessary to express new semantics for a HTTP request that
-  aren't specific to a single application or media type, and currently defined
-  methods are inadequate, it may be appropriate to register a new method.</t>
-
-  <t>New methods &SHOULD; be potentially applicable to any resource. I.e.,
-  they should not be specific to any particular media type, "type" of
-  resource, or application.</t>
-
-  <t>New methods &MUST-NOT; prohibit a message-body on either the request or
-  the response message; however they &MAY; specify that only a zero-length
-  body is allowed.</t>
-
-  <t>New methods &MUST; define whether they are safe (<xref
-  target="safe.methods"/>) and whether they are idempotent (<xref
-  target="idempotent.methods"/>). They &MUST; also state whether they can be
-  cached (&caching;); in particular what conditions a cache may store the
-  response, and under what conditions such a stored response may be used to
-  satisfy a subsequent request.</t>
-
-  <t>New methods &SHOULD; explain how conditional request headers
-  (&conditional;) affect the response (if there is any effect).</t>
-
-  <t>HTTP methods &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 title="Considerations for New Methods" anchor="considerations.for.new.methods">
+<t>
+   When it is necessary to express new semantics for a HTTP request that
+   aren't specific to a single application or media type, and currently defined
+   methods are inadequate, it may be appropriate to register a new method.
+</t>
+<t>
+   New methods &SHOULD; be potentially applicable to any resource. I.e.,
+   they should not be specific to any particular media type, "type" of
+   resource, or application.
+</t>
+<t>
+   New methods &MUST-NOT; prohibit a message-body on either the request or
+   the response message; however they &MAY; specify that only a zero-length
+   body is allowed.
+</t>
+<t>
+   New methods &MUST; define whether they are safe (<xref
+   target="safe.methods"/>) and whether they are idempotent (<xref
+   target="idempotent.methods"/>). They &MUST; also state whether they can be
+   cached (&caching;); in particular what conditions a cache may store the
+   response, and under what conditions such a stored response may be used to
+   satisfy a subsequent request.
+</t>
+<t>
+   New methods &SHOULD; explain how conditional request headers
+   (&conditional;) affect the response (if there is any effect).
+</t>
+<t>
+   HTTP methods &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>
 
@@ -3881 +3886 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/230"/>:
+      "Considerations for new methods"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/232"/>:
       "User-Agent guidelines" (relating to the 'User-Agent' header field)