Changeset 378


Ignore:
Timestamp:
Nov 14, 2008, 11:06:21 AM (11 years ago)
Author:
julian.reschke@…
Message:

add note about future ABNF appendix containing flattened list rules (related to #36)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed

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

    r376 r378  
    747747         at least one non-null element <em class="bcp14">MUST</em> be present. Default values are 0 and infinity so that "#element" allows any number, including zero; "1#element" requires at
    748748         least one; and "1#2element" allows one or two.
     749      </p>
     750      <p id="rfc.section.2.1.p.5"> <span class="comment">[abnf.list: At a later point of time, we may want to add an appendix containing the whole ABNF, with the list rules expanded to strict
     751            RFC 5234 notation.]</span>
    749752      </p>
    750753      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="basic.rules" href="#basic.rules">Basic Rules</a></h2>

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

    r376 r378  
    421421    two.
    422422  </t>
     423  <t>
     424    <cref anchor="abnf.list">
     425      At a later point of time, we may want to add an appendix containing
     426      the whole ABNF, with the list rules expanded to strict RFC 5234
     427      notation.
     428    </cref>
     429  </t>
    423430</section>
    424431
Note: See TracChangeset for help on using the changeset viewer.