Dear All, I agree as well in your position, a link with CEF seems really a relevant opportunity for FIWARE. BR Pier Da: fiware-chapter-leaders-bounces at lists.fi-ware.org [mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org] Per conto di Javier Soriano Inviato: venerdì 5 giugno 2015 09:30 A: De Lama Sanchez, Nuria Cc: fiware-wg-leaders at lists.fi-ware.org; fiware-chapter-leaders at lists.fi-ware.org; fiware-chapter-architects at lists.fi-ware.org Oggetto: Re: [Fiware-chapter-leaders] [Fiware-chapter-architects] IMPORTANT decision regarding incorporation of CEF common building blocks as FIWARE GEs Dear Juanjo, dear all, I completely agree with your position and also share the same view on this as Nuria. Best regards, Javier 2015-06-04 16:26 GMT+02:00 De Lama Sanchez, Nuria <nuria.delama at atos.net<mailto:nuria.delama at atos.net>>: Thanks Juanjo for the summary. I think you have explained that perfectly well. Coming from Atos, a company that has already committed to exploit FIWARE and therefore interested in its sustainability but furthermore on its impact in the “real” world I would like to add my opinion to these explanations. I am in favor of creating that fast track adoption procedure. I think we cannot afford not doing so; this means including for the first time components that come from a very different environment, so that we can test how the process works, but furthermore we are talking about components that are already being used by many Member States, leading to real users. Even though that reason would be sufficient, the fact that the request has been made by the European Commission (but different people to the ones who fund FIWARE) will give credibility to us and will be useful to convince all the other areas that believe that FIWARE is still an “experiment” (like the EIP on SCC). Let me share with you that yesterday I had a discussion with Peter Fatelnig precisely on the collaboration with CEF and data-related initiatives. He told me that this collaboration has already been subject of discussion between Mario Campolargo and the director. A negative answer from FIWARE will be very bad news at that level, with the corresponding implications. Nuria From: Juanjo Hierro [mailto:juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>] Sent: Thursday, June 04, 2015 7:56 AM To: fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>; fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org> Cc: fiware-wg-leaders at lists.fi-ware.org<mailto:fiware-wg-leaders at lists.fi-ware.org>; De Lama Sanchez, Nuria Subject: IMPORTANT decision regarding incorporation of CEF common building blocks as FIWARE GEs Dear all, Starting at the NetFutures event, a number of meetings and discussions have been running with representatives of the Connecting European Facility (CEF): http://ec.europa.eu/digital-agenda/en/connecting-europe-facility CEF is targeted to create and support Digital Service Infrastructures (DSIs) and common building (software) blocks which are intended to be used as technology foundation for digital services that are cross-borders. The CEF programme is considered a rather strategic programme within the EC and one of the pillars over which the new Digital Single Market plan will be established. Currently, the following common building blocks have been created: https://joinup.ec.europa.eu/community/cef/og_page/catalogue-building-blocks Interestingly, people in charge of the CEF programme have found relevant that some of these building blocks be promoted through the FIWARE programme. For this purpose, they have proposed to a) create a sandbox experimental environment on the FIWARE Lab for some of the existing CEF common building blocks, concretely eDelivery and b) propose some of the CEF common building blocks for adoption as FIWARE GEs, concretely eID (digital identity) and eDelivery. Regarding point a), there is no reason to object since this wouldn't mean anything different than creating a Community User account, with the necessary resources booked for creating the sandbox environment, which shouldn't be that high. Therefore, we have given them the instructions, to apply and get the necessary resources. Point b) is the more strategic movement. As mentioned, CEF is a rather strategic programme within the EC. Therefore, their proposal to advertise and promote usage CEF common building blocks through the FIWARE community means quite an important endorsement by the EC recognizing the relevance of FIWARE. Bear in mind that CEF common building blocks are recommended for the development of digital services cross-borders and they are somehow mandatory for these kind of services when implemented by Public Administrations in the Member States. Just this fact means that FIWARE will be in front of all Public Administrators. On the other hand, the fact that CEF common building blocks are implemented as open source and there will be funding for the maintenance and support over time gives response to the requirement about sustainability of FIWARE GEs. Last but not least, after some analysis we have run ourselves at Telefónica, we can state that both the eID and the eDelivery CEF common building blocks are compatible with the FIWARE Reference Architecture and, in fact, complementary to the existing set of FIWARE GEs. In the case of the eID (digital identity) building block, we believe it fits perfectly well with the IdM and Access Control framework but of course a more detailed analysis would require to setup a Task Force within the Security chapter. The EC has asked us for the fast-track adoption of the eDelivery and eID CEF common building blocks as FIWARE GEs and this would be a strategic move I would support and highly recommend. This would mean incorporating them in the catalogue of FIWARE GEs without the need to let them go through the incubation process. Of course, this would mean asking the EC to implement what is needed for the imported CEF common building blocks to comply with common practices, documentation, etc we require from any FIWARE GE. eDelivery would be the first CEF common building block to be imported and it would be imported as part of the Context/Data Management chapter through a dedicated Task Force. eID may come afterwards and it would be imported as part of the Security chapter, subject to the analysis of a Task Force to be created for this purpose. For this purpose, I will ask for a decision in the upcoming FIWARE chapter/wg leaders follow-up confcall that will take place on June 8, 14:30-16:30. FIWARE chapter architects are welcome to attend and provide views from a technical point of view as well as participate in the decision. Eventually, we may run a voting at the meeting, so please define a proxy if you have some position on the matter and cannot attend. In the meantime, I suggest that we exchange comments and initiate the discussion through the lists this mail has been sent through. Best regards, -- Juanjo ______________________________________________________ Coordinator and Chief Architect, FIWARE platform CTO Industrial IoT, Telefónica email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com> twitter: @JuanjoHierro You can follow FIWARE at: website: http://www.fiware.org twitter: @FIWARE facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição 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. _______________________________________________ Fiware-chapter-architects mailing list Fiware-chapter-architects at lists.fi-ware.org<mailto:Fiware-chapter-architects at lists.fi-ware.org> https://lists.fi-ware.org/listinfo/fiware-chapter-architects Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-wg-leaders/attachments/20150605/a530f435/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/fiware-wg-leaders/attachments/20150605/a530f435/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy