Review Comment:
This paper introduces SeMFIS, a tool(set) allowing semantic annotations of conceptual models. We like to structure the review based on the criteria for "Reports on tools and systems – short papers describing mature Semantic Web related tools and systems." (http://www.semantic-web-journal.net/reviewers): Quality{1}, Importance{2}, Impact{3}, Clarity{4}, Illustration{5}, Readability{6}.
We see the high importance {2} of a toolkit which enables to interact with conceptual (legacy) models in a easy manner. We see the use of such a toolkit especially in the times of always changing organisation structures (e.g. a fusion of two companies).
The topic is quite abstract and only the analogy (to textual, video or audio resources) provided at the beginning of the Chapter 2 actually enabled me to understand the problem SeMFIS is tackling. The introduction would become more penetrable from a first high-level illustration, and most importantly a toy example. Especially for people not familiar in the realm of conceptual models this might ease the introduction significantly.
As this is a tool for a rather specialized task and therefore a small potential group of users we like the approach of presenting use cases a lot. The style and scope of this use cases are well chosen and help to understand in how the tool might be used. Unfortunately these use cases are not reflecting people outside of work done by the authors group which somehow mitigates the impact{3} measure. Also we do not think that students, which are as a part of assignments using SeMFIS, should be taken as impact. The proof of impact of SeMFIS outside the authors group might be immediate but is not yet visible.
We think that the paper is overall well written. The paper is clear{4} structured and separates the concerns of each chapter. It was not always evident what functionality is provided by the ADOxx platform and what is added through SeMFIS. As SeMFIS is only working on top of ADOxx we regard this as minor.
The readability{6} of this paper was good except of the chapter "Scripting and Analysis Features" which reads like a hastily written documentation. We estimate that the paper can gain most in quality by reworking this part. Mostly we propose to after one example fo the script language to omit further examples.
Overall we propose to pick one specific use case SeMFIS solves (especially well) and show the tools capabilities based on this use case.
Finally the size of 15 pages (without references) does not adhere to the short paper definition by SWJ (10 pages). Therefore this paper needs a major revision.
Minor:
- Page 10: Copy-Paste errors: "
- Page 9: Program Code 6 is missing "CMD /c" before wget.exe ?
|