Ignore:
Timestamp:
Jul 30, 2009, 4:30:31 AM (10 years ago)
Author:
fielding@…
Message:

editorial: move remaining terminology to part 3 for later edit.
update HTML

File:
1 edited

Legend:

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

    r653 r660  
    236236   requirements had become in <xref target="RFC2616"/>.
    237237</t>
     238
     239<section title="Terminology" anchor="terminology">
     240<t>
     241   This specification uses a number of terms to refer to the roles
     242   played by participants in, and objects of, the HTTP communication.
     243</t>
     244<t>
     245  <iref item="content negotiation"/>
     246  <x:dfn>content negotiation</x:dfn>
     247  <list>
     248    <t>
     249      The mechanism for selecting the appropriate representation when
     250      servicing a request. The representation of entities in any response
     251      can be negotiated (including error responses).
     252    </t>
     253  </list>
     254</t>
     255<t>
     256  <iref item="entity"/>
     257  <x:dfn>entity</x:dfn>
     258  <list>
     259    <t>
     260      The information transferred as the payload of a request or
     261      response. An entity consists of metadata in the form of
     262      entity-header fields and content in the form of an entity-body.
     263    </t>
     264  </list>
     265</t>
     266<t>
     267  <iref item="representation"/>
     268  <x:dfn>representation</x:dfn>
     269  <list>
     270    <t>
     271      An entity included with a response that is subject to content
     272      negotiation. There may exist multiple
     273      representations associated with a particular response status.
     274    </t>
     275  </list>
     276</t>
     277<t>
     278  <iref item="variant"/>
     279  <x:dfn>variant</x:dfn>
     280  <list>
     281    <t>
     282      A resource may have one, or more than one, representation(s)
     283      associated with it at any given instant. Each of these
     284      representations is termed a `variant'.  Use of the term `variant'
     285      does not necessarily imply that the resource is subject to content
     286      negotiation.
     287    </t>
     288  </list>
     289</t>
     290</section>
    238291
    239292<section title="Requirements" anchor="intro.requirements">
Note: See TracChangeset for help on using the changeset viewer.