OK, thanks. I played around a little bit today with my own rules
DECLARE Group1;
DECLARE Group2;
DECLARE R3Dot1CurrentPurposeConstraint(Annotation group1, Annotation
group2);
BLOCK(eachEC) EC{}{
"(?i).*(must be (?:receiving|undergoing|using) (.*) for) (.*)" ->
R3Dot1CurrentPurposeConstraint,
Sounds great, thank you in advance!
Whatever comes up, don't hesitate to query back to us.
Cheers,
Sebastian
- Ursprüngliche Mail -
Von: "Peter Klügl"
An: "user"
Gesendet: Mittwoch, 14. September 2016 18:33:56
Betreff: Re: RUTA in Java: access object contents
Hi,
I created an issue
Hi,
I created an issue for it: https://issues.apache.org/jira/browse/UIMA-5108
I won't be able to fix it this week, and maybe not next week because of
some deadlines. I guess it will be fixed at least in the trunk before of
the end of the month.
Best,
Peter
Am 14.09.2016 um 18:25 schrieb
Hi Peter,
Indeed, I was talking about UIMA objects.
We tried to hunt down the error in deeper means and understood more of the
codes. Ahead of any details: again yes, we fail on types extending from TOP. In
our case it is "concept", which does not have a covering text.
In "SimpleFeatureEx", th
Hi,
yes, the types need to be declared before. The DECLARE statements have
been omitted in the example.
Ruta 2.4.0 introduced annotation expressions. Before that, annotations
have only ben e referenced by type expressons. Ruta tries to guess which
annotation is meant by the given type expressio
