All,
How do I obtain an RDF rendition of the Wikidata document http://www.wikidata.org/wiki/Q215607 ?
Naturally, I've scoured the Web for examples and I keep on coming up empty :-(
http://www.wikidata.org/entity/Q215607.nt which redirects to http://www.wikidata.org/wiki/Special:EntityData/Q215607.nt
The RDF stuff at Wikidata is in flux. The RDF you get probably won't contain all the data that the HTML page shows, and the RDF structure may change.
JC
On 15 August 2013 20:25, Kingsley Idehen kidehen@openlinksw.com wrote:
All,
How do I obtain an RDF rendition of the Wikidata document http://www.wikidata.org/wiki/Q215607 ?
Naturally, I've scoured the Web for examples and I keep on coming up empty :-(
--
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
On 15/08/13 19:33, Jona Christopher Sahnwaldt wrote:
http://www.wikidata.org/entity/Q215607.nt which redirects to http://www.wikidata.org/wiki/Special:EntityData/Q215607.nt
The RDF stuff at Wikidata is in flux. The RDF you get probably won't contain all the data that the HTML page shows, and the RDF structure may change.
Indeed, the feature is simply not fully implemented yet. The best "preview" you can get right now is the dump generated by the python script. The plan is to make essentially the same available on a per-item basis via the URIs and URLs as above (in several syntaxes, depending on URL or, when using the URI, content negotiation).
Markus
On 15 August 2013 20:25, Kingsley Idehen kidehen@openlinksw.com wrote:
All,
How do I obtain an RDF rendition of the Wikidata document http://www.wikidata.org/wiki/Q215607 ?
Naturally, I've scoured the Web for examples and I keep on coming up empty :-(
--
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
On 15 August 2013 21:23, Markus Krötzsch markus@semantic-mediawiki.orgwrote:
On 15/08/13 19:33, Jona Christopher Sahnwaldt wrote:
http://www.wikidata.org/**entity/Q215607.nthttp://www.wikidata.org/entity/Q215607.ntwhich redirects to http://www.wikidata.org/wiki/**Special:EntityData/Q215607.nthttp://www.wikidata.org/wiki/Special:EntityData/Q215607.nt
The RDF stuff at Wikidata is in flux. The RDF you get probably won't contain all the data that the HTML page shows, and the RDF structure may change.
Indeed, the feature is simply not fully implemented yet. The best "preview" you can get right now is the dump generated by the python script. The plan is to make essentially the same available on a per-item basis via the URIs and URLs as above (in several syntaxes, depending on URL or, when using the URI, content negotiation).
FWIW there's also RDF/XML if you use a *.rdf suffix. This btw is of great interest to us over in the schema.org project; earlier today I was showing http://www.wikidata.org/wiki/Special:EntityData/Q199154.rdf to colleagues there... this is a Wikidata description of a particular sport. In schema.orgwe have a few places that hardcode a short list of well known sports, and we're interested in mechanisms that allow us to hand off to Wikidata for the "long tail". So http://schema.org/SportsActivityLocation has 9 hand-designed subtypes; we have been discussing the idea of something like http://schema.org/SportsActivityLocation?sport=Q199154http://www.wikidata.org/wiki/Special:EntityData/Q199154.rdf to integrate Wikidata into the story for other sports. Similar issues arise with religions and places of worship (http://schema.org/PlaceOfWorship). Any thoughts on this from a Wikidata perspective would be great.
Is there any prospect of inline RDFa within the main Wikidata per-entity pages? It would be great to have http://schema.org/sameAs in those pages linking to dbpedia, wikipedia,freebase etc too...
Dan
On 15/08/13 21:38, Dan Brickley wrote: ...
FWIW there's also RDF/XML if you use a *.rdf suffix. This btw is of great interest to us over in the schema.org http://schema.org project; earlier today I was showing http://www.wikidata.org/wiki/Special:EntityData/Q199154.rdf http://www.wikidata.org/wiki/Special:EntityData/Q199154.rdf to colleagues there... this is a Wikidata description of a particular sport. In schema.org http://schema.org we have a few places that hardcode a short list of well known sports, and we're interested in mechanisms that allow us to hand off to Wikidata for the "long tail". So http://schema.org/SportsActivityLocation has 9 hand-designed subtypes; we have been discussing the idea of something like http://schema.org/SportsActivityLocation?sport=Q199154 http://www.wikidata.org/wiki/Special:EntityData/Q199154.rdf to integrate Wikidata into the story for other sports. Similar issues arise with religions and places of worship (http://schema.org/PlaceOfWorship). Any thoughts on this from a Wikidata perspective would be great.
This is definitely something that we would like to encourage. Wikidata ids are fairly stable (not based on labels or languages) and fairly well grounded (described and named in many languages + linked to many Wikipedia pages, authority files, and external databases). So they should make suitable identifiers. No identifier will ever be reused, but it can happen that a Wikidata item is deleted, in which case it is no longer a suitable identifier. In theory, it can also happen that the data of an item changes so completely that the meaning of the item is different, but this is quite unlikely. One can access historic data fairly easily as long as the item is not deleted completely (not sure if a "historic RDF export" [by revision number] is planned, but it would not be hard to implement). And of course one would want the identifiers to be somewhat dynamic to capture changes of ideas over time (sports change all the time, e.g., if official rules are modified, but probably one does not want new IDs for every version of "football").
I am not sure if one needs to use http://schema.org/SportsActivityLocation?sport=Q199154 instead of using http://http://www.wikidata.org/entity/www.wikidata.org/Q199154 directly. Would these two have different meanings somehow? I guess they could, but there should not be a problem with long-term sustainability of the Wikidata URIs (just in case this is the main reason for creating new URIs here).
Is there any prospect of inline RDFa within the main Wikidata per-entity pages? It would be great to have http://schema.org/sameAs in those pages linking to dbpedia, wikipedia,freebase etc too...
This is not currently planned. One interesting starting point could be to identify the Wikidata properties that express "same as". For example, many properties link to other data collections by giving IDs (which often correspond to URIs, only that URL datavalues are not quite implemented yet). However, the granularity of other databases is often not the same, and it might not be true that these IDs unambiguously define the identity of the subject. For example, we had on this list a question recently whether Norman Cook should have individual entities for his various synonyms or not; MusicBrainz has several IDs for him based on synonyms, but Wikipedia has only one article about the person. In such cases, links to other datasets should probably not be interpreted as sameAs.
We currently use schema.org's "about" for linking Wikipedia pages to Wikidata ids. It seems wrong to say that an abstract URI (about a Wikidata entity) is "the same" as the URL of a Webpage that covers that topic. (This comment is about the links to Wikipedia you mentioned, not about cases with dedicated URIs that are not the web page URLs; the URIs for Wikipedia articles are in a strong sense the Wikidata URIs that we already start from ;-)
Btw, it is planned (vaguely) that property pages can hold more information, which could be used to declare "identifier properties" in the system at some point. But this will still take a while to implement.
Markus
Von: "Markus Krötzsch" markus@semantic-mediawiki.org
This is not currently planned. One interesting starting point could be to identify the Wikidata properties that express "same as". For example, many properties link to other data collections by giving IDs (which often correspond to URIs, only that URL datavalues are not quite implemented yet). However, the granularity of other databases is often not the same, and it might not be true that these IDs unambiguously define the identity of the subject. For example, we had on this list a question recently whether Norman Cook should have individual entities for his various synonyms or not; MusicBrainz has several IDs for him based on synonyms, but Wikipedia has only one article about the person. In such cases, links to other datasets should probably not be interpreted as sameAs.
Agreed. Naively, one might suggest to use something "weaker" like an inverted "alsoRefersTo".
So as to deal with synonymes, one could as well distinguish between name and entity/item/person/... in a manner like: "Satchmo" 'A name of the person Louis Armstrong' "Louis Armstrong" 'A name of the person Louis Armstrong'
We currently use schema.org's "about" for linking Wikipedia pages to Wikidata ids. It seems wrong to say that an abstract URI (about a Wikidata entity) is "the same" as the URL of a Webpage that covers that topic.
Agreed. Also, btw. Wikipedia links are not stable over time, neither in terms of URLs nor in terms of page contents. It is not uncommon for example that an Article about a "new" scientific concept published in the recent 60 years is turned into a section link into the article about its initial publisher. This certainly does not make the concept another name for the person :-)
Purodha
On 8/15/13 2:33 PM, Jona Christopher Sahnwaldt wrote:
http://www.wikidata.org/entity/Q215607.nt which redirects to http://www.wikidata.org/wiki/Special:EntityData/Q215607.nt
The RDF stuff at Wikidata is in flux. The RDF you get probably won't contain all the data that the HTML page shows, and the RDF structure may change.
JC
Okay, so given the following RDF document URLs:
1. https://www.wikidata.org/wiki/Special:EntityData/Q215607.nt ; 2. http://www.wikidata.org/wiki/Special:EntityData/Q199154.nt ;
I am able to generate the following human-readable pages, respectively:
1. http://linkeddata.uriburner.com/describe/?uri=https%3A%2F%2Fwww.wikidata.org... 2. hhttp://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%... .
Comments:
What's happened to cross referencing URIs that denote entities already described by documents in the Linked Open Data Cloud? Examples:
1. http://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%... 2. http://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%... .
In both cases, adding a single relation with a DBpedia entity URIs as the object, is all you need re., hooking into the Linked Open Data cloud.
Anyway, I suspect/hope Anja and others are working on these issues?
Kingsley
On 15 August 2013 20:25, Kingsley Idehen kidehen@openlinksw.com wrote:
All,
How do I obtain an RDF rendition of the Wikidata document http://www.wikidata.org/wiki/Q215607 ?
Naturally, I've scoured the Web for examples and I keep on coming up empty :-(
--
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