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] [Reopened] (UIMA-3969) Add JSON Serialization for CASs and UIMA Descriptors
Date Tue, 26 Aug 2014 13:23:57 GMT

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

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


After writing several docs and emails about this, I am more motivated to refactor XmiCasSerialization
into two parts - one related to Xmi, and the other to the generic support code that figures
out the items to serialize.  That would be the part reusable by JSON serialization, and would
allow a better API - one for JSON and one for Xmi. 

Try this refactoring, and (assuming it works) also switch the exceptions reported by JSON
serialization back to IOException (instead of wrapping them).  

> 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)

Mime
View raw message