Changeset 154 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

05/01/08 14:13:28 (13 years ago)

Author:

julian.reschke@…

Message:

Use names of RFC4234 (RFC5234) core rules (HTAB, DQUOTE); addresses #36.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (10 diffs)

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

@@ -670 +670 @@
       indentation of continuation lines is used to indicate a rule
       definition that spans more than one line. Certain basic rules are
-      in uppercase, such as SP, LWS, HT, CRLF, DIGIT, ALPHA, etc. Angle
+      in uppercase, such as SP, LWS, HTAB, CRLF, DIGIT, ALPHA, etc. Angle
       brackets are used within definitions whenever their presence will
       facilitate discerning the use of rule names.
@@ -806 +806 @@
 <x:anchor-alias value="LF"/>
 <x:anchor-alias value="SP"/>
-<x:anchor-alias value="HT"/>
+<x:anchor-alias value="HTAB"/>
 <x:anchor-alias value="CRLF"/>
 <x:anchor-alias value="LWS"/>
@@ -823 +823 @@
    is defined by ANSI X3.4-1986 <xref target="USASCII"/>.
 </t>
-<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OCTET"/><iref primary="true" item="Grammar" subitem="CHAR"/><iref primary="true" item="Grammar" subitem="UPALPHA"/><iref primary="true" item="Grammar" subitem="LOALPHA"/><iref primary="true" item="Grammar" subitem="ALPHA"/><iref primary="true" item="Grammar" subitem="DIGIT"/><iref primary="true" item="Grammar" subitem="CTL"/><iref primary="true" item="Grammar" subitem="CR"/><iref primary="true" item="Grammar" subitem="LF"/><iref primary="true" item="Grammar" subitem="SP"/><iref primary="true" item="Grammar" subitem="HT"/>
+<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OCTET"/><iref primary="true" item="Grammar" subitem="CHAR"/><iref primary="true" item="Grammar" subitem="UPALPHA"/><iref primary="true" item="Grammar" subitem="LOALPHA"/><iref primary="true" item="Grammar" subitem="ALPHA"/><iref primary="true" item="Grammar" subitem="DIGIT"/><iref primary="true" item="Grammar" subitem="CTL"/><iref primary="true" item="Grammar" subitem="CR"/><iref primary="true" item="Grammar" subitem="LF"/><iref primary="true" item="Grammar" subitem="SP"/><iref primary="true" item="Grammar" subitem="HTAB"/><iref primary="true" item="Grammar" subitem="DQUOTE"/>
   OCTET          = &lt;any 8-bit sequence of data&gt;
   CHAR           = &lt;any US-ASCII character (octets 0 - 127)&gt;
@@ -835 +835 @@
   LF             = &lt;US-ASCII LF, linefeed (10)&gt;
   SP             = &lt;US-ASCII SP, space (32)&gt;
-  HT             = &lt;US-ASCII HT, horizontal-tab (9)&gt;
-  &lt;"&gt;            = &lt;US-ASCII double-quote mark (34)&gt;
+  HTAB           = &lt;US-ASCII HT, horizontal-tab (9)&gt;
+  DQUOTE         = &lt;US-ASCII double-quote mark (34)&gt;
 </artwork></figure>
 <t>
@@ -855 +855 @@
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="LWS"/>
-  LWS            = [CRLF] 1*( SP | HT )
+  LWS            = [CRLF] 1*( SP | HTAB )
 </artwork></figure>
 <t>
@@ -889 +889 @@
   token          = 1*&lt;any CHAR except CTLs or separators&gt;
   separators     = "(" | ")" | "&lt;" | "&gt;" | "@"
-                 | "," | ";" | ":" | "\" | &lt;"&gt;
+                 | "," | ";" | ":" | "\" | DQUOTE
                  | "/" | "[" | "]" | "?" | "="
-                 | "{" | "}" | SP | HT
+                 | "{" | "}" | SP | HTAB
 </artwork></figure>
 <t>
@@ -909 +909 @@
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-string"/><iref primary="true" item="Grammar" subitem="qdtext"/>
-  quoted-string  = ( &lt;"&gt; *(qdtext | quoted-pair ) &lt;"&gt; )
-  qdtext         = &lt;any TEXT excluding &lt;"> and "\">
+  quoted-string  = ( DQUOTE *(qdtext | quoted-pair ) DQUOTE )
+  qdtext         = &lt;any TEXT excluding DQUOTE and "\">
 </artwork></figure>
 <t>
@@ -1357 +1357 @@
    of LWS, though a single SP is preferred. Header fields can be
    extended over multiple lines by preceding each extra line with at
-   least one SP or HT. Applications ought to follow "common form", where
+   least one SP or HTAB. Applications ought to follow "common form", where
    one is known or indicated, when generating HTTP constructs, since
    there might exist some implementations that fail to accept anything
@@ -3806 +3806 @@
    Clients &SHOULD; be tolerant in parsing the Status-Line and servers
    tolerant when parsing the Request-Line. In particular, they &SHOULD;
-   accept any amount of SP or HT characters between fields, even though
+   accept any amount of SP or HTAB characters between fields, even though
    only a single SP is required.
 </t>
@@ -4133 +4133 @@
       Update media type registrations to use RFC4288 template.
     </t>
+    <t>
+      Use names of RFC4234 core rules DQUOTE and HTAB (work in progress on <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>)
+    </t>
   </list>
 </t>