You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Peter Klügl (Created JIRA)" <de...@uima.apache.org> on 2012/01/12 14:19:39 UTC

[jira] [Created] (UIMA-2330) Improve rule matching for filtered types

Improve rule matching for filtered types
----------------------------------------

                 Key: UIMA-2330
                 URL: https://issues.apache.org/jira/browse/UIMA-2330
             Project: UIMA
          Issue Type: Improvement
          Components: TextMarker
            Reporter: Peter Klügl
            Assignee: Peter Klügl


Improve rule matching for filtered types: Validate the behavior of the TextMarker rules for different configurations of filtering settings and add unit tests. When finding new anchors for rule elements the next annotations should also consider offsets after annotations of filtered types. This should result in a even better filtered inference than the old paradigm based on TextMarkerBasics and their stored anchors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Closed] (UIMA-2330) Improve rule matching for filtered types

Posted by "Peter Klügl (Closed JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Klügl closed UIMA-2330.
-----------------------------

    Resolution: Fixed

Filtering is now greedy. Closing this issue.
                
> Improve rule matching for filtered types
> ----------------------------------------
>
>                 Key: UIMA-2330
>                 URL: https://issues.apache.org/jira/browse/UIMA-2330
>             Project: UIMA
>          Issue Type: Improvement
>          Components: TextMarker
>            Reporter: Peter Klügl
>            Assignee: Peter Klügl
>
> Improve rule matching for filtered types: Validate the behavior of the TextMarker rules for different configurations of filtering settings and add unit tests. When finding new anchors for rule elements the next annotations should also consider offsets after annotations of filtered types. This should result in a even better filtered inference than the old paradigm based on TextMarkerBasics and their stored anchors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2330) Improve rule matching for filtered types

Posted by "Peter Klügl (Commented JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185048#comment-13185048 ] 

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

I have not included the changes I proposed in the description now, because getting possibly several annotations when calling something like moveToNext() is probably not intuitive for UIMA users. Instead, the filtering will behave greedy: All annotations will be ignored by rule matches if they are part of an annotation with a filtered type.
                
> Improve rule matching for filtered types
> ----------------------------------------
>
>                 Key: UIMA-2330
>                 URL: https://issues.apache.org/jira/browse/UIMA-2330
>             Project: UIMA
>          Issue Type: Improvement
>          Components: TextMarker
>            Reporter: Peter Klügl
>            Assignee: Peter Klügl
>
> Improve rule matching for filtered types: Validate the behavior of the TextMarker rules for different configurations of filtering settings and add unit tests. When finding new anchors for rule elements the next annotations should also consider offsets after annotations of filtered types. This should result in a even better filtered inference than the old paradigm based on TextMarkerBasics and their stored anchors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2330) Improve rule matching for filtered types

Posted by "Peter Klügl (Commented JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185052#comment-13185052 ] 

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

The changes caused a considerable slowdown of the rule inference, but I think this can be repaired without major problems. I will open another issue for it.
                
> Improve rule matching for filtered types
> ----------------------------------------
>
>                 Key: UIMA-2330
>                 URL: https://issues.apache.org/jira/browse/UIMA-2330
>             Project: UIMA
>          Issue Type: Improvement
>          Components: TextMarker
>            Reporter: Peter Klügl
>            Assignee: Peter Klügl
>
> Improve rule matching for filtered types: Validate the behavior of the TextMarker rules for different configurations of filtering settings and add unit tests. When finding new anchors for rule elements the next annotations should also consider offsets after annotations of filtered types. This should result in a even better filtered inference than the old paradigm based on TextMarkerBasics and their stored anchors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira