[sc34wg3] Subject Locators

Patrick Durusau sc34wg3@isotopicmaps.org
Fri, 10 Jun 2005 14:00:42 -0400


Bernard,

Perhaps this will help:

Fielding, 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 a generic interface 
defined by the resource identifier."

I take that to mean:

Address the resource, manipulate the representation.

Hope you are having a great day!

Patrick

Bernard Vatant wrote:

>*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
>
>
>  
>

-- 
Patrick Durusau
Patrick@Durusau.net
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model
Member, Text Encoding Initiative Board of Directors, 2003-2005

Topic Maps: Human, not artificial, intelligence at work!