title	release	latest update	latest version	author	format	license	cite as
Heritage Risk Assessment Ontology (HeRO)	2023-11-30	2024-04-30	2.0.0	Barzaghi, Sebastian	JSON-LD, RDF/XML, N-Triples, Turtle	https://creativecommons.org/licenses/by/4.0/	Barzaghi, S. (2023). Heritage Risk Assessment Ontology. https://w3id.org/sirius/ontology/hero.

HeRO

Description

The Heritage Risk Assessment Ontology (HeRO, https://w3id.org/sirius/ontology/hero) is a OWL 2 DL ontology for describing risk assessment activities in the cultural, environmental and digital heritage domain in a machine-actionable format. It was developed by using a slightly modified version of the Simplified Agile Methodology for Ontology Development (SAMOD).

This repository contains the full documentation produced during the development of HeRO. In particular:

• the data directory contains the full set of refactored ABoxes, one for each iteration, written in the Turtle RDF serialization;
• 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 Graffoo 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;
  • a crosswalk table, which bridges the development step with the refactoring step by documenting the alignment between the glossary terms and the refactored terms.
• 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.