Review Comment:
I have read the improved version of the submitted work and acknowledge the changes that have been brought to satisfy the requests of the reviewers and, in general, the quality of the article.
I am generally satisfied with this revision of the work; I have only quite a few remarks about the changes in section 2.1. What I addressed as an unclear and unexplained description of the properties of OWL has been replaced with another description seeming closer to an evangelist/seller approach than a paragraph showing grounded facts or at least true common knowledge about OWL. A few examples:
* “It also facilitates the machine-readable description of the relationship between different definitions of concepts across languages or traditions.” It’s hard for me to get the contribution of OWL here. This is about content and domain semantics…maybe this is, again, a contribution of OntoLex specifically as an OWL vocabulary?
* “Using a machine readable description in OWL, once again, in conjunction with an ontology modelling methodology such as OntoClean [5], and together a more human readable description given as documentation, can help to clarify (according to the expressive limitations of OWL) what we mean when we use a concept like ‘Sense’ or ‘Morpheme’ in a dataset. “
- small note: add “with” in between “together” and “a”
- OntoClean is not a modeling methodology (unless we consider, on a very broad spectrum of the meaning, “modeling methodology” anything that supports, at any extent, the development of an ontology, but a methodology about “A” would provide you with necessary and complete information for performing “A”, which OntoClean does not, wrt modeling). OntoClean specifically helps in validating the logical consistency of taxonomic relationships by means of meta-properties that are assigned on the basis of the interpretation of the ontology. E.g., if the concepts of student and human are clear in the mind of the developer, student will be considered anti-rigid while human is rigid and if, by mistake, human is put as a subclass of student, then (a processor implementing) OntoClean will tell that this is not ok because a rigid concept cannot be more specific than a non-rigid one. It is surely fascinating in that it provides computational rules for evaluating adequacy and consistency based on the interpretation of the concepts provided by the same developers. However, besides being a useful tool to be adopted for validating our work, it does not contribute much in clarifying the precise meaning of logical terms, as suggested by the authors (that is more clarified by documentation, which has been mentioned by the authors as well). Also, the expression “according to the expressive limitations of OWL” is not clear, why according to?
Overall, I’m in favor of accepting the paper with minor modifications, but that section needs to be cleaned and cleared, as it is vague and unprecise.
|