You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2015/05/24 01:12:17 UTC

[jira] [Updated] (UIMA-2552) Support for JCas classes in @TypeCapability annotation

     [ https://issues.apache.org/jira/browse/UIMA-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-2552:
---------------------------------------------
    Fix Version/s:     (was: 2.2.0uimaFIT)
                   2.3.0uimaFIT

> Support for JCas classes in @TypeCapability annotation
> ------------------------------------------------------
>
>                 Key: UIMA-2552
>                 URL: https://issues.apache.org/jira/browse/UIMA-2552
>             Project: UIMA
>          Issue Type: Technical task
>          Components: uimaFIT
>            Reporter: Richard Eckart de Castilho
>             Fix For: 2.3.0uimaFIT
>
>
> The current @TypeCapability annotation uses Strings for type names:
> {code}
> @TypeCapability(
>   inputs = { 
>     "org.cleartk.token.type.Sentence", 
>     "org.cleartk.token.type.Token:pos", 
>     "org.cleartk.token.type.Token:lemma" },
> {code}
> It would be nice if JCas classes could be used directly, for example like this:
> {code}
> @TypeCapability(
>   inputTypes = { 
>     @Type(Sentence.class),
>     @Type(value=Token.class, features={"pos", "lemma"})})
> {code}
> It would also be nice if features could be directly references (cf. UIMA-2147):
> {code}
> @TypeCapability(
>   inputTypes = { 
>     @Type(Sentence.class),
>     @Type(value=Token.class, features={Token.FEAT_POS, Token.FEAT_LEMMA})})
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)