On Sat, Nov 6, 2010 at 11:31 PM, Toby Inkster t...@g5n.co.uk wrote:
Not necessarily. If you take your ex:isDescribedBy predicate and add
that to a triple store where the non-Information-Resource resources are
identified using hash URIs, then the SPARQL query is just:
DESCRIBE uri ?res
On Fri, Nov 5, 2010 at 5:28 PM, Nathan nat...@webr3.org wrote:
URI resolution is essentially:
dereference( uri.toAbsolute() );
Which gives us the simplicity and semantic indirection which we need. Use
frags, forget HTTP, know that uri#frag is never going to be a document
(unless you
On Sat, 6 Nov 2010 12:33:34 +
Ian Davis li...@iandavis.com wrote:
On a practical level using frags can be inefficient when your linked
data output is backed by a triple store. If you use a slash URI then
generating the data for html/xml/turtle output is just a simple
describe uri. For
Hi all,
To aid discussion I create a small demo of the idea put forth in my
blog post http://iand.posterous.com/is-303-really-necessary
Here is the URI of a toucan:
http://iandavis.com/2010/303/toucan
Here is the URI of a description of that toucan:
http://iandavis.com/2010/303/toucan.rdf
As
Ian Davis wrote:
Hi all,
To aid discussion I create a small demo of the idea put forth in my
blog post http://iand.posterous.com/is-303-really-necessary
Here is the URI of a toucan:
http://iandavis.com/2010/303/toucan
Ian, where's the demo of /toucan#frag so everybody can see that you can
On Fri, Nov 5, 2010 at 12:37 PM, Nathan nat...@webr3.org wrote:
Ian Davis wrote:
Hi all,
To aid discussion I create a small demo of the idea put forth in my
blog post http://iand.posterous.com/is-303-really-necessary
Here is the URI of a toucan:
http://iandavis.com/2010/303/toucan
Ian,
Mike Kelly wrote:
On Fri, Nov 5, 2010 at 12:37 PM, Nathan nat...@webr3.org wrote:
Ian Davis wrote:
Hi all,
To aid discussion I create a small demo of the idea put forth in my
blog post http://iand.posterous.com/is-303-really-necessary
Here is the URI of a toucan:
I might be wrong but I dont like it much . Sindice would index it as 2
documents.
http://iandavis.com/2010/303/toucan
http://iandavis.com/2010/303/toucan.rdf
i *really* would NOT want to different URLs resolving to the same thing
thanks
Giovanni
On Fri, Nov 5, 2010 at 10:43 AM, Ian Davis
Hi,
On 5 November 2010 13:57, Giovanni Tummarello
giovanni.tummare...@deri.org wrote:
I might be wrong but I dont like it much . Sindice would index it as 2
documents.
http://iandavis.com/2010/303/toucan
http://iandavis.com/2010/303/toucan.rdf
Even though one returns a Content-Location?
On Fri, Nov 5, 2010 at 1:57 PM, Giovanni Tummarello
giovanni.tummare...@deri.org wrote:
I might be wrong but I dont like it much . Sindice would index it as 2
documents.
http://iandavis.com/2010/303/toucan
http://iandavis.com/2010/303/toucan.rdf
i *really* would NOT want to different URLs
On Fri, Nov 5, 2010 at 1:53 PM, Nathan nat...@webr3.org wrote:
Mike Kelly wrote:
On Fri, Nov 5, 2010 at 12:37 PM, Nathan nat...@webr3.org wrote:
Wrong question, correct question is if I 200 OK will people think this
is a
document, to which the answer is yes. You're toucan is a :Document.
Ah, it's magic in the header:
curl -i http://iandavis.com/2010/303/toucan
HTTP/1.1 200 OK
Date: Fri, 05 Nov 2010 14:22:40 GMT
Server: Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 PHP/5.2.4-2ubuntu5.10 with
Suhosin-Patch mod_wsgi/1.3 Python/2.5.2
Content-Location: toucan.rdf
Vary: negotiate
TCN: choice
Hi,
On 5 November 2010 12:37, Nathan nat...@webr3.org wrote:
Wrong question, correct question is if I 200 OK will people think this
is a document, to which the answer is yes. You're toucan is a :Document.
You keep reiterating this, but I'm still not clear on what you're saying.
1. It seems
On Fri, Nov 5, 2010 at 1:53 PM, Jörn Hees j_h...@cs.uni-kl.de wrote:
If I GET http://iandavis.com/2010/303/toucan i retrieve a document (I'll call
this A) with rdf statements.
This is not correct. You receive a response with an entity: the
representation. (Here entity is used in the rfc2616
Thanks for the clarification.
As I guess there are quite a lot of people who -- like me -- didn't notice
this part of your suggestion I'll summarize it like this:
You still want to include a Content-Location field in the header denoting that
you're actually retrieving a document more precisely
David Wood wrote:
On Nov 5, 2010, at 08:37, Nathan wrote:
Ian Davis wrote:
Hi all,
To aid discussion I create a small demo of the idea put forth in my
blog post http://iand.posterous.com/is-303-really-necessary
Here is the URI of a toucan:
http://iandavis.com/2010/303/toucan
Ian, where's the
Mike Kelly wrote:
On Fri, Nov 5, 2010 at 1:53 PM, Nathan nat...@webr3.org wrote:
Mike Kelly wrote:
On Fri, Nov 5, 2010 at 12:37 PM, Nathan nat...@webr3.org wrote:
Wrong question, correct question is if I 200 OK will people think this
is a
document, to which the answer is yes. You're toucan is
On Fri, Nov 5, 2010 at 3:52 PM, Nathan nat...@webr3.org wrote:
Mike Kelly wrote:
On Fri, Nov 5, 2010 at 1:53 PM, Nathan nat...@webr3.org wrote:
Mike Kelly wrote:
On Fri, Nov 5, 2010 at 12:37 PM, Nathan nat...@webr3.org wrote:
Wrong question, correct question is if I 200 OK will people
On Nov 5, 2010, at 11:42, Nathan nat...@webr3.org wrote:
David Wood wrote:
On Nov 5, 2010, at 08:37, Nathan wrote:
Ian Davis wrote:
Hi all,
To aid discussion I create a small demo of the idea put forth in my
blog post http://iand.posterous.com/is-303-really-necessary
Here is the URI of a
David Wood wrote:
On Nov 5, 2010, at 11:42, Nathan nat...@webr3.org wrote:
David Wood wrote:
On Nov 5, 2010, at 08:37, Nathan wrote:
Ian Davis wrote:
Hi all,
To aid discussion I create a small demo of the idea put forth in my
blog post http://iand.posterous.com/is-303-really-necessary
Here
Hi,
I submitted both urls to sindice earlier. Both were indexed and have the
same content. In the search results[1] one displays with title A
Toucan, the other with title, A Description of a Toucan.
http://sindice.com/search?q=toucan+domain%3Aiandavis.comqt=term
Robert.
On 05/11/10 09:43,
On Fri, Nov 5, 2010 at 4:42 PM, Robert Fuller robert.ful...@deri.org wrote:
I submitted both urls to sindice earlier. Both were indexed and have the
same content. In the search results[1] one displays with title A Toucan,
the other with title, A Description of a Toucan.
On 11/5/10 10:41 AM, Jörn Hees wrote:
Ah, it's magic in the header:
curl -i http://iandavis.com/2010/303/toucan
HTTP/1.1 200 OK
Date: Fri, 05 Nov 2010 14:22:40 GMT
Server: Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 PHP/5.2.4-2ubuntu5.10 with
Suhosin-Patch mod_wsgi/1.3 Python/2.5.2
Content-Location:
Le 05/11/2010 16:42, Nathan a écrit :
[skip]
Sadly your proposed 210 still has it, the true problem isn't a status
code thing, it's an if I can GET it, it's a document, hence the
earlier outlined problems with 303 as it stands, still the same problem.
So, you are against hash URIs? Because if
Antoine Zimmermann wrote:
Le 05/11/2010 16:42, Nathan a écrit :
[skip]
Sadly your proposed 210 still has it, the true problem isn't a status
code thing, it's an if I can GET it, it's a document, hence the
earlier outlined problems with 303 as it stands, still the same problem.
So, you are
Le 05/11/2010 14:57, Giovanni Tummarello a écrit :
I might be wrong but I dont like it much . Sindice would index it as 2
documents.
http://iandavis.com/2010/303/toucan
http://iandavis.com/2010/303/toucan.rdf
i *really* would NOT want to different URLs resolving to the same thing
Hmm, why
On 05/11/10 16:50, Ian Davis wrote:
On Fri, Nov 5, 2010 at 4:42 PM, Robert Fullerrobert.ful...@deri.org wrote:
I submitted both urls to sindice earlier. Both were indexed and have the
same content. In the search results[1] one displays with title A Toucan,
the other with title, A Description
Le 05/11/2010 18:01, Nathan a écrit :
Antoine Zimmermann wrote:
Le 05/11/2010 16:42, Nathan a écrit :
[skip]
Sadly your proposed 210 still has it, the true problem isn't a status
code thing, it's an if I can GET it, it's a document, hence the
earlier outlined problems with 303 as it stands,
Antoine Zimmermann wrote:
Le 05/11/2010 18:01, Nathan a écrit :
Antoine Zimmermann wrote:
Le 05/11/2010 16:42, Nathan a écrit :
[skip]
Sadly your proposed 210 still has it, the true problem isn't a status
code thing, it's an if I can GET it, it's a document, hence the
earlier outlined
29 matches
Mail list logo
