[Fiware-data] On the relation of the Metadata Processing GE (Siemens) and the CEP GE (IBM)

[Hutter, Andreas]

Dear Guy, all,

as agreed during the telco, I am taking up the discussion on the relation between the Metadata Processing GE (Siemens) and the CEP GE (IBM).
The question to be discussed is whether the CEP GE would already cover the functionalities of the Metadata Processing GE and, therefore, the latter one could be discarded.

My current understanding is the following:

a) The functionality of the (Meta)data Processing GE is to:
- manage the incoming streaming / data connections
- prepare the incoming data for further consumption in the analytics platform (e.g. transforming an XML document into JavaClasses, performing simple filtering operations, attaching reception time stamp, ...). There are no complex processing steps involved (e.g. correlations)
- provide the prepared data to the target consuming GE

b) These functions have corresponding functions that are provided inside the CEP GE.

Hence we need to answer two questions:
1. Do we provide an stand-alone GE to provide the functions currently proposed for the (Meta)data Processing GE ?
--> I believe that this would be beneficial because the tasks addressed by these functions are required all consuming GEs in the analytics platform. At the same time GE's like the CEP GE could provide their own internal "preprocessing components" to provide these functions, i.e. there is always the option to bypass the (Meta)data Processing GE.

2. Should we use the (Meta)data Processing GE proposed by Siemens or should we carve out the corresponding functions from the CEP GE by defining the appropriate interfaces and asking IBM to provide their implementation with these APIs  attiached ?
--> I do not have a strong opinion here. Either way is fine.

Best regards,
Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110617/9944ff1a/attachment.html>