Ignore:
Timestamp:
Mar 3, 2012, 3:56:54 PM (8 years ago)
Author:
fielding@…
Message:

(editorial) Consistently use lowercase for ABNF rule names other than header fields

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1554 r1557  
    401401
    402402<section title="Method" anchor="method">
    403   <x:anchor-alias value="Method"/>
     403  <x:anchor-alias value="method"/>
    404404  <x:anchor-alias value="extension-method"/>
    405405<t>
    406    The Method token indicates the request method to be performed on the target
     406   The method token indicates the request method to be performed on the target
    407407   resource (&effective-request-uri;). The method is case-sensitive.
    408408</t>
    409 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/>
    410   <x:ref>Method</x:ref>         = <x:ref>token</x:ref>
     409<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
     410  <x:ref>method</x:ref>         = <x:ref>token</x:ref>
    411411</artwork></figure>
    412412<t>
     
    449449<section title="Method Registry" anchor="method.registry">
    450450<t>
    451   The HTTP Method Registry defines the name space for the Method token in the
     451  The HTTP Method Registry defines the name space for the method token in the
    452452  Request line of an HTTP request.
    453453</t>
     
    630630<t>
    631631   The response header fields allow the server to pass additional
    632    information about the response which cannot be placed in the Status-Line.
     632   information about the response which cannot be placed in the status-line.
    633633   These header fields give information about the server and about
    634634   further access to the target resource (&effective-request-uri;).
     
    654654
    655655<section title="Status Code and Reason Phrase" anchor="status.code.and.reason.phrase">
    656   <x:anchor-alias value="Reason-Phrase"/>
    657   <x:anchor-alias value="Status-Code"/>
     656  <x:anchor-alias value="reason-phrase"/>
     657  <x:anchor-alias value="status-code"/>
    658658  <x:anchor-alias value="extension-code"/>
    659659<t>
    660    The Status-Code element is a 3-digit integer result code of the attempt to
     660   The status-code element is a 3-digit integer result code of the attempt to
    661661   understand and satisfy the request.
    662662</t>
    663663<t>
    664    The Reason-Phrase is intended to give a short textual description of the
    665    Status-Code and is intended for a human user. The client does not need
    666    to examine or display the Reason-Phrase.
    667 </t>
    668 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Status-Code"/><iref primary="true" item="Grammar" subitem="extension-code"/><iref primary="true" item="Grammar" subitem="Reason-Phrase"/>
    669   <x:ref>Status-Code</x:ref>    = 3<x:ref>DIGIT</x:ref>
    670   <x:ref>Reason-Phrase</x:ref>  = *( <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )
     664   The reason-phrase is intended to give a short textual description of the
     665   status-code and is intended for a human user. The client does not need
     666   to examine or display the reason-phrase.
     667</t>
     668<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/><iref primary="true" item="Grammar" subitem="extension-code"/><iref primary="true" item="Grammar" subitem="reason-phrase"/>
     669  <x:ref>status-code</x:ref>    = 3<x:ref>DIGIT</x:ref>
     670  <x:ref>reason-phrase</x:ref>  = *( <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )
    671671</artwork></figure>
    672672<t>
     
    694694</t>
    695695<texttable align="left">
    696   <ttcol>Status-Code</ttcol>
    697   <ttcol>Reason-Phrase</ttcol>
     696  <ttcol>status-code</ttcol>
     697  <ttcol>reason-phrase</ttcol>
    698698  <ttcol>Defined in...</ttcol>
    699699 
     
    752752<section title="Status Code Registry" anchor="status.code.registry">
    753753<t>
    754   The HTTP Status Code Registry defines the name space for the Status-Code
    755   token in the Status-Line of an HTTP response.
     754  The HTTP Status Code Registry defines the name space for the status-code
     755  token in the status-line of an HTTP response.
    756756</t>
    757757<t>
     
    917917  </rdf:Description>
    918918  <iref primary="true" item="OPTIONS method" x:for-anchor=""/>
    919   <iref primary="true" item="Methods" subitem="OPTIONS" x:for-anchor=""/>
     919  <iref primary="true" item="methods" subitem="OPTIONS" x:for-anchor=""/>
    920920<t>
    921921   The OPTIONS method requests information about the
     
    976976  </rdf:Description>
    977977  <iref primary="true" item="GET method" x:for-anchor=""/>
    978   <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/>
     978  <iref primary="true" item="methods" subitem="GET" x:for-anchor=""/>
    979979<t>
    980980   The GET method requests transfer of a current representation of
     
    10241024  </rdf:Description>
    10251025  <iref primary="true" item="HEAD method" x:for-anchor=""/>
    1026   <iref primary="true" item="Methods" subitem="HEAD" x:for-anchor=""/>
     1026  <iref primary="true" item="methods" subitem="HEAD" x:for-anchor=""/>
    10271027<t>
    10281028   The HEAD method is identical to GET except that the server &MUST-NOT;
     
    10491049<section title="POST" anchor="POST">
    10501050  <iref primary="true" item="POST method" x:for-anchor=""/>
    1051   <iref primary="true" item="Methods" subitem="POST" x:for-anchor=""/>
     1051  <iref primary="true" item="methods" subitem="POST" x:for-anchor=""/>
    10521052<t>
    10531053   The POST method requests that the origin server accept the
     
    11051105<section title="PUT" anchor="PUT">
    11061106  <iref primary="true" item="PUT method" x:for-anchor=""/>
    1107   <iref primary="true" item="Methods" subitem="PUT" x:for-anchor=""/>
     1107  <iref primary="true" item="methods" subitem="PUT" x:for-anchor=""/>
    11081108<t>
    11091109   The PUT method requests that the state of the target resource
     
    12271227<section title="DELETE" anchor="DELETE">
    12281228  <iref primary="true" item="DELETE method" x:for-anchor=""/>
    1229   <iref primary="true" item="Methods" subitem="DELETE" x:for-anchor=""/>
     1229  <iref primary="true" item="methods" subitem="DELETE" x:for-anchor=""/>
    12301230<t>
    12311231   The DELETE method requests that the origin server delete the target
     
    12631263  </rdf:Description>
    12641264  <iref primary="true" item="TRACE method" x:for-anchor=""/>
    1265   <iref primary="true" item="Methods" subitem="TRACE" x:for-anchor=""/>
     1265  <iref primary="true" item="methods" subitem="TRACE" x:for-anchor=""/>
    12661266<t>
    12671267   The TRACE method requests a remote, application-layer loop-back
     
    12921292<section title="CONNECT" anchor="CONNECT">
    12931293  <iref primary="true" item="CONNECT method" x:for-anchor=""/>
    1294   <iref primary="true" item="Methods" subitem="CONNECT" x:for-anchor=""/>
     1294  <iref primary="true" item="methods" subitem="CONNECT" x:for-anchor=""/>
    12951295<t>
    12961296   The CONNECT method requests that the proxy establish a tunnel
     
    13721372<section title="Status Code Definitions" anchor="status.codes">
    13731373<t>
    1374    The first digit of the Status-Code defines the class of response. The
     1374   The first digit of the status-code defines the class of response. The
    13751375   last two digits do not have any categorization role. There are 5
    13761376   values for the first digit:
     
    13981398</t>
    13991399<t>
    1400    Each Status-Code is described below, including any metadata required
     1400   Each status-code is described below, including any metadata required
    14011401   in the response.
    14021402</t>
     
    14101410<t>
    14111411   This class of status code indicates a provisional response,
    1412    consisting only of the Status-Line and optional header fields, and is
     1412   consisting only of the status-line and optional header fields, and is
    14131413   terminated by an empty line. There are no required header fields for this
    14141414   class of status code. Since HTTP/1.0 did not define any 1xx status
     
    19371937  <iref primary="true" item="Status Codes" subitem="405 Method Not Allowed" x:for-anchor=""/>
    19381938<t>
    1939    The method specified in the Request-Line is not allowed for the target
     1939   The method specified in the request-line is not allowed for the target
    19401940   resource. The response &MUST; include an Allow header field containing a
    19411941   list of valid methods for the requested resource.
     
    24252425</t>
    24262426<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/>
    2427   <x:ref>Allow</x:ref> = #<x:ref>Method</x:ref>
     2427  <x:ref>Allow</x:ref> = #<x:ref>method</x:ref>
    24282428</artwork></figure>
    24292429<t>
     
    39863986<figure>
    39873987<artwork type="abnf" name="p2-semantics.parsed-abnf">
    3988 <x:ref>Allow</x:ref> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ]
     3988<x:ref>Allow</x:ref> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    39893989
    39903990<x:ref>BWS</x:ref> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
     
    40034003
    40044004<x:ref>Max-Forwards</x:ref> = 1*DIGIT
    4005 <x:ref>Method</x:ref> = token
    40064005
    40074006<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
    40084007
    40094008<x:ref>RWS</x:ref> = &lt;RWS, defined in [Part1], Section 3.2.1&gt;
    4010 <x:ref>Reason-Phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )
    40114009<x:ref>Referer</x:ref> = absolute-URI / partial-URI
    40124010<x:ref>Retry-After</x:ref> = HTTP-date / delta-seconds
    40134011
    40144012<x:ref>Server</x:ref> = product *( RWS ( product / comment ) )
    4015 <x:ref>Status-Code</x:ref> = 3DIGIT
    40164013
    40174014<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [Part1], Section 2.7&gt;
     
    40524049
    40534050<x:ref>mailbox</x:ref> = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;
     4051<x:ref>method</x:ref> = token
    40544052<x:ref>minute</x:ref> = 2DIGIT
    40554053<x:ref>month</x:ref> = %x4A.61.6E ; Jan
     
    40754073<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
    40764074
     4075<x:ref>reason-phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )
    40774076<x:ref>rfc1123-date</x:ref> = day-name "," SP date1 SP time-of-day SP GMT
    40784077<x:ref>rfc850-date</x:ref> = day-name-l "," SP date2 SP time-of-day SP GMT
    40794078
    40804079<x:ref>second</x:ref> = 2DIGIT
     4080<x:ref>status-code</x:ref> = 3DIGIT
    40814081
    40824082<x:ref>time-of-day</x:ref> = hour ":" minute ":" second
     
    40934093; Location defined but not used
    40944094; Max-Forwards defined but not used
    4095 ; Reason-Phrase defined but not used
    40964095; Referer defined but not used
    40974096; Retry-After defined but not used
    40984097; Server defined but not used
    4099 ; Status-Code defined but not used
    41004098; User-Agent defined but not used
     4099; reason-phrase defined but not used
     4100; status-code defined but not used
    41014101</artwork></figure></section>
    41024102<?ENDINC p2-semantics.abnf-appendix ?>
     
    43134313    <t>
    43144314      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/94"/>:
    4315       "Reason-Phrase BNF"
     4315      "reason-phrase BNF"
    43164316    </t>
    43174317  </list>
     
    45224522    <t>
    45234523      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/137"/>:
    4524       "duplicate ABNF for Reason-Phrase"
     4524      "duplicate ABNF for reason-phrase"
    45254525    </t>
    45264526    <t>
Note: See TracChangeset for help on using the changeset viewer.