Review Comment:
This manuscript was submitted as 'Survey Article'. It provides a valuable source of information, referring to state of the art standards used in Cultural Heritage Information Retrieval.
Comments on survey article's dimensions:
(1) Suitability as introductory text, targeted at researchers, PhD students, or practitioners, to get started on the covered topic:
Yes. This is a good dictionary, definitively useful for a reader to start in the domain and to have an overview of what exists.
(2) How comprehensive and how balanced is the presentation and coverage.
The coverage is large, although I cannot say if it is exhaustive. A lot of standards and reference works are listed and described. However, we miss some clear synthesis that would help a novice to make a choice among them. Tables that are there for providing this synthesis should be presented before the details, and they should include additional details like where to find the models or tools, their creation date and if they are still maintained (activity)
(3) Readability and clarity of the presentation.
The article overall is well written, but really hard to read. The main reason is a dictionary-like presentation, with sometimes very long paragraphs (multiple columns). Probably bullet lists should be used instead. In almost all sections, the reader gets easily lost in all the listed items.
(4) Importance of the covered material to the broader Semantic Web community.
This is the first time I read a survey on Semantic Web applied to Cultural Heritage. The coverage seems large and might be an opportunity for the semantic web community to know the specific problems of CH Information Retrieval, how SW solves these problems and what is missing. However, due to the way the paper is written, identifying what is missing and the next steps required is difficult.
General Conclusion:
The article could be accepted under strong revisions, taking into account the comments and in particular revising the text and structure to increase readability.
Here are detailled comments:
-p2 top of 1st column: "(...)for or basically their question is a semantic one." => ???
-p3 top of 2nd column: "without realizing them(...)" => ???
-Section 3: a conclusion for each category (sub-section) is missing
-p6 top of 1st column: should be rewritten. RDF is independent from XML, and there are different syntaxes that can be used to represent RDF data (e.g. RDF7XML, N-Triples, RDFa, Turtle). XML (RDF/XML) is only one of these syntaxes.
-p7: the table should put in a correct place (no big blank space...). I suggest to put it before the details given for each KOS: first the synthesis, and then the details. Additionnally, several things are missing in the table: year of creation, link to the KOS (where is it available), is the KOS still maintained? (activity), ....
Those remarks can be taken into account also for all the tables summarizing SOTA items in the whole document.
-p9 "3.2 Data integration in metadata level": "at the" instead?
-p9 middle of 1st paragraph: "(...) and cannot be put aside easily." => why do you say this? can you explain?
-p9 footnotes number to revise
-p9 paragraphs are too big: consider making one per item or coherent group of items. 2nd column is badly written and hardly understandable: consider revision. End of the column: "(...) a demonstrator was developed at the end, which offered semantics results for the users." => what do you mean by "semantics results"?
-p10 end of 1st column: "Metadata is constructed with a human processing point of view (...) not appropriate for automated tools to infer (...)" => ok. but this is not true for ontological metadata, which are machine processable by definition.
-p10 end of 1st paragraph: "There is an attempt to understand the concepts (...)" => This is not necessarily true because there are generic domain-independent ontologies.
-p11 "is-a" rather than "isA", and "relation", not "hierarchy"
-p11 1st column, 2nd paragraph: too many things in one single paragraph. + refer to secton 3.4 where you first introduce RDF. + you can also refer to OWL2.
-p11 2nd column, beg. of section 3.4: 1st paragraph unclear, consider revision. "Besides the functions mentioned above (...)" => an example is needed.
-p11 2nd column: CIDOC-CRM is usually the name given. I am not sure CRM is really used, and since it is a generic name, I would not use it for the CIDOC-CRM: CIDOC alone would have more meaning. So please do not say it is also called CRM...
CIDOC-CRM is not really a formal ontology, but rather a "reference ontology for interchange of heritage information (ISO 21127:2014)". You can also refer to the OWL2-DL version (which is formal): bloody-byte.net/rdf/cidoc-crm
-p12-p13: paragraphs really too big: not readable...
-p14: revise page organisation with the table...
-p14, 3.4.1: "(...)EDM and CRM aer the two most dominant(...)": you have a lot of references for CIDOC-CRM, but only one for EDM. This does not reflect the popularity of EDM...
-p15: revise page organisation (reading order of column parts, with the table...)
-p15, end of 1st column: "(...)cannot be put aside easily." => again? Why do you say this? Also I am not sure this is correct from an English point of view.
-p15 2nd column. This part is interesting, but we would like to know if there are tools to map from one model to the other, and if they can be used jointly since they seem to be complementary. The question behind this is "how to join / integrate the two worlds of CRM and EDM, to avoid having data silos and allow machine reasoning on everything?"
-p16 end of section 3: "This is achieved if the ontology(...) => Why? Give some evidences. By saying this, you say implicitly that CRM-CIDOC is better than EDM, although even if one is more complete than the other, the two can probably be complementary...
-p16 section 4 title: "geo-spacial" instead of "sapatio-temporal" (?)
-p16-p17: again, the paper would gain in readability by using bullet lists, or any other way to avoid very big paragraphs. There is sometimes no apparent order in the way items are presented. In particular in section 4, it starts with GIS and the like about geospacial models, then jumps to 3D models, and then come back to geospacial standards with CityGML and 3DGIS. We understand only at the end of the section why the part on 3D models is there... => this should be reorganized.
-p17, end of 2nd column: "Since CIDOC CRM is an ISO standard(...)" => Why is this part about CIDOC-CRM here? Is this a cut/paste error?
-p19: "(...)we are going to discuss" => use "we discuss" instead.
-p19, middle of column 2: "There is an important point to note (...)" => not clear, rewrite.
-p22 section 5.2.2: Description Logic is not mandatory to allow reasoning...
-p23: 3D models are firstly presented in section 4, so maybe section 5.2.3 should be somehow merged
-p23, end of 2nd column, p24: Use of "ubicomp"... Not everyone knows what this is, so you should introduce the term.
-p24, column 2, 2nd paragraph: "(...)AR is quite close to the concept of ubiquitous computing(...)" => Putting AR in a section called "context-aware applications" is questionable. It should rather be put in a specific section dedicated to AR/VR.
|