Ignore:
Timestamp:
Jun 23, 2012, 5:01:38 AM (7 years ago)
Author:
julian.reschke@…
Message:

Simplify use of "Note:", make upper/lowercase of sentence start consistent; use "—" where appropriate

File:
1 edited

Legend:

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

    r1689 r1692  
    1616  <!ENTITY ID-YEAR "2012">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1819  <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1920  <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    15421543<x:note>
    15431544  <t>
    1544     <x:h>Note:</x:h> In HTTP/1.0, only the status codes 301 (Moved Permanently)
     1545    &Note; In HTTP/1.0, only the status codes 301 (Moved Permanently)
    15451546    and 302 (Found) were defined for the first type of redirect, and the second
    15461547    type did not exist at all (<xref target="RFC1945" x:fmt="," x:sec="9.3"/>).
     
    15731574<x:note>
    15741575  <t>
    1575     <x:h>Note:</x:h> An earlier version of this specification recommended a
     1576    &Note; An earlier version of this specification recommended a
    15761577    maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>).
    15771578    Content developers need to be aware that some clients might
     
    16331634<x:note>
    16341635  <t>
    1635     <x:h>Note:</x:h> For historic reasons, user agents &MAY; change the
     1636    &Note; For historic reasons, user agents &MAY; change the
    16361637    request method from POST to GET for the subsequent request. If this
    16371638    behavior is undesired, status code 307 (Temporary Redirect) can be used
     
    16561657<x:note>
    16571658  <t>
    1658     <x:h>Note:</x:h> For historic reasons, user agents &MAY; change the
     1659    &Note; For historic reasons, user agents &MAY; change the
    16591660    request method from POST to GET for the subsequent request. If this
    16601661    behavior is undesired, status code 307 (Temporary Redirect) can be used
     
    17391740<x:note>
    17401741  <t>
    1741     <x:h>Note:</x:h> This status code is similar to 302 Found, except that
     1742    &Note; This status code is similar to 302 Found, except that
    17421743    it does not allow rewriting the request method from POST to GET. This
    17431744    specification defines no equivalent counterpart for 301 Moved Permanently
     
    18381839<x:note>
    18391840  <t>
    1840     <x:h>Note:</x:h> HTTP/1.1 servers are allowed to return responses which are
     1841    &Note; HTTP/1.1 servers are allowed to return responses which are
    18411842    not acceptable according to the accept header fields sent in the
    18421843    request. In some cases, this might even be preferable to sending a
     
    20632064<x:note>
    20642065  <t>
    2065     <x:h>Note:</x:h> The existence of the 503 status code does not imply that a
     2066    &Note; The existence of the 503 status code does not imply that a
    20662067    server has to use it when becoming overloaded. Some servers might wish
    20672068    to simply refuse the connection.
     
    22342235<x:note>
    22352236  <t>
    2236     <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in
     2237    &Note; Recipients of date values are encouraged to be robust in
    22372238    accepting date values that might have been sent by non-HTTP
    22382239    applications, as is sometimes the case when retrieving or posting
     
    22422243<x:note>
    22432244  <t>
    2244     <x:h>Note:</x:h> HTTP requirements for the date/time stamp format apply only
     2245    &Note; HTTP requirements for the date/time stamp format apply only
    22452246    to their usage within the protocol stream. Clients and servers are
    22462247    not required to use these formats for user presentation, request
     
    25002501<x:note>
    25012502  <t>
    2502     <x:h>Note:</x:h> The "multipart/form-data" type has been specifically defined
     2503    &Note; The "multipart/form-data" type has been specifically defined
    25032504    for carrying form data suitable for processing via the POST
    25042505    request method, as described in <xref target="RFC2388"/>.
     
    28672868<x:note>
    28682869  <t>
    2869     <x:h>Note:</x:h> In practice, User-Agent based negotiation is fragile,
     2870    &Note; In practice, User-Agent based negotiation is fragile,
    28702871    because new clients might not be recognized.
    28712872  </t>
     
    29622963<x:note>
    29632964  <t>
    2964     <x:h>Note:</x:h> Use of the "q" parameter name to separate media type
     2965    &Note; Use of the "q" parameter name to separate media type
    29652966    parameters from Accept extension parameters is due to historical
    29662967    practice. Although this prevents any media type parameter named
     
    30443045</texttable>
    30453046<t>
    3046       <x:h>Note:</x:h> A user agent might be provided with a default set of quality
    3047       values for certain media ranges. However, unless the user agent is
    3048       a closed system which cannot interact with other rendering agents,
    3049       this default set ought to be configurable by the user.
     3047   &Note; A user agent might be provided with a default set of quality
     3048   values for certain media ranges. However, unless the user agent is
     3049   a closed system which cannot interact with other rendering agents,
     3050   this default set ought to be configurable by the user.
    30503051</t>
    30513052</section>
     
    31613162<x:note>
    31623163  <t>
    3163     <x:h>Note:</x:h> Most HTTP/1.0 applications do not recognize or obey qvalues
     3164    &Note; Most HTTP/1.0 applications do not recognize or obey qvalues
    31643165    associated with content-codings. This means that qvalues will not
    31653166    work and are not permitted with x-gzip or x-compress.
     
    32053206<x:note>
    32063207  <t>
    3207     <x:h>Note:</x:h> The "Basic Filtering" scheme (<xref target="RFC4647"
     3208    &Note; The "Basic Filtering" scheme (<xref target="RFC4647"
    32083209    x:fmt="," x:sec="3.3.1"/>) is identical to the matching scheme that was
    32093210    previously defined in <xref target="RFC2616" x:fmt="of" x:sec="14.4"/>.
     
    32253226<x:note>
    32263227  <t>
    3227     <x:h>Note:</x:h> When making the choice of linguistic preference available to
     3228    &Note; When making the choice of linguistic preference available to
    32283229    the user, we remind implementors of  the fact that users are not
    32293230    familiar with the details of language matching as described above,
     
    36933694<x:note>
    36943695  <t>
    3695     <x:h>Note:</x:h> Some recipients attempt to recover from Location fields
     3696    &Note; Some recipients attempt to recover from Location fields
    36963697    that are not valid URI references. This specification does not mandate or
    36973698    define such processing, but does allow it (see <xref target="intro.conformance.and.error.handling"/>).
     
    37063707<x:note>
    37073708  <t>
    3708     <x:h>Note:</x:h> The Content-Location header field (&header-content-location;) differs
     3709    &Note; The Content-Location header field (&header-content-location;) differs
    37093710    from Location in that the Content-Location identifies the most specific
    37103711    resource corresponding to the enclosed representation.
     
    38563857<x:note>
    38573858  <t>
    3858     <x:h>Note:</x:h> Revealing the specific software version of the server might
     3859    &Note; Revealing the specific software version of the server might
    38593860    allow the server machine to become more vulnerable to attacks
    38603861    against software that is known to contain security holes. Server
Note: See TracChangeset for help on using the changeset viewer.