Infrastructure discussion - Revision history

Francis Tyers: /* Modularity */

2008-04-13T14:29:02Z

Modularity

Francis Tyers at 19:12, 12 April 2008

2008-04-12T19:12:49Z

Francis Tyers: /* Example formats */

2008-02-27T22:48:13Z

Example formats

Trondtr: More formats

2008-02-25T17:03:02Z

More formats

Trondtr: Thanks for the answer.

2008-02-25T17:00:50Z

Thanks for the answer.

Francis Tyers: /* Example formats */ better order

2008-02-24T21:24:11Z

Example formats: better order

Francis Tyers: /* Modularity */

2008-02-24T14:23:35Z

Modularity

Francis Tyers at 14:20, 24 February 2008

2008-02-24T14:20:23Z

Trondtr: Modularity

2008-02-24T14:03:44Z

Modularity

New page

== Modularity ==

To what extent is the apertium system modular? To be specific: In our work we do not use agglutinative paradigms, but cascaded finite-state transducers (the Sámi languages we analyse have all to much non-concatenative morphology to be treated with such methods). We use Xerox tools, but the open-source sfst tools would be a possible alternative. Also, our disambiguation and syntactic analysis does not use HMM, but rather constraint grammar (the vislcg variety). Now, the question is to what extent the system is modular enough to take out one or more apertium component(s) and replace them with other components? [[User:Trondtr|Trondtr]] 14:03, 24 February 2008 (UTC).

[[Category:Discussions]]

@@ Line 30: / Line 30: @@
 :::Thank you for the answer. This was exactly the answer I hoped for. This really makes it a moduler system, and different projects could try out different modules, where the core translation engine probably would be the common ground. [[User:Trondtr|Trondtr]] 17:00, 25 February 2008 (UTC).
-The attempt to port VISLCG to use Apertium style analyses may be found [http://beta.visl.sdu.dk/svn/visl/tools/vislcg3/branches/vislcg3_apertium here]. - [[User:Francis Tyers|Francis Tyers]] 20:12, 12 April 2008 (BST)
+::::See [[Apertium and Constraint Grammar]]. - [[User:Francis Tyers|Francis Tyers]] 15:29, 13 April 2008 (BST)
 ===Example formats===

@@ Line 30: / Line 30: @@
 :::Thank you for the answer. This was exactly the answer I hoped for. This really makes it a moduler system, and different projects could try out different modules, where the core translation engine probably would be the common ground. [[User:Trondtr|Trondtr]] 17:00, 25 February 2008 (UTC).
+The attempt to port VISLCG to use Apertium style analyses may be found [http://beta.visl.sdu.dk/svn/visl/tools/vislcg3/branches/vislcg3_apertium here]. - [[User:Francis Tyers|Francis Tyers]] 20:12, 12 April 2008 (BST)
 ===Example formats===

@@ Line 43: / Line 43: @@
 ;Apertium
 <pre>
-^orða/orða<vblex><inf>/orð<n><nt><pl><gen><ind>$
+before tagging: ^orða/orða<vblex><inf>/orð<n><nt><pl><gen><ind>$
+after tagging : ^orð<n><nt><pl><gen><ind>$
 </pre>

@@ Line 45: / Line 45: @@
 ^orða/orða<vblex><inf>/orð<n><nt><pl><gen><ind>$
 </pre>
+;vislcg
+ "<orða>"
+ 	 "orða" V Ind Prs Pl
+ 	 "orð" N Neu Pl Gen Indef
+ 	 "orða" V Ind Prs 1Sg
+ 	 "orða" V Inf
+ 	 "orða" V Imp Sg
 [[Category:Discussions]]

@@ Line 27: / Line 27: @@
 ::Problems in incompatibility between text formats can be either taken care of in the code (e.g. add a mode to SFST to output Apertium style analyses), or using perl/python/awk scripts. - [[User:Francis Tyers|Francis Tyers]] 14:23, 24 February 2008 (UTC)
+:::Thank you for the answer. This was exactly the answer I hoped for. This really makes it a moduler system, and different projects could try out different modules, where the core translation engine probably would be the common ground. [[User:Trondtr|Trondtr]] 17:00, 25 February 2008 (UTC).
 ===Example formats===

@@ Line 25: / Line 25: @@
 :-[[User:Francis Tyers|Francis Tyers]] 14:20, 24 February 2008 (UTC)
+::Problems in incompatibility between text formats can be either taken care of in the code (e.g. add a mode to SFST to output Apertium style analyses), or using perl/python/awk scripts. - [[User:Francis Tyers|Francis Tyers]] 14:23, 24 February 2008 (UTC)
+===Example formats===
+;xsft
+<pre>
+orða	orð+N+Neu+Pl+Gen+Indef
+orða	orða+V+Inf
+orða	orða+V+Ind+Prs+1Sg
+orða	orða+V+Imp+Sg
+</pre>
+;Apertium
+<pre>
+^orða/orða<vblex><inf>/orð<n><nt><pl><ind><gen>$
+</pre>
 [[Category:Discussions]]

@@ Line 3: / Line 3: @@
 To what extent is the apertium system modular? To be specific: In our work we do not use agglutinative paradigms, but cascaded finite-state transducers (the Sámi languages we analyse have all to much non-concatenative morphology to be treated with such methods). We use Xerox tools, but  the open-source sfst tools would be a possible alternative. Also, our disambiguation and syntactic analysis does not use HMM, but rather constraint grammar (the vislcg variety). Now, the question is to what extent the system is modular enough to take out one or more apertium component(s) and replace them with other components? [[User:Trondtr|Trondtr]] 14:03, 24 February 2008 (UTC).
+:The Apertium system is implemented as a unix pipeline. Currently most language pairs have the following components:
+:* Deformat
+:* Morphological analyser
+:* POS Tagger
+:* Transfer (syntactic + lexical)
+:* Generation
+:* Post-generation
+:* Reformat
+:The more advanced pairs replace the "Transfer" stage with a three-stage transfer, which incorporates a chunker (rule-based) and the ability to move around chunks (NP, V, etc.) rather than lexical units.
+:All modules communicate using text streams, so it would be definitely possible to say use your morphological analysis + tagging, and then use our format management and transfer. e.g.:
+:* Apertium deformat
+:* sfst morphological analysis
+:* VISL constraint grammar
+:* Transfer (syntactic + lexical)
+:* sfst morphological generation
+:* Reformat
+:-[[User:Francis Tyers|Francis Tyers]] 14:20, 24 February 2008 (UTC)
 [[Category:Discussions]]