Using Wikibase for Managing Cultural Heritage Linked Open Data Based on CIDOC CRM (Q14): Difference between revisions
Jump to navigation
Jump to search
Varvantakis (talk | contribs) (Created claim: Keywords (P9): Wikibase (Q2)) |
Varvantakis (talk | contribs) (Created claim: Item type (P12): RPX (Q9)) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Property / Keywords | |||
| Property / Keywords: CIDOC CRM / rank | |||
Normal rank | |||
| Property / Keywords | |||
| Property / Keywords: Knowledge graph / rank | |||
Normal rank | |||
| Property / Keywords | |||
| Property / Keywords: Cultural Heritage / rank | |||
Normal rank | |||
| Property / Keywords | |||
| Property / Keywords: Linked Data / rank | |||
Normal rank | |||
| Property / Item type | |||
| Property / Item type: RPX / rank | |||
Normal rank | |||
Latest revision as of 08:38, 25 April 2023
Kesäniemi et al. 2022
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | Using Wikibase for Managing Cultural Heritage Linked Open Data Based on CIDOC CRM |
Kesäniemi et al. 2022 |
Statements
Joonas Kesäniemi, Mikko Koho, Eero Hyvönen (English)
0 references
2022
0 references
New Trends in Database and Information Systems (English)
0 references
This paper addresses the problem of maintaining CIDOC CRM-based knowledge graph (KG) by non-expert users. We present a practical method using Wikibase and specific data input conventions for creating and editing linked data that can be exported as CIDOC CRM compliant RDF. Wikibase is a proven and maintained software for generic KG maintenance with a fixed but flexible data model and easy-to-use user interface. It runs the collaboratively edited Wikidata KG, as well as increasing amount of domain specific services. The proposed solution introduces a set of data input conventions for Wikibase that can be used to generate CIDOC CRM compliant RDF without programming. The process relies on the aforementioned data input rules combined with generic mapping implementations and metadata stored as part of the KG. We argue that this convention over coding makes the system more easily approachable and maintainable for users that want to adhere to the CIDOC CRM principles, but are not ontology experts. As part of the preliminary evaluation of the proposed solution, an example on managing Cultural Heritage data in the military history domain with discussion on the limitations of the approach is presented (English)
0 references