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

Thank you Yang, this made a long, confusing thread much clearer to me.

As I understand it, we're talking about a data model with 2 classes:


1.       Stuff on the web;

2.       Everything else.

You can get 1. via http. It's quite easy to spot this stuff; it's broadly any stuff with a W3C spec (including stuff implied within that e.g. character data).

You can't get 2., but you can use a http URI to identify it as a convenient fiction. This is all the other stuff without a W3C spec.

[incidentally, both 1. and 2. are real-world objects; unless you're telling me that the web isn't in the real world? Also, not everything on the web is a document. This is a bit nit-picking though ;)]

OK, so the confusion sets in because you can identify a 1. which is about (or otherwise related to) a 2.

Standard practice must be to always put some redirection at a URI for a 2. which


a)      Points out that "you have reached the end of the web";

b)      Tells you about the 2. and/or its relations to other things (they could be 1. or 2. because according to this practice you'll just keep going til you get back to a 1.)

Is that the same problem that's been discussed here the last few days?

Cheers,

Michael

From: Yang Squared [mailto:yang.square@gmail.com]
Sent: 17 February 2012 22:38
To: public-lod@w3.org; semantic-web@w3.org
Subject: [http-range14] Definition of the Dereferencing URI

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/#!/yang_squared>