Changeset 2534

Timestamp:

04/01/14 02:07:15 (8 years ago)

Author:

fielding@…

Message:

another attempt to rephrase [2528] to be more understandable by non-spec-authors; see #540

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (1 diff)
• p1-messaging.xml (modified) (1 diff)

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

@@ -1286 +1286 @@
             </p>
             <p id="rfc.section.3.2.p.4">Since messages are parsed using a generic algorithm, independent of the individual header field names, the contents within
-               a given field-value are not parsed until a later stage of message interpretation (usually after the message's entire header
-               section has been processed). Consequently, this specification does not use specific ABNF rules to define each "Field-Name:
-               Field Value" pair, as was done in previous editions. Instead, this specification defines each of its header fields using an
-               ABNF rule that is named according to the registered field-name and that defines only the syntax within the field-value (i.e.,
-               after it has been extracted from the header section by a generic field parser).
+               a given field value are not parsed until a later stage of message interpretation (usually after the message's entire header
+               section has been processed). Consequently, this specification does not use ABNF rules to define the "Field-Name: Field Value"
+               pair, as was done in previous editions. Instead, this specification uses ABNF rules which are named according to each registered
+               field name, wherein the rule defines the valid grammar for that field's corresponding field values (i.e., after the field-value
+               has been extracted from the header section by a generic field parser).
             </p>
             <div id="field.extensibility">

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

@@ -1237 +1237 @@
 <t>
    Since messages are parsed using a generic algorithm, independent of the
-   individual header field names, the contents within a given field-value are
+   individual header field names, the contents within a given field value are
    not parsed until a later stage of message interpretation (usually after the
    message's entire header section has been processed).
-   Consequently, this specification does not use specific ABNF rules to define
-   each "Field-Name: Field Value" pair, as was done in previous editions.
-   Instead, this specification defines each of its header fields using an ABNF
-   rule that is named according to the registered field-name and that defines
-   only the syntax within the field-value (i.e., after it has been extracted
-   from the header section by a generic field parser).
+   Consequently, this specification does not use ABNF rules to define the
+   "Field-Name: Field Value" pair, as was done in previous editions.
+   Instead, this specification uses ABNF rules which are named according to
+   each registered field name, wherein the rule defines the valid grammar for
+   that field's corresponding field values (i.e., after the field-value
+   has been extracted from the header section by a generic field parser).
 </t>