On Mon, Aug 18, 2008 at 1:57 PM, MichaelNelson <RhodeWarri...@gmail.com>wrote:
> > The belief that "representations don't have their own id" seems to be
> > the root of the problem here. In HTTP, representations CAN have their
> > own identifiers (URIs) and thus can be addressed individually. As
> > evidence, the Content-Location header exists to notify a client of
> > this fact (http://tools.ietf.org/html/rfc2616#section-14.14). The
> > possibility of representation identifiers is even clearer in the case
> > of 300 Multiple Choices (http://tools.ietf.org/html/
> > rfc2616#section-10.3.1).
> That is where there is a discrepancy between RFC 2616 and AWW. In
> the http RFC, representations can have their own URIs. The AWWW
> seems to tip-toe around this. Consider:
> http://foo.edu/bar.abc
> That certainly appears to be a resource: it has a URI and when
> dereferenced it returns a representation (or, more likely, a
> "variant" in RFC-2616 terms).
> Now I show you these URIs:
> http://foo.edu/bar
> http://foo.edu/bar.abc
> http://foo.edu/bar.xyz
> and tell that the last two URIs identify possible representations
> for the 1st URI. That means "http://foo.edu/bar.abc" is both a
> resource in its own right *and* a representation for another
> resource. Effectively, its both a 1st and 2nd class citizen. RFC
> 2616 doesn't directly address this apparent inconsistency of URIs
> identifying both a resource and representation. Its perfectly
> obvious and reasonable from an implementation point of view, but
> its really non-sensical from a modeling point of view.
> The AWWW + friends introduce the concepts of "information resource"
> (i.e., web things like html and pdf) and "non-information resource"
> (i.e., real world things like cars and sandwiches) and 303 redirects
> (which can be thought of as a generalized version of http content
> negotiation as defined in RFC-2295). IMO, this is the opposite of
> the above: it makes sense from a modeling point of view but is silly
> from an implementation point of view ("so the only thing this URI
> will *ever* do is redirect me to this other URI? ok...")
There are numerous circumstances when making a distinction between a
resource and a representation is simply not all that useful, and thus the
idea that "it is perfectly obvious and reasonable from an implementation
point of view" ought to win the day. I fear that drawing the line between
those too strongly (especially since content negotiation is by no means
always practical or operational) may be dangerous.
That probably sounds heretical, but too much emphasis on "modeling" as
opposed to implementation may put too much emphasis on the producer and not
enough on the consumer. A consumer (i.e., implementation) ought to be able
to decide for itself, thus allowing for evolution, serendipitious reuse,
etc. The "contract" that a resource map producer asserts ought to be as
"secular" as possible -- "hypermedia as the engine of state" -- as the REST
principles state. ORE is really about asserting the "state" of a set of
resources, as embodied in each resource's relationship with other resources
and all of it described by links.
--peter keane
> regards,
> Michael
> > The domain model for ORE is still unclear to me, but on this one point
> > it seems like some heavyweight sources are being cited to work around
> > a relatively simple confusion. Somehow this workaround has come full-
> > circle and produced a resource without a representation that resolves
> > to a response that is indistinguishable from a representation. This
> > circularity implies that there are some concepts in ORE that can be
> > factored out.
> > Jeff
|
