W3C home > Mailing lists > Public > www-tag@w3.org > December 2007

Re: httpRange-14 - what are the use-cases?

From: Sean B. Palmer <sean@miscoranda.com>
Date: Sat, 15 Dec 2007 18:17:45 +0000
Message-ID: <b6bb4d890712151017w24db4b52jde3ebd3156fa56af@mail.gmail.com>
To: "Mikael Nilsson" <mikael@nilsson.name>
Cc: www-tag@w3.org

On Dec 5, 2007 10:38 AM, Mikael Nilsson <mikael@nilsson.name> wrote:

> II. Allow 200 for non-IRs.
> http://en.wikipedia.org/wiki/Paris can now be used to denote Paris,
> the city. It returns 200 Ok, with an xiaoshu:representation of Paris,
> i.e. some useful information about Paris.
> X = http://en.wikipedia.org/wiki/Paris
>
> Charlotte has noticed this, and produced the triple
>
> <http://en.wikipedia.org/wiki/Paris>
> owl:sameAs <http://dbpedia.org/resource/Paris>
>
> which Bob sees in his harvester. Thus, Bob can smush the two resources,
> and ends up with
>
> <http://dbpedia.org/resource/Paris> ex:annotation "Not suitable for
> making travel plans. Also, very bad grammar and difficult to read."

No he doesn't, because Charlotte wasn't silly enough to state that
Paris is not suitable for making travel plans, has very bad grammar,
and is difficult to read.

She may have written something like the following:

<http://dbpedia.org/resource/Paris>  web:representation [
   ex:annotation """Not suitable for making travel plans. Also,
very bad grammar and difficult to read.""" ] .

Or, a bit more interestingly, we may define ex:annotation to apply to
the content you get eventually when you dereference a URI. That'd even
work on 303 cases, because you might 303 the dbpedia Paris page to the
Wikipedia Paris page, right?

It'd probably be better to work on a particular representation though
because grammar and so forth changes on Wikipedia, as we all know.

I think it was good of you to try to come up with a use case; we
definitely need to see more of this. I rather liked Richard Cyganiak's
summary that we pushed the problem of what a URI identifies into a
smaller corner of the web architecture, because that certainly was a
big issue w.r.t. EARL circa 2002.

Nowadays I think that foaf:primaryTopic is probably enough of a
solution to carry many of the use case worries I had back then,
though.

-- 
Sean B. Palmer, http://inamidst.com/sbp/
Received on Saturday, 15 December 2007 18:17:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:51 GMT