User:Mary.szmary/proposal2017 - Revision history

Mary.szmary: /* Previous work */

2017-04-02T22:04:28Z

Previous work

Mary.szmary: /* Schedule */

2017-04-02T20:48:42Z

Schedule

Mary.szmary: /* Schedule */

2017-04-02T20:33:33Z

Schedule

Mary.szmary: /* Reasons why Google and Apertium should sponsor it */

2017-04-02T20:32:24Z

Reasons why Google and Apertium should sponsor it

Mary.szmary: /* Reasons why Google and Apertium should sponsor it */

2017-04-02T16:42:31Z

Reasons why Google and Apertium should sponsor it

Mary.szmary: /* Overview */

2017-04-01T19:34:16Z

Overview

Mary.szmary: /* Schedule */

2017-04-01T19:24:49Z

Schedule

Mary.szmary: /* Project description */

2017-04-01T19:24:15Z

Project description

Mary.szmary: /* Project description */

2017-04-01T19:15:55Z

Project description

Mary.szmary: /* Schedule */

2017-03-29T22:57:16Z

Schedule

@@ Line 35: / Line 35: @@
 ===Previous work===
-Apertium has [http://jonorthwash.github.io/visualise.html a web-interface] for visualising syntactic trees written in Java-Script and HTML. The interface works with three annotation formats, namely CoNLL-U, CG-3 and SD. It allows a user to either enter their trees in the text area or upload a treebank from a file and switch between sentences.
+Apertium has [http://jonorthwash.github.io/visualise.html a web-interface] for visualising syntactic trees written in Java-Script and HTML. The interface works with three annotation formats, namely CoNLL-U, CG-3 and SD. The current system allows a user to either enter their trees in the text area or upload a treebank from a file and switch between sentences.
 ===Project description===

@@ Line 93: / Line 93: @@
 ====Schedule====
-'''week 1''': thinking through the architecture, writing the skeleton of the project<br />
+'''week 1''': coding the skeleton of the project<br />
 '''weeks 2-3''': working on the graphical editor area<br />
 '''week 4''': finishing the basic interface<br />

@@ Line 97: / Line 97: @@
 '''week 4''': finishing the basic interface<br />
 '''Deliverable #1''': there is an interface which allows to edit trees an save changes<br />
-'''week 5''': working on keyboard shortcuts<br />
+'''week 5''': working on keyboard shortcuts, optimising and increasing usability of the toolbar<br />
-'''week 6''': optimising and increasing usability of the toolbar<br />
+'''week 6''': developing the interface for tree comparison and disambiguation<br />
-'''week 7''': developing the interface for tree comparison and disambiguation<br />
+'''week 7-8''': working on the saving and sharing part of service<br />
-'''week 8''': working on the saving and sharing part of service<br />
 '''27 June''': midterm evaluations deadline<br />
 '''Deliverable #2'''<br />

@@ Line 24: / Line 24: @@
 There is also [https://github.com/jonorthwash/ud-annotatrix a project] aimed to make a toolkit for working with dependency trees in Apertium. At the moment, it allows to visualize the trees. The aim of my project is to create an easy-to-use, quick and interactive interface tool for UD annotation based on the existing Apertium project. The tool should work both online and offline and allow a user to edit the annotation in both graphical and text modes.
-Apart from serving the wide interests of the linguistic community, the treebanks created with the help of this tool can be used for the purposes of the Apertium machine translation platform itself. E.g. the standardised annotated corpora available through the UD project could be immensely useful to training the disambiguation component of Apertium.
+Apart from serving the wide interests of the linguistic community, the treebanks created with the help of this tool can be used for the purposes of the Apertium machine translation platform itself. E.g., the standardised annotated corpora available through the Universal Dependencies project could be immensely useful to training the Apertium's PoS taggers. Although the taggers do not need the full tree structure, treebanks is the richest source of standardised annotation, which Apertium is able to make use of.
+Moreover, as dependency annotation is more general purpose activity, there would be much more people willing to be involved in it. So, Apertium will be more likely to receive the data for its needs as a side product than by trying to get people to doing Apertium-specific annotation.
+Another possible application is to extract CG rules from dependency annotation. There is no existing tool for doing so yet, but there is also a project aiming to create such a tool.
+Finally, making such a functional and easy-to-use tool for dependency annotation could be beneficial for Apertium in that it will attract wider attention of another linguistic community, also concerned about minority languages problems and creating free/open-source linguistic resources.
 ===A description of how and who it will benefit in society===

@@ Line 19: / Line 19: @@
 ===Reasons why Google and Apertium should sponsor it===
+Dependency treebank is a corpus of sentences with annotated dependency structure. It can be used both for the purposes of linguistic research and for training statistical parser, which in turn can serve different purposes of natural language processing. For creating a good treebank, manual annotation and/or disambiguation is required.
-Currently there is an interface for doing syntactic annotation called [http://brat.nlplab.org/ brat] with both online and offline. However, the interface has a number of issues. Firstly, it does not allow a user to edit the source. Secondly, it does not allow to edit tokenisation. Basically, this interface lacks a lot of features that could be very useful for annotation. Finally, it requires a web-server in order to be used by a team of annotators.
+Currently there is an interface for doing syntactic annotation called [http://brat.nlplab.org/ brat]. However, the interface has a number of issues. Firstly, it does not allow a user to edit the source. Secondly, it does not allow to edit tokenisation. Basically, this interface lacks a lot of features that could be very useful for annotation. Finally, it requires a web-server in order to be used by a team of annotators.
 There is also [https://github.com/jonorthwash/ud-annotatrix a project] aimed to make a toolkit for working with dependency trees in Apertium. At the moment, it allows to visualize the trees. The aim of my project is to create an easy-to-use, quick and interactive interface tool for UD annotation based on the existing Apertium project. The tool should work both online and offline and allow a user to edit the annotation in both graphical and text modes.
+Apart from serving the wide interests of the linguistic community, the treebanks created with the help of this tool can be used for the purposes of the Apertium machine translation platform itself. E.g. the standardised annotated corpora available through the UD project could be immensely useful to training the disambiguation component of Apertium.
 ===A description of how and who it will benefit in society===

@@ Line 77: / Line 77: @@
 *Closer examination and evaluation of the tools that can be used, e.g.:
 ** [https://github.com/cytoscape/cytoscape.js-edgehandles cytoscape] is a nice tool for making interactive graphs
+** [https://d3js.org/ d3js] is another nice tool
 * Thinking more about the architecture of the app

@@ Line 48: / Line 48: @@
 ** provide keyboard shortcuts for switching between ambiguous analyses in CG-3 view
 * syncronise graphical and text modes
-* allow to save the current treebank on server and give a link for sharing
+* allow to save the current treebank on server and give a link for sharing, as described in [https://github.com/jonorthwash/ud-annotatrix/issues/17 issue #17]
-* display the difference between two (or more?) trees in a case of ambiguous analyses
+* display the difference between two (or more?) trees in a case of ambiguous analyses, as described in [https://github.com/jonorthwash/ud-annotatrix/issues/11 issue #11]
 * tokenise new text input and create a skeleton for annotation, as described in [https://github.com/jonorthwash/ud-annotatrix/issues/1 issue #1]
@@ Line 60: / Line 60: @@
 * Buttons allowing to:
 ** upload a treebank
-** save changes, undo, redo (?) (also done by keyboard shortcuts)
+** save changes, undo, redo and so on (also done by keyboard shortcuts)
 ** save the treebank on the server
 ** export the treebank (in CoNLL-U and CG-3)
 * The bar for switching between sentences below. It will allow to both go back and forward and choose a sentence by number.
+If there are too many functions, some buttons will be replaced with a toolbar.
 ----

@@ Line 87: / Line 87: @@
 '''week 1''': thinking through the architecture, writing the skeleton of the project<br />
 '''weeks 2-3''': working on the graphical editor area<br />
-'''week 4''': <br />
+'''week 4''': finishing the basic interface<br />
 '''Deliverable #1''': there is an interface which allows to edit trees an save changes<br />
 '''week 5''': working on keyboard shortcuts<br />
-'''week 6''': optimising and increasing usability of the toolbar<br />
+'''week 6''': optimising and increasing usability of the toolbar (?)<br />
 '''week 7''': developing the interface for tree comparison and disambiguation<br />
-'''week 8''': <br />
+'''week 8''': working on the saving and sharing part of service (?)<br />
 '''27 June''': midterm evaluations deadline<br />
 '''Deliverable #2'''<br />
-'''week 9-10''': <br />
+'''week 9-10''': increasing the functionality <br />
 '''week 11''': testing, fixing bugs<br />
 '''week 12''': cleaning up the code, last fixes, writing documentation<br />
-'''Project completed''': a user-friendly interactive annotation interface is ready
+'''Project completed''': a user-friendly interactive annotation interface is ready to use
 == List your skills and give evidence of your qualifications ==