- From: Alexandre Passant <alexandre.passant@deri.org>
- Date: Wed, 18 Aug 2010 07:42:45 +0100
- To: Patrick van Kleef <pkleef@openlinksw.com>
- Cc: Linked Data community <public-lod@w3.org>
On 17 Aug 2010, at 21:25, Patrick van Kleef wrote:
> HI Alexandre,
>
>>>>
>>>> Running SPARQL queries on the DBpedia endpoint [1] produces different results than queries on the LOD one [2] when restricting to the dbpedia graph.
>>>> Which one contains the latest datasets ?
>>>>
>>>> NB: Is there a voiD description associated to these endpoints ?
>>>>
>>>> [1] http://dbpedia.org/sparql
>>>> [2] http://lod.openlinksw.com/sparql
>>>
>>>
>>> Both dbpedia.org and lod.openlinksw.com contain the same DBpedia 3.5.1 dataset, however in LOD certain datafiles are loaded in their own graph at this time:
>>
>> Thanks - but how comes that I have different results on the endpoints while indicating http://dbpedia.org as the default graph in both queries ?
>> For instance, when running
>>
>> SELECT ?o count(?o) as ?c WHERE {
>> ?s rdf:type ?o
>> }
>> ORDER BY DESC(?c)
>> LIMIT 50
>>
>> I have
>>
>> http://dbpedia.org/class/yago/LivingPeople 236951
>>
>> As a result on the DBpedia endpoint, but not on the LOD one.
>> Are the Yago mappings loaded in the http://dbpedia.org graph (and not on the Yago one, as you mention below) in the DBpedia endpoint ?
>>
>
> No, as stated before on LOD the yago class data is in a separate graph,
Ah, thanks, I misunderstood your initial email.
So the http://dbpedia.org graph contains different data in the DBpedia endpoint and in the LOD one.
That's imo a bit counter-intuitive (as hosted by the same vendor, etc.)
Alex.
> so you would need to use:
>
> SELECT ?o count(?o) as ?c
> FROM <http://dbpedia.org/yagoclasses>
> WHERE {
> ?s rdf:type ?o
> }
> ORDER BY DESC(?c)
> LIMIT 50
>
> See:
> http://bit.ly/bF0yo3
>
>
>>>
>>> bookmashup_links.nt.gz http://dbpedia.org/bookmashup
>>> dailymed_links.nt.gz http://dbpedia.org/dailymed
>>> dblp_links.nt.gz http://dbpedia.org/dblp
>>> diseasome_links.nt.gz http://dbpedia.org/diseasome
>>> drugbank_links.nt.gz http://dbpedia.org/drugbank
>>> eurostat_links.nt.gz http://dbpedia.org/eurostat
>>> factbook_links.nt.gz http://dbpedia.org/factbook
>>> flickr_links.nt.gz http://dbpedia.org/flickr
>>> freebase_links.nt.gz http://dbpedia.org/freebase
>>> geonames_links.nt.gz http://dbpedia.org/geonames
>>> gutenberg_links.nt.gz http://dbpedia.org/gutenberg
>>> musicbrainz_links.nt.gz http://dbpedia.org/musicbrainz
>>> nyt_links.nt.gz http://dbpedia.org/nyt
>>> opencyc_links.nt.gz http://dbpedia.org/opencyc
>>> revyu_links.nt.gz http://dbpedia.org/revyu
>>> sider_links.nt.gz http://dbpedia.org/sider
>>> tcm_links.nt.gz http://dbpedia.org/tcm
>>> uscensus_links.nt.gz http://dbpedia.org/uscensus
>>> wikicompany_links.nt.gz http://dbpedia.org/wikicompany
>>> wordnet_links.nt.gz http://dbpedia.org/wordnet
>>> yago_links.nt.gz http://dbpedia.org/yago
>>> yagoclasses_links.nt.gz http://dbpedia.org/yagoclasses
>>>
>>>
>>> All other dbpedia data files are loaded in http://dbpedia.org
>
> Best regards,
>
> Patrick
>
--
Dr. Alexandre Passant
Digital Enterprise Research Institute
National University of Ireland, Galway
:me owl:sameAs <http://apassant.net/alex> .
Received on Wednesday, 18 August 2010 06:43:51 UTC