Changeset 576 for draft-ietf-httpbis/latest

Timestamp:

06/05/09 07:11:26 (13 years ago)

Author:

julian.reschke@…

Message:

Make spec consistent in not stating "decimal" when it's already clear from the ABNF (related to #161)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (4 diffs)
• p1-messaging.xml (modified) (3 diffs)
• p5-range.html (modified) (5 diffs)
• p5-range.xml (modified) (4 diffs)
• p6-cache.html (modified) (2 diffs)
• p6-cache.xml (modified) (2 diffs)

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

@@ -471 +471 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">May 3, 2009</td>
+            <td class="header right">May 6, 2009</td>
          </tr>
       </table>
@@ -1263 +1263 @@
          </li>
          <li>
-            <p>If a Content-Length header field (<a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;8.2</a>) is present, its decimal value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header
-               field <em class="bcp14">MUST NOT</em> be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). If a message is received
+            <p>If a Content-Length header field (<a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;8.2</a>) is present, its value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header field <em class="bcp14">MUST NOT</em> be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). If a message is received
                with both a Transfer-Encoding header field and a Content-Length header field, the latter <em class="bcp14">MUST</em> be ignored.
             </p>
@@ -1653 +1652 @@
       <div id="rfc.iref.h.4"></div>
       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="header.content-length" href="#header.content-length">Content-Length</a></h2>
-      <p id="rfc.section.8.2.p.1">The entity-header field "Content-Length" indicates the size of the entity-body, in decimal number of OCTETs, sent to the recipient
+      <p id="rfc.section.8.2.p.1">The entity-header field "Content-Length" indicates the size of the entity-body, in number of OCTETs, sent to the recipient
          or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET.
       </p>
@@ -3001 +3000 @@
       <p id="rfc.section.E.8.p.1">Closed issues: </p>
       <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
+         </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/162">http://tools.ietf.org/wg/httpbis/trac/ticket/162</a>&gt;: "comment ABNF"
          </li>

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

@@ -1401 +1401 @@
     <x:lt><t>
      If a Content-Length header field (<xref target="header.content-length"/>) is present, its
-     decimal value in OCTETs represents both the entity-length and the
+     value in OCTETs represents both the entity-length and the
      transfer-length. The Content-Length header field &MUST-NOT; be sent
      if these two lengths are different (i.e., if a Transfer-Encoding
@@ -2243 +2243 @@
 <t>
    The entity-header field "Content-Length" indicates the size of the
-   entity-body, in decimal number of OCTETs, sent to the recipient or,
+   entity-body, in number of OCTETs, sent to the recipient or,
    in the case of the HEAD method, the size of the entity-body that
    would have been sent had the request been a GET.
@@ -4910 +4910 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
+      "base for numeric protocol elements"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/162"/>:
       "comment ABNF"

draft-ietf-httpbis/latest/p5-range.html

@@ -467 +467 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">May 1, 2009</td>
+            <td class="header right">May 6, 2009</td>
          </tr>
       </table>
@@ -724 +724 @@
       </p>
       <p id="rfc.section.5.2.p.6">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
-         selected resource as a decimal number. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
+         selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
       </p>
       <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
@@ -808 +808 @@
   <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
 </pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
-         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are
-         decimal and start at zero.
+         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
+         at zero.
       </p>
       <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
@@ -820 +820 @@
       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
   <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
-</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the decimal suffix-length
-         value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length,
-         the entire entity-body is used.
+</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That
+         is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
+         entire entity-body is used.
       </p>
       <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
@@ -1227 +1227 @@
       </ul>
       <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
+      <p id="rfc.section.D.8.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> 

draft-ietf-httpbis/latest/p5-range.xml

@@ -548 +548 @@
    satisfiable) &SHOULD; include a Content-Range field with a byte-range-resp-spec
    of "*". The instance-length specifies the current length of
-   the selected resource as a decimal number. A response with status code 206 (Partial
+   the selected resource. A response with status code 206 (Partial
    Content) &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
 </t>
@@ -721 +721 @@
    of the first byte in a range. The last-byte-pos value gives the
    byte-offset of the last byte in the range; that is, the byte
-   positions specified are inclusive. Byte offsets are decimal and start at zero.
+   positions specified are inclusive. Byte offsets start at zero.
 </t>
 <t>
@@ -746 +746 @@
 <t>
    A suffix-byte-range-spec is used to specify the suffix of the
-   entity-body, of a length given by the decimal suffix-length value. (That is,
+   entity-body, of a length given by the suffix-length value. (That is,
    this form specifies the last N bytes of an entity-body.) If the
    entity is shorter than the specified suffix-length, the entire
@@ -1585 +1585 @@
 <section title="Since draft-ietf-httpbis-p5-range-06" anchor="changes.since.06">
 <t>
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
+      "base for numeric protocol elements"
+    </t>
+  </list>
 </t>
 </section>

draft-ietf-httpbis/latest/p6-cache.html

@@ -965 +965 @@
   <a href="#header.age" class="smpl">Age-v</a> = <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
 </pre><div id="rule.delta-seconds">
-         <p id="rfc.section.3.1.p.3">  Age field-values are non-negative decimal integers, representing time in seconds.</p>
+         <p id="rfc.section.3.1.p.3">  Age field-values are non-negative integers, representing time in seconds.</p>
       </div>
       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
@@ -1706 +1706 @@
       </ul>
       <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></h2>
+      <p id="rfc.section.C.8.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> 

draft-ietf-httpbis/latest/p6-cache.xml

@@ -895 +895 @@
 <t anchor="rule.delta-seconds">
   <x:anchor-alias value="delta-seconds" />
-  Age field-values are non-negative decimal integers, representing time in seconds.
+  Age field-values are non-negative integers, representing time in seconds.
 </t>
 <figure><artwork type="abnf2616"><iref item="Grammar" primary="true" subitem="delta-seconds" />
@@ -2308 +2308 @@
 <section anchor="changes.since.06" title="Since draft-ietf-httpbis-p6-cache-06">
 <t>
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
+      "base for numeric protocol elements"
+    </t>
+  </list>
 </t>
 </section>