|Review Comment: |
QUALITY AND IMPACT
Although it builds on an existing publication, the paper takes this further, and gives the reader a birds eye view of the wider field, the barriers and opportunities, and the particular aims and modus operandii of Ontowiki as a front-end application for the Semantic Web.
The paper is logical, lucid and cogent, structuring the presentation around the ability of OntoWiki to address the barriers to use which they present at the beginning.
Although it is intended to be a descriptive overview of the application, it would have been helpful if the Case Studies had also included some feedback from users about the problems, tensions or even opportunities that arose during the implementation. This may not be necessary for this type of presentation, so is not necessarily a factor for this special issues, but it would have given the reader a better basis to consider who usable it was in practice, and the nature of the barriers.
CLARITY,CONTENT AND READABILITY
The text is authoritative and detailed, (though rather long), using illustrations and Case Studies from different disciplines to give a more tangible taste of the potential of this approach for collaborative research. I particularly liked the contrast between the types of case study - using a business and a digital humanities project to convey how this would work in practice, and what the potential is for less technical readers in particular.
There were some minor preposition and word order comments which I have corrected on the pdf printout. Happy to correct them directly using 'tracking' on a Word document and return them if this is helpful. (Overview on ...to Overview of etc).
These are minor, however, these make minimal difference to readability and are not essential. I have listed them below in case.
p1 - overview of (not on)
- However it is (not its)
p3 - collaborators work (not to work)
p4 - already lists (not lists already)
- overview of
p5 - it is built (not build)
p7 - Wrappers (not Wrapper)
p11 - stastical data (not statistic)
p12 -usually have (not have usually)
p13 - most frequently requested features
p14 - a method of manipulating and controlling..
- more specifically
p18 - a unified
p20 - HAS already significantly influenced
p23 - The script OCPY exports, transforms and imports the knowledge base according to...
- balancing of (not between)
p24 - by better leveraging (not by leveraging more)
As a description of an application this could be published as it is, and provides a detailed and authoritative contribution. I have indicated minor revisions but could have gone either way.