[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki

[ Back to the navigation ]

You are here: start » user » zeman » interset » to-do

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
user:zeman:interset:to-do [2014/06/16 11:14]
zeman tagset::common vyčištěno a hlavně zrušeno :-) 		user:zeman:interset:to-do [2014/06/16 16:19]
zeman Dokumentace rysů tense a subtense aktualizována.
Line 8: Line 8:
     * Přejmenovat prep na adp?     * Přejmenovat prep na adp?
     * Úplně rozpustit subpos?     * Úplně rozpustit subpos?
-    * Dokumentace nových rysů: nountype, adjtype, verbtype, conjtype. 
     * Nemohli bychom zrušit rys synpos?     * Nemohli bychom zrušit rys synpos?
-    * Nová hodnota prn v prontype. 
-    * Sloučeny rysy tense a subtense. 
     * Co s číslovkami?     * Co s číslovkami?
 +  * Doplnit soubor Changes. Zjistit, zda by se nemohl jmenovat Changes.txt (jde o to, aby ho nadále našel plugin do Distzilly NextRelease).
 +  * Zakomponovat ''driver-test.pl en::penn'' do instalačního testu ''test.t''.
 +  * Dodělat dokumentaci POD tak, aby všechny funkce, které má uživatel k dispozici, byly zdokumentovány.
   * Přenést všechny ovladače, které vznikly v Treexu a do SVN Intersetu se zatím nedostaly.   * Přenést všechny ovladače, které vznikly v Treexu a do SVN Intersetu se zatím nedostaly.
   * Oprášit pravidelné kopírování wiki stránek Intersetu do repozitáře SVN (resp. Redmine). Nyní je tam zastaralá kopie.   * Oprášit pravidelné kopírování wiki stránek Intersetu do repozitáře SVN (resp. Redmine). Nyní je tam zastaralá kopie.
Line 26: Line 26:
   * Query feature value: a shared function detects array and if it is array, searches it for a given value.    * Query feature value: a shared function detects array and if it is array, searches it for a given value.
   * New test in driver-test.pl: does a driver decode into arrays? If so, what features are affected? If not, is it capable of encoding arrays (i.e. does it call the function that gets rid of arrays)?   * New test in driver-test.pl: does a driver decode into arrays? If so, what features are affected? If not, is it capable of encoding arrays (i.e. does it call the function that gets rid of arrays)?
-  * New test in driver-test.pl: how many tags / what proportion of the tagset are decoded using the ''other'' feature? Enumerate them. Maybe, tags that set the ''other'' feature should not be considered when building the list of possible feature structures? (Sometimes it happens that a feature-value combination is permitted only in an ''other'' tag. Although the set of set/unset features could be used as an additional clue leading to this tag, such tags are often marginal stuff that one does not want to use as default.) 
-    * A workaround. Simulate decoding from foreign tagsets. 1. Decode all tags of tagset A. 2. Clear the features ''tagset'' and ''other'' in all feature structures. 3. Now force the tags to defaults (some obscure categories are lost and the tags have to adapt themselves to the fallback categories). 4. Encode all tags again. 5. Check the resulting tags. It is OK if a tag was transformed into another correct tag. However, if a tag was rendered incorrect, it should be discarded from the set of tags that define the correct feature-value combinations. 
   * Extend the ''print_permitted_fs.pl'' tool so that it can search all available drivers. If it is called that way, it prints the name of the driver in front of every feature structure generated by that driver. Print to STDOUT (now it prints to STDERR). Let the user query and filter the feature structure directly: '$_->{mood} eq "ind" && $_->{other} =~ m/^X/'. Grepping the textual output is less powerful.   * Extend the ''print_permitted_fs.pl'' tool so that it can search all available drivers. If it is called that way, it prints the name of the driver in front of every feature structure generated by that driver. Print to STDOUT (now it prints to STDERR). Let the user query and filter the feature structure directly: '$_->{mood} eq "ind" && $_->{other} =~ m/^X/'. Grepping the textual output is less powerful.
   * Enable checking out the latest development version directly from the Subversion repository.   * Enable checking out the latest development version directly from the Subversion repository.

[ Back to the navigation ] [ Back to the content ]