Ignore:
Timestamp:
09/12/12 16:54:07 (8 years ago)
Author:
fielding@…
Message:

Clean up pseudo normative text regarding use of registered values; partly addresses #419

File:
1 edited

Legend:

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

    r2046 r2047  
    380380</artwork></figure>
    381381<t>
    382    Media-type values are registered with the Internet Assigned Number
    383    Authority (IANA). The media type registration process is
    384    outlined in <xref target="BCP13"/>. Use of non-registered media types is
    385    discouraged.
     382   Internet media types ought to be registered with IANA according to the
     383   procedures defined in <xref target="BCP13"/>.
    386384</t>
    387385</section>
     
    398396</artwork></figure>
    399397<t>
    400    The IANA Character Set registry
     398   Charset names ought to be registered in IANA Character Set registry
    401399   (<eref target="http://www.iana.org/assignments/character-sets"/>)
    402    maintains the set of tokens registered for use on the Internet as
    403    charset names  <xref target="RFC2978"/>.
     400   according to the procedures defined in <xref target="RFC2978"/>.
    404401</t>
    405402</section>
     
    526523   used to allow a representation to be compressed or otherwise usefully
    527524   transformed without losing the identity of its underlying media type
    528    and without loss of information. Frequently, the representation is stored in
    529    coded form, transmitted directly, and only decoded by the recipient.
     525   and without loss of information. Frequently, the representation is stored
     526   in coded form, transmitted directly, and only decoded by the recipient.
    530527</t>
    531528<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-coding"/>
     
    533530</artwork></figure>
    534531<t>
    535    All content-coding values are case-insensitive and &SHOULD; be registered
     532   All content-coding values are case-insensitive and ought to be registered
    536533   within the HTTP Content Coding registry, as defined in
    537534   <xref target="content.coding.registry"/>. They are used in the
     
    11741171<t>
    11751172   Additional methods &MAY; be used in HTTP; many have already been
    1176    standardized outside the scope of this specification and registered
    1177    within the HTTP Method Registry maintained by IANA, as defined in
    1178    <xref target="method.registry"/>.
     1173   standardized outside the scope of this specification and ought to be
     1174   registered within the HTTP Method Registry maintained by IANA, as defined
     1175   in <xref target="method.registry"/>.
    11791176</t>
    11801177<t>
     
    43454342<t>
    43464343   The requirements for header field names are defined in
    4347    <xref target="BCP90"/>.  Authors of specifications
    4348    defining new fields are advised to keep the name as short as practical, and
    4349    not to prefix them with "X-" if they are to be registered (either
    4350    immediately or in the future).
     4344   <xref target="BCP90"/>.  Authors of specifications defining new fields are
     4345   advised to keep the name as short as practical and to not prefix the name
     4346   with "X-" unless the header field will never be used on the Internet.
     4347   (The "x-" prefix idiom has been extensively misused in practice; it was
     4348   intended to only be used as a mechanism for avoiding name collisions inside
     4349   proprietary software or intranet processing, since the prefix would ensure
     4350   that private names never collide with a newly registered Internet name.)
    43514351</t>
    43524352<t>
Note: See TracChangeset for help on using the changeset viewer.