On Fri, Oct 27, 2017 at 11:06 AM, Jakob Voß Jakob.Voss@gbv.de wrote:
Hi Lydia an all of you,
Lydia wrote:
The identifier can often be expanded to a full URI. (For example, LoC ID n81114174 becomes http://id.loc.gov/authorities/names/n81114174.) This full URI can then be used in the linked open data web to match our data with other datasets and use both of them together easily.
From today on, Wikidata has full URIs for statements that represent external identifiers in its RDF exports, and thereby becomes a proper citizen of the linked open data web. To make this work the property for the external ID needs to have a statement with property “URI used in RDF” (https://www.wikidata.org/wiki/Property:P1921).
Could you give an example? The RDF of item Q43027 with LoC ID n81114174 does not include the URI http://id.loc.gov/authorities/names/n81114174 if exported with http://www.wikidata.org/wiki/Special:EntityData/Q43027
I also tried with a statement just added to make sure it's not some caching issue. Is the feature not enabled yet?
In particular I'm interested how the external URI and Wikidata URI are connected.
subject: http://www.wikidata.org/entity/Q43027 property: ??? object: http://id.loc.gov/authorities/names/n81114174
I'm sure the RDF-property also depends on the Wikidata-property so this feature requires some additional tweaking. At least the property is not always owl:sameAs because we have at least 1-to-n relationships between Wikidata items and external ids.
Hey :)
It is back and your example works now for me.
Cheers Lydia