Ignore:
Timestamp:
04/01/14 02:07:15 (7 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:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2533 r2534  
    12861286            </p>
    12871287            <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
    1288                a given field-value are not parsed until a later stage of message interpretation (usually after the message's entire header
    1289                section has been processed). Consequently, this specification does not use specific ABNF rules to define each "Field-Name:
    1290                Field Value" pair, as was done in previous editions. Instead, this specification defines each of its header fields using an
    1291                ABNF rule that is named according to the registered field-name and that defines only the syntax within the field-value (i.e.,
    1292                after it has been extracted from the header section by a generic field parser).
     1288               a given field value are not parsed until a later stage of message interpretation (usually after the message's entire header
     1289               section has been processed). Consequently, this specification does not use ABNF rules to define the "Field-Name: Field Value"
     1290               pair, as was done in previous editions. Instead, this specification uses ABNF rules which are named according to each registered
     1291               field name, wherein the rule defines the valid grammar for that field's corresponding field values (i.e., after the field-value
     1292               has been extracted from the header section by a generic field parser).
    12931293            </p>
    12941294            <div id="field.extensibility">
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2533 r2534  
    12371237<t>
    12381238   Since messages are parsed using a generic algorithm, independent of the
    1239    individual header field names, the contents within a given field-value are
     1239   individual header field names, the contents within a given field value are
    12401240   not parsed until a later stage of message interpretation (usually after the
    12411241   message's entire header section has been processed).
    1242    Consequently, this specification does not use specific ABNF rules to define
    1243    each "Field-Name: Field Value" pair, as was done in previous editions.
    1244    Instead, this specification defines each of its header fields using an ABNF
    1245    rule that is named according to the registered field-name and that defines
    1246    only the syntax within the field-value (i.e., after it has been extracted
    1247    from the header section by a generic field parser).
     1242   Consequently, this specification does not use ABNF rules to define the
     1243   "Field-Name: Field Value" pair, as was done in previous editions.
     1244   Instead, this specification uses ABNF rules which are named according to
     1245   each registered field name, wherein the rule defines the valid grammar for
     1246   that field's corresponding field values (i.e., after the field-value
     1247   has been extracted from the header section by a generic field parser).
    12481248</t>
    12491249
Note: See TracChangeset for help on using the changeset viewer.