[Fiware-technical-committee] Feedback needed Name of Context Information Management API

Pezuela, Clara clara.pezuela at atos.net
Fri Sep 15 10:12:46 CEST 2017


Dear Jose Manuel,

FIWARE is now quite identified with NGSI, and we are using such word everywhere when we talk about FIWARE. Don’t you think that change of name will be initially confusing? I am not saying I don’t understand the change and that things have to evolve, but I would take care of how we communicate the message and be sure that we are doing well the transition from one word to another word to avoid people got lost or that they perceive a wrong message.

Here my two cents

Best regards

Clara Pezuela
Head of IT Market
Research and Innovation Group
ARI booklet<https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf>
Atos Spain SA
Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net>
+34 675 62 9974

[cid:7206F4B45C675D4FA60A576B4DAED2AE at mail.sis.atos.net]

From: fiware-technical-committee-bounces at lists.fiware.org [mailto:fiware-technical-committee-bounces at lists.fiware.org] On Behalf Of José Manuel Cantera
Sent: Friday, September 15, 2017 8:57 AM
To: fiware-technical-committee at lists.fiware.org
Subject: [Fiware-technical-committee] Feedback needed Name of Context Information Management API

Dear all,

There is a formal proposal on the table (currently supported by ETSI and Orange) of naming the Context Information Management API as C3IM. (Cross-Cutting Context Information Management). Nice thing about this proposal is two-fold:

A/ It keeps the letters C,I,M in the letters but at the same time avoids colliding with “CIM” a very overloaded acronym.
B/ It is pronounced similarly to CIM if you see the “3” as en e ;)
C/ It has the word “Context” in it

So, it seems to meet various requirements. This is an important decision that may affect FIWARE in the future as, if this initiative succeeds, then no longer it will be talked about FIWARE NGSI but about C3IM.

So, please send us your feedback as soon as possible. We can deal with this during next TSC, (don’t know whether we have one next Monday)

Many thanks, Best

[cid:image003.png at 01D32E0B.04859E60]

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170915/b8725043/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 21019 bytes
Desc: image003.png
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170915/b8725043/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 4796 bytes
Desc: image004.jpg
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170915/b8725043/attachment-0001.jpg>


More information about the Fiware-technical-committee mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy