Opened 11 years ago

Closed 9 years ago

#315 closed editorial (incorporated)

method semantics: retrieval/representation

Reported by: julian.reschke@… Owned by: fielding@…
Priority: normal Milestone: 22
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:


See <>:

  • clarify that GET is *the* retrieval method
  • be careful with "retrieving resource" vs "retrieving a representation of a resource"

(or maybe introduce a shorthand to simplify the prose?)

Change History (6)

comment:1 Changed 10 years ago by mnot@…

  • Owner changed from draft-ietf-httpbis-p2-semantics@… to fielding@…

comment:3 Changed 10 years ago by masinter@…

"If the response status code is 200 or 203 and the request method was GET, the response payload is a representation of the target resource"

this statement establishes the framework for clients and servers speaking the HTTP protocol this is part of an overall framework:

  • if you're writing a client and send a GET and get back a 200 or 203, you should expect the response to be a representation of the target resource
  • if you're writing a server and get a GET, you should try to return a representation of the target resource with a 200 or 203

communication will happen if the client and server agree on what they think the target resources and how to interpret the representation that is transmitted

Some people read "is" to be to strong.

Change 'is' to 'should be'? since implicitly "when things go well" or expand this sentence.

comment:4 Changed 9 years ago by fielding@…

From [2088]:

(editorial) Clarify that GET means retrieval; addresses #315

comment:5 Changed 9 years ago by fielding@…

From [2112]:

(editorial) the final answer on representation; addresses #315

comment:6 Changed 9 years ago by fielding@…

  • Milestone changed from unassigned to 22
  • Resolution set to incorporated
  • Status changed from new to closed

The communication via HTTP indicates what is intended by the sender, not necessarily what is intended by the minter of a URI or the controller of a resource or the author of a link. When they differ, it might indicate an error in implementation, an error in representation, or an incorrect or outdated assumption about the target resource. It is not our responsibility to decide which of the various potential causes of inconsistency is the most authoritative.

Note: See TracTickets for help on using tickets.