waiting for input from Appscend

talked to Gabi; he will send around an invite for this Thursday.

held conf call with Peter and Appsend on march 21
Appsend will provide further information on how their product may complement Orion, Proton, and Cepheus

waiting for input from appsend

Appsend shared input

in view of the overlap of appscend with existing enablers, especially Orionthe decision to include them would have to be taken by the architecture board /Technical Committee

proposed them to integrate via demo scenarios, integration as full-fledged GE unlikely at this stage

Request to Gilles to submit formally to the Technical Steering Committe

This request doesn't seem a Technical issue - it seems a Management issue to me

By the Governance Model, the process can be started just with submitting specs.
http://docs.telepat.io/#the-api-endpoint - is this document enough for specs?

Do we have formal statements on the existing overlap with Proton or other Enablers?

kind regards
Peter

Uri can you please help with Peter's question about Proton?

Sure,
Proton CEP (as far as I know) does not have functional overlaps with other GEs, but it interacts with them. Specifically with ORION, which seems to be the most common use case.
In a way, you can view the ORION context dependent handling and routing of events to be some kind of event processing, but it is not "complex" event processing as per the Proton capabilities.

you can see on the interactions with other GEs in the documentation.

I hope that helps.

• Uri