Review Comment:
The paper presents the output of the beArchaeo project, which includes the formalization of an ontological structure that extends the capabilities of cultural heritage models associated to CIDOC-CRM, especially CRMSci and CRMArchaeo, to encompass other aspects of the praxis of archaeoogical investigation such as archaometrics, and by extension their reach into other related disciplines such as chemistry. The model is enjoying adoption within the beArchaeo community and alignments with well-known controlled vocabularies like AAT.
There is a prior version of this paper that was reviewed earlier. Compared to that version, it appears that the authors have put a lot of effort into heeding the comments of the reviewers and I agree that the paper is in much better shape right now, therefore I will only highlight the last few changes required and elaborate on the new content.
The ontology description has been given adequate space and structure and now elaborates on the characteristics that a reader of this journal, even on a domain-specific special issue, will find themselves comfortable with. The structure of this section is, in fact, so detailed that it makes me wish other sections were similarly structured: particularly, Section 3 is very long and, since there is a perceived sequencing of the phases of the data curation model, perhaps numbered subsections reflecting these phases would be more inline with the ontology section structure.
The authors have provided the methodological underpinnings of their development process: the choice of the NeOn methodology makes perfect sense, however, in the interest of having the paper as self-describing as possible, it would be useful to spend a few words reminding the reader what the scenarios are about. It's enough to just quote the scenario title from the NeOn book (e.g. "Scenario 2: Reusing and re-engineering non-ontological resources") and let the reader look it up for more details.
I also observe that it is now much clearer in which ways the beArchaeo ontologies relate to other models like ArCo and thesauri like AAT. What I find myself less comfortable with is the choice of how to represent alignments. The authors have opted for bespoke terms for the vocabulary to refer to (e.g. hasGettyAATMaterial): this is one of the possible ways to do it and is used for e.g. authority control in Wikidata, but there are concerns about the flexibility of this model as it fuels the expectation that the ontology will need to be extended should another vocabulary, say GND, be incorporated. An alternative way would be to use a single hasMaterial property that may reference values in AAT, beArchaeo and other indistinctly, and attach provenance information to these alignments as needed (though that might be best achieved using more recent methods of annotating statements like RDF*).
I am also interested to know if the authors have looked into how basic knowledge patterns of what they modelled in beArchaeo, if any, have been represented in foundational ontologies (e.g. how measurements, regions and parameters are modelled in DOLCE/DUL) and if subsuming concepts from these ontologies could be considered.
What seems to be the most important addition to this new version is a preliminary evaluation section. This is largely based on a discourse that is part qualitative, part describing how beArchaeo is situated in its research network. Obviously, it would have been unrealistic to expect that a full-fledged user evaluation be scheduled and carried out between revisions of the paper, so on that basis the provided content may even suffice. I still wonder if some more context could be provided to substantiate important statements like "The archaeologists have found the model accurate": for example, with a few quantitative data about the size and nature of the group that gave such feedback, or if the process to reach such accuracy (did they also argue about completeness by the way?) was iterative and based on multiple feedback rounds or not. Within the boundaries of what is sensible to expect, the more concrete this section can be made the better.
For a stable resource link, the authors have supplied the URL of an OWL/XML document that imports the entire ontology structure. This is acceptable as the authors have also generated LODE documentation as requested and provided its URL in the paper: perhaps the authors could clarify if the entire parent directory http://www.di.unito.it/~vincenzo/ontologies/beArchaeo/ is a relevant reference for the paper content as well?
Several footnotes (those linking to CRMsci, CRMarchaeo, ArCo and others) have corresponding publications, journal/conference papers as well as white/technical papers: please turn as many of these as possible into bibliographical references.
More detailed things to look into (notation in page:line range)
* 3:14-15 - including representations of specific domains is not a job of the Semantic Web paradigm, please rephrase (one possible way is to replace "pardigm" with "schema coverage" but there might be a better formulation)
* 10:44-46 - "the beArchaeo ontology comprises three modules: [...]"
* 10:48 - "non-ontological sources"
* 10:17 - "NeOn" is capitalized like this
* 11:10 - rather than providing a human-readable version of the ontology, LODE automatically produces ontology documentation.
* 12:32 - I understand the reason for an isEqualTo propety separated from ontological equivalence, but perhaps the property could be renamed to reflect that the equivalence relation is that of belonging to the same stratum
* 14:32: capitalized as PROV-O
* 15:37 - shouldn't it be "thermoluminescence" with an 'h'?
* 17:29-30 - "[...] that are being used for interpretation and will be the basis for the final exhibition."
* 17:44 - "Some interesting issues also rose" (or "were also raised")
* 18:46 - "The conceptual model _is_ the outcome" (or "was")
* 18:32-35 - that this is the first born-Semantic archaeological approach is a rather bold statement: would one argue that prior projects like Pelagios do not apply? I would advise a scrutiny of the state of the art in e.g. the Digital Classicist wiki at https://wiki.digitalclassicist.org/Category:Linked_open_data (by the way, pleae make sure to be there).
|