Hi Marshall, I think that those things you mention, view filtering, FS embedding, as well as determining multiple FS references, really are the key to solving my use case. By embedding non-shared FSs within a view in the serialization it would probably be much easier to load CASs based on just a subset of views, as well as merge any changes back into the full serialized CAS.
-- Jens On Thu, Aug 28, 2014 at 4:12 PM, Marshall Schor (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/UIMA-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113830#comment-14113830 > ] > > Marshall Schor commented on UIMA-3969: > -------------------------------------- > > Another facet to this: embedding. The Xmi has embedding for non-shared > lists and arrays. I don't know if XMI allows this (I know JSON does), but > it's possible Xmi could support embedding for other non-shared objects, > like user-defined feature structures. Example: > {code:xml} > <xyz:MyType xmi:id="382"> > <myFeat> > <xyz:EmbeddedType xmi:id="404" .... /> <-- a directly > embedded FS, otherwise represented via an FsRef integer > </myFeat> > </xyz:MyType> > {code} > > Consider extending the current implementation to support embedding (at > least for JSON) of non-shared FSs besides lists and arrays. Also consider > making this configurable, that is, having a mode which turns off all > embedding - this would make the representation more uniform, and perhaps > easier to parse and handle (fewer cases to consider) at the cost of some > extra bytes. . > > > Add JSON Serialization for CASs and UIMA Descriptors > > ---------------------------------------------------- > > > > Key: UIMA-3969 > > URL: https://issues.apache.org/jira/browse/UIMA-3969 > > Project: UIMA > > Issue Type: New Feature > > Components: Core Java Framework > > Affects Versions: 2.6.0SDK > > Reporter: Marshall Schor > > Assignee: Marshall Schor > > Priority: Minor > > Fix For: 2.6.1SDK > > > > > > Recent trends toward moving things into the cloud motivated me to > consider what a JSON serialization of the CAS and descriptor metadata (more > particularly, type systems) might look like. > > I've put up a Wiki page with some of the thoughts so far in this > exploration, here: > https://cwiki.apache.org/confluence/display/UIMA/JSON+serialization+for+UIMA > > I'm also fooling around with a proof-of-concept implementation, based on > our current XMI serialization for the CAS, as well as our > MetaDataObject_impl serialization for UIMA descriptors, in order to work > out the details. There are additional nits (like how to configure things) > not yet worked out. > > Comments and discussion appreciated; I've put this up as a Jira to > record them together - but feel free to use email also for any comments you > feel might be better being more ephemeral. > > > > -- > This message was sent by Atlassian JIRA > (v6.2#6252) >
