You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2020/09/15 17:42:00 UTC

[jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Richard Eckart de Castilho created UIMA-6265:
------------------------------------------------

             Summary: Drop JVinci and SOAP support from UIMAv3
                 Key: UIMA-6265
                 URL: https://issues.apache.org/jira/browse/UIMA-6265
             Project: UIMA
          Issue Type: Brainstorming
          Components: Transport Adapters - SOAP, Vinci
            Reporter: Richard Eckart de Castilho


Does anybody know if we still need JVinci and SOAP these days?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Posted by Daniel Gruhl <me...@gmail.com>.
Fair enough - but jVINCI is both a data and control format (it says how to
put a CAS into XML). We need some way to do this. I agree that JSON would
handle both at some point.

  -= Dan

On Tue, Sep 22, 2020 at 8:09 AM Richard Eckart de Castilho <re...@apache.org>
wrote:

> On 22. Sep 2020, at 16:46, Daniel Gruhl <me...@gmail.com> 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
>

Re: [jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Posted by Richard Eckart de Castilho <re...@apache.org>.
On 22. Sep 2020, at 16:46, Daniel Gruhl <me...@gmail.com> 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

Re: [jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Posted by Daniel Gruhl <me...@gmail.com>.
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.

         -= Dan

On Mon, Sep 21, 2020 at 12:58 PM Richard Eckart de Castilho <re...@apache.org>
wrote:

> On 21. Sep 2020, at 18:20, Daniel Gruhl <me...@gmail.com> wrote:
> >
> > And probably want to not drop it until we have a network replacement (see
> > Json suggestion!) :)
>
> Doesn't UIMA-AS serve as a replacement? jVinci / SOAP is only a transport
> protocol and not a data format - so why/how is it related to a JSON
> proposal for you?
>
> -- Richard

Re: [jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Posted by Richard Eckart de Castilho <re...@apache.org>.
On 21. Sep 2020, at 18:20, Daniel Gruhl <me...@gmail.com> wrote:
> 
> And probably want to not drop it until we have a network replacement (see
> Json suggestion!) :)

Doesn't UIMA-AS serve as a replacement? jVinci / SOAP is only a transport protocol and not a data format - so why/how is it related to a JSON proposal for you?

-- Richard

Re: [jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Posted by Daniel Gruhl <me...@gmail.com>.
And probably want to not drop it until we have a network replacement (see
Json suggestion!) :)

  -= Dan

On Sun, Sep 20, 2020 at 12:30 PM Marshall Schor <ms...@schor.com> wrote:

> deprecation is fine.  dropping with some kind of feature toggle, where it
> could
> be restored if it turns out some people are using it, would be best...
>
> -Marshall
>
> On 9/15/2020 1:42 PM, Richard Eckart de Castilho (Jira) wrote:
> > Richard Eckart de Castilho created UIMA-6265:
> > ------------------------------------------------
> >
> >              Summary: Drop JVinci and SOAP support from UIMAv3
> >                  Key: UIMA-6265
> >                  URL: https://issues.apache.org/jira/browse/UIMA-6265
> >              Project: UIMA
> >           Issue Type: Brainstorming
> >           Components: Transport Adapters - SOAP, Vinci
> >             Reporter: Richard Eckart de Castilho
> >
> >
> > Does anybody know if we still need JVinci and SOAP these days?
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.4#803005)
>

Re: [jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Posted by Marshall Schor <ms...@schor.com>.
deprecation is fine.  dropping with some kind of feature toggle, where it could
be restored if it turns out some people are using it, would be best...

-Marshall

On 9/15/2020 1:42 PM, Richard Eckart de Castilho (Jira) wrote:
> Richard Eckart de Castilho created UIMA-6265:
> ------------------------------------------------
>
>              Summary: Drop JVinci and SOAP support from UIMAv3
>                  Key: UIMA-6265
>                  URL: https://issues.apache.org/jira/browse/UIMA-6265
>              Project: UIMA
>           Issue Type: Brainstorming
>           Components: Transport Adapters - SOAP, Vinci
>             Reporter: Richard Eckart de Castilho
>
>
> Does anybody know if we still need JVinci and SOAP these days?
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)

Re: [jira] [Created] (UIMA-6265) Drop JVinci and SOAP support from UIMAv3

Posted by Marshall Schor <ms...@schor.com>.
I believe that one or both of these was the default for the predecessor of
uima-as, Collection Processing Engine (CPE / CPM).  See for example,

http://uima.apache.org/d/uimaj-current/references.html#ugr.ref.xml.cpe_descriptor.descriptor.operational_parameters

and notice the cpeConfig param setting "deployAs".

-Marshall

On 9/15/2020 1:42 PM, Richard Eckart de Castilho (Jira) wrote:
> Richard Eckart de Castilho created UIMA-6265:
> ------------------------------------------------
>
>              Summary: Drop JVinci and SOAP support from UIMAv3
>                  Key: UIMA-6265
>                  URL: https://issues.apache.org/jira/browse/UIMA-6265
>              Project: UIMA
>           Issue Type: Brainstorming
>           Components: Transport Adapters - SOAP, Vinci
>             Reporter: Richard Eckart de Castilho
>
>
> Does anybody know if we still need JVinci and SOAP these days?
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)