Ignore:
Timestamp:
05/01/13 12:02:19 (10 years ago)
Author:
fielding@…
Message:

(editorial) further clarify that a representation might be old

File:
1 edited

Legend:

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

    r2088 r2089  
    294294   abstraction to represent ("take the place of") the current or desired state
    295295   of that thing in our communications. We call that abstraction a
    296    "<x:dfn>representation</x:dfn>" <xref target="REST"/>.
    297 </t>
    298 <t>
    299    For the purposes of HTTP, a <x:dfn>representation</x:dfn> is information
    300    that reflects the current or desired state of a given resource, in a format
    301    that can be readily communicated via the protocol, consisting of a set of
    302    representation metadata and a potentially unbounded stream of
    303    representation data.
     296   representation <xref target="REST"/>.
     297</t>
     298<t>
     299   For the purposes of HTTP, a "<x:dfn>representation</x:dfn>" is information
     300   that is intended to reflect a past, current, or desired state of a given
     301   resource, in a format that can be readily communicated via the protocol,
     302   and that consists of a set of representation metadata and a potentially
     303   unbounded stream of representation data.
    304304</t>
    305305
Note: See TracChangeset for help on using the changeset viewer.