The biggest overhead associated with calling annotators configured as services is due to CAS serialization and communication. In order to minimize this overhead, we are planning to implement two new features: "CAS projections" and "delta CAS".

CAS projection will allow only the subset of a CAS needed by an annotator service to be serialized and delivered to the service. For the reply from processing, delta CAS will enable returning only the changes to the CAS made by the annotator service.

Our design objective is to make these changes be transparent to annotator developers, but there are some cases where component descriptor changes will be needed to be able to best take advantage of these new capabilities.

Details on the proposal are in the following sections.

1. Service registration by the client is done by making a getMeta call, requesting metadata describing the service. The getMeta response will be modified to include service preferences for the input CAS format. A new component descriptor parameter will specify that the service accepts CAS projections. CAS projections as input will not work if the input capabilities do not include all the types & views required by the annotator. To avoid the possibility of breaking existing services, CAS projections will not be enabled by default.

Similarly, a new property will be added to the getMeta call indicating the desire for a delta CAS reply format.

A new property will be added to the processCAS call indicating the desire for a delta CAS reply format since the service will handle requests from multiple clients. Older clients not supporting delta CAS replies will of course not ask for delta CAS and will be able to utilize new services .Older services will ignore requests for delta CAS and continue to return a complete CAS.  In the case where the client sends a "CAS projection" in the processCAS call, the new property will indicate that the client requires that the service return a delta CAS.

2. A CAS projection is the subset of a CAS defined by the cross product of the types and views (Sofas) declared in the service's input capabilities. The option to generate CAS projection will be built into XMI serialization code. Proposed rules for creating a CAS projection are:

  • The _InitialView is always included in the list of views to be sent.
  • All specified types (and their subtypes) which are indexed in the specified views are added to the projection. Note that specifying uima.cas.TOP will result in all indexed FS for the specified views being included.
  • Non-indexed FS which are referenced by FS previously added to the projection are also added, if their type is specified, but with the following exception: any annotation FS belonging to a view not in the specified list of views is not added.
  • FS features that are references to FS excluded from the projection will get a unique value that will be used to generate an exception to service code attempting to instantiate that reference.

3. Delta CAS capability will be built into the XMI serialization done in a service, and into the deserialization done on the client. Deserialization already supports merging new content into an existing CAS; a new deserialization option will enable or disable modifications of preexisting CAS content. Note that the XMI standard already includes add, delete and replace elements to be used in the delta CAS format.

The current XMI CAS serialization format is used to represent the Delta CAS serialzation with the addition of the following three attributes to the cas::View element:

  1. added_members - list of XMI ids of feature structures newly indexed in this view.
  2. deleted_members - list of XMI ids of feature structures delete from this view.
  3. reindexed_members - list of XMI ids of feature structures that need to be reindexed as the feature values may have been modified.
  • No labels

1 Comment

  1. Delta CAS design

    The current XMI deserializer already supports deserialization and merging in of new content into a CAS by remembering the max XMI id of feature structures in the CAS and deserializing only those feature structures whose XMI id is greater that this high water mark.

    To implement delta CAS support for modifications to existing feature structures and to views, in addition to the max XMI id, the CAS object needs to be extended to maintain a journal of the feature structures and views that had been changed. For delta CAS purposes, this journal is a simple vector consisting of the XMI ids of feature structures and views that were updated.

    XMI serialization in delta CAS format will consist of the new content identified by feature structures with id greater than the high water mark and modified content as listed in the journal. XMI deserialization of delta CAS will add and update the CAS object as well as add to the journal. This is required to support delta CAS in UIMA aggregates so that the journal contains an aggregation of all changes made by downstream components which can then be serialized in delta CAS format for sending to upstream components.

    To support provenance tracking as described in Improving UIMA Debug Capabilities, the journal will be enhanced to keep track of every modification as well as which component make the change. This more detailed provenance tracking is optional and the behavior will be controlled via the operational descriptor.