[Fiware-technical-committee] Chapter reshuffle input for next TSC

[gilles.privat at orange.com]

Dear Jose Manuel

Your proposal goes into the right direction, I agree with Clara that "Data acquisition" is more appropriate because data becomes Context in the FIWARE sense after it has been aggregated.
"edge computing" is not a proper functional denomination for Cepheus, you could call it "edge CEP" (Proton being the backend CEP), but Cepheus does also include a broker (edge broker if you will), which may create confusion
As a matter of fact the edge/backend distinction is more of an infrastructure issue, orthogonal to  functional distinctions, and I am not sure where this would fit under  your proposal

De : fiware-technical-committee-bounces at lists.fiware.org [mailto:fiware-technical-committee-bounces at lists.fiware.org] De la part de Pezuela, Clara
Envoyé : vendredi 23 juin 2017 16:03
À : José Manuel Cantera; fiware-technical-committee at lists.fiware.org
Objet : Re: [Fiware-technical-committee] Chapter reshuffle input for next TSC

Dear Jose Manuel,

At first glance, two comments from my side:

-          I would call it just Data Acquisition Chapter. For me the context is more related to the Context Brokering chapter.

-          Not sure if the title for Data Acquisition is completely correct having inside also the Edge functionality, as this implies not only storing of data but also computing.

-          I am not sure that Security GEs are well placed in Economy of Data chapter. Maybe they make more sense in Infrastructure chapter due to the fact that is horizontal and affecting to all chapters. What do you think? In this way, any extension of security/privacy in the future could be here.

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> [mailto:fiware-technical-committee-bounces at lists.fiware.org] On Behalf Of José Manuel Cantera
Sent: Friday, June 23, 2017 2:17 PM
To: fiware-technical-committee at lists.fiware.org<mailto:fiware-technical-committee at lists.fiware.org>
Subject: [Fiware-technical-committee] Chapter reshuffle input for next TSC

Dear all,

As per the action I took during the last TSC please find attached a presentation with proposals for Chapter reshuffling in FIWARE. This has taken into account inputs provided during last Summit and other stakeholders.

I will present it during next TSC (Monday 26th), feedback now is welcome as well.

Thanks, best


__________________________________________________________________________________________

You can get more information about our cookies and privacy policies on the following links:
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE

Fiware-technical-committee mailing list
Fiware-technical-committee at lists.fiware.org<mailto:Fiware-technical-committee at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware-technical-committee
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.

_________________________________________________________________________________________________________________________

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,
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, 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/fiware-technical-committee/attachments/20170623/390fc681/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4664 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170623/390fc681/attachment-0001.jpg>