Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
Am 01.09.2013 00:54, schrieb Kingsley Idehen: To be clear, my only focus (as exemplified by my examples) was those items for which there could be cross-link-mappings i.e., a typical DBpedia linkeset with Wikidata URIs as the target. Beyond the common entities oriented linkset, I suspect DBpedia domain URIs might be the only option, since we have little control over Wikidata etc.. Priority wise though, I would encourage initial production of linksets aimed at mapping common TBox and ABox items across DBpedia and Wikidata. I think Hady will succeed in doing both + datatypes. Live Updates are out-of-scope, but might follow soon. One problem is, that we will not have uniformity in queries. If we replicate only Wikidata ids with no DBpedia Link, then people might need a UNION in SPARQL. I think the best way to decide, would be if Hady made some examples, how the RDF could look like. Sebastian Kingsley -- 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 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
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
I guess the problem we're facing is rather common: Organisation A (in our case, Wikidata) publishes data about some entities and defines an identifier for each entity. Organisation B (in our case, DBpedia) wants to publish additional data about these entities. Does B have to use new identifiers? That doesn't feel right. In RDF, URIs are primarily IDs. Their use as URLs is secondary. Why is it so important what data I get when I use a URI as a URL? I honestly don't quite understand. DBpedia can offer triple files for download which contain Wikidata URIs, and DBpedia can load such triples into a triple store. For example, the triples available at dbpedia.org/sparql can use any namespaces they want, they are by no means restricted to dbpedia.org. What DBpedia can't do is change the data that an HTTP request to a Wikidata URI returns. So what? Slightly puzzled, Christopher On 1 September 2013 11:08, Sebastian Hellmann hellm...@informatik.uni-leipzig.de wrote: Am 01.09.2013 00:54, schrieb Kingsley Idehen: To be clear, my only focus (as exemplified by my examples) was those items for which there could be cross-link-mappings i.e., a typical DBpedia linkeset with Wikidata URIs as the target. Beyond the common entities oriented linkset, I suspect DBpedia domain URIs might be the only option, since we have little control over Wikidata etc.. Priority wise though, I would encourage initial production of linksets aimed at mapping common TBox and ABox items across DBpedia and Wikidata. I think Hady will succeed in doing both + datatypes. Live Updates are out-of-scope, but might follow soon. One problem is, that we will not have uniformity in queries. If we replicate only Wikidata ids with no DBpedia Link, then people might need a UNION in SPARQL. I think the best way to decide, would be if Hady made some examples, how the RDF could look like. Sebastian Kingsley -- 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 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 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/.. does not dereference anything lets take an example to recup Q42
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
Hi Kingsley all, Wikidata RDF URIs are of the form http://www.wikidata.org/entity/Q42 , not http://www.wikidata.org/entity/Q42#this . Maybe the response codes of Wikidata's HTTP server are not quite correct yet, but http://www.wikidata.org/entity/Q42 is not meant to be the URI of a document about Douglas Adams. It's meant to be the Wikidata RDF URI for the entity otherwise known as Douglas Adams. I also didn't understand how appending #this helps with our current problem. As I understand it, the problem is that DBpedia wants to publish data about Wikidata items, but that data won't be returned by HTTP requests to Wikidata URIs. Regards, Christopher On 31 August 2013 19:58, Kingsley Idehen kide...@openlinksw.com wrote: 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
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
On 9/1/13 11:42 AM, Jona Christopher Sahnwaldt wrote: Hi Kingsley all, Wikidata RDF URIs are of the form http://www.wikidata.org/entity/Q42 , not http://www.wikidata.org/entity/Q42#this . I didn't imply they were. What I am demonstrating is the fact that adding #this produces a global identifier that can be used for denotation in a manner that facilitates cross linkage. The URI/URL http://www.wikidata.org/entity/Q42 denotes a Web Document. The URI http://www.wikidata.org/entity/Q42#this denotes something else e.g., the entity described by the document http://www.wikidata.org/entity/Q42 . Net effect, you can make a linkset comprised of owl:sameAs relations without minting new URIs e.g., new DBpedia URIs. You also end up with RDF triples that can be merged in the context of owl:sameAs based reasoning etc.. Maybe the response codes of Wikidata's HTTP server are not quite correct yet, but http://www.wikidata.org/entity/Q42 is not meant to be the URI of a document about Douglas Adams. At this point in time, that's exactly what it is. The Wikidata folks could also opt to achieve disambiguation via the use of #this or #{whatever} at a later date. The most important point here is that we have a loosely coupled solution that handles the fact that we have two distinct projects moving at different rates, for a myriad of reasons. It's meant to be the Wikidata RDF URI for the entity otherwise known as Douglas Adams. See my comments above. The meaning is currently out-of-band until the URIs of the document and the entity 'Douglas Adams' are disambiguated in the the RDF document content. This is the eternal issue with RDF and Linked Data. I've tried to explain, tirelessly, that RDF != Linked Data. Having an RDF document with out-of-band data isn't necessarily fine-grained Linked Data. You have to disambiguate between Document and other Entities so that the meaning conveyed by RDF statements is clear to humans and machines. I also didn't understand how appending #this helps with our current problem. I hope I've explained that above. Basically, it negates the need for 303 based disambiguation which ultimately becomes a headache for someone e.g., the Wikidata folks. As I understand it, the problem is that DBpedia wants to publish data about Wikidata items, but that data won't be returned by HTTP requests to Wikidata URIs. DBpedia wants to be able to merge data from Wikidata with data that already exists in DBpedia. If done right, this brings Wikidata into the LOD cloud etc.. Kingsley Regards, Christopher On 31 August 2013 19:58, Kingsley Idehen kide...@openlinksw.com wrote: 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
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
On 9/1/13 4:31 PM, Kingsley Idehen wrote: On 9/1/13 11:42 AM, Jona Christopher Sahnwaldt wrote: Hi Kingsley all, Wikidata RDF URIs are of the form http://www.wikidata.org/entity/Q42 , not http://www.wikidata.org/entity/Q42#this . I didn't imply they were. What I am demonstrating is the fact that adding #this produces a global identifier that can be used for denotation in a manner that facilitates cross linkage. The URI/URL http://www.wikidata.org/entity/Q42 denotes a Web Document. The URI http://www.wikidata.org/entity/Q42#this denotes something else e.g., the entity described by the document http://www.wikidata.org/entity/Q42 . Net effect, you can make a linkset comprised of owl:sameAs relations without minting new URIs e.g., new DBpedia URIs. You also end up with RDF triples that can be merged in the context of owl:sameAs based reasoning etc.. I've just re-run some tests against the Wikidata URIs using curl, here's what I am now seeing: curl -IL http://www.wikidata.org/entity/Q42 HTTP/1.0 302 Moved Temporarily Date: Sun, 01 Sep 2013 22:29:23 GMT Server: Apache *Location: https://www.wikidata.org/wiki/Special:EntityData/Q42* Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 303 See Other Server: nginx/1.1.19 Date: Sun, 01 Sep 2013 22:29:24 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 HTTP/1.1 200 OK Server: nginx/1.1.19 Date: Sun, 01 Sep 2013 22:29:25 GMT Content-Type: application/json; charset=UTF-8 Conclusion: In a pretty awkward way, Wikidata is asserting that: http://www.wikidata.org/entity/Q42 denotes an entity e.g., 'Douglas Adams' . https://www.wikidata.org/wiki/Special:EntityData/Q42 denotes a document that describes http://www.wikidata.org/entity/Q42. Thus, one can conclude: http://www.wikidata.org/entity/Q42 owl:sameAs http://dbpedia.org/resource/Douglas_Adams . Still not requiring DBpedia specific URIs for Wikidata. On the TBox side, we have: curl -IL http://www.wikidata.org/entity/Q215627 HTTP/1.0 302 Moved Temporarily Date: Sun, 01 Sep 2013 22:38:42 GMT Server: Apache *Location: https://www.wikidata.org/wiki/Special:EntityData/Q215627* Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 303 See Other Server: nginx/1.1.19 Date: Sun, 01 Sep 2013 22:38:43 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: Sun, 01 Sep 2013 22:38:43 GMT Location: https://www.wikidata.org/wiki/Special:EntityData/Q215627.json We can also conclude: http://www.wikidata.org/entity/Q215627 denotes the class 'Person' . Document URI/URL https://www.wikidata.org/wiki/Special:EntityData/Q215627 denotes a Document that describes http://www.wikidata.org/entity/Q215627. Thus, http://www.wikidata.org/entity/Q215627 owl:equivalentClass dbpedia-owl:Person . Please note that during the evolution of this conversation, Wikidata has moved from serving up Turtle to serving JSON. The content-types don't help (e.g. text/html) which ultimately is going to break follow-your-nose exploration. Based on the gymnastics that have occurred over this weekend, alone, I can understand the desire to actually mint DBpedia domain URIs with follow-your-nose exploration protection in mind. This thread is basically justification for what (until now) I've opposed re., justification for DBpedia URI minting for structured data from Wikidata. IMHO., when it comes to Linked Data, follow-your-nose exploration is non negotiable, we must protect it at all times, even if it means minting new DBpedia URIs ! -- 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: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature -- 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
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] Mapping Wikidata properties to DBpedia ones
On 8/29/13 2:48 PM, Jona Christopher Sahnwaldt wrote: Hi Hady, On 29 August 2013 20:45, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, WikiData URIs inside DBpedia is under a new name space called wikidata on the form http://wikidata.dbpedia.org/resource/Q1293045 the sameas dump contains mappings between URIs of Wikidata entities inside DBpedia (the one described above) and DBpedia entities. 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 Why don't you just use the WIkidata URI? Correct! These have to be Wikidata Linked Data URIs, as per my earlier post. cURL analysis: 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 Kingsley Cheers, JC i was intending to add this in the next release, but if it's needed for loading up the data i guess we can let it run before that. thanks Regards On Thu, Aug 29, 2013 at 7:22 PM, Jona Christopher Sahnwaldt j...@sahnwaldt.de wrote: On 29 August 2013 17:26, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 11:15 AM, Jona Christopher Sahnwaldt wrote: On 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Specifically, the following: 1. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-sameas.ttl.gz 2. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-labels.ttl.gz 3. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata.ttl.gz . We loaded these into our LOD cloud cache only to find out that the subject URIs for the sameAs relations where incorrect i.e., they don't resolve. For example, the dataset had http://wikidata.dbpedia.org/resource/Q1293045 when it should be http://www.wikidata.org/entity/Q1293045 . I don't know about these. @Hady @Sebastian, can you help? Kingsley Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
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 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: http://www.linkedin.com/in/kidehen -- 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 -- Kontokostas Dimitris -- 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/30/13 2:50 AM, Dimitris Kontokostas wrote: Hi Kingsley, The main reason we use new URIs is because we want to assert new triples (based on the DBpedia ontology) and make this knowledge dereferencable in the future. There's no need for minting new URIs for the following reasons: 1. An owl:sameAs relation is simply about asserting coreference between two URIs -- so when you merge (smush) to end up with a richer description that applies to either URI 2. An owl:sameAs relation is symmetrical -- i.e., the subject or object role in the relationship (facilitated by the owl:sameAs relation) doesn't change anything. Maybe we are doing something wrong (and this is why we do an early release) but imo, it's the same reason we didn't use the Wikipedia URIs in DBpedia in the first place. There's a difference here, Wikidata is publishing RDF model based Linked Data. Wikipedia doesn't publish RDF model based Linked Data. Re., Wikipedia, also note, that we forward-chained relations in the version we host such that each Wikipedia document URI/URL is the subject of a foaf:primaryTopic relation that has a DBpedia Entity URI as its object -- which enables easy discovery of DBpedia URIs associated with Wikipedia Document URI/URLs using follow-your-nose patterns via a browser or SPARQL query etc.. I was also thinking of a little shorter name like data.dbpedia.org http://data.dbpedia.org, or db ;) Best you stick with the Wikidata Linked Data URIs. All other options are problematic cost-generating vectors. Although using just dbpedia.org http://dbpedia.org and moving existing English DBpedia to en.dbpedia.org http://en.dbpedia.org would be the best approach (that ain't gonna happen soon) Correct :-) Kingsley Cheers, Dimitris On Thu, Aug 29, 2013 at 9:48 PM, Jona Christopher Sahnwaldt j...@sahnwaldt.de mailto:j...@sahnwaldt.de wrote: Hi Hady, On 29 August 2013 20:45, Hady elsahar hadyelsa...@gmail.com mailto:hadyelsa...@gmail.com wrote: Hello All, WikiData URIs inside DBpedia is under a new name space called wikidata on the form http://wikidata.dbpedia.org/resource/Q1293045 the sameas dump contains mappings between URIs of Wikidata entities inside DBpedia (the one described above) and DBpedia entities. 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 Why don't you just use the WIkidata URI? Cheers, JC i was intending to add this in the next release, but if it's needed for loading up the data i guess we can let it run before that. thanks Regards On Thu, Aug 29, 2013 at 7:22 PM, Jona Christopher Sahnwaldt j...@sahnwaldt.de mailto:j...@sahnwaldt.de wrote: On 29 August 2013 17:26, Kingsley Idehen kide...@openlinksw.com mailto:kide...@openlinksw.com wrote: On 8/29/13 11:15 AM, Jona Christopher Sahnwaldt wrote: On 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com mailto:kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org http://www.wikidata.org for equivalent wikidata properties (and to schema.org http://schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Specifically, the following: 1. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-sameas.ttl.gz 2. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-labels.ttl.gz 3. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata.ttl.gz . We loaded these into our LOD cloud cache only to find out that the subject URIs for the sameAs relations where incorrect i.e., they don't resolve. For example, the dataset had http://wikidata.dbpedia.org/resource/Q1293045 when it
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
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: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature -- 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
Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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
Hi guys, this is really well done :-) I will take a look at it as soon as possible. Bravo Hady and mentors :-) Cheers Andrea 2013/8/29 Jona Christopher Sahnwaldt j...@sahnwaldt.de Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature -- 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 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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: http://www.linkedin.com/in/kidehen -- 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 -- 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/29/13 11:15 AM, Jona Christopher Sahnwaldt wrote: On 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Mappings from DBpedia to Wikidata via owl:sameAs relations. Ditto any other mappings, e.g., what's taking shape re. the TBox (i.e. ontology ). Kingsley Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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: http://www.linkedin.com/in/kidehen -- 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 -- 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: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature -- 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
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
Hi Hady, regarding the Google Doc - I removed the pointy braces from the Wikidata property URIs so Google Docs turns them into clickable links. I hope that's ok. Makes work a little easier. It would be great if you could add a column with the English labels of the Wikidata properties, if that's not too much work. We'd still have to click on the link to Wikidata to really understand what the proerty means, but it would make the table much more readable. Cheers, JC On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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/29/13 11:15 AM, Jona Christopher Sahnwaldt wrote: On 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Specifically, the following: 1. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-sameas.ttl.gz 2. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-labels.ttl.gz 3. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata.ttl.gz . We loaded these into our LOD cloud cache only to find out that the subject URIs for the sameAs relations where incorrect i.e., they don't resolve. For example, the dataset had http://wikidata.dbpedia.org/resource/Q1293045 when it should be http://www.wikidata.org/entity/Q1293045 . Kingsley Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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: http://www.linkedin.com/in/kidehen -- 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 -- 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: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature -- Learn the
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
On 29 August 2013 17:21, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 11:15 AM, Jona Christopher Sahnwaldt wrote: On 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Mappings from DBpedia to Wikidata via owl:sameAs relations. These relations are contained in the ontology. The ontology at http://mappings.dbpedia.org/server/ontology/dbpedia.owl is always up to date and contains links like owl:ObjectProperty rdf:about=http://dbpedia.org/ontology/author; ... owl:equivalentProperty rdf:resource=http://schema.org/author/ owl:equivalentProperty rdf:resource=http://www.wikidata.org/entity/P50/ /owl:ObjectProperty Ditto any other mappings, e.g., what's taking shape re. the TBox (i.e. ontology ). Kingsley Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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: http://www.linkedin.com/in/kidehen -- 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 -- 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: http://www.linkedin.com/in/kidehen
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
On 29 August 2013 17:26, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 11:15 AM, Jona Christopher Sahnwaldt wrote: On 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Specifically, the following: 1. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-sameas.ttl.gz 2. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-labels.ttl.gz 3. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata.ttl.gz . We loaded these into our LOD cloud cache only to find out that the subject URIs for the sameAs relations where incorrect i.e., they don't resolve. For example, the dataset had http://wikidata.dbpedia.org/resource/Q1293045 when it should be http://www.wikidata.org/entity/Q1293045 . I don't know about these. @Hady @Sebastian, can you help? Kingsley Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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: http://www.linkedin.com/in/kidehen -- 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 -- 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:
Re: [Dbpedia-discussion] [Dbpedia-developers] Mapping Wikidata properties to DBpedia ones
Hello All, WikiData URIs inside DBpedia is under a new name space called wikidata on the form http://wikidata.dbpedia.org/**resource/Q1293045http://wikidata.dbpedia.org/resource/Q1293045 the sameas dump contains mappings between URIs of Wikidata entities inside DBpedia (the one described above) and DBpedia entities. 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 i was intending to add this in the next release, but if it's needed for loading up the data i guess we can let it run before that. thanks Regards On Thu, Aug 29, 2013 at 7:22 PM, Jona Christopher Sahnwaldt j...@sahnwaldt.de wrote: On 29 August 2013 17:26, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 11:15 AM, Jona Christopher Sahnwaldt wrote: On 29 August 2013 17:07, Kingsley Idehen kide...@openlinksw.com wrote: On 8/29/13 9:49 AM, Jona Christopher Sahnwaldt wrote: Hi Hady and all, good stuff! After a few changes [1][2][3][4], the mappings wiki now renders http links to property pages on www.wikidata.org for equivalent wikidata properties (and to schema.org and bibo as well). Cheers, Christopher [1] http://mappings.dbpedia.org/index.php/Template:LinkProperties?action=history [2] http://mappings.dbpedia.org/index.php/Template:LinkProperty?action=history [3] http://mappings.dbpedia.org/index.php/Template:DatatypeProperty?action=history [4] http://mappings.dbpedia.org/index.php/Template:ObjectProperty?action=history Great! Is there new URL for a revised dump? Or is the revised dump accessible using the existing dump URL? which dump? Specifically, the following: 1. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-sameas.ttl.gz 2. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata-labels.ttl.gz 3. http://wiktionary.dbpedia.org/wikidata_tmp/wikidatawiki-20130817-wikidata.ttl.gz . We loaded these into our LOD cloud cache only to find out that the subject URIs for the sameAs relations where incorrect i.e., they don't resolve. For example, the dataset had http://wikidata.dbpedia.org/resource/Q1293045 when it should be http://www.wikidata.org/entity/Q1293045 . I don't know about these. @Hady @Sebastian, can you help? Kingsley Kingsley On 29 August 2013 13:25, Hady elsahar hadyelsa...@gmail.com wrote: Hello All, as a part of GSoC2013 project , integrating WikiData inside DBpedia , we are in the phase of mapping Wikidata properties to DBpedia ones . this is important because once all mappings are done we can extract a complete DBpedia facts dump with DBpedia properties from the Wikidata one So, we need a little help from the community to in mapping of Wikidata properties , there's around 544 Wikdata properties in use , that needs mapping you can check most important ones in that Google spreadsheet to start with ,also properties that weren't mapped yet. in this wikipage there are detailed steps to add the mappings. thanks Regards - Hady El-Sahar Research Assistant Center of Informatics Sciences | Nile University -- 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 -- 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 -- 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: