[Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE

[t.elsaleh at surrey.ac.uk]

Hello Carlos, Fermin, Tobias,

After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following:


·         NGSI-9 standard operations

o   Register, discover, subscribe/notify

·         NGSI-9 convenience operations

o   Register, discover, subscribe/notify

·         NGSI-9 associations

·         NGSI-9 discovery restrictions (scopes)

·         NGSI-9 subscription restrictions

Fermin, Tobias, have I missed something?

I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view.

Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well.


Best regards,
Tarek

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130417/2a745d3d/attachment.html>