Ignore:
Timestamp:
Jul 22, 2010, 2:06:27 AM (9 years ago)
Author:
fielding@…
Message:

Addresses #109: Clarify entity / representation / variant terminology

Replaced entity with representation.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r864 r866  
    465465<t>
    466466   Content coding values indicate an encoding transformation that has
    467    been or can be applied to an entity. Content codings are primarily
    468    used to allow a document to be compressed or otherwise usefully
     467   been or can be applied to a representation. Content codings are primarily
     468   used to allow a representation to be compressed or otherwise usefully
    469469   transformed without losing the identity of its underlying media type
    470    and without loss of information. Frequently, the entity is stored in
     470   and without loss of information. Frequently, the representation is stored in
    471471   coded form, transmitted directly, and only decoded by the recipient.
    472472</t>
     
    707707<section title="Entity" anchor="entity">
    708708<t>
    709    Request and Response messages &MAY; transfer an entity if not otherwise
    710    restricted by the request method or response status code. An entity
    711    consists of entity-header fields and an entity-body, although some
     709   Request and Response messages &MAY; transfer a representation if not otherwise
     710   restricted by the request method or response status code. A representation
     711   consists of entity-header fields and a representation body, although some
    712712   responses will only include the entity-headers.
    713713</t>
    714714<t>
    715715   In this section, both sender and recipient refer to either the client
    716    or the server, depending on who sends and who receives the entity.
     716   or the server, depending on who sends and who receives the message.
    717717</t>
    718718
     
    966966<t>
    967967   For entity-header fields, both sender and recipient refer to either the
    968    client or the server, depending on who sends and who receives the entity.
     968   client or the server, depending on who sends and who receives the message.
    969969</t>
    970970
     
    10491049   Verbally, this would be interpreted as "text/html and text/x-c are
    10501050   the preferred media types, but if they do not exist, then send the
    1051    text/x-dvi entity, and if that does not exist, send the text/plain
    1052    entity."
     1051   text/x-dvi representation, and if that does not exist, send the text/plain
     1052   representation."
    10531053</t>
    10541054<t>
     
    13111311<t>
    13121312   The "Content-Encoding" entity-header field indicates what content-codings
    1313    have been applied to the entity-body, and thus what decoding mechanisms
     1313   have been applied to the representation, and thus what decoding mechanisms
    13141314   must be applied in order to obtain the media-type referenced by the
    13151315   Content-Type header field. Content-Encoding is primarily used to allow a
    1316    document to be compressed without losing the identity of its underlying
     1316   representation to be compressed without losing the identity of its underlying
    13171317   media type.
    13181318</t>
     
    13281328</artwork></figure>
    13291329<t>
    1330    The content-coding is a characteristic of the entity identified by
    1331    the Effective Request URI (&effective-request-uri;). Typically, the entity-body is stored with this
     1330   The content-coding is a characteristic of the representation.
     1331   Typically, the representation body is stored with this
    13321332   encoding and is only decoded before rendering or analogous usage.
    13331333   However, a non-transparent proxy &MAY; modify the content-coding if the
     
    13361336</t>
    13371337<t>
    1338    If the content-coding of an entity is not "identity", then the
    1339    response &MUST; include a Content-Encoding entity-header (<xref target="header.content-encoding"/>)
     1338   If the content-coding of a representation is not "identity", then the
     1339   representation metadata &MUST; include a Content-Encoding header
     1340   field (<xref target="header.content-encoding"/>)
    13401341   that lists the non-identity content-coding(s) used.
    13411342</t>
     
    13461347</t>
    13471348<t>
    1348    If multiple encodings have been applied to an entity, the content
     1349   If multiple encodings have been applied to a representation, the content
    13491350   codings &MUST; be listed in the order in which they were applied.
    13501351   Additional information about the encoding parameters &MAY; be provided
    1351    by other entity-header fields not defined by this specification.
     1352   by other header fields not defined by this specification.
    13521353</t>
    13531354</section>
     
    13601361<t>
    13611362   The "Content-Language" entity-header field describes the natural
    1362    language(s) of the intended audience for the entity. Note that this might
     1363   language(s) of the intended audience for the representation. Note that this might
    13631364   not be equivalent to all the languages used within the entity-body.
    13641365</t>
     
    13701371   Language tags are defined in <xref target="language.tags"/>. The primary purpose of
    13711372   Content-Language is to allow a user to identify and differentiate
    1372    entities according to the user's own preferred language. Thus, if the
     1373   representations according to the user's own preferred language. Thus, if the
    13731374   body content is intended only for a Danish-literate audience, the
    13741375   appropriate field is
     
    13931394</artwork></figure>
    13941395<t>
    1395    However, just because multiple languages are present within an entity
     1396   However, just because multiple languages are present within a representation
    13961397   does not mean that it is intended for multiple linguistic audiences.
    13971398   An example would be a beginner's language primer, such as "A First
     
    15261527   any transfer-encoding applied to the message-body. If the message is
    15271528   received with a transfer-encoding, that encoding &MUST; be removed
    1528    prior to checking the Content-MD5 value against the received entity.
     1529   prior to checking the Content-MD5 value against the received representation.
    15291530</t>
    15301531<t>
Note: See TracChangeset for help on using the changeset viewer.