Ignore:
Timestamp:
04/08/10 15:03:20 (10 years ago)
Author:
julian.reschke@…
Message:

regen HTML using latest version of xslt

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/orig/rfc5234.html

    r598 r978  
    3737}
    3838
    39 dl.empty dd {
     39ul.empty {
     40  list-style-type: none;
     41}
     42ul.empty li {
    4043  margin-top: .5em;
    4144}
     
    118121}
    119122table.header {
     123  border-spacing: 1px;
    120124  width: 95%;
    121125  font-size: 10pt;
     
    129133  white-space: nowrap;
    130134}
    131 td.header {
     135table.header td {
    132136  background-color: gray;
    133137  width: 50%;
    134138}
    135 td.header a {
     139table.header a {
    136140  color: white;
    137141}
     
    305309      <link rel="Alternate" title="Authorative ASCII Version" href="http://www.ietf.org/rfc/rfc5234.txt">
    306310      <link rel="Help" title="Additional Information on tools.ietf.org" href="http://tools.ietf.org/html/rfc5234">
    307       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.438, 2009-05-27 13:34:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     311      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.520, 2010-07-14 12:36:35, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    308312      <meta name="keywords" content="ABNF, Augmented, Backus-Naur, Form, electronic, mail">
    309       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    310       <meta name="DC.Creator" content="Crocker, D.">
    311       <meta name="DC.Creator" content="Overell, P.">
    312       <meta name="DC.Identifier" content="urn:ietf:rfc:5234">
    313       <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-01">
    314       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:4234">
    315       <meta name="DC.Description.Abstract" content="Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order- independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.">
    316       <meta name="DC.isPartOf" content="urn:ISSN:2070-1721">
     313      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     314      <meta name="dct.creator" content="Crocker, D.">
     315      <meta name="dct.creator" content="Overell, P.">
     316      <meta name="dct.identifier" content="urn:ietf:rfc:5234">
     317      <meta name="dct.issued" scheme="ISO8601" content="2008-01">
     318      <meta name="dct.replaces" content="urn:ietf:rfc:4234">
     319      <meta name="dct.abstract" content="Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order- independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.">
     320      <meta name="dct.isPartOf" content="urn:issn:2070-1721">
     321      <meta name="description" content="Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order- independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.">
    317322   </head>
    318323   <body>
    319       <!--WARNING: document uses ABNF syntax, but doesn't reference RFC 2234, 4234 or 5234.-->
    320       <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
    321          <tr>
    322             <td class="header left">Network Working Group</td>
    323             <td class="header right">D. Crocker, Editor</td>
    324          </tr>
    325          <tr>
    326             <td class="header left">Request for Comments: 5234</td>
    327             <td class="header right">Brandenburg InternetWorking</td>
    328          </tr>
    329          <tr>
    330             <td class="header left">Obsoletes:
    331                <!--WARNING: front matter mentions RFC 4234 for which there is no reference element--><a href="http://tools.ietf.org/html/rfc4234">4234</a></td>
    332             <td class="header right">P. Overell</td>
    333          </tr>
    334          <tr>
    335             <td class="header left">STD: 68</td>
    336             <td class="header right">THUS plc.</td>
    337          </tr>
    338          <tr>
    339             <td class="header left">Category: Standards Track</td>
    340             <td class="header right">January 2008</td>
    341          </tr>
     324      <table class="header">
     325         <tbody>
     326            <tr>
     327               <td class="left">Network Working Group</td>
     328               <td class="right">D. Crocker, Editor</td>
     329            </tr>
     330            <tr>
     331               <td class="left">Request for Comments: 5234</td>
     332               <td class="right">Brandenburg InternetWorking</td>
     333            </tr>
     334            <tr>
     335               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc4234">4234</a></td>
     336               <td class="right">P. Overell</td>
     337            </tr>
     338            <tr>
     339               <td class="left">STD: 68</td>
     340               <td class="right">THUS plc.</td>
     341            </tr>
     342            <tr>
     343               <td class="left">Category: Standards Track</td>
     344               <td class="right">January 2008</td>
     345            </tr>
     346         </tbody>
    342347      </table>
    343348      <p class="title">Augmented BNF for Syntax Specifications: ABNF</p>
     
    394399         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    395400      </ul>
    396       <hr class="noprint">
    397401      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction
    398402      </h1>
     
    408412         separate from its formal status.
    409413      </p>
    410       <hr class="noprint">
    411       <h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;Rule Definition
     414      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Rule Definition
    412415      </h1>
    413416      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;Rule Naming
     
    479482</pre>  <p>will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC", and "ABC".</p>
    480483      <p id="rfc.section.2.3.p.10"> </p>
    481       <dl class="empty">
    482          <dd>To specify a rule that is case sensitive, specify the characters individually.</dd>
    483       </dl>
     484      <ul class="empty">
     485         <li>To specify a rule that is case sensitive, specify the characters individually.</li>
     486      </ul>
    484487      <div id="rfc.figure.u.8"></div>
    485488      <p>For example:</p>  <pre>
     
    499502         syntax.
    500503      </p>
    501       <hr class="noprint">
    502       <h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a>&nbsp;Operators
     504      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Operators
    503505      </h1>
    504506      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Concatenation:  Rule1 Rule2
     
    519521      </p>
    520522      <p id="rfc.section.3.1.p.5">NOTE: </p>
    521       <dl class="empty">
    522          <dd>This specification for ABNF does not provide for implicit specification of linear white space.</dd>
    523       </dl>
     523      <ul class="empty">
     524         <li>This specification for ABNF does not provide for implicit specification of linear white space.</li>
     525      </ul>
    524526      <p id="rfc.section.3.1.p.6">Any grammar that wishes to permit linear white space around delimiters or string segments must specify it explicitly. It is
    525527         often useful to provide for such white space in "core" rules that are then used variously among higher-level rules. The "core"
     
    618620         (loosest) at the bottom:
    619621      </p>
    620       <dl class="empty">
    621          <dd>Rule name, prose-val, Terminal value</dd>
    622          <dd>Comment</dd>
    623          <dd>Value range</dd>
    624          <dd>Repetition</dd>
    625          <dd>Grouping, Optional</dd>
    626          <dd>Concatenation</dd>
    627          <dd>Alternative</dd>
    628       </dl>
     622      <ul class="empty">
     623         <li>Rule name, prose-val, Terminal value</li>
     624         <li>Comment</li>
     625         <li>Value range</li>
     626         <li>Repetition</li>
     627         <li>Grouping, Optional</li>
     628         <li>Concatenation</li>
     629         <li>Alternative</li>
     630      </ul>
    629631      <p id="rfc.section.3.10.p.2">Use of the alternative operator, freely mixed with concatenations, can be confusing.</p>
    630632      <p id="rfc.section.3.10.p.3"> </p>
    631       <dl class="empty">
    632          <dd>Again, it is recommended that the grouping operator be used to make explicit concatenation groups.</dd>
    633       </dl>
    634       <hr class="noprint">
    635       <h1 id="rfc.section.4" class="np"><a href="#rfc.section.4">4.</a>&nbsp;ABNF Definition of ABNF
     633      <ul class="empty">
     634         <li>Again, it is recommended that the grouping operator be used to make explicit concatenation groups.</li>
     635      </ul>
     636      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;ABNF Definition of ABNF
    636637      </h1>
    637638      <p id="rfc.section.4.p.1"> </p>
     
    710711                             ;  without angles
    711712                             ; prose description, to be used as
    712                              ;  last resort </pre> <hr class="noprint">
    713       <h1 id="rfc.section.5" class="np"><a href="#rfc.section.5">5.</a>&nbsp;Security Considerations
     713                             ;  last resort </pre> <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;Security Considerations
    714714      </h1>
    715715      <p id="rfc.section.5.p.1">Security is truly believed to be irrelevant to this document.</p>
    716       <hr class="noprint">
    717       <h1 id="rfc.references" class="np"><a id="rfc.section.6" href="#rfc.section.6">6.</a> References
     716      <h1 id="rfc.references"><a id="rfc.section.6" href="#rfc.section.6">6.</a> References
    718717      </h1>
    719       <h2 class="np" id="rfc.references.1"><a href="#rfc.section.6.1" id="rfc.section.6.1">6.1</a> Normative References
    720       </h2>
    721       <table summary="Normative References"
     718      <h2 id="rfc.references.1"><a href="#rfc.section.6.1" id="rfc.section.6.1">6.1</a> Normative References
     719      </h2>
     720      <table
    722721         <tr>
    723722            <td class="reference"><b id="US-ASCII">[US-ASCII]</b></td>
     
    729728      <h2 id="rfc.references.2"><a href="#rfc.section.6.2" id="rfc.section.6.2">6.2</a> Informative References
    730729      </h2>
    731       <table summary="Informative References">   
     730      <table>   
    732731         <tr>
    733732            <td class="reference"><b id="RFC733">[RFC733]</b></td>
     
    737736         <tr>
    738737            <td class="reference"><b id="RFC822">[RFC822]</b></td>
    739             <td class="top"><a href="mailto:DCrocker@UDel-Relay" title="University of Delaware, Dept. of Electrical&#xA;                     Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD&nbsp;11, RFC&nbsp;822, August&nbsp;1982.
     738            <td class="top"><a href="mailto:DCrocker@UDel-Relay" title="University of Delaware, Dept. of Electrical&#xA;                     Engineering">Crocker, D.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD&nbsp;11, RFC&nbsp;822, August&nbsp;1982.
    740739            </td>
    741740         </tr>
    742741      </table>
    743       <hr class="noprint">
    744       <h1 id="rfc.authors" class="np"><a href="#rfc.authors">Authors' Addresses</a></h1>
    745       <address class="vcard"><span class="vcardline"><span class="fn">Dave Crocker</span>
    746             (editor)
    747             <span class="n hidden"><span class="family-name">Crocker</span><span class="given-name">Dave</span></span></span><span class="org vcardline">Brandenburg InternetWorking</span><span class="adr"><span class="street-address vcardline">675 Spruce Dr.</span><span class="vcardline"><span class="locality">Sunnyvale</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94086</span></span><span class="country-name vcardline">US</span></span><span class="vcardline tel">Phone: <a href="tel:+1.408.246.8253"><span class="value">+1.408.246.8253</span></a></span><span class="vcardline">Email: <a href="mailto:dcrocker@bbiw.net"><span class="email">dcrocker@bbiw.net</span></a></span></address>
    748       <address class="vcard"><span class="vcardline"><span class="fn">Paul Overell</span><span class="n hidden"><span class="family-name">Overell</span><span class="given-name">Paul</span></span></span><span class="org vcardline">THUS plc.</span><span class="adr"><span class="street-address vcardline">1/2 Berkeley Square, </span><span class="street-address vcardline">99 Berkeley Street</span><span class="vcardline"><span class="locality">Glasgow</span>, <span class="postal-code">G3 7HR</span></span><span class="country-name vcardline">UK</span></span><span class="vcardline">Email: <a href="mailto:paul.overell@thus.net"><span class="email">paul.overell@thus.net</span></a></span></address>
    749       <hr class="noprint">
     742      <div class="avoidbreak">
     743         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     744         <address class="vcard"><span class="vcardline"><span class="fn">Dave Crocker</span>
     745               (editor)
     746               <span class="n hidden"><span class="family-name">Crocker</span><span class="given-name">Dave</span></span></span><span class="org vcardline">Brandenburg InternetWorking</span><span class="adr"><span class="street-address vcardline">675 Spruce Dr.</span><span class="vcardline"><span class="locality">Sunnyvale</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94086</span></span><span class="country-name vcardline">US</span></span><span class="vcardline tel">Phone: <a href="tel:+1.408.246.8253"><span class="value">+1.408.246.8253</span></a></span><span class="vcardline">Email: <a href="mailto:dcrocker@bbiw.net"><span class="email">dcrocker@bbiw.net</span></a></span></address>
     747         <address class="vcard"><span class="vcardline"><span class="fn">Paul Overell</span><span class="n hidden"><span class="family-name">Overell</span><span class="given-name">Paul</span></span></span><span class="org vcardline">THUS plc.</span><span class="adr"><span class="street-address vcardline">1/2 Berkeley Square,</span><span class="street-address vcardline">99 Berkeley Street</span><span class="vcardline"><span class="locality">Glasgow</span>, <span class="postal-code">G3 7HR</span></span><span class="country-name vcardline">UK</span></span><span class="vcardline">Email: <a href="mailto:paul.overell@thus.net"><span class="email">paul.overell@thus.net</span></a></span></address>
     748      </div>
    750749      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;Acknowledgements
    751750      </h1>
     
    765764      </p>
    766765      <p id="rfc.section.A.p.4">Julian Reschke warrants a special thanks for converting the Draft Standard version to XML source form.</p>
    767       <hr class="noprint">
    768       <h1 id="rfc.section.B" class="np"><a href="#rfc.section.B">B.</a>&nbsp;<a id="CORE" href="#CORE">Core ABNF of ABNF</a></h1>
     766      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="CORE" href="#CORE">Core ABNF of ABNF</a></h1>
    769767      <p id="rfc.section.B.p.1">This appendix contains some basic rules that are in common use. Basic rules are in uppercase. Note that these rules are only
    770768         valid for ABNF encoded in 7-bit ASCII or in characters sets that are a superset of 7-bit ASCII.
     
    832830      </p>
    833831      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     832      <p>Copyright © The IETF Trust (2008).</p>
    834833      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    835834         authors retain all their rights.
     
    840839         WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    841840      </p>
    842       <hr class="noprint">
    843       <h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
     841      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    844842      <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
    845843         be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
     
    850848      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    851849         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    852          of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
     850         of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
    853851      </p>
    854852      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
Note: See TracChangeset for help on using the changeset viewer.