[
https://issues.apache.org/jira/browse/UIMA-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682807#comment-13682807
]
Richard Eckart de Castilho commented on UIMA-2942:
--------------------------------------------------
This is not my main line of argumentation, but just for the sake of
illustration consider the following case (code is illustratory and doesn't work
as written here):
{code}
AnalysisEngineDescription aggregate = createAggregateDescription(
createTypeSystemDescription("my.NameAnnotation"),
createDescription("ThirdPartyDictionaryAnnotatorPEAR.xml",
"dictionaryFile", new File("myDictionary"),
"outputType", "my.NameAnnotation")));
{code}
In this scenario, I get a pre-packaged aggregate
"ThirdPartyDictionaryAnnotatorPEAR.xml" from an external source and configure
it to produce the type I desire using a dictionary I provide. What you suggest
is, that I do this instead:
{code}
AnalysisEngineDescription aggregate = createAggregateDescription(
createPrimitiveDescription(NullAnnotator.class,
createTypeSystemDescription("my.NameAnnotation")),
createDescription("ThirdPartyDictionaryAnnotatorPEAR.xml",
"dictionaryFile", new File("myDictionary"),
"outputType", "my.NameAnnotation")));
{code}
This is possible of course, but it appears pretty unnatural to add a
NullAnnotator just to be able to add more types.
> Allow configuring a type system on the level of an aggregate
> ------------------------------------------------------------
>
> Key: UIMA-2942
> URL: https://issues.apache.org/jira/browse/UIMA-2942
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Richard Eckart de Castilho
> Priority: Minor
>
> Allow configuring a type system on the level of an aggregate. Priorities and
> indexes are allowed, but setting a type system is forbidden. Seems to be
> inconsequent.
> Consider I get an aggregate from some person. It contains a Ruta script (or
> something else that is type agnostic/type configurable). I reconfigure the
> aggregate with my own script which creates different annotations (e.g. using
> parameter overrides on the aggregate). Now, I would have to reconfigure the
> aggregate with new types as well. I wouldn't want to dive down into the
> individual components of the aggregate to do that - after all, the aggregate
> is meant to be a component in its own right.
--
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
