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-3969) Add JSON Serialization for CASs and UIMA Descriptors
Date Fri, 03 Oct 2014 20:21:34 GMT

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

Marshall Schor commented on UIMA-3969:

Some users have expressed an interest in exploiting JSONs capabiliies to have more embedding
(we currently embed lists and arrays as feature values if they are marked in the type system
as {{<multipleReferencesAllowed>false</multipleReferencesAllowed>}}.

They would like this embedding to include FSs within other FSs (FSs means FeatureStructures).
 And they would like this done based on dynamically determining if the embed candidate is
multiply-referenced or not.  When I delve into this, I see some issues with supporting this
and delta CAS formats.  

One approach is to drop delta CAS formats.  I'm wondering if this might be reasonable, given
that we have XMI serialization as an alternative (or various binary ones).  I think the main
motivation for JSON serialization is to connect the output of UIMA pipelines with non-UIMA
web or cloud applications; this is probably a quite different model than the standard UIMA
pipeline with remotes model, where the intent is to send a CAS to a remote, and have it be
"returned" (often as a Delta). 

I'd like to hear from anyone listening of your views on this trade-off between supporting
dynamic embeddability and supporting delta-CAS formats.

> 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
> I've put up a Wiki page with some of the thoughts so far in this exploration, here: 
> 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

View raw message