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=58040911&iu=/4140/ostg.clktrk
_______________________________________________ Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
