uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Klügl (JIRA) <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-2937) Leading optional matching conditions in Ruta
Date Wed, 12 Jun 2013 13:04:20 GMT

    [ https://issues.apache.org/jira/browse/UIMA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681186#comment-13681186
] 

Peter Klügl commented on UIMA-2937:
-----------------------------------

I do not see a good solution for this problem. The rule is normally forced to start with the
first rule element, but that is optional. If we do not want to match on it, the rule should
not start its match with that rule element. I added the manual selection of the rule anchoring
in UIMA-2975, which can be used to avoid this problem. There is now also a section in the
documentation describing the problem and the new functionality.
                
> Leading optional matching conditions in Ruta
> --------------------------------------------
>
>                 Key: UIMA-2937
>                 URL: https://issues.apache.org/jira/browse/UIMA-2937
>             Project: UIMA
>          Issue Type: Bug
>          Components: ruta
>    Affects Versions: 2.0.1ruta
>            Reporter: Peter Klügl
>            Assignee: Peter Klügl
>             Fix For: 2.0.2ruta
>
>
> Armin Wegner reported:
> In Ruta 2.0.2-SNAPSHOT, rules with an optional first element do not work. The optional
part seems to be mandatory. Using
> DECLARE Test;
> "a"? "b" "c"{->MARK(Test, 1, 3)};
> on
> a b c x b c
> marks "a b c" (0, 5) but not "b c" (8, 11).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message