We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Constraints for Linked Open Data

Formale Metadaten

Titel
Constraints for Linked Open Data
Serientitel
Anzahl der Teile
15
Autor
Mitwirkende
Lizenz
CC-Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Deutschland:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
The University of Chicago Library is creating a single platform to support the development of future digital humanities projects and to maintain existing projects. This project is called UChicagoNode. The goal of the platform is to increase the visibility and sustainability of digital humanities work of the students and scholars at the university. At the forefront of making the data more discoverable is adopting the RDF standards of Dublin Core and the Europeana Data Model. We are using OCHRE as the data imput platform, which is feeding a MarkLogic TripleStore. However, how do we ensure that the data is accurate and standardized for ease of search? We have adopted SHACL, the Shapes Constraint Language, to validate the data in our RDF store and to ensure its accuracy. The implementation of SHACL we are currently using is the Topbraid reference implementation. SHACL provides some practical constraints for the open-world assumption of OWL. Providing constraints on RDF data provides several benefits: better reliability in querying the data, ensuring the quality of the data, and accuracy of data integration pipelines. This presentation will show how SHACL fits into our workflow, how SHACL aids the quality control over our Linked Open Data, and some examples of complex SHACL constraints.