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
Well if I've understood correctly, uri4uri is an extreme version of
reification. rdfs: gave a way to describe a triple in triples but it
still related resources together, not the identifiers for those
resources. That makes it impossible to make statements about, say, what
authority assigned
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 the
I wouldn't want to download peta/exa-bytes of data. Can we have a SPARQL
endpoint? ^^
Cheers,
Claus
On 04/01/2013 11:32 AM, Sarven Capadisli wrote:
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
hello all
I am trying to make an owl:sameAs assertion in some RDFa but when I test
it only the first statement (rnews:about bbc:thing) is being picked up,
the owl:sameAs to the corresponding dbpedia URI is being ignored:
span rel=rnews:about;
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
But, the same technology was known from a long time with the name
Forward
Inference
Scheduling
Hub
--
Jean-Claude Moissinac
Signal and Image processing - Multimedia Group
TELECOM ParisTech
FRANCE
E-mail: moissi...@telecom-paristech.fr
Tel: (+33) 1.45.81.80.88
2013/4/1 Christopher Gutteridge
For the specific case of the BMs endpoint would the ideal situation be that
there is no formal attribution requirement (friction free) but rather some
encouraging (but not mandatory) words about embedding at least the URI of the
object record in a web publication.
There is no need for every
Hi Dominic,
Nice when it is the holiday weekend, so we hear from you :-)
On 1 Apr 2013, at 13:19, Dominic Oldman do...@oldman.me.uk
wrote:
For the specific case of the BMs endpoint would the ideal situation be that
there is no formal attribution requirement (friction free) but rather
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
Hugh,
Yes, you are correct... and there are also issues when mashing together data
from different sites.This is yet another reason why formal and mandatory 'URI
attribution' is not workable. The original question was a sort of provocation.
Therefore the encouraging words would be about using
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 be the
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
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 will
That would save a LOT of typing. I haven't used ftp:// in years, maybe
we could just go 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
In which case we can probably get rid of the ':' too?
On Mon, Apr 1, 2013 at 3:00 PM, Barry Norton barry.nor...@ontotext.com wrote:
That would save a LOT of typing. I haven't used ftp:// in years, maybe we
could just go for : and assume it's HTTP?
Barry
On 01/04/2013 14:57, Hugh Glaser
Thanks Kingsley.
Would be nice if I did :-)
Unfortunately just the little panel at the top left that you look at is
actually constructed by resolving at least the 33 URIs at
http://southampton.rkbexplorer.com/crs/export/?uri=http://southampton.rkbexplorer.com/id/person-07113
If you add in the
In Turtle/SPARQL my single namespace and graph name is :
If the protocol were the same that would really show those 'developers
can't understand multiple namespaces guys'.
(I also find triples too complicated and just use : for the middle bit.
I love graphs and all, but this stuff is really
On 4/1/13 10:38 AM, Hugh Glaser wrote:
Thanks Kingsley.
Would be nice if I did :-)
Unfortunately just the little panel at the top left that you look at is
actually constructed by resolving at least the 33 URIs at
On 1 Apr 2013, at 15:32, Yves Raimond yves.raim...@gmail.com wrote:
In which case we can probably get rid of the ':' too?
And the domain name too? Everything good is on facebook.com anyways.
Richard
On Mon, Apr 1, 2013 at 3:00 PM, Barry Norton barry.nor...@ontotext.com
wrote:
That
Hi Jeremy,
On Mon, Apr 1, 2013 at 6:26 AM, Jeremy Tarling jeremy.tarl...@bbc.co.ukwrote:
hello all
I am trying to make an owl:sameAs assertion in some RDFa but when I test
it only the first statement (rnews:about bbc:thing) is being picked up, the
owl:sameAs to the corresponding dbpedia
Hi Steph
On 01/04/2013 16:33, Stéphane Corlosquet wrote:
Hi Jeremy,
Your markup works fine for me. Try this on www.w3.org/2012/pyRdfa/
http://www.w3.org/2012/pyRdfa/ or http://rdf.greggkellogg.net/distiller
div prefix=rnews: http://iptc.org/std/rNews/2011-10-07#;
span rel=rnews:about;
On 4/1/13 11:44 AM, Jeremy Tarling wrote:
Hi Steph
On 01/04/2013 16:33, Stéphane Corlosquet wrote:
Hi Jeremy,
Your markup works fine for me. Try this on www.w3.org/2012/pyRdfa/
http://www.w3.org/2012/pyRdfa/ or
http://rdf.greggkellogg.net/distiller
div prefix=rnews:
On 01/04/2013 16:52, Kingsley Idehen wrote:
But rdfs:sameAs doesn't exist i.e., it isn't defined anywhere, or am I
missing something here?
yes will replace with owl:sameAs
I'm working with a horrible template-driven system that takes months to
change so may end up with inline vocab
Dear all,
On behalf of AKSW research group [1] I'm proud to announce an innovative
approach for coloring the Data Web. The monochromacity of the Data Web
is widely perceived to be the main obstacle for a wider deployment and
penetration of Linked Data and Semantic Technology (cf. e.g. [2]).
So
Hi Michael,
An immense breakthrough, thanks!
Tomorrow I will definitely show it to our MarCom team, I bet they'll
finally fall in love with linked data. The risk is that they start building
URIs patterns that matching the company's style guide... but I guess the
inconsistency of our URIs is an
Hi Michael,
There is a small bug in the Turtle representation: in e.g. my colour
http://companjen.name/id/BC a rdf:Resource ;
cold:colour loc:26bd27 .
cold:color a owl:AnnotationProperty ;
rdfs:label color@en ;
rdfs:domain rdf:Resource ;
rdfs:range
28 matches
Mail list logo
