Ontology-based Thematic Framing of Tangible and Intangible Cultural Heritage

Tracking #: 4047-5261

Authors: 
Silvia Gola
Alessandro Umbrico
Andrea Orlandini

Responsible editor: 
Guest Editors 2025 OD+CH

Submission type: 
Full Paper
Abstract: 
The digitization of cultural heritage demands advanced methods for structuring and managing knowledge. Semantic web technologies and ontologies provide a powerful framework for intelligent reasoning, interoperability, and personalized content generation. This work explores how ontology-based models and semantic reasoning can drive innovative solutions for cultural heritage engagement, enabling dynamic, context-aware, and personalized information delivery. Specifically, this paper presents an ontology-driven approach to the thematic characterization of cultural heritage knowledge. We realize an intelligent assistant, called \HerMeS, that leverages semantic reasoning and contextual temporal planning to generate adaptive cultural itineraries, improving user engagement with historical and artistic assets. Unlike conventional recommendation systems, our approach integrates knowledge representation techniques for context-aware and thematic reasoning. Here, we discuss the ontology model, its integration with Artificial Intelligence planning, and its role in enabling personalized and interpretable cultural experiences, contributing to scalable and sustainable digital heritage solutions. The work is developed within a collaborative research project between the National Research Council of Italy and La Sapienza University.
Full PDF Version: 
Tags: 
Reviewed

Decision/Status: 
Accept

Solicited Reviews:
Click to Expand/Collapse
Review #1
By Jouni Tuominen submitted on 17/Apr/2026
Suggestion:
Accept
Review Comment:

This manuscript was submitted as 'full paper' and should be reviewed along the usual dimensions for research contributions which include (1) originality, (2) significance of the results, and (3) quality of writing. Please also assess the data file provided by the authors under “Long-term stable URL for resources”. In particular, assess (A) whether the data file is well organized and in particular contains a README file which makes it easy for you to assess the data, (B) whether the provided resources appear to be complete for replication of experiments, and if not, why, (C) whether the chosen repository, if it is not GitHub, Figshare or Zenodo, is appropriate for long-term repository discoverability, and (4) whether the provided data artifacts are complete. Please refer to the reviewer instructions and the FAQ for further information.

The authors have made corrections to the paper based on the previous round of reviews. Overall, my comments have been taken into consideration.

My specific comments:

(A) whether the data file is well organized and in particular contains a README file which makes it easy for you to assess the data,

The repository is now well organized (and contains a README file).

(B) whether the provided resources appear to be complete for replication of experiments, and if not, why,

The GitHub repository of the source code of the system (REST API) and the Docker Hub page for the server container image now contain documentation and instructions for running the application, and thus seem to be complete for replication.

(C) whether the chosen repository, if it is not GitHub, Figshare or Zenodo, is appropriate for long-term repository discoverability, and

GitHub and Zenodo are used as repositories.

(4) whether the provided data artifacts are complete.

Instead of copying the ontology in the KG file, the ontology is now imported, which helps to keep the KG and ontology file in sync.

The Zenodo repository and the GitHub repository seem to be in sync now.

The repository now contains instructions for running the SPARQL endpoint.

The data artifacts seem to be complete.

Minor/language remarks:

- Page 8: "the concepts and relationships the concepts and the relationsthe concepts and the relations refinement of ArCo are summarized below." - Please correct.

- Page 17: "list 1" -> "listing 1"

- Page 23: "As seen in the implementation of the previous CQ, the relation hermes:isCorrelatedWith* is used in conjunction with the pattern on the subject of the retrieved triples, rdfs:subClassOf*." - 1) "hermes:isCorrelatedWith*" -> "hermes:isCorrelatedWith"; 2) The sentence is difficult to understand ("in conjunction with the pattern on the subject of the retrieved triples"), please reformulate.

Review #2
Anonymous submitted on 14/Jun/2026
Suggestion:
Accept
Review Comment:

This manuscript is the third version that I am reviewing of a paper that presents the ArCo-based HerMeS ontology, which realises tangible and intangible cultural heritage through the use case of cultural itinerary planning.

Considering the great effort made in bringing the initial, problematic version to one that was appealing to a scholar on the topics this journal, there were only a few punctual improvements remaining that would have helped said reader make sense of some ways to present the ontology, that appeared more than a little confusing. The authors have since onboarded that advice and made all the necessary corrections on the illustrations, competency question queries and result sets. The changes have introduced no further clarity issues.

On top of that, I must acknowledge that the remarks made by fellow reviewers, such as documenting the GitHub repository and introducing Zenodo, were also essential, as was addresing them by the authors.

Sorry to have possibly sounded pedantic regarding the REST API denomination, but honestly, I feel it reads better the way it is now.

I have no more changes to request and am now happy to recommend the paper for publication.