Given that the operators of this service claim that we can “trust them to do
the right thing”, I find it disappointing that they re-invented their own
integer literals rather than re-using existing identifiers such as those from
Linked Open Numbers.
Other than that, looks like a great service.
Hello Chris,
what a great step forward ! Now if the RDF WG would adopt this proposal,
LOD and RDF would really be ready to save the world!
http://www.brunni.de/extending_the_rdf_triple_model.html
Regards,
Michael Brunnbauer
On Mon, Apr 01, 2013 at 12:13:19AM +0100, Christopher Gutteridge
the URI and when.
On 01/04/2013 08:49, Michael Brunnbauer wrote:
Hello Chris,
what a great step forward ! Now if the RDF WG would adopt this proposal,
LOD and RDF would really be ready to save the world!
http://www.brunni.de/extending_the_rdf_triple_model.html
Regards,
Michael Brunnbauer
On 04/01/2013 01:13 AM, Christopher Gutteridge wrote:
Apparently http://uri4uri.net/ launched today and claims to solves many
of the problems of Linked data. It looks promising..
I wasn't able to download their URI-dump to my desktop, so I'm not yet
convinced that they really have all
of Linked data. It looks promising..
I wasn't able to download their URI-dump to my desktop, so I'm not yet
convinced that they really have all the copies. Besides, will it even
work on Linux?
-Sarven
Hi all,
uri4uri is clearly missing provenance information and a SPARQL endpoint.
I have started a harvester which fetches all URI data on uri4uri.net. I
will post the SPARQL endpoint once the harvesting is done. ETA is
2014-03-31T23:59Z.
Kind regards,
Pieter
On 04/01/2013 11:52 AM, Claus
authority assigned
the URI and when.
On 01/04/2013 08:49, Michael Brunnbauer wrote:
Hello Chris,
what a great step forward ! Now if the RDF WG would adopt this proposal,
LOD and RDF would really be ready to save the world!
http://www.brunni.de/**extending_the_rdf_triple_**model.htmlhttp
Shouldn't the path component of the URIs be percent-encoded? That is,
http://uri4uri.net/uri/%0Ahttp%3A%2F%2Fdbpedia.org%2Fresource%2FCopenhagen
instead of
http://uri4uri.net/uri/http://dbpedia.org/resource/Copenhagen
Martynas
graphity.org
On Mon, Apr 1, 2013 at 11:37 AM, Christopher
Well, the colon should be. No reason why the / should be in this case.
You can't have more than one colon in a URI.
(Though you can in what's typed in a browser bar).
Also, the TAG is going to eliminate the // soon, which will make
everything much simpler.
Tim
(hmmm ...So what would
In principle you are probably right, but in practice this is a stunningly
useful site, and requiring users to URLEncode would make it much more opaque.
And in fact prone to error - I'm not sure what your %0A in the encoded URI
denotes?
Unfortunately things like
http://uri4uri.net/uri/http%3A%2F
On 1 Apr 2013, at 14:38, Tim Berners-Lee ti...@w3.org
wrote:
Well, the colon should be. No reason why the / should be in this case.
You can't have more than one colon in a URI.
(Though you can in what's typed in a browser bar).
Also, the TAG is going to eliminate the // soon, which
be in this case.
You can't have more than one colon in a URI.
(Though you can in what's typed in a browser bar).
Also, the TAG is going to eliminate the // soon, which will make
everything much simpler.
That's great news Tim!
After all these years.
The savings in time and bandwidth will be enormous
wrote:
On 1 Apr 2013, at 14:38, Tim Berners-Lee ti...@w3.org
wrote:
Well, the colon should be. No reason why the / should be in this case.
You can't have more than one colon in a URI.
(Though you can in what's typed in a browser bar).
Also, the TAG is going to eliminate the // soon, which
for : and assume it's HTTP?
Barry
On 01/04/2013 14:57, Hugh Glaser wrote:
On 1 Apr 2013, at 14:38, Tim Berners-Lee ti...@w3.org
wrote:
Well, the colon should be. No reason why the / should be in this case.
You can't have more than one colon in a URI.
(Though you can in what's typed in a browser
be in this case.
You can't have more than one colon in a URI.
(Though you can in what's typed in a browser bar).
Also, the TAG is going to eliminate the // soon, which will make
everything much simpler.
That's great news Tim!
After all these years.
The savings in time and bandwidth will be enormous
On 1 April 2013 01:13, Christopher Gutteridge c...@ecs.soton.ac.uk wrote:
Apparently http://uri4uri.net/ launched today and claims to solves many
of the problems of Linked data. It looks promising..
Thanks for the pointer!
The single most important development in the history of the Semantic
On Sun, Mar 31, 2013 at 6:56 PM, Melvin Carvalho
melvincarva...@gmail.comwrote:
On 1 April 2013 01:13, Christopher Gutteridge c...@ecs.soton.ac.uk wrote:
Apparently http://uri4uri.net/ launched today and claims to solves many
of the problems of Linked data. It looks promising..
Thanks
As a beta user who's been using this service for about a year now, I can
attest that it is everything it claims to be and more. Love it and can't
recommend it highly enough.
Lee
On 3/31/2013 7:13 PM, Christopher Gutteridge wrote:
Apparently http://uri4uri.net/ launched today and claims to
Yes, me too.
It's great to see their excellent stuff get more visibility.
Well spotted, Chris.
Hugh
On 1 Apr 2013, at 04:05, Lee Feigenbaum l...@thefigtrees.net wrote:
As a beta user who's been using this service for about a year now, I can
attest that it is everything it claims to be and
19 matches
Mail list logo
