[
https://issues.apache.org/jira/browse/UIMA-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891591#action_12891591
]
Adam Lally commented on UIMA-1840:
----------------------------------
I'm not understanding case 1 of the intersection logic you propose. If prim
lang output capability = x-unspecified and result spec lang = en, my first
thought was that the result spec should stay as en. This is the case where an
annotator says it supports any language but an aggregate says only en. Then,
if a CAS comes through that has language es, the annotator should not produce
anything, right?
Basically I guess what I'm suggesting is that the resulting language should be
the most specific (where x-unspecified subsumes en subsumes en-us). Am I
missing something?
> 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.
