[
https://issues.apache.org/jira/browse/UIMA-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891620#action_12891620
]
Eddie Epstein commented on UIMA-1840:
-------------------------------------
bq. 1. Prim lang output capability = x-unspecified, result-spec should change
its language (just for this primitive) to x-unspecified.
As Adam says, this is wrong and I don't think it agrees with what we discussed.
If an aggregate has lang=en, and a delegate has lang=x-unspecified, the
intersection should be en for the delegate. The same is true for aggregate
lang=x-unspecified and delegate lang=en.
So a capability intersection rule should simply be that x-unspecified will
match with any other language, and if the delegate lang=x-unspecified, its
capabilities will be mapped to the other language.
> Result Specification behavior incorrect for aggregates
> ------------------------------------------------------
>
> Key: UIMA-1840
> URL: https://issues.apache.org/jira/browse/UIMA-1840
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Eddie Epstein
>
> For a scenario using default result specifications, if an annotator with
> language "x-unspecified" is included in an aggregate with a different
> language, say "en", any containsType method calls from the annotator will
> return false.
> This behavior is incorrect given that the annotator has declared that it will
> work with any language.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
