Re: [Wikidata-l] Wikidata RDF Issues
Am 21.10.2013 23:43, schrieb Kingsley Idehen: Kingsley, do you think having two 303s (from /entity/Q$1 to /wiki/Special:EntityData/$1 and another one to wiki/Special:EntityData/$1.xxx) would be appropriate or at least better than what we have now? Yes. 303 is what you want. Also note that 303's can now be cached re. newer HTTP spec guidelines. Thus, this is your simplest fix. Ticked filed: https://bugzilla.wikimedia.org/show_bug.cgi?id=56307 -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Am 17.10.2013 20:16, schrieb Kingsley Idehen: On 10/17/13 12:46 PM, Daniel Kinzler wrote: I've run it through our variant of Vapour re. Linked Data verification: http://bit.ly/1gM7oYa . Nearly there. Your use of 302 is what's going to trip up existing Linked Data clients. Why aren't you using 303 for redirection? There actually is a 303 *and* a 302, and in the wrong order. The ops guys had some issues coming up with the correct rewrite rules, and then it got stuck, I'm afraid. -- daniel Can't this get fixed? A 302 isn't the same thing as a 303. Sure it could. It would probably take the right person 15 minutes. I have been trying to find the right person for half a year now. The truth is, this is simply not very high on anyones priority list (including mine). It's an issue, it bothers me, i'd love to see it fixed, but there's a lot of things with a lot more impact for a lot more people on my list. -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On Mon, Oct 21, 2013 at 2:49 PM, Kingsley Idehen kide...@openlinksw.com wrote: Daniel, Being interoperable with the Linked Open Data cloud via DBpedia is a low cost high-impact affair for Wikidata. I don't know of anything of higher impact in the grand scheme of thing bearing in mind we all know that NIH (Not Invented Here) is ultimately always a shortcut to time-wasted. Let's always avert generating undue costs. This is a highly beneficial issue that simply requires a single individual to make a trivial tweak. There are things that are more high-impact that this right now. For example getting the numbers datatype and queries done. That being said if there is someone who knows their way around apache rewrite rules very well and would be willing to look into this please send them my way. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Obentrautstr. 72 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/21/13 8:58 AM, Lydia Pintscher wrote: On Mon, Oct 21, 2013 at 2:49 PM, Kingsley Idehen kide...@openlinksw.com wrote: Daniel, Being interoperable with the Linked Open Data cloud via DBpedia is a low cost high-impact affair for Wikidata. I don't know of anything of higher impact in the grand scheme of thing bearing in mind we all know that NIH (Not Invented Here) is ultimately always a shortcut to time-wasted. Let's always avert generating undue costs. This is a highly beneficial issue that simply requires a single individual to make a trivial tweak. There are things that are more high-impact that this right now. For example getting the numbers datatype and queries done. That being said if there is someone who knows their way around apache rewrite rules very well and would be willing to look into this please send them my way. Cheers Lydia Lydia, If you can share the existing re-write rules file via a URL or github project, I'll have get someone (should I not get round to it) to fix them accordingly. Ball back in your court, so to speak :-) -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On Mon, Oct 21, 2013 at 3:26 PM, Kingsley Idehen kide...@openlinksw.com wrote: If you can share the existing re-write rules file via a URL or github project, I'll have get someone (should I not get round to it) to fix them accordingly. Ball back in your court, so to speak :-) Hehe. Here you go: https://gerrit.wikimedia.org/r/#/admin/projects/operations/apache-config Thanks for looking into it! Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Obentrautstr. 72 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/21/13 9:59 AM, Lydia Pintscher wrote: On Mon, Oct 21, 2013 at 3:26 PM, Kingsley Idehen kide...@openlinksw.com wrote: If you can share the existing re-write rules file via a URL or github project, I'll have get someone (should I not get round to it) to fix them accordingly. Ball back in your court, so to speak :-) Hehe. Here you go: https://gerrit.wikimedia.org/r/#/admin/projects/operations/apache-config Thanks for looking into it! Cheers Lydia Can someone not change 302 to 303 re: RewriteRule ^/entity/(.*)$ https://www.wikidata.org/wiki/Special:EntityData/$1 [R=302,QSA] ? See: http://pastebin.com/dbmGmCt8 . -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
From 'temporary redirect' to 'see other' ? Addshore On 21 October 2013 16:48, Kingsley Idehen kide...@openlinksw.com wrote: On 10/21/13 9:59 AM, Lydia Pintscher wrote: On Mon, Oct 21, 2013 at 3:26 PM, Kingsley Idehen kide...@openlinksw.com wrote: If you can share the existing re-write rules file via a URL or github project, I'll have get someone (should I not get round to it) to fix them accordingly. Ball back in your court, so to speak :-) Hehe. Here you go: https://gerrit.wikimedia.org/**r/#/admin/projects/operations/** apache-confighttps://gerrit.wikimedia.org/r/#/admin/projects/operations/apache-config Thanks for looking into it! Cheers Lydia Can someone not change 302 to 303 re: RewriteRule ^/entity/(.*)$ https://www.wikidata.org/wiki/**Special:EntityData/$1https://www.wikidata.org/wiki/Special:EntityData/$1[R=302,QSA] ? See: http://pastebin.com/dbmGmCt8 . -- Regards, Kingsley Idehen Founder CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/**blog/~kidehenhttp://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/**112399767740508618350/abouthttps://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/**kidehenhttp://www.linkedin.com/in/kidehen ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Am 21.10.2013 16:48, schrieb Kingsley Idehen: Can someone not change 302 to 303 re: RewriteRule ^/entity/(.*)$ https://www.wikidata.org/wiki/Special:EntityData/$1 [R=302,QSA] ? The thing is that we intended this to be an internal apache rewrite, not a HTTP redirect at all. Because Special:EntityData itself implements the content negotiation that triggers a 303 when appropriate. So, currently we get a 302 from /entity/Q$1 to /wiki/Special:EntityData/$1 (the generic document URI), which then applies content negotiation and sends a 303 pointing to e.g. /wiki/Special:EntityData/$1.ttl (the URL of a specific serialization, e.g. in turtle). What I want is to remove the initial 302 completely using an internal rewrite, not replace it with another 303 - since I don't think that's semantically correct. This did not work when tried, for reasons unknown to me. Someone suggester that the wrong options where set for the rewrite rule, who knows. Kingsley, do you think having two 303s (from /entity/Q$1 to /wiki/Special:EntityData/$1 and another one to wiki/Special:EntityData/$1.xxx) would be appropriate or at least better than what we have now? -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/21/13 4:52 PM, Daniel Kinzler wrote: Am 21.10.2013 16:48, schrieb Kingsley Idehen: Can someone not change 302 to 303 re: RewriteRule ^/entity/(.*)$ https://www.wikidata.org/wiki/Special:EntityData/$1 [R=302,QSA] ? The thing is that we intended this to be an internal apache rewrite, not a HTTP redirect at all. Because Special:EntityData itself implements the content negotiation that triggers a 303 when appropriate. So, currently we get a 302 from /entity/Q$1 to /wiki/Special:EntityData/$1 (the generic document URI), which then applies content negotiation and sends a 303 pointing to e.g. /wiki/Special:EntityData/$1.ttl (the URL of a specific serialization, e.g. in turtle). What I want is to remove the initial 302 completely using an internal rewrite, not replace it with another 303 - since I don't think that's semantically correct. This did not work when tried, for reasons unknown to me. Someone suggester that the wrong options where set for the rewrite rule, who knows. Kingsley, do you think having two 303s (from /entity/Q$1 to /wiki/Special:EntityData/$1 and another one to wiki/Special:EntityData/$1.xxx) would be appropriate or at least better than what we have now? Yes. 303 is what you want. Also note that 303's can now be cached re. newer HTTP spec guidelines. Thus, this is your simplest fix. Now, if you are concerned about the 303 traffic, you can use a different pattern (again based on newer HTTP spec guidelines) where your server returns a 200 OK on the entity URI and then returns the actual description document URL in the Location: response header, as exemplified below: curl -I http://dbpedia.org/resource/Linked_Data *HTTP/1.1 303 See Other* Date: Mon, 21 Oct 2013 21:34:42 GMT Content-Type: text/html; charset=UTF-8 Content-Length: 0 Connection: keep-alive Server: Virtuoso/07.00.3204 (Linux) i686-generic-linux-glibc212-64 VDB Accept-Ranges: bytes *Location: http://dbpedia.org/page/Linked_Data** * and curl -I http://dbpedia.org/resource/Linked_Data *HTTP/1.1 200 OK* Date: Mon, 21 Oct 2013 21:34:42 GMT Content-Type: text/html; charset=UTF-8 Content-Length: 0 Connection: keep-alive Server: Virtuoso/07.00.3204 (Linux) i686-generic-linux-glibc212-64 VDB Accept-Ranges: bytes *Location: http://dbpedia.org/page/Linked_Data* Meanings: the client requested a document denoted http://dbpedia.org/resource/Linked_Data and the server confirms that there is a document associated with said URI (albeit not in a direct denotation oriented relationship) via 200 OK, and then returns the actual document location via Location: header. The only problem with this last solution is that its new and I doubt most existing Linked Data clients support the pattern. Kingsley -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/2/13 1:09 PM, Daniel Kinzler wrote: Am 02.10.2013 17:00, schrieb Kingsley Idehen: Daniel, When will the fixed data be generated and published? October 14, if all goes well. -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l Status? -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
For a while I've noticed that your messages don't show up properly in Windows Live Mail. I have many circumstances that are pushing me towards gmail, but you should correct this because you can assume that you hear maybe 1% of the time when people have a problem. -Original Message- From: Kingsley Idehen Sent: Wednesday, October 16, 2013 9:11 AM To: wikidata-l@lists.wikimedia.org Subject: Re: [Wikidata-l] Wikidata RDF Issues ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l attachment: badEmail.PNG___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/16/13 12:02 PM, Paul A. Houle wrote: For a while I've noticed that your messages don't show up properly in Windows Live Mail. Which implies that said email application has a problem with pkcs#7 attachments i.e., my attached digital signature bearing document. I have many circumstances that are pushing me towards gmail, but you should correct this because you can assume that you hear maybe 1% of the time when people have a problem. I have nothing to fix if I want to continue sending digitally signed emails, based on the S/MIME standard :-) Thanks for the notification though! Related: [1] http://bit.ly/19McSik -- G+ note about YouID (certificate generator) which has links to various posts about digitally signing emails . Kingsley -Original Message- From: Kingsley Idehen Sent: Wednesday, October 16, 2013 9:11 AM To: wikidata-l@lists.wikimedia.org Subject: Re: [Wikidata-l] Wikidata RDF Issues ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Am 16.10.2013 15:11, schrieb Kingsley Idehen: On 10/2/13 1:09 PM, Daniel Kinzler wrote: Am 02.10.2013 17:00, schrieb Kingsley Idehen: Daniel, When will the fixed data be generated and published? October 14, if all goes well. -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l Status? Went live yesterday, seems to work now :) data:Q64 a schema:Dataset ; schema:about entity:Q64 ; cc:license http://creativecommons.org/publicdomain/zero/1.0/ ; schema:version 78607403 ; schema:dateModified 2013-10-16T11:30:43Z^^xsd:dateTime . -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/16/13 4:43 PM, Daniel Kinzler wrote: Am 16.10.2013 15:11, schrieb Kingsley Idehen: On 10/2/13 1:09 PM, Daniel Kinzler wrote: Am 02.10.2013 17:00, schrieb Kingsley Idehen: Daniel, When will the fixed data be generated and published? October 14, if all goes well. -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l Status? Went live yesterday, seems to work now :) data:Q64 a schema:Dataset ; schema:about entity:Q64 ; cc:license http://creativecommons.org/publicdomain/zero/1.0/ ; schema:version 78607403 ; schema:dateModified 2013-10-16T11:30:43Z^^xsd:dateTime . -- daniel I've run it through our variant of Vapour re. Linked Data verification: http://bit.ly/1gM7oYa . Nearly there. Your use of 302 is what's going to trip up existing Linked Data clients. Why aren't you using 303 for redirection? Kingsley ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Am 01.10.2013 20:14, schrieb Tom Morris: How about not creating a fork just so you can delete a couple of directories? The full download is a whopping 260KB. Is that really too big/complex to include in its entirety and just ignore the parts you don't use? Not deploying code we do not use, especially if it is complex, is a requirement from the ops team. And deploying a standalone HTTP end point (as contained in the EasyRDF distribution) on the boxes that server Wikipedia is an absolute no go. We had the choice of either deleting the unneeded parts, or writing our own. This is actually not the first time I'm having this problem with an RDF library when all I want to do is export. Last time, I ended up writing my own (in Java). -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/2/13 10:42 AM, Daniel Kinzler wrote: Am 01.10.2013 20:14, schrieb Tom Morris: How about not creating a fork just so you can delete a couple of directories? The full download is a whopping 260KB. Is that really too big/complex to include in its entirety and just ignore the parts you don't use? Not deploying code we do not use, especially if it is complex, is a requirement from the ops team. And deploying a standalone HTTP end point (as contained in the EasyRDF distribution) on the boxes that server Wikipedia is an absolute no go. We had the choice of either deleting the unneeded parts, or writing our own. This is actually not the first time I'm having this problem with an RDF library when all I want to do is export. Last time, I ended up writing my own (in Java). -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l Daniel, When will the fixed data be generated and published? -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 02/10/2013 15:42, Daniel Kinzler daniel.kinz...@wikimedia.de wrote: Am 01.10.2013 20:14, schrieb Tom Morris: How about not creating a fork just so you can delete a couple of directories? The full download is a whopping 260KB. Is that really too big/complex to include in its entirety and just ignore the parts you don't use? Not deploying code we do not use, especially if it is complex, is a requirement from the ops team. And deploying a standalone HTTP end point (as contained in the EasyRDF distribution) on the boxes that server Wikipedia is an absolute no go. We had the choice of either deleting the unneeded parts, or writing our own. This is actually not the first time I'm having this problem with an RDF library when all I want to do is export. Last time, I ended up writing my own (in Java). -- daniel Hello, Making EasyRdf more modular, making it possible to only use the parts that you need, is definitely on my roadmap. I think RDF.rb does this very well. Although it is a difficult to balance up against keeping it easy to install and use. In the meantime, would it help to have a script that automatically creates a cut down version of EasyRdf from the git repo? nick. - http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. - ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Am 02.10.2013 17:00, schrieb Kingsley Idehen: Daniel, When will the fixed data be generated and published? October 14, if all goes well. -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 10/2/13 1:09 PM, Daniel Kinzler wrote: Am 02.10.2013 17:00, schrieb Kingsley Idehen: Daniel, When will the fixed data be generated and published? October 14, if all goes well. -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l Daniel, Note, cross references in DBpedia won't change following your fix. What will emerge, as a result of these fixes, is the ability to demonstrate the power of owl:sameAs inference [1], at Web-scale, using Linked Data from the DBpedia and Wikidata data spaces on the Web :-) [1] http://bit.ly/19pgtiP -- post about DBpedia and Wikidata cross references that's missing a typical live demonstration link re. full implications of owl:sameAs relations based reasoning and inference . -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Ok, I have now found and tackled the issue. This was indeed a bug in EasyRDF that got fixed since we forked half a year ago. I have updated easyrdf_lite now: https://github.com/Wikidata/easyrdf_lite/commit/025c32da17d82a51950230b80c254be5b3dc20d6. The respective patch for Wikibase is in review, see https://gerrit.wikimedia.org/r/86858. Having to maintain the fork is really a pain, I wish there was a better way to do this. I think there's a strong use case for project that only need RDF export, no import or serving. Being able to deploy the serialization code separately would be very useful. Nicholas, do you think it would be an option for EasyRdf to offer support for this use case? The most obvious (but also rather painful) way would be to spin off the serialization bit into a separate repository. But maybe it would be feasible to provide a build script that could be used to carve/reduce the code base to the parts needed in a particular scenario? -- daniel Am 27.09.2013 01:17, schrieb Nicholas Humfrey: On 26/09/2013 15:33, Daniel Kinzler daniel.kinz...@wikimedia.de wrote: Am 26.09.2013 14:54, schrieb Nicholas Humfrey: Wikidata uses a fork of EasyRdf: https://github.com/Wikidata/easyrdf_lite Which should handle this correctly. Looks like it doesn't, but I'll investigate. Hi, I have just double-checked by writing an extra test and EasyRdf (the version in master) handles this correctly: https://github.com/njh/easyrdf/commit/3121bd2201fca987c85bedb976d2148c862aa e78 So either Wikidata is passing the integer though differently or it was fixed since you took a fork... nick. - http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. - ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On Tue, Oct 1, 2013 at 1:01 PM, Daniel Kinzler daniel.kinz...@wikimedia.dewrote: Ok, I have now found and tackled the issue. This was indeed a bug in EasyRDF that got fixed since we forked half a year ago. [] Having to maintain the fork is really a pain, I wish there was a better way to do this. How about not creating a fork just so you can delete a couple of directories? The full download is a whopping 260KB. Is that really too big/complex to include in its entirety and just ignore the parts you don't use? Tom ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
There was a long discussion not so long ago about using established RDF tools for Wikipedia dumps instead of home-brewed ones, but I guess someone hasn't learnt the lesson yet. On Thu, Sep 26, 2013 at 2:22 PM, Kingsley Idehen kide...@openlinksw.com wrote: All, See: https://www.wikidata.org/wiki/Q76 The resource to which the URI above resolves contains: schema:version 72358096^^xsd:integer . It should be: schema:version 72358096^^xsd:integer . Who is responsible for RDF resource publication and issue report handling? -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Wikidata uses a fork of EasyRdf: https://github.com/Wikidata/easyrdf_lite Which should handle this correctly. However I don't seem to be able to content negotiate for Turtle today. This is returning HTML for me now: curl -H 'Accept: text/turtle' http://www.wikidata.org/wiki/Q76 Does anyone have an example curl command working? nick. On 26/09/2013 13:33, Martynas Jusevičius marty...@graphity.org wrote: There was a long discussion not so long ago about using established RDF tools for Wikipedia dumps instead of home-brewed ones, but I guess someone hasn't learnt the lesson yet. On Thu, Sep 26, 2013 at 2:22 PM, Kingsley Idehen kide...@openlinksw.com wrote: All, See: https://www.wikidata.org/wiki/Q76 The resource to which the URI above resolves contains: schema:version 72358096^^xsd:integer . It should be: schema:version 72358096^^xsd:integer . Who is responsible for RDF resource publication and issue report handling? -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l - http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. - ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On Thu, Sep 26, 2013 at 2:22 PM, Kingsley Idehen kide...@openlinksw.com wrote: All, See: https://www.wikidata.org/wiki/Q76 The resource to which the URI above resolves contains: schema:version 72358096^^xsd:integer . It should be: schema:version 72358096^^xsd:integer . Who is responsible for RDF resource publication and issue report handling? Hi Kingsley, You know https://www.wikidata.org/wiki/Special:EntityData/Q76.n3 right? Nevertheless the problem is there as well and this looks like a bug in EasyRdf which we're using as Nicholas says. Do you have time to report this to them? Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Technical Projects Wikimedia Deutschland e.V. Obentrautstr. 72 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
Am 26.09.2013 14:54, schrieb Nicholas Humfrey: Wikidata uses a fork of EasyRdf: https://github.com/Wikidata/easyrdf_lite Which should handle this correctly. Looks like it doesn't, but I'll investigate. However I don't seem to be able to content negotiate for Turtle today. This is returning HTML for me now: curl -H 'Accept: text/turtle' http://www.wikidata.org/wiki/Q76 Does anyone have an example curl command working? That's because http://www.wikidata.org/wiki/Q76 is the URI of the HTML document. The URI of the entity itself is http://www.wikidata.org/entity/Q76, which will perform content negotiation (though you need to tell curl to follow redirects): curl -L -H 'Accept: text/turtle' http://www.wikidata.org/entity/Q76 The URI of the turtle representation is https://www.wikidata.org/wiki/Special:EntityData/Q76.n3 (http://www.wikidata.org/entity/Q76.ttl will also work). -- daniel ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 26/09/2013 15:33, Daniel Kinzler daniel.kinz...@wikimedia.de wrote: Am 26.09.2013 14:54, schrieb Nicholas Humfrey: Wikidata uses a fork of EasyRdf: https://github.com/Wikidata/easyrdf_lite Which should handle this correctly. Looks like it doesn't, but I'll investigate. However I don't seem to be able to content negotiate for Turtle today. This is returning HTML for me now: curl -H 'Accept: text/turtle' http://www.wikidata.org/wiki/Q76 Does anyone have an example curl command working? That's because http://www.wikidata.org/wiki/Q76 is the URI of the HTML document. The URI of the entity itself is http://www.wikidata.org/entity/Q76, which will perform content negotiation (though you need to tell curl to follow redirects): curl -L -H 'Accept: text/turtle' http://www.wikidata.org/entity/Q76 The URI of the turtle representation is https://www.wikidata.org/wiki/Special:EntityData/Q76.n3 (http://www.wikidata.org/entity/Q76.ttl will also work). Oops, yes, I did know that, sorry! Why do you prefer .n3 over .ttl? (Turtle is a W3C Candidate Recommendation and Notation3 is an incomplete super-set of RDF) nick. - http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. - ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata RDF Issues
On 9/26/13 10:27 AM, Lydia Pintscher wrote: On Thu, Sep 26, 2013 at 2:22 PM, Kingsley Idehen kide...@openlinksw.com wrote: All, See: https://www.wikidata.org/wiki/Q76 The resource to which the URI above resolves contains: schema:version 72358096^^xsd:integer . It should be: schema:version 72358096^^xsd:integer . Who is responsible for RDF resource publication and issue report handling? Hi Kingsley, You know https://www.wikidata.org/wiki/Special:EntityData/Q76.n3 right? Nevertheless the problem is there as well and this looks like a bug in EasyRdf which we're using as Nicholas says. Do you have time to report this to them? Cheers Lydia Lydia, Issue logged, and in Linked Data form too :-) [1] http://bit.ly/1h5KKr9 -- Issue #1 re. EasyRDF and Wikidata . -- 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 ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
