uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-2478) Add CAS interface method that allows user to obtain a list of Markers associated with a given CAS
Date Wed, 03 Jul 2013 20:21:20 GMT

    [ https://issues.apache.org/jira/browse/UIMA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699398#comment-13699398
] 

Marshall Schor commented on UIMA-2478:
--------------------------------------

There are several intertwined issues here.

1) This is a request to have the CAS instance, itself, hold onto the marker.  A possible difficulty
is that the marker data is not a serializable part of the CAS.   So, it would be necessary
to examine all possible scenarios to insure that in all cases this is OK.  

2) This is also a request to surface this at the CAS API level (rather than have it be just
an aspect of the implementation.  I wonder if the Marker mechanism(s) are evolved enough to
warrant the implied stability putting them into the CAS (not CASImpl) interface implies.

3) Markers are created internally by UIMA for its own purpose(s) (for instance, UIMA-AS services
create them); there could be some "clashes" between "users" making use of them and internal
systems using this.  Because of this, it would be good to keep this out of the public CAS
API, for now.
                
> Add CAS interface method that allows user to obtain a list of Markers associated with
a given CAS
> -------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-2478
>                 URL: https://issues.apache.org/jira/browse/UIMA-2478
>             Project: UIMA
>          Issue Type: New Feature
>            Reporter: Benjamin Segal
>         Attachments: UIMA-2478.bps.patch
>
>
> Add a convenience function that removes the need for applications that create Markers
for many CASes to separately manage them (e.g., map CAS to its related Marker), and thereby
simplify application code.
> Today's current level of support allows a user to create a Marker for a given CAS (through
the createMarker() method which is part of the CAS interface).
> This proposed support will allow the user to subsequently query a given CAS and obtain
a complete list of Markers created against this CAS. This function is a natural extension
to the given level of support (i.e., if one can create Marker for a given CAS, one should
be able to query the CAS to find said Marker.)
> Having this support significant simplifies application code, offering advantages from
a memory overhead, performance, and maintainability standpoint.  For example, the application
won't need to build and maintain a map of CASes to Markers, given the Marker is hanging off
the CAS to begin with.

--
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

Mime
View raw message