Actually, I think that in is questionable whether the type should be extensible 
in either of the two fashions. Anybody who wants to store additional meta data 
in a CAS could create a custom type instead of modifying DocumentAnnotation 
either through the officially documented was, through type merging, or through 
derivation. 

Do you suggest that only derivation should be prohibited, but type merging 
should be allowed, possibly even encouraged?

-- Richard

Am 09.08.2013 um 15:13 schrieb Marshall Schor <[email protected]>:

> Hi,
> 
> There's an unfortunate ambiguity in the word "extend". There's two kinds of 
> Type
> extensions in UIMA. The UIMA documentation I think uses this term to mean
> defining an a type with additional features and having it merged at pipeline
> initialization time with all other definitions of this same type, perhaps
> resulting in a definition with additional features (merged from other types).
> 
> There's another definition coming from the Object Oriented world and Java, 
> where
> extend means to create a subclass.  UIMA has that too.
> 
> Which one of these are you talking about here?
> 
> 
> -Marshall
> 
> On 8/9/2013 9:00 AM, Richard Eckart de Castilho (JIRA) wrote:
>> Richard Eckart de Castilho created UIMA-3167:
>> ------------------------------------------------
>> 
>>             Summary: Remove ability to extend type DocumentAnnotation
>>                 Key: UIMA-3167
>>                 URL: https://issues.apache.org/jira/browse/UIMA-3167
>>             Project: UIMA
>>          Issue Type: Improvement
>>          Components: Core Java Framework
>>            Reporter: Richard Eckart de Castilho
>>             Fix For: incompatible
>> 
>> 
>> DocumentAnnotation is a special type in UIMA with special integration into 
>> the JCas/CAS interfaces. Being able to extend it causes all kinds of special 
>> cases. It has been suggested to remove the ability of extending the type
>> 
>> See discussion here: http://markmail.org/thread/dczxs5i5nctubj5l
>> 
>> --
>> 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