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