Re: [http-range14] Definition of the Dereferencing URI

Hi,

I think it would be good to read the docs recently proposed in this thread(ish) by Leo Sauermann:

http://linkeddatabook.com/editions/1.0/

and

http://www.w3.org/TR/cooluris/

this, in order to have at least some common definitions, otherwise we exchange mails to define what we mean for "de-referencing" ;)

In short:
- de-referencing comes from the server (which may imply the "owner", without venturing in other issues).
- it is the act of pointing the agent to another resource which can be retrieved and which relates to the requested URI (for which there is no document). **read the linked data tutorial for more precision**
- this is still different from content negotiation, that is what "usually" related to the header request.

The canonical story goes:
- You ask to resolve the identifier of Berlin: http://germany.de/Berlin (just an example)
- The server answer: cannot provide "Berlin".. but you can see my page about Berlin (http://germany.de/wikiGermany/Berlin)
- You ask for the page saying: I'd like have it in rdf/html etc. (could be a request in the header).

If you have some more question, I'm happy to answer... but I guess off mailing list it would be better!
Many people here heard these things over and over!

best,
Andrea


Il giorno 18/feb/2012, alle ore 10.14, Ghalem Ouadjed (EOWEO) ha scritto:

Hi
the thing is not clear for me is that dereferencing a uri is not an act coming from the agent which is calling "this" uri but by the uri owner himself. So dereferencing is not the act of retrieving a uri but the act of providing a uri in a way to make it correspond to the header s definition of the agent...

Ghalem

Le 17/02/2012 23:37, Yang Squared a écrit :
Hi all,

I am writing a paper and I would like to define the meaning of the Dereferencing URI on the Web.

When resolve a URI on the traditional Web, we retrieve a document representation of the resource with status code 200OK, means we resolve the URI successfully. On the Semantic Web, when resolve a Real World Object URI, we cannot retrieve the object itself, but we will redirect to a information resource (a RDF document) which describes the URI, by parsing the RDF, we can understand the meaning of the URI according to the RDF triples description, we conclude that the request succeeded.

Here are my definitions:

Resource: Anything can be identified by a URI.

Dereferencing URI:  the act of retrieving a representation of a resource or the semantic description of a resource created by the URI owner.

Dereferencing Succeeded: When dereferencing a URI, an agent successfully retrieved the representation of the resource or received the semantic description of a resource via the protocol specified within the URI.


Any comment is welcome,

Thanks,
Yang

-----------------------------------

Web and Internet Science

Room 3027 EEE Building

Electronics and Computer Science

University of Southampton, SO17 1BJ


Tel: +44(0)23 8059 8346

twitter: @yang_squared<http://twitter.com/#%21/yang_squared>


--
Ghalem Ouadjed Formateur France en Technologies Sémantiques Certification et Conseil en Web Sémantique Membre Associé du STI International : http://www.sti2.org/associate-members Mob : 0616674816 gouadjed@eoweo.com<mailto:gouadjed@eoweo.com> | http://blog.eoweo.com<http://blog.eoweo.com/> | http://www.viadeo.com/fr/profile/ghalem.ouadjed | twitter : @ghalem_ouadjed