Hello All, Thank you again for all of your responses about the UIMA CAS Store. I'm glad that you were interested in this topic, and I would like to submit another summary to see if we can concisely define what would be requirements interfacing with a CAS Store.
We talked a bit about implementation (Binary vs XMI, DB vs File system), but I would like to first discuss an interface for a CAS Store. The reason being is that it seems while there is consistent functionality in a CAS store, there might be different implementation constraints / preferences. I'll try to be concise, and if you would like to comment, please do so. Implementation: - Compatible with current UIMA implementations (UIMAj, UIMACpp, UIMAFit) - Well defined API - Documentation Functionality: - Accessible from a Web Service (SOAP / REST) - Maintain Collection of CASes - INSERT / DELETE/ UPDATE / READ CASes - INSERT / DELETE/ UPDATE / READ Cas Fragments (Objects within a CAS) - READ FSes produced by a certain annotator across all CASes in all collections or in a certain collection - Query CASes that already have annotations - Use stable identification of CAS As for the identification of CASes and objects within, I would like to push the idea of a Feature Structure ID, as I've written about before. Were there any other thoughts / suggestions about such an object?
