On 22. Sep 2020, at 16:46, Daniel Gruhl <[email protected]> wrote: > > Not so much - UIMA-AS is java only. The jVinci/SOAP provides a 'wire > format' for data going from Java UIMA to other services (it used to be C++ > in WebFountain). A JSON "wire format" would replace that.
Isn't the wire format for UIMA-AS as well as for jVinci/SOAP basically XMI (with binary options for UIMA-AS as well - not sure if binary CAS is also supported in jVinci/SOAP)? So a JSON format would I imagine be an alternative to the XMI or binary representations of the CAS. Such a JSON format could then be coupled with say a REST-style endpoint which might serve a similar function as UIMA-AS / jVinci - but the same REST-style endpoint could just as well work with any other format (XMI, binary CAS). So communication protocol (REST, UIMA-AS messaging service, SOAP) and data format (XMI, binary CAS, JSON) seem pretty orthogonal to me. -- Richard
