Changeset 2089


Ignore:
Timestamp:
Jan 5, 2013, 4:02:19 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) further clarify that a representation might be old

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2088 r2089  
    843843         which one can observe and act upon such a thing only through the communication of messages to some independent actor on the
    844844         other side, then we need an abstraction to represent ("take the place of") the current or desired state of that thing in our
    845          communications. We call that abstraction a "<dfn>representation</dfn>" <a href="#REST" id="rfc.xref.REST.1"><cite title="Architectural Styles and the Design of Network-based Software Architectures">[REST]</cite></a>.
    846       </p>
    847       <p id="rfc.section.3.p.2">For the purposes of HTTP, a <dfn>representation</dfn> is information that reflects the current or desired state of a given resource, in a format that can be readily communicated
    848          via the protocol, consisting of a set of representation metadata and a potentially unbounded stream of representation data.
     845         communications. We call that abstraction a representation <a href="#REST" id="rfc.xref.REST.1"><cite title="Architectural Styles and the Design of Network-based Software Architectures">[REST]</cite></a>.
     846      </p>
     847      <p id="rfc.section.3.p.2">For the purposes of HTTP, a "<dfn>representation</dfn>" is information that is intended to reflect a past, current, or desired state of a given resource, in a format that can be
     848         readily communicated via the protocol, and that consists of a set of representation metadata and a potentially unbounded stream
     849         of representation data.
    849850      </p>
    850851      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="representation.metadata" href="#representation.metadata">Representation Metadata</a></h2>
  • 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.