[sc34wg3] Subject Locators

Bernard Vatant sc34wg3@isotopicmaps.org
Fri, 10 Jun 2005 19:58:10 +0200

Bingo, I think I understand, reading further Section 6.2.2 "Manipulating Shadows"

"Defining resource such that a URI identifies a concept rather than a document leaves us
with another question: how does a user access, manipulate, or transfer a concept such that
they can get something useful when a hypertext link is selected? REST answers that
question by defining the things that are manipulated to be representations of the
identified resource, rather than the resource itself. An origin server maintains a mapping
from resource identifiers to the set of representations corresponding to each resource. A
resource is therefore manipulated by transferring representations through the generic
interface defined by the resource identifier."

So you *address* the resource through http, but what you *get* in any case is a
*representation* of the resource. Is that what you meant? And it makes no difference if
the resource type is "concept", "information resource" or "organization".
In that case, we fully agree ...


> -----Message d'origine-----
> De : sc34wg3-admin@isotopicmaps.org
> [mailto:sc34wg3-admin@isotopicmaps.org]De la part de Bernard Vatant
> Envoye : vendredi 10 juin 2005 19:37
> A : sc34wg3@isotopicmaps.org
> Objet : RE: [sc34wg3] Subject Locators
> *BV
> > I guess Jan meant to write *you can never ever address a resource,
> > > only a representation*
> *Jan
> > No, no typo. With HTTP/URI you can never ever address a
> > representation, only a resource.
> *BV
> > > ... otherwise I'm lost.
> So I'm lost. I guess we have not the same understanding of either "address", or
> "representation" or "resource" (or all of those words) in this context :((
> > Have you read Fielding's dissertation? It is quite clear.
> Only excerpts - I guess I should read it throughout - not tonight ...
> I read in section 6.2.1. quoted by Patrick
> "REST accomplishes this by defining a resource to be the semantics of what the author
> intends to identify, rather than the value corresponding to those semantics at the time
> the reference is created. It is then left to the author to ensure that the identifier
> chosen for a reference does indeed identify the intended semantics."
> *the value corresponding to those semantics* is a "representation", Y/N? and it is what
> you "address", Y/N? So it's not the  resource itself, Y/N? Where is the flaw in my
> understanding?
> But, beyond that, I guess you agree with the rest of my post? (which is the most
> important)
> Bernard
> _______________________________________________
> sc34wg3 mailing list
> sc34wg3@isotopicmaps.org
> http://www.isotopicmaps.org/mailman/listinfo/sc34wg3