[Fiware-wpl] [Suspected Spam] URGENT Fwd: [Instant Mobility][Fi-Ware] technical virtual meeting

BISSON Pascal pascal.bisson at thalesgroup.com
Wed May 9 10:39:22 CEST 2012


>From my side I couldn't make it but If Daniel can make it I can replace me effectively at this Virtual Meeting

@Daniel please answer from your side.

BR
Pascal

De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro
Envoyé : mardi 8 mai 2012 08:38
À : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [Fiware-wpl] [Suspected Spam] URGENT Fwd: [Instant Mobility][Fi-Ware] technical virtual meeting

Hi all,

  Please find below an email I have received from the InstantMobility project regarding the bilateral session they requested (don't get confused if you see that our colleague Thierry is the sender, because he is also involved in InstantMobility :-).

  I have inserted my potential response between lines.   Despite I disagree with some of the arguments made by the InstantMobility project, I believe it shouldn't be a problem to arrange the requested virtual meeting if we are able to ...

  I NEED the confirmation from representatives of the chapters referred in InstantMobility's email (I2ND, Data/Context Management, IoT, Cloud, Apps, Security) to confirm whether they (or someone else of their chapter) would be available on the proposed date/time for such a virtual meeting.    Note that according to the agenda that InstantMobility suggested, this session would be mostly organized so that InstantMobility will describe us how they plan to use FI-WARE GEs and how they plan to integrate them with other domain-specific GEs they are planning to develop, so that they can collect our feedback.    Therefore, it is not expected that we prepare any presentation for the session (although, of course, we have to be ready to answer doubts, questions).

  BESIDES, if you believe there is any issue with any of my proposed responses (between lines of their message) please let me know.

  Cheers,

-- Juanjo


-------- Original Message --------
Subject:

[Instant Mobility][Fi-Ware] technical virtual meeting

Date:

Mon, 7 May 2012 11:24:48 +0200

From:

thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> <thierry.nagellen at orange.com><mailto:thierry.nagellen at orange.com>

To:

JUAN JOSE HIERRO SUREDA <jhierro at tid.es><mailto:jhierro at tid.es>

CC:

patrick.gatellier at thalesgroup.com<mailto:patrick.gatellier at thalesgroup.com> <patrick.gatellier at thalesgroup.com><mailto:patrick.gatellier at thalesgroup.com>, jean-marie.dautelle at thalesgroup.com<mailto:jean-marie.dautelle at thalesgroup.com> <jean-marie.dautelle at thalesgroup.com><mailto:jean-marie.dautelle at thalesgroup.com>


Dear Juanjo,

We fully agree that educational sessions are useful to better understand what Fi-Ware would deliver especially for the first release. But this is not a common developers' session as Instant Mobility technical team would organize with Fi-Ware.

Our objective is clearly to work on interfaces between Instant Mobility Specific Enablers and FI-Ware Generic Enablers to reach an agreement and to be able to use some of them for our prototype. The objective is not to better understand FI-Ware GE but to provide technical details on interactions between specific enablers and generic enablers and identify functionalities and documented APIs which could bring consistency to ensure Instant Mobility prototype development.

Response: the educational sessions are not just organized around description of the FI-WARE Generic Enablers.   Probably you are aware that each of the days during those educational weeks are splitted in two.  One part devoted actually to description of FI-WARE GEs (despite we intend to make this parts of the sessions rather interactive with the UC projects present).   However, the other part is organized by the UC projects so that they can explain what is the Architecture of the Applications they are designing, how they plan to use the FI-WARE GEs within that Architecture and what domain-specific Enablers they are planning to develop.   That's why we have always insisted that the kind of session you pretend to organize fits clearly within the scope of what we intend to do in the educational weeks (note that "education" happens in the two directions: UC projects will learn more about FI-WARE, but FI-WARE will learn more about UC projects.)

We are deeply convinced that a virtual meeting is not an optimal way to reach this objective, to analyze everything in details, to use schemas and some engineering tools to reach a common view. Virtual meeting will just support information exchange and will require some other meetings to clarify technical topics. So virtual meetings will require more times for both teams, Instant Mobility and FI-Ware, to achieve a common work.

Response: Actually, the optimal way is to have a f2f meeting.   That was why the educational sessions were defined, and we selected two weeks to make it easier to adapt to UC project's calendars.  We also hope that you can agree that we cannot have dedicated and separate meetings for each and every UC project.    We have planned to have dedicated meetings with the UC projects (this is what the second parts of the educational weeks are designed for) but need to concentrate them for the sake of managing resources and budget properly.    The trade-off was to have two weeks so that each UC project can better adapt to the one that fits better within its calendar.    I remind you here that if this still doesn't fit well into the calendar, you would have the ability to justify a fine adjustment of your calendar in order to better synchronize with FI-WARE.    The EC has several times shown they would be willing to accept such kind of fine-tune adjustments in projects' planning.
Nevertheless, regarding FI-Ware time constraints to organize this session, we propose to organize a virtual meeting on Wednesday, May 16th  from 10:00 AM to 1:00 PM (3 hours) to deal with some issues regarding the following chapters of FI-Ware (I2ND, Data & &Context Management, IoT, Cloud, Applications & Services Ecosystem, Security). This meeting will happen before our review and when our technical team is available. If you agree on this date we will provide the agenda ASAP.

Response: Having a virtual meeting with the agenda you initially proposed would certainly add more time to the time allocated to InstantMobility in the educational session week were a session dedicated to the project will be planned, so let's arrange the one at the time you propose.   We'll do our best to have representatives of the mentioned chapters during that confcall.  We assume that the session would be mostly organized so that InstantMobility will describe us how they plan to use FI-WARE GEs and how they plan to integrate them with other domain-specific GEs you are planning to develop, so that you can collect our feedback.   FI-WARE wouldn't need to prepare any specific presentation on FI-WARE's chapters although, of course, we will respond any questions, doubts that may arise during the discussion.


Best regards
Thierry Nagellen
Program Manager Future Internet
Orange Labs Networks & Carriers
905 rue Albert Einstein
06921 Sophia Antipolis Cedex
+33 492 94 52 84
+33 679 85 08 44
New email address: thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>


________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20120509/ec2b5d16/attachment.html>


More information about the Fiware-wpl mailing list

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