Ignore:
Timestamp:
Feb 18, 2012, 2:29:16 AM (8 years ago)
Author:
fielding@…
Message:

Move definitions of Transfer-Encoding and Content-Length to where
they are first used. Move other transfer encoding stuff (codings,
TE, and Trailers) to its own section. Moved text is unchanged.
Make Upgrade use protocol tokens instead of product tokens (WTF?)
and move product tokens to p2. Reduce protocol registry requirements.
Removed now-empty section on protocol parameters.

File:
1 edited

Legend:

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

    r1536 r1538  
    7272  <!ENTITY media-types                "<xref target='Part3' x:rel='#media.types' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7373  <!ENTITY message-body               "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    74   <!ENTITY product-tokens             "<xref target='Part1' x:rel='#product.tokens' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7574  <!ENTITY media-type-message-http    "<xref target='Part1' x:rel='#internet.media.type.message.http' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7675  <!ENTITY status-206                 "<xref target='Part5' x:rel='#status.206' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    386385  <x:anchor-alias value="comment"/>
    387386  <x:anchor-alias value="partial-URI"/>
    388   <x:anchor-alias value="product"/>
    389387  <x:anchor-alias value="URI-reference"/>
    390388<t>
     
    395393  <x:ref>comment</x:ref>       = &lt;comment, defined in &field-components;&gt;
    396394  <x:ref>partial-URI</x:ref>   = &lt;partial-URI, defined in &uri;&gt;
    397   <x:ref>product</x:ref>       = &lt;product, defined in &product-tokens;&gt;
    398395  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in &uri;&gt;
    399396</artwork></figure>
     
    23822379</section>
    23832380
     2381<section title="Product Tokens" anchor="product.tokens">
     2382  <x:anchor-alias value="product"/>
     2383  <x:anchor-alias value="product-version"/>
     2384<t>
     2385   Product tokens are used to allow communicating applications to
     2386   identify themselves by software name and version. Most fields using
     2387   product tokens also allow sub-products which form a significant part
     2388   of the application to be listed, separated by whitespace. By
     2389   convention, the products are listed in order of their significance
     2390   for identifying the application.
     2391</t>
     2392<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="product"/><iref primary="true" item="Grammar" subitem="product-version"/>
     2393  <x:ref>product</x:ref>         = <x:ref>token</x:ref> ["/" <x:ref>product-version</x:ref>]
     2394  <x:ref>product-version</x:ref> = <x:ref>token</x:ref>
     2395</artwork></figure>
     2396<t>
     2397   Examples:
     2398</t>
     2399<figure><artwork type="example">
     2400  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     2401  Server: Apache/0.8.4
     2402</artwork></figure>
     2403<t>
     2404   Product tokens &SHOULD; be short and to the point. They &MUST-NOT; be
     2405   used for advertising or other non-essential information. Although any
     2406   token octet &MAY; appear in a product-version, this token &SHOULD;
     2407   only be used for a version identifier (i.e., successive versions of
     2408   the same product &SHOULD; only differ in the product-version portion of
     2409   the product value).
     2410</t>
     2411</section>
     2412
    23842413
    23852414<section title="Header Field Definitions" anchor="header.field.definitions">
     
    27652794</t>
    27662795<t>
    2767    The field can contain multiple product tokens (&product-tokens;) and
     2796   The field can contain multiple
     2797   product tokens (<xref target="product.tokens"/>) and
    27682798   comments (&header-fields;) identifying the server and any significant
    27692799   subproducts. The product tokens are listed in order of their significance
     
    28102840</t>
    28112841<t>
    2812    The field can contain multiple product tokens (&product-tokens;)
     2842   The field can contain multiple
     2843   product tokens (<xref target="product.tokens"/>)
    28132844   and comments (&header-fields;) identifying the agent and its
    28142845   significant subproducts. By convention, the product tokens are listed in
Note: See TracChangeset for help on using the changeset viewer.