[Fiware-iot] Naming of Configuration Management GE

[Tobias Jacobs]

Hi Tarek and all,

As said in the F2F meeting I do not have any strong opinion on that, but let me sum up some pros and cons

“ConfMan”
+ If you interpret “configuration” as context availability information (including association information), then “Configuration Management” sounds not too bad.
+ historical reasons
- not clear to new users what “configuration” is

“IoT Discovery”
+ describes what the component is used for
- “Discovery” is only one of the operations, as also the registration operation is important.
- historical reasons

Best
Tobias

From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of t.elsaleh at surrey.ac.uk
Sent: Donnerstag, 14. März 2013 13:07
To: fermin at tid.es
Cc: fiware-iot at lists.fi-ware.eu
Subject: [Fiware-iot] Naming of Configuration Management GE

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̶ 1; would >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

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