Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
Hi Kingsley, Sorry but I still don't see a clear solution with your suggestion. Just like in Wikipedia when we see an Infobox_Person we assume that the resource is an dbo:Person we want to do the same in WikiData when we see a P107 Q215627http://www.wikidata.org/entity/Q215627claim In the 1st case it's an unstructured text to LD the 2nd is an LD2LD but to a less complicated and well-known schema (that will make existing DBpedia queries compatible to Wikidata) Thus, When I wrote the triple Q42 a dbo:Person, that triple did not came from dbr:Douglas_Adams as you replied but directly from the Wikidata claim Now, does Q42 need to be the original Wikidata resource http://www.wikidata.org/entity/Q42 and if yes, how should DBpedia publish dereference these triples? Or should we use our own domain and make owl:sameAs / foaf:primaryTopic links to Wikidata like we did with all Wikipedia language editions? Other suggestions / directions are also welcome of course! Best, Dimitris On Fri, Aug 30, 2013 at 7:45 PM, Kingsley Idehen kide...@openlinksw.comwrote: On 8/30/13 12:25 PM, Dimitris Kontokostas wrote: Thanks Kingsley, for now we don't host the data so wikidata.dbpedia.org/resource/.. does not dereference anything lets take an example to recup Q42 (Douglas Adams), besides the answer to the ultimate question [1] :) has the following triple http://www.wikidata.org/entity/Q42 http://www.wikidata.org/entity/P107 http://www.wikidata.org/entity/Q215627 which in our dump *will* be translated to http://wikidata.dbpedia.org/resource/Q42 owl:sameAs http://www.wikidata.org/entity/Q42 http://wikidata.dbpedia.org/resource/Q42 rdf:type dbpedia-owl:Person If I get it right, your suggestion is to generate this triple directly right? http://www.wikidata.org/entity/Q42 rdf:type dbpedia-owl:Person but in this case, when someone opens Q42 he/she will not see out added triples Having taken a closer look at the RDF content in WikiData documents It should be: http://www.wikidata.org/entity/Q42 foaf:primartyTopic http://dbpedia.org/resource/Douglas_Adamshttp://dbpedia.org/resource/Douglas_Adams. To be really safe, i.e., not vulnerable to changes relating to how they evolve handling of entity disambiguation via content negotiation etc., you can opt to be much more specific about the RDF document URLs: http://www.wikidata.org/entity/Q42.nt foaf:primaryTopic http://dbpedia.org/resource/Douglas_Adamshttp://dbpedia.org/resource/Douglas_Adams. http://www.wikidata.org/entity/Q42.rdf foaf:primaryTopic http://dbpedia.org/resource/Douglas_Adamshttp://dbpedia.org/resource/Douglas_Adams. That's it, let the Web of Linked Data do the rest :-) Kingsley. Cheers, Dimitris [1] http://en.wikipedia.org/wiki/42_%28number%29#The_Hitchhiker.27s_Guide_to_the_Galaxy On Fri, Aug 30, 2013 at 5:57 PM, Kingsley Idehen kide...@openlinksw.comwrote: On 8/29/13 2:45 PM, Hady elsahar wrote: i guess what we need now is to map between the original WikiData URIs and their URIs we use in DBpedia under the new namespace , for example : http://wikidata.dbpedia.org/resource/Q1293045 owl:sameAs http://wikidata.org/entity/Q1293045 No. As per my last two mails. You are making unnecessary work here. Wikidata is publishing RDF based Linked Data. Thus, simply use their URIs. Example of the implications of your current approach: curl -ILH Accept: text/turtle http://wikidata.dbpedia.org/resource/Q1293045 curl: (6) Couldn't resolve host 'wikidata.dbpedia.org' Just map the WikiData URI to the DBpedia URI and you leverage the benefits of: curl -ILH Accept: text/turtle http://wikidata.org/entity/Q1293045 HTTP/1.0 301 Moved Permanently Date: Fri, 30 Aug 2013 14:51:49 GMT Server: Apache *Location: http://www.wikidata.org/entity/Q1293045* *Content-Type: text/html*; charset=iso-8859-1 HTTP/1.0 302 Moved Temporarily Date: Fri, 30 Aug 2013 14:51:49 GMT Server: Apache *Location: https://www.wikidata.org/wiki/Special:EntityData/Q1293045* *Content-Type: text/html*; charset=iso-8859-1 HTTP/1.1 303 See Other Server: nginx/1.1.19 Date: Fri, 30 Aug 2013 14:51:54 GMT *Content-Type: text/html*; charset=utf-8 Connection: close X-Content-Type-Options: nosniff Cache-Control: private, s-maxage=0, max-age=0, must-revalidate Vary: Accept-Encoding,X-Forwarded-Proto,Cookie Expires: Thu, 01 Jan 1970 00:00:00 GMT Last-Modified: Fri, 30 Aug 2013 14:51:54 GMT *Location: https://www.wikidata.org/wiki/Special:EntityData/Q1293045.ttl* HTTP/1.1 200 OK Server: nginx/1.1.19 Date: Fri, 30 Aug 2013 14:51:55 GMT *Content-Type: text/turtle*; charset=UTF-8 Content-Length: 8388 -- Regards, Kingsley Idehen Founder CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile:
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
Hi everybody, we should focus on features, we can provide: Major Feature 1: loading data for SPARQL queries. This is independent from the URIs and we might use the Wikidata URIs or new ones. Major Feature 2: providing linked data for the data in the store. If we reuse Wikidata URIs, we will end up having data in the store, which is not crawlable via linked data. I see this as an essential feature, since we provide for now: 1. flat, easy RDF 2. properties mapped to the DBpedia Ontology 3. wikidata entities typed via the DBpedia Ontology 4. improved datatypes refined for compatability with xsd Suggesting the use of Wikidata URIs will disallow retrieving: http://www.wikidata.org/entity/QXXX a dbo:Person . http://www.wikidata.org/entity/QXXX dbo:birthPlace 1960-01-01^^xsd:date . while this will do: http://wd.dbpedia.org/entity/QXXX a dbo:Person . http://wd.dbpedia.org/entity/QXXX dbo:birthPlace 1960-01-01^^xsd:date . http://wd.dbpedia.org/entity/QXXX owl:sameAs http://www.wikidata.org/entity/QXXX . I am against losing this feature. Please everybody look at: https://www.wikidata.org/wiki/Special:EntityData/Q42.ttl You can find *only* labels and language links, not the cool data. Furthermore, I doubt that this will be available any time soon. Cleaning datatypes is no easy process. Hady is still young, but already quite a good and goal-oriented programmer and working overtime, so it is quite an investment, which is probably not high on their list. Failing to provide crawlable linked data will likely result in an effort like dbpedialite to fill the gap. We might shorten wikidata.dbpedia.org to wd.dbpedia.org though or just data.dbpedia.org @Kingsley and JC: do you agree? -- Sebastian Am 31.08.2013 09:20, schrieb Dimitris Kontokostas: Hi Kingsley, Sorry but I still don't see a clear solution with your suggestion. Just like in Wikipedia when we see an Infobox_Person we assume that the resource is an dbo:Person we want to do the same in WikiData when we see a P107 Q215627 http://www.wikidata.org/entity/Q215627 claim In the 1st case it's an unstructured text to LD the 2nd is an LD2LD but to a less complicated and well-known schema (that will make existing DBpedia queries compatible to Wikidata) Thus, When I wrote the triple Q42 a dbo:Person, that triple did not came from dbr:Douglas_Adams as you replied but directly from the Wikidata claim Now, does Q42 need to be the original Wikidata resource http://www.wikidata.org/entity/Q42 and if yes, how should DBpedia publish dereference these triples? Or should we use our own domain and make owl:sameAs / foaf:primaryTopic links to Wikidata like we did with all Wikipedia language editions? Other suggestions / directions are also welcome of course! Best, Dimitris On Fri, Aug 30, 2013 at 7:45 PM, Kingsley Idehen kide...@openlinksw.com mailto:kide...@openlinksw.com wrote: On 8/30/13 12:25 PM, Dimitris Kontokostas wrote: Thanks Kingsley, for now we don't host the data so wikidata.dbpedia.org/resource/ http://wikidata.dbpedia.org/resource/.. does not dereference anything lets take an example to recup Q42 (Douglas Adams), besides the answer to the ultimate question [1] :) has the following triple http://www.wikidata.org/entity/Q42 http://www.wikidata.org/entity/P107 http://www.wikidata.org/entity/Q215627 which in our dump *will* be translated to http://wikidata.dbpedia.org/resource/Q42 owl:sameAs http://www.wikidata.org/entity/Q42 http://wikidata.dbpedia.org/resource/Q42 rdf:type dbpedia-owl:Person If I get it right, your suggestion is to generate this triple directly right? http://www.wikidata.org/entity/Q42 rdf:type dbpedia-owl:Person but in this case, when someone opens Q42 he/she will not see out added triples Having taken a closer look at the RDF content in WikiData documents It should be: http://www.wikidata.org/entity/Q42 foaf:primartyTopic http://dbpedia.org/resource/Douglas_Adams http://dbpedia.org/resource/Douglas_Adams . To be really safe, i.e., not vulnerable to changes relating to how they evolve handling of entity disambiguation via content negotiation etc., you can opt to be much more specific about the RDF document URLs: http://www.wikidata.org/entity/Q42.nt foaf:primaryTopic http://dbpedia.org/resource/Douglas_Adams http://dbpedia.org/resource/Douglas_Adams . http://www.wikidata.org/entity/Q42.rdf foaf:primaryTopic http://dbpedia.org/resource/Douglas_Adams http://dbpedia.org/resource/Douglas_Adams . That's it, let the Web of Linked Data do the rest :-) Kingsley. Cheers, Dimitris [1] http://en.wikipedia.org/wiki/42_%28number%29#The_Hitchhiker.27s_Guide_to_the_Galaxy On Fri, Aug 30, 2013 at 5:57 PM, Kingsley Idehen kide...@openlinksw.com mailto:kide...@openlinksw.com wrote: On 8/29/13 2:45 PM, Hady elsahar
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
I'm not going to weigh in on the URI minting, but I did want to correct a couple of misconceptions. On Sat, Aug 31, 2013 at 3:20 AM, Dimitris Kontokostas jimk...@gmail.comwrote: Just like in Wikipedia when we see an Infobox_Person we assume that the resource is an dbo:Person That's a bad assumption. Not all Wikipedia articles which contain an Infobox:Person are about a person. we want to do the same in WikiData when we see a P107 Q215627http://www.wikidata.org/entity/Q215627claim P107 is going away. Don't use it. http://www.wikidata.org/wiki/Property:P107 Tom -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk___ Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
On 8/31/13 3:20 AM, Dimitris Kontokostas wrote: Hi Kingsley, Sorry but I still don't see a clear solution with your suggestion. Just like in Wikipedia when we see an Infobox_Person we assume that the resource is an dbo:Person we want to do the same in WikiData when we see a P107 Q215627 http://www.wikidata.org/entity/Q215627 claim In the 1st case it's an unstructured text to LD the 2nd is an LD2LD but to a less complicated and well-known schema (that will make existing DBpedia queries compatible to Wikidata) Thus, When I wrote the triple Q42 a dbo:Person, that triple did not came from dbr:Douglas_Adams as you replied but directly from the Wikidata claim Now, does Q42 need to be the original Wikidata resource http://www.wikidata.org/entity/Q42 and if yes, how should DBpedia publish dereference these triples? Or should we use our own domain and make owl:sameAs / foaf:primaryTopic links to Wikidata like we did with all Wikipedia language editions? Other suggestions / directions are also welcome of course! Best, Dimitris We have to first understand the Wikidata URIs. Let's use the following: 1. http://www.wikidata.org/entity/Q215627 -- a Document that describes a 'Person' class 2. http://www.wikidata.org/entity/Q42 -- a Document that describes 'Douglas Adams' (an instance of 'Person' class). The mapping would be as follows: TBox (Ontology): ## Wikidata RDF document describes a 'Person' class http://www.wikidata.org/entity/Q215627 http://open.vocab.org/terms/describes http://www.wikidata.org/entity/Q215627#this . ## Wikidata 'Person' class is equivalent to DBpedia 'Person' class http://www.wikidata.org/entity/Q215627#this owl:equivalentClass dbpedia-owl:Person . ABox (Assertions): ## Wikidata RDF Document describes 'Douglas Adams' but without explicit denotation via a URI ## thus, #this heuristic is used to derive a Linked Data URI for 'Douglas Adams' from the Wikidata RDF Document URL. http://www.wikidata.org/entity/Q42 http://open.vocab.org/terms/describes http://www.wikidata.org/entity/Q42#this ; foaf:primaryTopic http://www.wikidata.org/entity/Q42#this . ## derived URI for 'Douglas Adams' is then used as the subject or object of an owl:sameAs relation with the DBpedia URI for 'Douglas Adams' http://www.wikidata.org/entity/Q42#this owl:sameAs http://dbpedia.org/resource/Douglas_Adams . What I've outlined above is what exists right now with regards to the RDF documents produced by Wikidata. You don't need to mint new wikidata.dbpedia.org URIs . Kingsley On Fri, Aug 30, 2013 at 7:45 PM, Kingsley Idehen kide...@openlinksw.com mailto:kide...@openlinksw.com wrote: On 8/30/13 12:25 PM, Dimitris Kontokostas wrote: Thanks Kingsley, for now we don't host the data so wikidata.dbpedia.org/resource/ http://wikidata.dbpedia.org/resource/.. does not dereference anything lets take an example to recup Q42 (Douglas Adams), besides the answer to the ultimate question [1] :) has the following triple http://www.wikidata.org/entity/Q42 http://www.wikidata.org/entity/P107 http://www.wikidata.org/entity/Q215627 which in our dump *will* be translated to http://wikidata.dbpedia.org/resource/Q42 owl:sameAs http://www.wikidata.org/entity/Q42 http://wikidata.dbpedia.org/resource/Q42 rdf:type dbpedia-owl:Person If I get it right, your suggestion is to generate this triple directly right? http://www.wikidata.org/entity/Q42 rdf:type dbpedia-owl:Person but in this case, when someone opens Q42 he/she will not see out added triples Having taken a closer look at the RDF content in WikiData documents It should be: http://www.wikidata.org/entity/Q42 foaf:primartyTopic http://dbpedia.org/resource/Douglas_Adams http://dbpedia.org/resource/Douglas_Adams . To be really safe, i.e., not vulnerable to changes relating to how they evolve handling of entity disambiguation via content negotiation etc., you can opt to be much more specific about the RDF document URLs: http://www.wikidata.org/entity/Q42.nt foaf:primaryTopic http://dbpedia.org/resource/Douglas_Adams http://dbpedia.org/resource/Douglas_Adams . http://www.wikidata.org/entity/Q42.rdf foaf:primaryTopic http://dbpedia.org/resource/Douglas_Adams http://dbpedia.org/resource/Douglas_Adams . That's it, let the Web of Linked Data do the rest :-) Kingsley. Cheers, Dimitris [1] http://en.wikipedia.org/wiki/42_%28number%29#The_Hitchhiker.27s_Guide_to_the_Galaxy On Fri, Aug 30, 2013 at 5:57 PM, Kingsley Idehen kide...@openlinksw.com mailto:kide...@openlinksw.com wrote: On 8/29/13 2:45 PM, Hady elsahar wrote: i guess what we need now is to map between the original WikiData URIs and their URIs we use in DBpedia under the new namespace , for example : http://wikidata.dbpedia.org/resource/Q1293045 owl:sameAs
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
On 8/31/13 8:08 AM, Sebastian Hellmann wrote: Hi everybody, we should focus on features, we can provide: Major Feature 1: loading data for SPARQL queries. This is independent from the URIs and we might use the Wikidata URIs or new ones. Wikidata URIs as per the mail I just sent in response to Dimitris. Major Feature 2: providing linked data for the data in the store. If we reuse Wikidata URIs, we will end up having data in the store, which is not crawlable via linked data. The #this heuristic gets you around that problem. Thus, the follow-your-nose pathways remain intact, modulo any bugs in the actual RDF published by Wikidata (e.g., there are some bugs right now re. datatypes e.g., xsd:integer missing an r so you have xsd:intege etc.. Just typo style bugs in some places). I see this as an essential feature, since we provide for now: 1. flat, easy RDF 2. properties mapped to the DBpedia Ontology 3. wikidata entities typed via the DBpedia Ontology 4. improved datatypes refined for compatability with xsd Yes. Suggesting the use of Wikidata URIs will disallow retrieving: http://www.wikidata.org/entity/QXXX a dbo:Person . http://www.wikidata.org/entity/QXXX dbo:birthPlace 1960-01-01^^xsd:date . See my example: ## Wikidata RDF document describes a 'Person' class http://www.wikidata.org/entity/Q215627 http://open.vocab.org/terms/describes http://www.wikidata.org/entity/Q215627#this . ## Wikidata 'Person' class is equivalent to DBpedia 'Person' class http://www.wikidata.org/entity/Q215627#this owl:equivalentClass dbpedia-owl:Person . ABox (Assertions): ## Wikidata RDF Document describes 'Douglas Adams' but without explicit denotation via a URI ## thus, #this heuristic is used to derive a Linked Data URI for 'Douglas Adams' from the Wikidata RDF Document URL. http://www.wikidata.org/entity/Q42 http://open.vocab.org/terms/describes http://www.wikidata.org/entity/Q42#this ; foaf:primaryTopic http://www.wikidata.org/entity/Q42#this . ## derived URI for 'Douglas Adams' is then used as the subject or object of an owl:sameAs relation with the DBpedia URI for 'Douglas Adams' http://www.wikidata.org/entity/Q42#this owl:sameAs http://dbpedia.org/resource/Douglas_Adams . while this will do: http://wd.dbpedia.org/entity/QXXX a dbo:Person . http://wd.dbpedia.org/entity/QXXX dbo:birthPlace 1960-01-01^^xsd:date . http://wd.dbpedia.org/entity/QXXX owl:sameAs http://www.wikidata.org/entity/QXXX . You don't need that, if you follow the pattern outlined in the example above. You arrive at the very same place via: http://www.wikidata.org/entity/Q42#this owl:sameAs http://dbpedia.org/resource/Douglas_Adams . Both URIs resolve, and if owl:sameAs reasoning is applied, you get the union based mesh (smush) of the triples describing both of the entities participating in the aforementioned relation. I am against losing this feature. Please everybody look at: https://www.wikidata.org/wiki/Special:EntityData/Q42.ttl You can find *only* labels and language links, not the cool data. Yes, because that's a Turtle document, as per my example. Furthermore, I doubt that this will be available any time soon. Cleaning datatypes is no easy process. Hady is still young, but already quite a good and goal-oriented programmer and working overtime, so it is quite an investment, which is probably not high on their list. Failing to provide crawlable linked data will likely result in an effort like dbpedialite to fill the gap. We might shorten wikidata.dbpedia.org to wd.dbpedia.org though or just data.dbpedia.org @Kingsley and JC: do you agree? I agree with the fact that any mapping endeavor MUST keep follow-your-nose pattern crawling intact. I also believe we can achieve this via #this heuristic which ultimately save time and work in the future, one in which Wikidata will get better at publishing RDF based documents that bear Linked Data :-) Kingsley -- Sebastian Am 31.08.2013 09:20, schrieb Dimitris Kontokostas: Hi Kingsley, Sorry but I still don't see a clear solution with your suggestion. Just like in Wikipedia when we see an Infobox_Person we assume that the resource is an dbo:Person we want to do the same in WikiData when we see a P107 Q215627 http://www.wikidata.org/entity/Q215627 claim In the 1st case it's an unstructured text to LD the 2nd is an LD2LD but to a less complicated and well-known schema (that will make existing DBpedia queries compatible to Wikidata) Thus, When I wrote the triple Q42 a dbo:Person, that triple did not came from dbr:Douglas_Adams as you replied but directly from the Wikidata claim Now, does Q42 need to be the original Wikidata resource http://www.wikidata.org/entity/Q42 and if yes, how should DBpedia publish dereference these triples? Or should we use our own domain and make owl:sameAs / foaf:primaryTopic links to Wikidata like we did with all Wikipedia language editions? Other suggestions / directions are also
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
Am 31.08.2013 19:58, schrieb Kingsley Idehen: Suggesting the use of Wikidata URIs will disallow retrieving: http://www.wikidata.org/entity/QXXX a dbo:Person . http://www.wikidata.org/entity/QXXX dbo:birthPlace 1960-01-01^^xsd:date . See my example: ## Wikidata RDF document describes a 'Person' class http://www.wikidata.org/entity/Q215627 http://open.vocab.org/terms/describes http://www.wikidata.org/entity/Q215627#this . ## Wikidata 'Person' class is equivalent to DBpedia 'Person' class http://www.wikidata.org/entity/Q215627#this owl:equivalentClass dbpedia-owl:Person . That's a fine pattern for an OWL class mapping. ABox (Assertions): ## Wikidata RDF Document describes 'Douglas Adams' but without explicit denotation via a URI ## thus, #this heuristic is used to derive a Linked Data URI for 'Douglas Adams' from the Wikidata RDF Document URL. http://www.wikidata.org/entity/Q42 http://open.vocab.org/terms/describes http://www.wikidata.org/entity/Q42#this ; foaf:primaryTopic http://www.wikidata.org/entity/Q42#this . ## derived URI for 'Douglas Adams' is then used as the subject or object of an owl:sameAs relation with the DBpedia URI for 'Douglas Adams' http://www.wikidata.org/entity/Q42#this owl:sameAs http://dbpedia.org/resource/Douglas_Adams . I could agree for Wikidata URIs with a mapping to a DBpedia URI, but what about the remaining 8.948.128 URIs, which do not have such mapping ( 13,266,153 - 4,318,025, numbers are not accurate, because of functional pages) The owl:sameAs Linked Data doesn't work in these cases. -- Sebastian while this will do: http://wd.dbpedia.org/entity/QXXX a dbo:Person . http://wd.dbpedia.org/entity/QXXX dbo:birthPlace 1960-01-01^^xsd:date . http://wd.dbpedia.org/entity/QXXX owl:sameAs http://www.wikidata.org/entity/QXXX . You don't need that, if you follow the pattern outlined in the example above. You arrive at the very same place via: http://www.wikidata.org/entity/Q42#this owl:sameAs http://dbpedia.org/resource/Douglas_Adams . Both URIs resolve, and if owl:sameAs reasoning is applied, you get the union based mesh (smush) of the triples describing both of the entities participating in the aforementioned relation. I am against losing this feature. Please everybody look at: https://www.wikidata.org/wiki/Special:EntityData/Q42.ttl You can find *only* labels and language links, not the cool data. Yes, because that's a Turtle document, as per my example. Furthermore, I doubt that this will be available any time soon. Cleaning datatypes is no easy process. Hady is still young, but already quite a good and goal-oriented programmer and working overtime, so it is quite an investment, which is probably not high on their list. Failing to provide crawlable linked data will likely result in an effort like dbpedialite to fill the gap. We might shorten wikidata.dbpedia.org to wd.dbpedia.org though or just data.dbpedia.org @Kingsley and JC: do you agree? I agree with the fact that any mapping endeavor MUST keep follow-your-nose pattern crawling intact. I also believe we can achieve this via #this heuristic which ultimately save time and work in the future, one in which Wikidata will get better at publishing RDF based documents that bear Linked Data :-) Kingsley -- Sebastian Am 31.08.2013 09:20, schrieb Dimitris Kontokostas: Hi Kingsley, Sorry but I still don't see a clear solution with your suggestion. Just like in Wikipedia when we see an Infobox_Person we assume that the resource is an dbo:Person we want to do the same in WikiData when we see a P107 Q215627 http://www.wikidata.org/entity/Q215627 claim In the 1st case it's an unstructured text to LD the 2nd is an LD2LD but to a less complicated and well-known schema (that will make existing DBpedia queries compatible to Wikidata) Thus, When I wrote the triple Q42 a dbo:Person, that triple did not came from dbr:Douglas_Adams as you replied but directly from the Wikidata claim Now, does Q42 need to be the original Wikidata resource http://www.wikidata.org/entity/Q42 and if yes, how should DBpedia publish dereference these triples? Or should we use our own domain and make owl:sameAs / foaf:primaryTopic links to Wikidata like we did with all Wikipedia language editions? Other suggestions / directions are also welcome of course! Best, Dimitris On Fri, Aug 30, 2013 at 7:45 PM, Kingsley Idehen kide...@openlinksw.com mailto:kide...@openlinksw.com wrote: On 8/30/13 12:25 PM, Dimitris Kontokostas wrote: Thanks Kingsley, for now we don't host the data so wikidata.dbpedia.org/resource/ http://wikidata.dbpedia.org/resource/.. does not dereference anything lets take an example to recup Q42 (Douglas Adams), besides the answer to the ultimate question [1] :) has the following triple http://www.wikidata.org/entity/Q42 http://www.wikidata.org/entity/P107 http://www.wikidata.org/entity/Q215627
Re: [Dbpedia-discussion] [Dbpedia-developers] [ANN] [GSoC 2013]: DBpedia Viewer
Great job, folks! It's roundhouse kick-ass!!! I didn't find the DBpedia Spotlight plug there. Where is it? :) Cheers, Pablo On Fri, Aug 30, 2013 at 9:42 AM, Denis Lukovnikov lukovni...@outlook.comwrote: Hi all, We're pleased to announce the new (beta) version of the DBpedia Linked Data interface page as a part of a Google Summer of Code project. The new version now features: - A revamped Linked Data view - Quick filtering of properties and their values - Quick Links to important properties - Entity search using DBpedia Lookup - Text annotation with DBpedia Spotlight - previews on hover The new DBpedia Viewer is deployed at the Dutch DBpediahttp://nl.dbpedia.org/ . All feedback, comments and thumbs up are welcome :). For issues: https://github.com/lukovnikov/dbpedia-vad-i18n/issues To check it out, visit http://nl.dbpedia.org/page/Chuck_Norris. Greetings, Denis, Claus, Dimitris, Sebastian -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ Dbpedia-developers mailing list dbpedia-develop...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-developers -- Pablo N. Mendes http://pablomendes.com -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk___ Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
