atom feed15 messages in org.w3.ietf-http-wgRe: i109: Clarify entity / representa...
FromSent OnAttachments
Mark NottinghamMay 8, 2008 11:09 pm 
Stefan EissingMay 9, 2008 1:01 am 
Julian ReschkeMay 9, 2008 7:01 am 
Brian SmithMay 9, 2008 9:40 am 
Roy T. FieldingMay 9, 2008 3:45 pm 
Julian ReschkeMay 10, 2008 1:30 am 
Brian SmithMay 10, 2008 7:30 am 
Mark NottinghamJul 28, 2008 6:48 am 
Jonathan ReesFeb 6, 2009 4:40 am 
Mark NottinghamFeb 6, 2009 5:49 am 
Roy T. FieldingFeb 6, 2009 11:03 am 
Robert BrewerFeb 6, 2009 11:14 am 
Jonathan ReesFeb 6, 2009 12:56 pm 
Brian SmithFeb 6, 2009 2:05 pm 
Mark NottinghamFeb 6, 2009 3:07 pm 
Subject:Re: i109: Clarify entity / representation / variant terminology
From:Roy T. Fielding (fiel@gbiv.com)
Date:May 9, 2008 3:45:39 pm
List:org.w3.ietf-http-wg

On May 9, 2008, at 7:02 AM, Julian Reschke wrote:

But not every entity transferred over HTTP is a representation of a resource. Example: the response body sent with a 404 status.

It is a representation of a 404 response.

<http://www.ics.uci.edu/~fielding/pubs/dissertation/ rest_arch_style.htm#sec_5_2_1_2>

Depending on the message control data, a given representation may indicate the current state of the requested resource, the desired state for the requested resource, or the value of some other resource, such as a representation of the input data within a client's query form, or a representation of some error condition for a response.

....Roy