Review Comment:
This manuscript was submitted as 'Ontology Description' and should be reviewed along the following dimensions: (1) Quality and relevance of the described ontology (convincing evidence must be provided). (2) Illustration, clarity and readability of the describing paper, which shall convey to the reader the key aspects of the described ontology. 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.
==
This paper presents the Onto4AIR2 ontology, a revision of the Onto4AIR ontology. It is unclear how the two versions differ other than the support of both English and Spanish. The ontology is designed to support the registration and lookup of theses information in institutional registries in Mexico. The ontology was designed following a standard methodology, and has been represented in OWL, by extending Schema.org, Dublin Core and FOAF. The motivation for the ontology is semantic ambiguity of some of the standard DC fields supported by the OpenAIRE OAI-PMH protocol.
The paper is a bit hard to read in some places, which obfuscates the author's message. Also, the paper explains a lot of information using pictures, which is not the most concise way of explaining everything, and takes up a lot of space.
I have not been able to find a persistent link to the ontology itself.
* Related Work
The related work section contains a lot of references to unrelated work; and it's often not clear why the references are included. Why describe the OWLIM reasoner? Why refer to the LUBM benchmark without discussing its underlying ontology? Other references are missing, e.g. the extensive VIVO ontology. More importantly, a related work section serves the purpose of showing the novelty of the presented approach. In this case, there is no discussion of shortcomings of the related work, nor is there a comparison with the Onto4AIRE2 ontology. How does Onto4AIRE2 improve over the state of the art?
* The ontology
The methodology used is fairly standard (which is a good thing), but there is no discussion of why the competency questions are the right ones to ask. Also, they are a bit hard to understand: what does "how are the theses organized" mean? What kind of answer is expected? The discussion of the steps in the methodology is not thorough enough. For instance, the "define classes and construct their hierarchy" discusses rdfs:isDefinedBy, rdfs:seeAlso and rdfs:comment... which are useful to have, but provide no formal semantics. Also, the necessary and recommended properties are discussed in a table, but it is not shown how they are modeled (why 'identifier' if every instance already has an IRI?).
Table 3 lists properties, with their domain and range. Many of these are listed as functional or inverse functional, where it is not clear that they should be, or vice versa. For instance "isManagedBy" should not be IF: why can an IR manager not manage multiple repositories? Conversely, firstAuthorOf is not IF; while that would allow multiple first authors... but it *is* defined as functional, which makes that any student can only be the first author of a single thesis (can't one graduate in multiple subjects?). Similarly, students can only have one advisor ... overall these definitions are overly restrictive and sometimes incorrect.
* Results
The "description of a thesis" in Fig. 7 shows a number of things that are incorrect in the ontology: "Date" is not xsd:date but rdfs:Literal, the Spanish title has no language tag, but the English one does. The creator is of type rdfs:Literal... why not link to an instance of the Author class? Similarly for the dct:rights property, the knowledge field and the knowledgeArea (and what's the difference between the two?).
* Evaluation
The paper presents an evaluation of the ontology obtained through a survey, and through an NPS score. I would have preferred to see a more qualitative analysis of the ontology, comparing it to related ontologies and to see whether it can capture all metadata for the MSc theses.
Overall the work is not substantial, nor novel enough for publication. The language of the paper needs work, and the ontology itself is not really well defined. I encourage the authors to look at VIVO https://duraspace.org/vivo/ and its underlying ontology.
|