Re: New ResourceMe Version

On 1/6/12 7:46 PM, bergi wrote:
> 'HTTP/1.1 303 See Other
> Server: Virtuoso/06.03.3131 (Linux) x86_64-generic-linux-glibc25-64  VDB
> Connection: close
> Date: Sat, 07 Jan 2012 00:11:48 GMT
> Accept-Ranges: bytes
> TCN: choice
> Vary: negotiate,accept
> Content-Location: sioc.rdf
> Content-Type: application/rdf+xml
> Location:http://kingsley.idehen.net/dataspace/raw/person/sioc.rdf
> Content-Length: 0

Bergi,

Here is an explanation of the above, also see the HTTP response code 
page from Wikipedia [1] for reference also note the URI debug URL [2] 
below re. the descriptor resource that has URL: 
http://kingsley.idehen.net/dataspace/person/kidehen .

Content-Location --- reference for an alternate location for the 
returned data
Location --- used in redirection, or when a new resource has been created.

URL: http://kingsley.idehen.net/dataspace/person/kidehen isA resource 
address, representation is negotiable. Thus, you have two paths to the 
representation you seek depending on whether your client thinks in terms 
of Content-Location or redirection oriented Location re. header responses.

For WebID, what's important to you is the location of the composite key 
comprised of WebID and Public Key components that enables "mirrored 
claim" triangulation. How you get to the graph shouldn't matter. It the 
composite key lookup or failure that should determine success or failure.

At the end of the day you are looking for a signed claim match :-)

-- 

Regards,

Kingsley Idehen	
Founder&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen