title	Release	Latest version	Revision	Issued on	Authors	Contributors	Available formats	License	Cite as
Cultural Heritage Acquisition and Digitisation Application Profile (CHAD-AP)	2024-04-16	https://w3id.org/dharc/ontology/chad-ap	1.0.0	2024-04-16	Barzaghi, Sebastian; Peroni, Silvio	Heibi, Ivan; Moretti, Arianna	JSON-LD, RDF/XML, N-Triples, Turtle	http://creativecommons.org/licenses/by/4.0/	Barzaghi, S. and Peroni, S. (2024). Cultural Heritage Acquisition and Digitisation Application Profile. https://w3id.org/dharc/ontology/chad-ap.

CHAD-AP

Introduction

The Cultural Heritage Acquisition and Digitisation Application Profile (CHAD-AP) is a OWL 2 DL-based metadata application profile of CIDOC CRM for describing cultural heritage digitisation data and processes in a FAIR-compliant and machine-readable format.

CHAD-AP was developed and refined while working on the Aldrovandi case study. It includes ontological constructs to formalize the data and metadata of the objects contained in the exhibition and the various activities that make up the digitisation workflow.

It was developed by leveraging the Simplified Agile Methodology for Ontology Development (SAMOD).

Description

This repository contains the full documentation produced during the development of CHAD-AP. In particular:

• the docs folder contains the documentation about the current state of the model and some examples;
• the object folder contains the full documentation of the module specific to modeling the exhibition objects starting from their bibliographic metadata;
• the process folder contains the full documentation of the module specific to modeling the digitisation workflow of the exhibition.

In turn, both the object and the process folder are organized as follows:

• the data directory contains the full set of refactored ABoxes, one for each iteration, written in the Turtle RDF serialisation;
• the development directory contains a folder per development iteration, each containing a full test case with:
  • a motivating scenario, which defines the scope of the single iteration, along with some examples;
  • a list of informal Competency Questions, written in natural language;
  • a glossary of terms, which defines a set of meaningful words and expressions - representing possible entities and relationships - collected from the scenario and the competency questions;
  • a visual diagram of the entites and relationships recorded in the glossary, rendered in .png format and coupled with the .graphml file it has been exported from;
  • a terminology component (TBox), which defines a formal schema based on the diagram;
  • an assertion component (ABox), which organizes the examples data according to the schema;
  • a list of formal Competency Questions, which reformulate the informal competency questions into proper SPARQL queries;
  • a testing notebook, which is used to test the SPARQL queries against both the TBox and the ABox;
• the diagrams directory contains the full set of Graffoo diagrams representing the refactored model of each iteration;
• the docs directory contains the full set of files related to the final model and its versions in time;
• the sparql directory contains the full set of refactored Formal Competency Questions.