[
https://issues.apache.org/jira/browse/UIMA-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244091#comment-17244091
]
Peter Klügl commented on UIMA-6262:
-----------------------------------
Ok, this actually tricker than I thought, not the potential fix, but the rule.
I am thinking about rather referring to it not as a bug but a feature. Labels
should be valid and keep their assignment completely during the root statement
(Enumeration in this case). Maybe dc1 and cue should be reassigned or cleared,
but one could also argue to remember the last valid assignment (-> feature).
The problem with this rule can be fixed by rewriting it to:
{noformat}
Enumeration
<-{dc1:DiagnosisConcept{dc1.negatedBy!=null};}
<-{cue:dc1.negatedBy;}
->{dc2:DiagnosisConcept{dc2.negatedBy==null -> dc2.negatedBy=cue};
};
{noformat}
which specifies a conjunction of both inlined rule as action. The expected
result is achieved....
> Ruta: label not reset in inlined rule
> -------------------------------------
>
> Key: UIMA-6262
> URL: https://issues.apache.org/jira/browse/UIMA-6262
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
> Affects Versions: 2.8.1ruta, 3.0.1ruta
> Reporter: Peter Klügl
> Assignee: Peter Klügl
> Priority: Major
> Fix For: 2.9.0ruta, 3.1.0ruta
>
>
> Example:
> {noformat}
> Enumeration
> <-{dc1:DiagnosisConcept{dc1.negatedBy!=null}; cue:dc1.negatedBy;}
> ->{dc2:DiagnosisConcept{dc2.negatedBy==null -> dc2.negatedBy=cue};
> };
> {noformat}
> In a document with several enumerations, the label value is not resetted
> resulting in a false assignment of the feature over a long distance skipping
> potentially several enumerations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
