[Fiware-iot] Naming of Configuration Management GE

[Fermín Galán Márquez]

Dear Tarek,

I don't know the reason: when I arrived to the project on October 2012, that was the name it was used ;)

Anyway, I don't have any strong opinion on the name of this GE, as the name of the actual piece of software implementing (Orion Context Broker) it has nothing to do with it.

Best regards,

------
Fermín

El 14/03/2013 13:07, t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk> escribió:
Hello Fermin, All,

>From the architectural outcomes of the IoT F2F meeting, we have decided to have 2 or 3 implementations of the Configuration Management GE - TID, USURREY and possibly NEC.

Out of concern with having a comprehensible architecture, I am concerned with the naming of the GE. I understand that the main theme that the 3 implementations share is "Discovery". The GE uses NGSI-9, which explicitly handles "discovery". What I don't understand is, why is it called "Configuration Management"? There might be some relevance in the term, but I would of thought something along the lines of "Discovery" or "IoT Discovery" would be more accurate and make more sense to someone unfamiliar with the architecture.

In the F2F meeting I did not get a clear answer, but Fermin, would you be able to briefly explain WHY this GE is called Configuration Management, and whether it is the most accurate term for the GE?...since I will contributing an implementation under this name.

Best regards,
Tarek



________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130314/ad8992da/attachment.html>