Changeset 367 for draft-ietf-httpbis

Timestamp:

13/11/08 19:00:16 (12 years ago)

Author:

julian.reschke@…

Message:

fix typo (related to #36)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (6 diffs)
• p1-messaging.xml (modified) (2 diffs)

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

@@ -796 +796 @@
       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.LWS" class="smpl">LWS</a>            = [<a href="#core.rules" class="smpl">CRLF</a>] 1*<a href="#core.rules" class="smpl">WSP</a>
 </pre><div id="rule.whitespace">
-         <p id="rfc.section.2.2.p.5">         <span class="comment">[rfc.comment.2: Add prose introducing the different kinds of WS.]</span>  
-         </p>
-         <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#rule.whitespace" class="smpl">OWS</a>            = 1*( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> )
+         <p id="rfc.section.2.2.p.5">        </p>
+      </div>
+      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#rule.whitespace" class="smpl">OWS</a>            = *( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> )
                  ; "optional" white space
   <a href="#rule.whitespace" class="smpl">RWS</a>            = 1*( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> )
@@ -805 +805 @@
                  ; "bad" white space
   <a href="#rule.whitespace" class="smpl">obs-fold</a>       = <a href="#core.rules" class="smpl">CRLF</a>
-                 ; <span class="comment">[rfc.comment.3: to be explained: do not produce]</span>
-</pre></div>
-      <div id="rule.TEXT">
-         <p id="rfc.section.2.2.p.6">  The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message
+                 ; <span class="comment">[rfc.comment.2: to be explained: do not produce]</span>
+</pre><div id="rule.TEXT">
+         <p id="rfc.section.2.2.p.7">  The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message
             parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than ISO-8859-1 <a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a> only when encoded according to the rules of <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a>.
          </p>
@@ -814 +813 @@
       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#rule.TEXT" class="smpl">TEXT</a>           = %x20-7E / %x80-FF / <a href="#rule.LWS" class="smpl">LWS</a>
                  ; any <a href="#core.rules" class="smpl">OCTET</a> except <a href="#core.rules" class="smpl">CTL</a>s, but including <a href="#rule.LWS" class="smpl">LWS</a>
-</pre><p id="rfc.section.2.2.p.8">A CRLF is allowed in the definition of TEXT only as part of a header field continuation. It is expected that the folding LWS
+</pre><p id="rfc.section.2.2.p.9">A CRLF is allowed in the definition of TEXT only as part of a header field continuation. It is expected that the folding LWS
          will be replaced with a single SP before interpretation of the TEXT value.
       </p>
       <div id="rule.token.separators">
-         <p id="rfc.section.2.2.p.9">      Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>).
+         <p id="rfc.section.2.2.p.10">      Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>).
          </p>
       </div>
@@ -833 +832 @@
   <a href="#rule.token.separators" class="smpl">token</a>          = 1*<a href="#rule.token.separators" class="smpl">tchar</a>
 </pre><div id="rule.comment">
-         <p id="rfc.section.2.2.p.11">    Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
+         <p id="rfc.section.2.2.p.12">    Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
             in fields containing "comment" as part of their field value definition. In all other fields, parentheses are considered part
             of the field value.
@@ -841 +840 @@
   <a href="#rule.comment" class="smpl">ctext</a>          = &lt;any <a href="#rule.TEXT" class="smpl">TEXT</a> excluding "(" and ")"&gt;
 </pre><div id="rule.quoted-string">
-         <p id="rfc.section.2.2.p.13">    A string of text is parsed as a single word if it is quoted using double-quote marks.</p>
+         <p id="rfc.section.2.2.p.14">    A string of text is parsed as a single word if it is quoted using double-quote marks.</p>
       </div>
       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#rule.quoted-string" class="smpl">quoted-string</a>  = ( <a href="#core.rules" class="smpl">DQUOTE</a> *(<a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a> )
   <a href="#rule.quoted-string" class="smpl">qdtext</a>         = &lt;any <a href="#rule.TEXT" class="smpl">TEXT</a> excluding <a href="#core.rules" class="smpl">DQUOTE</a> and "\"&gt;
 </pre><div id="rule.quoted-pair">
-         <p id="rfc.section.2.2.p.15">    The backslash character ("\") <em class="bcp14">MAY</em> be used as a single-character quoting mechanism only within quoted-string and comment constructs.
+         <p id="rfc.section.2.2.p.16">    The backslash character ("\") <em class="bcp14">MAY</em> be used as a single-character quoting mechanism only within quoted-string and comment constructs.
          </p>
       </div>
@@ -1159 +1158 @@
                    ; and consisting of either *<a href="#rule.TEXT" class="smpl">TEXT</a> or combinations
                    ; of <a href="#rule.token.separators" class="smpl">token</a>, <a href="#rule.token.separators" class="smpl">separators</a>, and <a href="#rule.quoted-string" class="smpl">quoted-string</a>
-</pre><p id="rfc.section.4.2.p.3"> <span class="comment">[rfc.comment.4: whitespace between field-name and colon is an error and MUST NOT be accepted]</span> 
+</pre><p id="rfc.section.4.2.p.3"> <span class="comment">[rfc.comment.3: whitespace between field-name and colon is an error and MUST NOT be accepted]</span> 
       </p>
       <p id="rfc.section.4.2.p.4">The field-content does not include any leading or trailing LWS: linear white space occurring before the first non-whitespace

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

@@ -515 +515 @@
   <x:anchor-alias value="RWS"/>
   <x:anchor-alias value="obs-fold"/>
-  <cref>Add prose introducing the different kinds of WS.</cref>
+  
+</t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OWS"/><iref primary="true" item="Grammar" subitem="RWS"/><iref primary="true" item="Grammar" subitem="BWS"/>
-  <x:ref>OWS</x:ref>            = 1*( [ obs-fold ] <x:ref>WSP</x:ref> )
+  <x:ref>OWS</x:ref>            = *( [ obs-fold ] <x:ref>WSP</x:ref> )
                  ; "optional" white space
   <x:ref>RWS</x:ref>            = 1*( [ obs-fold ] <x:ref>WSP</x:ref> )
@@ -526 +527 @@
                  ; <cref>to be explained: do not produce</cref>
 </artwork></figure>
-</t>
 <t anchor="rule.TEXT">
   <x:anchor-alias value="TEXT"/>