source: DASISH/t5.6/docs/LREC/final/reviewes.txt @ 4668

Last change on this file since 4668 was 4668, checked in by olhsha, 10 years ago


File size: 8.9 KB
Line 
1On 24/01/14 13:03, "lrec@lrec-conf.org" <lrec@lrec-conf.org> wrote:
2
3Dear Przemyslaw Lenkiewicz:
4
5We are pleased to inform you that the following submission has been
6accepted for a Poster + Demo presentation at the 9th  International
7Conference on Language Resources and Evaluation:
8
9     The DWAN framework: Application of a web annotation
10           framework for the general humanities to the domain of
11           language resources
12
13Following the advice of reviewers, the LREC2014 Programme Committee
14suggests that you run a demonstration during your Poster presentation.
15Please let us know if you accept this suggestion and do intend to present
16a demo alongside the Poster sending an email to this address
17(lrec@lrec-conf.org).
18
19Please inform your co-author(s), if any. Each submission has been
20reviewed by three reviewers; please find attached their comments, if any.
21
22Poster Sessions will be placed in parallel to Oral Sessions and therefore
23their length varies accordingly: during the session you will have the
24opportunity to describe your work and interact with interested conference
25participants. We request that you be at your Poster Session for the
26entire time slot. Further details for poster presenters will be detailed
27on the conference web site at due time.
28
29Regarding technical details and requests of your Demo, please contact
30Sara Goggi at the following email address: lrec@ilc.cnr.it.
31
32
33The conditions for your participation in a Poster Session at LREC are the
34following:
35
361) you confirm your participation by registering for LREC by March 15,
372014 which is also the deadline for early registration with reduced fee
38(at least ONE author of the paper MUST register);
39AND
402) you submit the final version of your paper by March 22, 2014 (FIRM
41deadline) in compliance with the "Authors' Kit" which is available on the
42LREC 2014 web site
43(http://lrec2014.lrec-conf.org/en/submission/authors-kit/) and contains
44the Style sheet and the length for papers to appear in the Proceedings.
45
46You can upload your final manuscript at the following site:
47
48     https://www.softconf.com/lrec2014/main/
49
50You will be prompted to login to your START account and thus access to
51your User Console: from here please choose "Your current Submission(s)"
52for accessing the list of your submission(s). Click on this submission id
53for submitting the final full paper.
54
55In case you need it, this is the passcode associated with your submission:
56   
571053X-H3H6A7B9C5
58
59We would like to remind you that there is no quality difference between
60Oral and Poster presentations and there will be no difference between
61them in the Proceedings.  The choice of style of presentation of your
62paper was made based on what would be the most informative and effective
63way to communicate the scientific contents of your presentation. There
64will be Chairpersons both for oral and poster sessions.
65
66We remind you that you can update/revise the data for the LRE Map on the
67submission page and invite you to contribute to the "Share your LRs!"
68initiative as well.
69
70Online registration and hotel booking, conference details and local
71information about Reykjavik will be soon available at the LREC 2014
72website (http://lrec2014.lrec-conf.org/en/).
73
74If your organization requires you to have an official letter of
75acceptance from the LREC2014 Programme Committee in order to make
76arrangements to attend the conference, please request such a letter from
77the Conference Chair at: lrec@ilc.cnr.it.
78
79If you require an official letter of invitation from the local organizer
80(e.g. to obtain a visa), you have the possibility of requesting such a
81letter via the registration tool which will be available by mid-February
82on the Conference web site.
83
84We would like to thank you for your participation in LREC and look
85forward to your presentation at the conference.
86
87Best regards,
88LREC2014 Programme Committee
89
90
91==========================================================================
92==
93LREC 2014  Reviews for Submission #1053
94==========================================================================
95==
96
97Title: The DWAN framework: Application of a web annotation framework for
98the general humanities to the domain of language resources
99
100Authors: Przemyslaw Lenkiewicz, Olha Shkaravska, Twan Goosen, Daan
101Broeder, Menzo Windhouwer, Stephanie Roth and Olof Olsson
102==========================================================================
103==
104                            REVIEWER #1
105==========================================================================
106==
107
108
109--------------------------------------------------------------------------
110-
111Comments
112--------------------------------------------------------------------------
113-
114
115The paper briefly describes an annotation framework that may be used to
116integrate or to extend existing annotation tools. It additionally presents
117results of interviews of linguistic researchers regarding their
118requirements
119for annotation software. The architecture of the system, relying on an
120object
121oriented data model of users, annotators and annotation objects, is only
122very
123briefly described. What I also miss are references to the literature,
124especially, to related web-based tools that also come along with object
125oriented data models. In this sense, the Related Work part of the paper is
126definitely too short. Though I am sure that the MPI has very nice and
127important
128tools what regards linguistic annotation, I suspect that this is the only
129source for such software. Finally, the interviews are summarized in a
130post-hoc
131manner. Seemingly, the architecture has been developed first and only
132later, it
133has been justified by the results of the interview (page 3: "These
134requirements
135are well in line with the specification of DWAN framework."). In contrast
136to
137this, one should start from a requirements analysis before one starts with
138coding. Is there a justification why this order has been changed?
139
140==========================================================================
141==
142                            REVIEWER #2
143==========================================================================
144==
145
146
147--------------------------------------------------------------------------
148-
149Comments
150--------------------------------------------------------------------------
151-
152
153The abstract presents DWAN, a collaborative annotation environment that
154leverages existing technology, such as the Wired-Marker Firefox extension
155for
156in-browser annotation. DWAN adds server-side functionality to enable
157collaboration, functionality that is reachable via a REST API.
158
159Beside supporting collaboration, the server-based approach also provides
160data
161persistence, protecting the annotation metadata from changes to the
162original
163content, and assisting with migrating the annotaiton to the new version,
164when
165such changes occur.
166
167This work is clearly of high relevance to the research community and the
168DWAN
169annotation framework is of great practical use.
170
171The English used in the paper is of a very high standard. The references
172are
173fine, though there are a a few more systems that could be used for
174comparison,
175e.g. BRAT (http://brat.nlplab.org/), or GATE Teamware
176(http://gate.ac.uk/teamware/), to name just two.
177
178==========================================================================
179==
180                            REVIEWER #3
181==========================================================================
182==
183
184
185--------------------------------------------------------------------------
186-
187Comments
188--------------------------------------------------------------------------
189-
190
191The paper describes an annotation framework roughly compatible with the
192open
193annotation framework, exposing REST API and offering a history/version
194support.
195One note on the section "Introduction": i would change sentence to "who
196is not
197NECESSARILY the owner.."
198I suggest to add more references. I don't know if the authors cut them
199from the
200ext abstract, but they were not counted in the limit, and from this
201shorter
202version it is not clear if proper reference is made to state of the art.
203As the authors are putting the accent on the framework more than client
204solutions, they may want to cite this:
205
206Manuel Fiorelli, Maria Teresa Pazienza and Armando Stellato A
207Comprehensive
208Framework for Semantic Annotation of Web Content, International
209Conference on
210Knowledge Engineering and Ontology Development (KEOD 2013), Vilamoura,
211Algarve,
212Portugal, September, 19-22, 2013
213
214Also, the authors cite the open annotation data model, so why didn't they
215opted
216for a direct RDF storage?
217It is not clear also how complex the annotations can be. We only know
218there are
219annotations, we know there is metadata, but don't know how much of the
220open
221annotation format is being covered. Does the framework annotation schema
222allows
223for a span or are these only global annotations on a document? (guess the
224former from sections 3.1/3.2, but better to make it clear in the
225appropriate
226sections than hinting at it later). Are multispanned annotations
227representable?
228
229I suggest to take these specifications into consideration in case the
230paper is
231accepted for publication
232
Note: See TracBrowser for help on using the repository browser.