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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130314/e9f097bd/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy