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

Richard Eckart de Castilho updated UIMA-2552:
---------------------------------------------

    Issue Type: Technical task  (was: Improvement)
        Parent: UIMA-2896
    
> 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.1.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to