[Fiware-iot] Naming of Configuration Management GE

[thierry.nagellen at orange.com]

Dear all,

As I remember, we spoke about Configuration for things to be able to describe which devices and IoT resources compose a Thing. So we configure a Thing with some other entities which could be devices or IoT resources and the composition of a thing could change "dynamically" with mobile devices or things...

Two examples
A room could have its own sensors but if it is a meeting room, when people are in with their phones and maybe with additional devices as a beamer you can change the composition of the thing "room"
Traffic jam: you can include all vehicles as the road infrastructure (especially if you have some sensors embedded in the road) but also all traffic lights if they have a Road Side Unit. Of course each new vehicle which arrives in the traffic jam is a new element of the thing but each vehicle which succeed to exit the traffic jam would also impact the configuration of the thing.

Hope it helps.

BR
Thierry

De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Fermín Galán Márquez
Envoyé : jeudi 14 mars 2013 13:39
À : t.elsaleh at surrey.ac.uk
Cc : fiware-iot at lists.fi-ware.eu
Objet : Re: [Fiware-iot] Naming of Configuration Management GE

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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

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