You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2014/09/16 20:10:35 UTC

[jira] [Reopened] (UIMA-3969) Add JSON Serialization for CASs and UIMA Descriptors

     [ https://issues.apache.org/jira/browse/UIMA-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor reopened UIMA-3969:
----------------------------------

Fix issues with byteArray serialization.  This is done for JSON as "binary" data following JSON/Jackson conventions - so it is encoded as base64.  The format should not have [] around the value.  Also, add a @featureByeArrays to the @context.  

Change the namespace support to only do namespaces where they're required, type by type.  (Meaning some types may not use namespaces, and others will).


> 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.3.4#6332)