Issues

From UNL Wiki
(Difference between revisions)
Jump to: navigation, search
(Front-end)
(Front-end)
Line 39: Line 39:
 
;Shared resources (1.1)
 
;Shared resources (1.1)
 
:Shared resources must bring the possibility of being reordered (currently, we cannot reorder them)
 
:Shared resources must bring the possibility of being reordered (currently, we cannot reorder them)
;NL inputs and UNL documents (1.1)
+
;NL and UNL documents (1.1)
:Shared NL inputs (currently, it's only possible to send them, but then the changes are not propagated). And they should work as
+
:Shared NL inputs (currently, it's only possible to send them, but then the changes are not propagated). And they should work as dictionaries and grammars (we should have the option of grouping them and loading more than one at a time)
dictionaries and grammars (we should have the option of grouping them and loading more than one at a time)
+
 
;IAN/EUGENE communication (1.1)
 
;IAN/EUGENE communication (1.1)
 
:A given output of IAN could be used as the input for EUGENE and vice-versa - using the loaded resources
 
:A given output of IAN could be used as the input for EUGENE and vice-versa - using the loaded resources

Revision as of 09:08, 17 October 2012

List of pending features and known bugs.

Contents

IAN and EUGENE

Back-end

Parsing (1.0)
Parsing of rules need to be improved. IAN and EUGENE were accepting rules with unbalanced parentheses. There is also a problem of an extra comma in the rules. The sensitivity of syntactic check of the Engines should be higher. Eugene and IAN must be sensitive to the following syntactic error:
  • (%a,A,B,C):=((%a,+E); (This rule is being accepted by the system)
Encoding (1.0)
Eugene and IAN should reject wrong UTF-8 encoding. From the perspective of the user, the rule was perfect, and the string was clearly and correctly displayed; but the machine was replacing it by empty.
Consistency of graphs (1.1)
Rules leading to impossible graphs are working. The example below is generating an impossible graph.
(NB(N,%n;JB(%j;%j2),{and|or},%adjc),%m):= (JB(%j;%j2),rel=%adjc) (NB(N,%n;%j),rel=%m)(NB(N,%n;%j2),rel=%m);
This rule is putting the same node %j in two different positions in the node list. This should not be possible. A node cannot be inside two different nodes in a list structure.
Preprocessing module (1.1)
A module for preprocessing is needed in IAN. It will serve for sentence segmentation and morphological preprocessing. Rules of the preprocessing module will be only of the LL type, will only deal with strings and will apply before any dictionary search. They will be used to assign STAIL and SHEAD. Regular expressions should be admitted. The unit of processing will be the paragraph (i.e., any string between \n and \r). Examples of possible rules:
  • (" .",%x):=(%x)(+STAIL,%y);
  • (".",%x)(/[ABCDEFGHIJKLMNOPQRSTUVWXYZ]/,%y):=(%z,+SHEAD)(%x)(%y);
  • ("an ",%x)(/[aeiouy]/,%y):=("a ",%x)(%y);
Observations:
  • +STAIL automatically creates SHEAD (in addition to STAIL itself), and +SHEAD automatically create STAIL.
  • The preprocessing module should be provided in a separate tab (S-Rules, for segmentation rules)
Mathematical operations (1.1) (574)
Mathematical operations inside nodes
  • (%x):=(%x-1); (i.e., reduce the value of %x in 1)
  • (%x):=(%x+1); (i.e., add 1 to %x)
  • (%x):=(%x*2); (i.e., multiply %x by 2)
  • (%x):=(%x/2); (i.e., divide % by 2)

Front-end

Drag-and-drop (1.1)
To include the possibility of using "drag-and-drop" to reorder dictionaries and dictionary entries, and grammars and grammar rules (in addition to the current one);
Test sets (1.1)
To improve the test sets. They should show only the differences.
Trace (1.1)
The trace must be thoroughly revised. The desired structure is presented at
Groups (1.1)
Groups should be collapsible/expandable, and a single file may participate in several groups (grouping must be done using tags,

instead of exclusive categories)

Shared resources (1.1)
Shared resources must bring the possibility of being reordered (currently, we cannot reorder them)
NL and UNL documents (1.1)
Shared NL inputs (currently, it's only possible to send them, but then the changes are not propagated). And they should work as dictionaries and grammars (we should have the option of grouping them and loading more than one at a time)
IAN/EUGENE communication (1.1)
A given output of IAN could be used as the input for EUGENE and vice-versa - using the loaded resources

LILY

End-user interface

  1. (BETA)To remove the option "compiled resources" from the interface. There will be an admin page where the configuration will be set.
  2. (BETA) LILY is not accepting Arabic input.
  3. (BETA)To replace the localization file (translations to be provided by the UNDL Foundation)
  4. (BETA)To replace the logos of the UNDLF and UNL by others with higher-resolution (to be provided by the UNDL Foundation)
  5. (BETA)To replace the copyright (to be provided by the UNDL Foundation)
  6. (BETA)To remove the login in the end-user final version
  7. (BETA)To replace the contact to info@undlfoundation.org
  8. (BETA) Background images are not being aligned in zoom in and zoom out (CSS). The application is not working in IE.
  9. (BETA)To reduce the size of the logos
  10. (BETA)To synchronize users and passwords with the UNLweb
  11. (1.0)Feedback from users (source, UNL and target must be stored with the corresponding evaluation)

Test interface

  1. To have IAN's and EUGENE's dictionary, t-rules and d-rules tab in the same interface inside the UNLdev.

NORMA

SEAN

Software