Mapping SKOS Concept to Wikidata Class

[saumier]

When uploading the UDA Bottin to Artsdata, we also mapped the UDA Occupations SKOS Concepts to Wikidata classes so we could then upload artists to Wikidata.

In the SKOS model it is not allowed to map to Wikidata classes directly since the SKOS model only allows the range of skos:closeMatch to be another skos:Concept.

We tried 2 approaches to mapping SKOS concepts to Wikidata classes.

The first approach was to link the UDA SKOS concept using schema:about to a schema:ItemList. Each ItemList has one or more schema:itemListElements that capture the mapping to Wikidata.

The second approach, which we adopted in the end, was to use skos:closeMatch and create SKOS concepts to represent matching Wikidata classes. The Wikidata concepts were also typed using a schema:DefinedTerm to allow us to add properties such as the name, description and Wikidata Q-number (using schema:termCode) as well as the Wikidata meta class Q-number (using schema:inDefinedTermSet). This approach appears to be a significant improvement over the first approach in clarity and simplicity. It will most likely be applied to other projects with mapping between SKOS concepts and Wikidata, such as the Artsdata Event Categories controlled vocabulary. A federated SPARQL was used to fill in data for the matching Wikidata classes linked to the SKOS concepts. The name in English and French as well as the description and the high level class was added.

Is this the right approach?

[saumier]

See UDA Upload 2022 report https://docs.google.com/document/d/1Z3YqQsKyoL1HYoi1L_HgJ6ar_EOBC2PjyaIhDj3MXmE/edit?usp=sharing

[saumier]

Using SKOS related concepts in Wikidata https://www.wikidata.org/wiki/Wikidata:Property_proposal/mapping_relation_type