From jhierro at tid.es  Thu Mar  1 11:50:22 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Thu, 01 Mar 2012 11:50:22 +0100
Subject: [Fiware-wpa] Fwd: Status of deliverables for month 9
In-Reply-To: <4F4F5435.1060100@tid.es>
References: <4F4F5435.1060100@tid.es>
Message-ID: <4F4F546E.8070006@tid.es>

FYI,

-- Juanjo

-------- Original Message --------
Subject:        Status of deliverables for month 9
Date:   Thu, 01 Mar 2012 11:49:25 +0100
From:   Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>
To:     Arian.ZWEGERS at ec.europa.eu<mailto:Arian.ZWEGERS at ec.europa.eu> <Arian.ZWEGERS at ec.europa.eu><mailto:Arian.ZWEGERS at ec.europa.eu>
CC:     FI-WARE project EC mailbox <INFSO-ICT-285248 at ec.europa.eu><mailto:INFSO-ICT-285248 at ec.europa.eu>, Miguel Carrillo <mcp at tid.es><mailto:mcp at tid.es>, Jose Jimenez <jimenez at tid.es><mailto:jimenez at tid.es>, "jhierro >> \"Juan J. Hierro\"" <jhierro at tid.es><mailto:jhierro at tid.es>


Hi Arian,

  This is to brief you regarding status of the different deliverables for month 9.

 *   D.2.3.a "FI-WARE Architecture"
    *   As commented during our brief meeting in Brussels, we have made public those parts of the deliverable that we consider rather mature.  They will give you a view of the level of detail and concreteness that we have intended to achieve regarding this deliverable.   Once all its contents be available, we believe that UC project Architects will definitively have all the information that is needed to drive definition of the architecture in their projects.   Furthermore, application developers will have a clear understanding about the programming model that will inherent to usage of each FI-WARE GEs.  Actually, descriptions go up to the level of names of interfaces and operations, including high-level description of arguments/behaviour of those operations.
    *   You can find the placeholder of the deliverable (with partial contents already uploaded) at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture_%28PRELIMINARY%29
    *   Rest of contents are on their way and will be delivered on March 6th.   They have already reached the same level of detail as what we have already published, but we are still carrying out some final adjustments in order to make sure that the whole Architecture description looks consistent and there are not gaps.   Only the description of a few GEs are inmature and we are pushing hard the corresponding caretaker.
 *   D.2.4.a "FI-WARE Technical Roadmap"
    *   We want this deliverable to be rather sharp/short and accurate, dealing with the description of what will go in the first release of FI-WARE and what will be planned to the second release and deferred for rest of releases.
    *   We plan to deliver this someday between March 6th and March 9th.
 *   D.10.1.a "FI-WARE Testbed Design"
    *   We consider this rather mature and we are just carrying out a final peer-review of its contents by members of the Cloud and I2ND chapters.
    *   We plan to deliver this on March 6th.   As agreed with you, we will deliver a PU and CO version (the CO version mostly due to the fact we will include info about the developments with Red.es)
 *   D.11.4.a "Standardization Plan and Report"
    *   Going just through last peer-reviews.
    *   We plan to deliver it on March 6th or earlier.
 *   D.1.3.a "Open Call Planning and Report"
    *   Already delivered to you

  Don't hesitate to formulate any question or comment.

  Best regards,


-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________
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-wpa/attachments/20120301/22cad53f/attachment.html>

From jhierro at tid.es  Thu Mar  1 11:58:02 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Thu, 01 Mar 2012 11:58:02 +0100
Subject: [Fiware-wpa] Fwd: FI-WARE Architecture and Technical Roadmap
	deliverables
In-Reply-To: <4F4F5613.9010400@tid.es>
References: <4F4F5613.9010400@tid.es>
Message-ID: <4F4F563A.5090306@tid.es>


  Mail sent to members of the Architecture Board.

  Cheers,

-- Juanjo

-------- Original Message --------
Subject:        FI-WARE Architecture and Technical Roadmap deliverables
Date:   Thu, 01 Mar 2012 11:57:23 +0100
From:   Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>
To:     ab at fi-ppp.eu<mailto:ab at fi-ppp.eu> <ab at fi-ppp.eu><mailto:ab at fi-ppp.eu>


Dear all,

  This is to brief you regarding status of the FI-WARE Architecture and Technical Roadmap deliverables.

 *   D.2.3.a "FI-WARE Architecture"
    *   Yesterday we made public those parts of the deliverable that we consider rather mature.  They will give you a view of the level of detail and concreteness that we have intended to achieve regarding this deliverable.   Once all its contents be available, we believe that UC project Architects will definitively have all the information that is needed to drive definition of the architecture in their projects.   Furthermore, application developers will have a clear understanding about the programming model that will be inherent to the usage of each FI-WARE GEs.  Actually, descriptions go up to the level of names of interfaces and operations, including high-level description of arguments/behaviour of those operations.
    *   You can find the placeholder of the deliverable (with partial contents already uploaded) at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture_%28PRELIMINARY%29
    *   Rest of contents are on their way and will be delivered on March 6th.   They have already reached the same level of detail as what we have already published, but we are still carrying out some final adjustments in order to make sure that the whole Architecture description looks consistent and there are not gaps.   Only the description of a few GEs are still inmature but I hope we will push them to the same level by March 6th.
 *   D.2.4.a "FI-WARE Technical Roadmap"
    *   We want this deliverable to be rather sharp/short and accurate, dealing with the description of what will go in the first release of FI-WARE and what will be planned to the second release and deferred for rest of releases.
    *   We plan to deliver this someday between March 6th and March 9th.

  Besides this, we will produce a "FI-WARE Testbed Design" deliverable by March 6th, part of which will also be made available to you.  I believe it will help you to understand what the FI-WARE project has designed for the FI-WARE Testbed.

  A Standardization Plan will also be produced in the same dates, which I guess may also bring additional valuable information.

  Don't hesitate to formulate any question or comment.

  Best regards,


-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________
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-wpa/attachments/20120301/63830ff3/attachment.html>

From jhierro at tid.es  Thu Mar  1 20:02:43 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Thu, 01 Mar 2012 20:02:43 +0100
Subject: [Fiware-wpa] Guidelines for the FI-WARE Technical Roadmap
	deliverable
Message-ID: <4F4FC7D3.3050104@tid.es>

Hi all,

  Late but hopefully providing a clear template and guidelines to follow, I have setup the space in the FI-WARE Private Wiki to develop the contents of the D.2.4.a deliverable "FI-WARE Technical Roadmap".    You can find the placeholders for your contributions as well as the guidelines to follow at:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4
  Given the fact that this template arrived late, and as already announced to our PO, we should plan to have this deliverable ready for submission by Thursday March 8th, next week.   So you have one week to develop what will not be longer than two pages.   Remember: it's not about producing a long text, but be able to distil a good piece of text.

  I hope that you will find the guidelines quite clear and unambiguous.  Nevertheless, don't hesitate to formulate any question.

  Best regards,


-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________
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-wpa/attachments/20120301/7becb047/attachment.html>

From jhierro at tid.es  Mon Mar  5 18:19:21 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Mon, 05 Mar 2012 18:19:21 +0100
Subject: [Fiware-wpa] IMPORTANT REMARKS regarding the FI-WARE Technical
	Roadmap Deliverable
Message-ID: <4F54F599.5040701@tid.es>

Hi all,

  I guess you are dealing with the writing of the FI-WARE Technical Roadmap deliverable.   I also guess that you would agree that, while the text we are going to produce here doesn't need to be long, it may be highly relevant because we are trying to fix there WHAT WE COMMIT TO DELIVER WHEN.   Therefore, I would like to make a couple of remarks:

 *   Please try to commit for the first release what we believe is strictly a MUST, that is, things we believe that, if not brought, FI-WARE will be useless to the UC projects (or, at least, they will blame of us :-)   Note that we didn't specify what we were going to bring in the first release within the current signed DoW.   Therefore, nobody will be able to make the point that we are not fulfilling the DoW if we do not deliver this or that.   HOWEVER, we will JUDGED with respect to whatever we commit to deliver now: if we promise to deliver something in the first release now and then we fail to deliver it, then the reviewers will have the right to say we failed and reject acceptance of, among others, the FI-WARE Testbed deliverable.

 *   It's not a matter of committing to deliver what we believe we can develop and have ready for integration by end of April based on selected baseline assets.   Don't underestimate the integration efforts on the testbed.  Also don't underestimate integration coordination efforts: just following up that a given GE is properly installed and configured in the Testbed will take its time not only to leaders of tasks in WP10, but also to you as chapters leads and myself ... so, why should we spent time in something that nobody would consider urgent/must ?  It's better that we rather concentrate on integrating the less things possible for the first release and leave integration of things that can wait for later.   We should just focus on what can be a STABLE integrated FI-WARE Release and then make it grow, adding new GEs or features in already integrated GEs.

 *   Despite we talk just about Major Releases in the FI-WARE DoW or in the Technical Roadmap Deliverable, we should plan to be able to upgrade the testbed at our convenience every three months, so that new GE software or upgrades on existing GEs arrives end of July 2012, October 2012, January 2013, Abril 2013, July 2013, ... and then new releases of the testbed are published by end of October 2012, January 2013, Abril 2013, July 2013, October 2013 respectively (we typically book three months for integration testing in the testbed).     So don't hesitate to defer things for the first or the second minor release within the second major release of FI-WARE in your planning.

 *   I propose the following to handle what is planned in the different minor releases of the second major release.   We will publish the Technical Roadmap deliverable just making the distinction on what goes in the first Major Release and what goes in the second Major Release of FI-WARE.    And please be conservative promising things for the First Major Release.   Then, what we will do is ask the UC projects:   Is there anything planned for the Second Major Release you wish to have prioritized ?   Then, based on their feedback, we will prioritize the features they highlight and will try to deliver then a little bit in advance, planning them in the first minor releases of the second major release (e.g., to get it ready in the FI-WARE Testbed either by end of October 2012 or end of January 2013).   Doing so, we are showing we care about their priorities and show some flexibility.

  Best regards,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________
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-wpa/attachments/20120305/5181d4b8/attachment.html>

From jhierro at tid.es  Fri Mar  9 08:18:54 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Fri, 09 Mar 2012 08:18:54 +0100
Subject: [Fiware-wpa] Update on status of deliverables
In-Reply-To: <4F54F599.5040701@tid.es>
References: <4F54F599.5040701@tid.es>
Message-ID: <4F59AEDE.5050302@tid.es>

Hi,

  We are about to close the second round of contributions to the Architecture Description deliverable.   I hope we will close what we will finally publish by EOB today.

  Regarding the Technical Roadmap, I'm reviewing it carefully prior to publication.   I know this will mean a bit of delay with respect to what was planned but this deliverable is quite important because it is where we will declare what we commit to deliver when.    I'm reviewing it at the light of the remarks I forwarded to you at the beginning of this week (attached below for your convenience).

  On the other hand,  we cannot go for publishing it if there is an important piece that is missing (technical roadmap of Apps Chapter).   Therefore, SAP, please you should deliver this URGENTLY.

  Best regards,


-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932



-------- Original Message --------
Subject:        IMPORTANT REMARKS regarding the FI-WARE Technical Roadmap Deliverable
Date:   Mon, 05 Mar 2012 18:19:21 +0100
From:   Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>
To:     fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> <fiware-wpl at lists.fi-ware.eu><mailto:fiware-wpl at lists.fi-ware.eu>, fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> <fiware-wpa at lists.fi-ware.eu><mailto:fiware-wpa at lists.fi-ware.eu>


Hi all,

  I guess you are dealing with the writing of the FI-WARE Technical Roadmap deliverable.   I also guess that you would agree that, while the text we are going to produce here doesn't need to be long, it may be highly relevant because we are trying to fix there WHAT WE COMMIT TO DELIVER WHEN.   Therefore, I would like to make a couple of remarks:

 *   Please try to commit for the first release what we believe is strictly a MUST, that is, things we believe that, if not brought, FI-WARE will be useless to the UC projects (or, at least, they will blame of us :-)   Note that we didn't specify what we were going to bring in the first release within the current signed DoW.   Therefore, nobody will be able to make the point that we are not fulfilling the DoW if we do not deliver this or that.   HOWEVER, we will JUDGED with respect to whatever we commit to deliver now: if we promise to deliver something in the first release now and then we fail to deliver it, then the reviewers will have the right to say we failed and reject acceptance of, among others, the FI-WARE Testbed deliverable.

 *   It's not a matter of committing to deliver what we believe we can develop and have ready for integration by end of April based on selected baseline assets.   Don't underestimate the integration efforts on the testbed.  Also don't underestimate integration coordination efforts: just following up that a given GE is properly installed and configured in the Testbed will take its time not only to leaders of tasks in WP10, but also to you as chapters leads and myself ... so, why should we spent time in something that nobody would consider urgent/must ?  It's better that we rather concentrate on integrating the less things possible for the first release and leave integration of things that can wait for later.   We should just focus on what can be a STABLE integrated FI-WARE Release and then make it grow, adding new GEs or features in already integrated GEs.

 *   Despite we talk just about Major Releases in the FI-WARE DoW or in the Technical Roadmap Deliverable, we should plan to be able to upgrade the testbed at our convenience every three months, so that new GE software or upgrades on existing GEs arrives end of July 2012, October 2012, January 2013, Abril 2013, July 2013, ... and then new releases of the testbed are published by end of October 2012, January 2013, Abril 2013, July 2013, October 2013 respectively (we typically book three months for integration testing in the testbed).     So don't hesitate to defer things for the first or the second minor release within the second major release of FI-WARE in your planning.

 *   I propose the following to handle what is planned in the different minor releases of the second major release.   We will publish the Technical Roadmap deliverable just making the distinction on what goes in the first Major Release and what goes in the second Major Release of FI-WARE.    And please be conservative promising things for the First Major Release.   Then, what we will do is ask the UC projects:   Is there anything planned for the Second Major Release you wish to have prioritized ?   Then, based on their feedback, we will prioritize the features they highlight and will try to deliver then a little bit in advance, planning them in the first minor releases of the second major release (e.g., to get it ready in the FI-WARE Testbed either by end of October 2012 or end of January 2013).   Doing so, we are showing we care about their priorities and show some flexibility.

  Best regards,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________
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-wpa/attachments/20120309/5aa9e3a3/attachment.html>

From stefano.depanfilis at eng.it  Fri Mar  9 13:34:12 2012
From: stefano.depanfilis at eng.it (stefano de panfilis)
Date: Fri, 9 Mar 2012 13:34:12 +0100
Subject: [Fiware-wpa] [Fiware-wpl] Update on status of deliverables
In-Reply-To: <4F59AEDE.5050302@tid.es>
References: <4F54F599.5040701@tid.es>
	<4F59AEDE.5050302@tid.es>
Message-ID: <CAAtfhW_m7v5Vz+Kun+erDUwwpiMZuMsoozKD5Wk50v0yDOY6-w@mail.gmail.com>

dear juanjo,

please consider that d01.1.a just released also contains an implementation
roadmap and both must be alligned.
happy to revise d10.1.a if you find major discrepancies.

let me know how can i help.

ciao,
stefano

2012/3/9 Juanjo Hierro <jhierro at tid.es>

>  Hi,
>
>   We are about to close the second round of contributions to the
> Architecture Description deliverable.   I hope we will close what we will
> finally publish by EOB today.
>
>   Regarding the Technical Roadmap, I'm reviewing it carefully prior to
> publication.   I know this will mean a bit of delay with respect to what
> was planned but this deliverable is quite important because it is where we
> will declare what we commit to deliver when.    I'm reviewing it at the
> light of the remarks I forwarded to you at the beginning of this week
> (attached below for your convenience).
>
>   On the other hand,  we cannot go for publishing it if there is an
> important piece that is missing (technical roadmap of Apps Chapter).
> Therefore, SAP, please you should deliver this URGENTLY.
>
>   Best regards,
>
> -- Juanjo
>
> -------------
> Product Development and Innovation (PDI) - Telefonica Digital
> website: www.tid.es
> email: jhierro at tid.es
> twitter: twitter.com/JuanjoHierro
>
> FI-WARE (European Future Internet Core Platform) Chief Architect
>
> You can follow FI-WARE at:
>   website:  http://www.fi-ware.eu
>   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
>   twitter:  http://twitter.com/FIware
>   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
>
>
>
> -------- Original Message --------  Subject: IMPORTANT REMARKS regarding
> the FI-WARE Technical Roadmap Deliverable  Date: Mon, 05 Mar 2012
> 18:19:21 +0100  From: Juanjo Hierro <jhierro at tid.es> <jhierro at tid.es>  To:
> fiware-wpl at lists.fi-ware.eu <fiware-wpl at lists.fi-ware.eu><fiware-wpl at lists.fi-ware.eu>,
> fiware-wpa at lists.fi-ware.eu <fiware-wpa at lists.fi-ware.eu><fiware-wpa at lists.fi-ware.eu>
>
> Hi all,
>
>   I guess you are dealing with the writing of the FI-WARE Technical
> Roadmap deliverable.   I also guess that you would agree that, while the
> text we are going to produce here doesn't need to be long, it may be highly
> relevant because we are trying to fix there WHAT WE COMMIT TO DELIVER
> WHEN.   Therefore, I would like to make a couple of remarks:
>
>    - Please try to commit for the first release what we believe is
>    strictly a MUST, that is, things we believe that, if not brought, FI-WARE
>    will be useless to the UC projects (or, at least, they will blame of us
>    :-)   Note that we didn't specify what we were going to bring in the first
>    release within the current signed DoW.   Therefore, nobody will be able to
>    make the point that we are not fulfilling the DoW if we do not deliver this
>    or that.   HOWEVER, we will JUDGED with respect to whatever we commit to
>    deliver now: if we promise to deliver something in the first release now
>    and then we fail to deliver it, then the reviewers will have the right to
>    say we failed and reject acceptance of, among others, the FI-WARE Testbed
>    deliverable.
>
>
>    - It's not a matter of committing to deliver what we believe we can
>    develop and have ready for integration by end of April based on selected
>    baseline assets.   Don't underestimate the integration efforts on the
>    testbed.  Also don't underestimate integration coordination efforts: just
>    following up that a given GE is properly installed and configured in the
>    Testbed will take its time not only to leaders of tasks in WP10, but also
>    to you as chapters leads and myself ... so, why should we spent time in
>    something that nobody would consider urgent/must ?  It's better that we
>    rather concentrate on integrating the less things possible for the first
>    release and leave integration of things that can wait for later.   We
>    should just focus on what can be a STABLE integrated FI-WARE Release and
>    then make it grow, adding new GEs or features in already integrated GEs.
>
>
>    - Despite we talk just about Major Releases in the FI-WARE DoW or in
>    the Technical Roadmap Deliverable, we should plan to be able to upgrade the
>    testbed at our convenience every three months, so that new GE software or
>    upgrades on existing GEs arrives end of July 2012, October 2012, January
>    2013, Abril 2013, July 2013, ... and then new releases of the testbed are
>    published by end of October 2012, January 2013, Abril 2013, July 2013,
>    October 2013 respectively (we typically book three months for integration
>    testing in the testbed).     So don't hesitate to defer things for the
>    first or the second minor release within the second major release of
>    FI-WARE in your planning.
>
>
>    - I propose the following to handle what is planned in the different
>    minor releases of the second major release.   We will publish the Technical
>    Roadmap deliverable just making the distinction on what goes in the first
>    Major Release and what goes in the second Major Release of FI-WARE.    And
>    please be conservative promising things for the First Major Release.
>    Then, what we will do is ask the UC projects:   Is there anything planned
>    for the Second Major Release you wish to have prioritized ?   Then, based
>    on their feedback, we will prioritize the features they highlight and will
>    try to deliver then a little bit in advance, planning them in the first
>    minor releases of the second major release (e.g., to get it ready in the
>    FI-WARE Testbed either by end of October 2012 or end of January 2013).
>    Doing so, we are showing we care about their priorities and show some
>    flexibility.
>
>   Best regards,
>
> -- Juanjo
>
> -------------
> Product Development and Innovation (PDI) - Telefonica Digital
> website: www.tid.es
> email: jhierro at tid.es
> twitter: twitter.com/JuanjoHierro
>
> FI-WARE (European Future Internet Core Platform) Chief Architect
>
> You can follow FI-WARE at:
>   website:  http://www.fi-ware.eu
>   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
>   twitter:  http://twitter.com/FIware
>   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
>
>
> ------------------------------
> 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
>
> _______________________________________________
> Fiware-wpl mailing list
> Fiware-wpl at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware-wpl
>
>


-- 
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy

tel (direct): +39-068307-4295
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120309/f03093ab/attachment.html>

From jhierro at tid.es  Fri Mar  9 16:38:59 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Fri, 09 Mar 2012 16:38:59 +0100
Subject: [Fiware-wpa] Fwd: Submission of deliverable D.10.1.a FI-WARE
	Testbed Design
In-Reply-To: <4F563A4A.1060600@tid.es>
References: <4F563A4A.1060600@tid.es>
Message-ID: <4F5A2413.9010009@tid.es>


  FYI,

-- Juanjo

-------- Original Message --------
Subject:        Submission of deliverable D.10.1.a FI-WARE Testbed Design
Date:   Tue, 6 Mar 2012 17:24:42 +0100
From:   MIGUEL CARRILLO PACHECO <mcp at tid.es><mailto:mcp at tid.es>
To:     Arian.ZWEGERS at ec.europa.eu<mailto:Arian.ZWEGERS at ec.europa.eu> <Arian.ZWEGERS at ec.europa.eu><mailto:Arian.ZWEGERS at ec.europa.eu>, INFSO-ICT-285248 at ec.europa.eu<mailto:INFSO-ICT-285248 at ec.europa.eu> <INFSO-ICT-285248 at ec.europa.eu><mailto:INFSO-ICT-285248 at ec.europa.eu>
CC:     JOSE JIMENEZ DELGADO <jimenez at tid.es><mailto:jimenez at tid.es>, JUAN JOSE HIERRO SUREDA <jhierro at tid.es><mailto:jhierro at tid.es>, Stefano De Panfilis <stefano.depanfilis at eng.it><mailto:stefano.depanfilis at eng.it>, Paolo Zampognaro <paolo.zampognaro at eng.it><mailto:paolo.zampognaro at eng.it>



Dear Arian,

This is the official submission of deliverable D.10.1.a "FI-WARE Testbed Design" of the FI-WARE project.

We would also like to share some information that is sensitive but very relevant. The official deliverable (public) is complemented with another one that is restricted (dissemination level PP), that basically has an extra section.

Best regards,

Miguel

--
----------------------------------------------------------------------
      _/          _/_/                     Miguel Carrillo Pacheco
     _/   _/     _/  _/   Telef?nica       Distrito Telef?nica
    _/ _/_/_/   _/   _/   Investigaci?n y  Edifico Oeste 1, Planta 9
   _/   _/     _/  _/     Desarrollo       Ronda de la Comunicaci?n S/N
  _/          _/_/                         28050 Madrid (Spain)
                                           Tel:  (+34) 91 483 26 77

                                           e-mail: mcp at tid.es<mailto:mcp at tid.es>

Follow FI-WARE on the net

        Website:  http://www.fi-ware.eu
        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
        Twitter:  http://twitter.com/Fiware
        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------




________________________________
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-wpa/attachments/20120309/1b3d471b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D10_1a FI-WARE Testbed Design_PU.pdf
Type: application/pdf
Size: 2105057 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120309/1b3d471b/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D10_1a FI-WARE Testbed Design_PP.pdf
Type: application/pdf
Size: 2138995 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120309/1b3d471b/attachment-0001.pdf>

From jhierro at tid.es  Mon Mar 12 08:53:15 2012
From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA)
Date: Mon, 12 Mar 2012 08:53:15 +0100
Subject: [Fiware-wpa] REMINDER: Joint FI-WARE WPLs/WPAs follow-up confcall
Message-ID: <CB8369FB.4B84%jhierro@tid.es>


We'll use powwownow.   PIN: 050662.   Local dial-in phone numbers at:

http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf

________________________________
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-wpa/attachments/20120312/0ce1fb10/attachment.html>

From jhierro at tid.es  Mon Mar 12 08:53:45 2012
From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA)
Date: Mon, 12 Mar 2012 08:53:45 +0100
Subject: [Fiware-wpa] Joint FI-WARE WPLs/WPAs follow-up confcall
Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A8F@EXCLU2K7.hi.inet>

When: Monday, March 12, 2012 11:00 AM-12:30 PM. Central European Standard Time

*~*~*~*~*~*~*~*~*~*

<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><div>We'll use powwownow. &nbsp; PIN: 050662. &nbsp; Local dial-in phone numbers at:</div><div><br></div><div>http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf</div></div></body></html>

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 --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 3776 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120312/b4438ac3/attachment.ics>

From jhierro at tid.es  Mon Mar 12 10:45:47 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Mon, 12 Mar 2012 10:45:47 +0100
Subject: [Fiware-wpa] Webex details and shared minutes
In-Reply-To: <237315909.1331543365171.JavaMail.nobody@jsj2wl017.webex.com>
References: <237315909.1331543365171.JavaMail.nobody@jsj2wl017.webex.com>
Message-ID: <4F5DC5CB.6060907@tid.es>

Hi all,

  As in recent follow-up confcalls, we will setup a Webex and share the minutes.   Webex details are in the attached email.  You will find the shared google document with the minutes at:

https://docs.google.com/document/d/1Jn0AiOfoAQlULcihSvE3FEkruK-p496CXcwW7ppEti4/edit

  Talk to you in few minutes.   Cheers,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932



-------- Original Message --------
Subject:        Meeting invitation: FI-WARE Joint WPLs/WPAs follow-up confcall
Date:   Mon, 12 Mar 2012 10:09:25 +0100
From:   Gestor i-Reunion webex6100 <messenger at webex.com><mailto:messenger at webex.com>
Reply-To:       Webex6100 at tid.es<mailto:Webex6100 at tid.es> <Webex6100 at tid.es><mailto:Webex6100 at tid.es>
To:     JUAN JOSE HIERRO SUREDA <jhierro at tid.es><mailto:jhierro at tid.es>


Hello ,

Gestor i-Reunion webex6100 invites you to attend this online meeting.

Topic: FI-WARE Joint WPLs/WPAs follow-up confcall
Date: Monday, March 12, 2012
Time: 11:00 am, Europe Time (Paris, GMT+01:00)
Meeting Number: 967 440 874
Meeting Password: 1234abcD


-------------------------------------------------------
To join the online meeting (Now from iPhones too!)
-------------------------------------------------------
1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=191624752&UID=1275261912&PW=NYjIzZjgxZTA2&RT=MiMyMw%3D%3D
2. Enter your name and email address.
3. Enter the meeting password: 1234abcD
4. Click "Join Now".

To view in other time zones or languages, please click the link:
https://telefonica.webex.com/telefonica-en/j.php?ED=191624752&UID=1275261912&PW=NYjIzZjgxZTA2&ORT=MiMyMw%3D%3D


-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://telefonica.webex.com/telefonica-en/mc
2. On the left navigation bar, click "Support".

You can contact me at:
Webex6100 at tid.es<mailto:Webex6100 at tid.es>


To add this meeting to your calendar program (for example Microsoft Outlook), click this link:
https://telefonica.webex.com/telefonica-en/j.php?ED=191624752&UID=1275261912&ICS=MI&LD=1&RD=2&ST=1&SHA2=luPQQMmVkj184ib36N4LTRxX2JSNZFdAslivi65jCd8=&RT=MiMyMw%3D%3D

The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com



IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session.


________________________________
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-wpa/attachments/20120312/f81446d2/attachment.html>

From jhierro at tid.es  Wed Mar 14 08:22:10 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Wed, 14 Mar 2012 08:22:10 +0100
Subject: [Fiware-wpa] Detailed comments on Technical Roadmap deliverable
Message-ID: <4F604722.1020703@tid.es>

Hi,

  Here you have a list of issues/doubts that have came to my mind while reading the Technical Roadmap of each chapter.   I believe it would be worth solving them prior final publication.

  I'm still working on the comments for the IoT and Data/Context Management Chapter.   I couldn't bring comments on the I2ND and Development Support Tools chapters because changes recently agreed hadn't been incorporated yet and I prefer to make comments on a revised version.

Apps Chapter:

 *   First Release:
    *   You say ... "This is handled in conjunction with the 1st Open Call" ... But ... What is handled in conjunction with the 1st Open Call ?  The sentence that is below or the list of functions enumerated above the sentence ?   It was unclear.   Using a semicolon, it would be more clear.
    *   I will assume that what is handled in conjunction with the 1st Open Call ...  However, it is not that clear what do we intend to provide when we say that we will support the "Ability to expose a REST Service through SOAP protocol in order to enable a Compositor Editor supporting SOAP to compose REST Services".   My assumption is that you aim to rely on the ability to implement a service interface and describe it in a technology/protocol-neutral way using the IDL that the middleware to be developed as a result of the 1st Open Call will support.   Operations in the service interface will then be accessible through several protocols (i.e., REST, SOAP, IIOP, ...).    Is my assumption correct ?   If so, I would suggest explain it a bit better ... (I hope that the above description may help)
    *   It seems like there is some missing indentation in the last bullet list (the one after "These features will be ...")  ... I mean when you say "Basic interaction of the Composition Engine with the Marketplace regarding" ... shouldn't the two following items indented ?  how many of the following items ?
    *   I guess that when you say "Ability of the Composition Environment to read/write service description into the Repository using USDL" it would be more accurate to say "Ability of the Composition Environment to read/write service descriptions from/into the Repository that are described using USDL"
    *   It is not very clear what you mean when you say "Use of the Mediator Proxy generator through a Web Interface to generate a proxy to mediate SOAP to REST" ... what kind of Web interface are we talking about ?   I would suggest saying instead "ability to compose both SOAP and REST services using the capacities of a Mediator Proxy generator" but ... anything more clear
    *   We shouldn't refer to companies or products.  We are delivering what are going to be Open Specifications of FI-WARE GEs and a reference implementation of those specifications.  Therefore, it doesn't make sense to talk about the "DT Mashup Platform".
    *   What do we mean by "mediated SOAP services" ?   mediated through what ?   from where ?  to what ?
    *   typo: "die GEs" ... I guess should be "these GEs"
    *   Saying "The general integration between die GEs will not yet provided for the first release and will become a focus of the second release" may confuse a bit because there is some degree of integration between some of the GEs that will be achieved in the first release.   Please elaborate more on what will NOT be integrated.
 *   Second Release:
    *   Elaborate a bit on what new functions will come as a result of a closer integration of the store and the marketplace.  Add some "(e.g., xxx)" may help
    *   I don't understand what does "Adaptation of the service language USDL to the integrated technical setting" exactly means.
    *   You should elaborate (at least giving some examples) of how you intend to integrate Identity Management.
    *   You should elaborate (at least giving some examples) of how you intend to integrate aspects related to the Internet of Things
 *   Future releases:
    *   No particular comment

Cloud Chapter:

 *   General comments:
    *   Drop-out the text in bold coming from the guidelines

 *   First Release:
    *   I would shift the reference to the cloud portal to the beginning.  For instance, I would rewrite the first bullet as follows:
       *   Management of Individual virtual machines and associated resources in a datacenter through a set of standardized APIs as well as a Cloud Portal:
          *   Ability to automate the provision, as well as management of the lifecycle, of virtual machines and the associated compute, storage and network resources
          *   Ability to define and maintain a library of pre-configured virtual machine images that can be used for the automated provisioning of new virtual machines
    *   Is the concept of  "enhanced hardware-supported trust" described in the Architecture Description ?  If so, try to have a hyperlink to the proper section from here
    *   Same for the concept of "composite multi-VM services"
    *   Weren't we going to distinguish between what will be delivered at the beginning and at the end of 3Q2012 ?
 *   Second Release:
    *   We talk about "network bandwith" management in the first bullet ... do we mean it referred only to internal datacenter connectivity (i.e., VLANs) ?   Managing it end to end (i.e., from application clients to applications running on the backend hosted in a Cloud datacenter) would require using interfaces defined in the I2ND chapter ... and I wonder whether we are postponing management of those interfaces to future releases (this would be what makes sense IMHO).   We need to clarify this.
    *   While we focus on simple VMs allocation in the first release ... what about allocation of VLANs and virtual disk storage shared by several VMs ?   Wouldn't we support this level of allocation in the second release ?
    *   We talk about "federation" but we don't talk about cloudbursting - hybrids clouds.   If you consider them special cases of "federation", please explain that.
    *   What do we mean by "Image management for cloud edge appliances" ?
 *   Future Releases:
    *   I would reword the sentence saying "Exposing more software defined networking capabilities of the Interface to Connected Devices chapter through Cloud Hosting service interfaces" by something like "Ability to elastically manage allocation of network resources outside datacenter boundaries along the whole communication path between the end user and the applications backends, using interfaces produced in the I2ND chapter"

I2ND Chapter:


 *   NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR LAST DISCUSSION !!

Security Chapter:

 *   General comments:
    *   For the shake of consistency across all chapter contributions, I wouldn't number the list of features, just use bullets.

 *   First Release:
    *   Explain what IDM stands for the first time the acronym appears (Identity Management)
    *   I understand that the web interface that the IDM GE will expose will be a Restful interface ...  therefore I would move the reference to REST API to the first bullet of the General Remarks subsection, which I would simply rewrite as follows:
       *   The IDM GE will provide a common Restful API to clients
    *   You should postpone optional Security GEs to the second release as per discussion during our last joint WPLs/WPAs follow-up confcall.   Only if UC projects requires any of them explictly, we will evaluate how they can be delivered in upgrades of the Testbed after delivery of the first release.
    *   Honestly speaking, I believe that it would be better if we move the Context-based Security and Compliance GE to the second release because my understanding is that it has to be closely integrated within the architecture of the Apps Chapter ... Has such integration been carefully designed ?  What are we going to be able to provide in a first release if not ?   I guess it makes sense to address such integration for the second release, once the Architecture of the Apps chapter is more consolidated.   Unless a UC projects requires this, let's commit this for the second release.
    *   "offered for Release 1" to be dropped in the last bullet (point 5)

 *   Second Release:
    *   "offered for Release 2" should be dropped in many of the points (just redundant, since the bullets are within a section titled "Second Release")
    *   Integration with Data/Context Management GEs should be addressed in the Data Handling GE for the Second Release (include an additional point on the matter)

 *   Future Releases:
    *   For the sake of consistency across the different points, I would re-title the first bullet as "Security Monitoring GE functionalities"
    *   Merge the point on Ovalyzer with the corresponding sub-bullet, making it just one bullet


Development Support Tools Chapter:

 *   NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR LAST DISCUSSION (i.e., moving testing tools to second release) !!



-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________
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-wpa/attachments/20120314/1b338693/attachment.html>

From pierangelo.garino at telecomitalia.it  Wed Mar 14 08:52:14 2012
From: pierangelo.garino at telecomitalia.it (Garino Pierangelo)
Date: Wed, 14 Mar 2012 08:52:14 +0100
Subject: [Fiware-wpa] R: [Fiware-wpl] Detailed comments on Technical Roadmap
	deliverable
In-Reply-To: <4F604722.1020703@tid.es>
References: <4F604722.1020703@tid.es>
Message-ID: <FAD9D9EABF4BFE4695279BA86C05F1A92C46CC0CBB@GRFMBX707BA020.griffon.local>

Hi Juanjo,

I2ND page is updated according to the changes agreed except for CDI second and future releases. These will be completed today.

BR
Pier



Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro
Inviato: mercoled? 14 marzo 2012 08:22
A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Oggetto: [Fiware-wpl] Detailed comments on Technical Roadmap deliverable

Hi,

  Here you have a list of issues/doubts that have came to my mind while reading the Technical Roadmap of each chapter.   I believe it would be worth solving them prior final publication.

  I'm still working on the comments for the IoT and Data/Context Management Chapter.   I couldn't bring comments on the I2ND and Development Support Tools chapters because changes recently agreed hadn't been incorporated yet and I prefer to make comments on a revised version.

Apps Chapter:

 *   First Release:
    *   You say ... "This is handled in conjunction with the 1st Open Call" ... But ... What is handled in conjunction with the 1st Open Call ?  The sentence that is below or the list of functions enumerated above the sentence ?   It was unclear.   Using a semicolon, it would be more clear.
    *   I will assume that what is handled in conjunction with the 1st Open Call ...  However, it is not that clear what do we intend to provide when we say that we will support the "Ability to expose a REST Service through SOAP protocol in order to enable a Compositor Editor supporting SOAP to compose REST Services".   My assumption is that you aim to rely on the ability to implement a service interface and describe it in a technology/protocol-neutral way using the IDL that the middleware to be developed as a result of the 1st Open Call will support.   Operations in the service interface will then be accessible through several protocols (i.e., REST, SOAP, IIOP, ...).    Is my assumption correct ?   If so, I would suggest explain it a bit better ... (I hope that the above description may help)
    *   It seems like there is some missing indentation in the last bullet list (the one after "These features will be ...")  ... I mean when you say "Basic interaction of the Composition Engine with the Marketplace regarding" ... shouldn't the two following items indented ?  how many of the following items ?
    *   I guess that when you say "Ability of the Composition Environment to read/write service description into the Repository using USDL" it would be more accurate to say "Ability of the Composition Environment to read/write service descriptions from/into the Repository that are described using USDL"
    *   It is not very clear what you mean when you say "Use of the Mediator Proxy generator through a Web Interface to generate a proxy to mediate SOAP to REST" ... what kind of Web interface are we talking about ?   I would suggest saying instead "ability to compose both SOAP and REST services using the capacities of a Mediator Proxy generator" but ... anything more clear
    *   We shouldn't refer to companies or products.  We are delivering what are going to be Open Specifications of FI-WARE GEs and a reference implementation of those specifications.  Therefore, it doesn't make sense to talk about the "DT Mashup Platform".
    *   What do we mean by "mediated SOAP services" ?   mediated through what ?   from where ?  to what ?
    *   typo: "die GEs" ... I guess should be "these GEs"
    *   Saying "The general integration between die GEs will not yet provided for the first release and will become a focus of the second release" may confuse a bit because there is some degree of integration between some of the GEs that will be achieved in the first release.   Please elaborate more on what will NOT be integrated.
 *   Second Release:
    *   Elaborate a bit on what new functions will come as a result of a closer integration of the store and the marketplace.  Add some "(e.g., xxx)" may help
    *   I don't understand what does "Adaptation of the service language USDL to the integrated technical setting" exactly means.
    *   You should elaborate (at least giving some examples) of how you intend to integrate Identity Management.
    *   You should elaborate (at least giving some examples) of how you intend to integrate aspects related to the Internet of Things
 *   Future releases:
    *   No particular comment

Cloud Chapter:

 *   General comments:
    *   Drop-out the text in bold coming from the guidelines

 *   First Release:
    *   I would shift the reference to the cloud portal to the beginning.  For instance, I would rewrite the first bullet as follows:
       *   Management of Individual virtual machines and associated resources in a datacenter through a set of standardized APIs as well as a Cloud Portal:
          *   Ability to automate the provision, as well as management of the lifecycle, of virtual machines and the associated compute, storage and network resources
          *   Ability to define and maintain a library of pre-configured virtual machine images that can be used for the automated provisioning of new virtual machines
    *   Is the concept of  "enhanced hardware-supported trust" described in the Architecture Description ?  If so, try to have a hyperlink to the proper section from here
    *   Same for the concept of "composite multi-VM services"
    *   Weren't we going to distinguish between what will be delivered at the beginning and at the end of 3Q2012 ?
 *   Second Release:
    *   We talk about "network bandwith" management in the first bullet ... do we mean it referred only to internal datacenter connectivity (i.e., VLANs) ?   Managing it end to end (i.e., from application clients to applications running on the backend hosted in a Cloud datacenter) would require using interfaces defined in the I2ND chapter ... and I wonder whether we are postponing management of those interfaces to future releases (this would be what makes sense IMHO).   We need to clarify this.
    *   While we focus on simple VMs allocation in the first release ... what about allocation of VLANs and virtual disk storage shared by several VMs ?   Wouldn't we support this level of allocation in the second release ?
    *   We talk about "federation" but we don't talk about cloudbursting - hybrids clouds.   If you consider them special cases of "federation", please explain that.
    *   What do we mean by "Image management for cloud edge appliances" ?
 *   Future Releases:
    *   I would reword the sentence saying "Exposing more software defined networking capabilities of the Interface to Connected Devices chapter through Cloud Hosting service interfaces" by something like "Ability to elastically manage allocation of network resources outside datacenter boundaries along the whole communication path between the end user and the applications backends, using interfaces produced in the I2ND chapter"

I2ND Chapter:

 *   NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR LAST DISCUSSION !!

Security Chapter:

 *   General comments:
    *   For the shake of consistency across all chapter contributions, I wouldn't number the list of features, just use bullets.

 *   First Release:
    *   Explain what IDM stands for the first time the acronym appears (Identity Management)
    *   I understand that the web interface that the IDM GE will expose will be a Restful interface ...  therefore I would move the reference to REST API to the first bullet of the General Remarks subsection, which I would simply rewrite as follows:
       *   The IDM GE will provide a common Restful API to clients
    *   You should postpone optional Security GEs to the second release as per discussion during our last joint WPLs/WPAs follow-up confcall.   Only if UC projects requires any of them explictly, we will evaluate how they can be delivered in upgrades of the Testbed after delivery of the first release.
    *   Honestly speaking, I believe that it would be better if we move the Context-based Security and Compliance GE to the second release because my understanding is that it has to be closely integrated within the architecture of the Apps Chapter ... Has such integration been carefully designed ?  What are we going to be able to provide in a first release if not ?   I guess it makes sense to address such integration for the second release, once the Architecture of the Apps chapter is more consolidated.   Unless a UC projects requires this, let's commit this for the second release.
    *   "offered for Release 1" to be dropped in the last bullet (point 5)

 *   Second Release:
    *   "offered for Release 2" should be dropped in many of the points (just redundant, since the bullets are within a section titled "Second Release")
    *   Integration with Data/Context Management GEs should be addressed in the Data Handling GE for the Second Release (include an additional point on the matter)

 *   Future Releases:
    *   For the sake of consistency across the different points, I would re-title the first bullet as "Security Monitoring GE functionalities"
    *   Merge the point on Ovalyzer with the corresponding sub-bullet, making it just one bullet



Development Support Tools Chapter:

 *   NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR LAST DISCUSSION (i.e., moving testing tools to second release) !!





-- Juanjo



-------------

Product Development and Innovation (PDI) - Telefonica Digital

website: www.tid.es<http://www.tid.es>

email: jhierro at tid.es<mailto:jhierro at tid.es>

twitter: twitter.com/JuanjoHierro



FI-WARE (European Future Internet Core Platform) Chief Architect



You can follow FI-WARE at:

  website:  http://www.fi-ware.eu

  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

  twitter:  http://twitter.com/FIware

  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932

________________________________
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
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.

[cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120314/ce94b3e5/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-wpa/attachments/20120314/ce94b3e5/attachment.jpg>

From matteo.melideo at eng.it  Wed Mar 14 09:28:28 2012
From: matteo.melideo at eng.it (Matteo Melideo)
Date: Wed, 14 Mar 2012 09:28:28 +0100
Subject: [Fiware-wpa] [Fiware-wpl] Detailed comments on Technical
	Roadmap deliverable
In-Reply-To: <4F604722.1020703@tid.es>
References: <4F604722.1020703@tid.es>
Message-ID: <4F6056AC.1020904@eng.it>

Juanjo Hi,
why in capital letters the reminder to Wp9? Are there any problems?
I was honestly waiting for your inputs. Reading at the minutes the only 
point I can see is: "Development tools: Juanjo will check what is there 
and make a proposal on what items to be postponed for second release of 
FI-WARE"

Said that sorry if I missed this agreement!

M.


Il 14/03/2012 08:22, Juanjo Hierro ha scritto:
> Hi,
>
>   Here you have a list of issues/doubts that have came to my mind 
> while reading the Technical Roadmap of each chapter.   I believe it 
> would be worth solving them prior final publication.
>
>   I'm still working on the comments for the IoT and Data/Context 
> Management Chapter.   I couldn't bring comments on the I2ND and 
> Development Support Tools chapters because changes recently agreed 
> hadn't been incorporated yet and I prefer to make comments on a 
> revised version.
>
> *Apps Chapter:*
>
>   * First Release:
>       o You say ... "This is handled in conjunction with the 1st Open
>         Call" ... But ... What is handled in conjunction with the 1st
>         Open Call ?  The sentence that is below or the list of
>         functions enumerated above the sentence ?   It was unclear.  
>         Using a semicolon, it would be more clear.
>       o I will assume that what is handled in conjunction with the 1st
>         Open Call ...  However, it is not that clear what do we intend
>         to provide when we say that we will support the "Ability to
>         expose a REST Service through SOAP protocol in order to enable
>         a Compositor Editor supporting SOAP to compose REST
>         Services".   My assumption is that you aim to rely on the
>         ability to implement a service interface and describe it in a
>         technology/protocol-neutral way using the IDL that the
>         middleware to be developed as a result of the 1st Open Call
>         will support.   Operations in the service interface will then
>         be accessible through several protocols (i.e., REST, SOAP,
>         IIOP, ...).    Is my assumption correct ?   If so, I would
>         suggest explain it a bit better ... (I hope that the above
>         description may help)
>       o It seems like there is some missing indentation in the last
>         bullet list (the one after "These features will be ...")  ...
>         I mean when you say "Basic interaction of the Composition
>         Engine with the Marketplace regarding" ... shouldn't the two
>         following items indented ?  how many of the following items ?
>       o I guess that when you say "Ability of the Composition
>         Environment to read/write service description into the
>         Repository using USDL" it would be more accurate to say
>         "Ability of the Composition Environment to read/write service
>         descriptions from/into the Repository that are described using
>         USDL"
>       o It is not very clear what you mean when you say "Use of the
>         Mediator Proxy generator through a Web Interface to generate a
>         proxy to mediate SOAP to REST" ... what kind of Web interface
>         are we talking about ?   I would suggest saying instead
>         "ability to compose both SOAP and REST services using the
>         capacities of a Mediator Proxy generator" but ... anything
>         more clear
>       o We shouldn't refer to companies or products.  We are
>         delivering what are going to be Open Specifications of FI-WARE
>         GEs and a reference implementation of those specifications. 
>         Therefore, it doesn't make sense to talk about the "DT Mashup
>         Platform".
>       o What do we mean by "mediated SOAP services" ?   mediated
>         through what ?   from where ?  to what ?
>       o typo: "die GEs" ... I guess should be "these GEs"
>       o Saying "The general integration between die GEs will not yet
>         provided for the first release and will become a focus of the
>         second release" may confuse a bit because there is some degree
>         of integration between some of the GEs that will be achieved
>         in the first release.   Please elaborate more on what will NOT
>         be integrated.
>   * Second Release:
>       o Elaborate a bit on what new functions will come as a result of
>         a closer integration of the store and the marketplace.  Add
>         some "(e.g., xxx)" may help
>       o I don't understand what does "Adaptation of the service
>         language USDL to the integrated technical setting" exactly means.
>       o You should elaborate (at least giving some examples) of how
>         you intend to integrate Identity Management.
>       o You should elaborate (at least giving some examples) of how
>         you intend to integrate aspects related to the Internet of Things
>   * Future releases:
>       o No particular comment
>
>
> *Cloud Chapter:*
>
>   * General comments:
>       o Drop-out the text in bold coming from the guidelines
>
>   * First Release:
>       o I would shift the reference to the cloud portal to the
>         beginning.  For instance, I would rewrite the first bullet as
>         follows:
>           + Management of Individual virtual machines and associated
>             resources in a datacenter through a set of standardized
>             APIs as well as a Cloud Portal:
>               # Ability to automate the provision, as well as
>                 management of the lifecycle, of virtual machines and
>                 the associated compute, storage and network resources
>               # Ability to define and maintain a library of
>                 pre-configured virtual machine images that can be used
>                 for the automated provisioning of new virtual machines
>       o Is the concept of  "enhanced hardware-supported trust"
>         described in the Architecture Description ?  If so, try to
>         have a hyperlink to the proper section from here
>       o Same for the concept of "composite multi-VM services"
>       o Weren't we going to distinguish between what will be delivered
>         at the beginning and at the end of 3Q2012 ?
>   * Second Release:
>       o We talk about "network bandwith" management in the first
>         bullet ... do we mean it referred only to internal datacenter
>         connectivity (i.e., VLANs) ?   Managing it end to end (i.e.,
>         from application clients to applications running on the
>         backend hosted in a Cloud datacenter) would require using
>         interfaces defined in the I2ND chapter ... and I wonder
>         whether we are postponing management of those interfaces to
>         future releases (this would be what makes sense IMHO).   We
>         need to clarify this.
>       o While we focus on simple VMs allocation in the first release
>         ... what about allocation of VLANs and virtual disk storage
>         shared by several VMs ?   Wouldn't we support this level of
>         allocation in the second release ?
>       o We talk about "federation" but we don't talk about
>         cloudbursting - hybrids clouds.   If you consider them special
>         cases of "federation", please explain that.
>       o What do we mean by "Image management for cloud edge appliances" ?
>   * Future Releases:
>       o I would reword the sentence saying "Exposing more software
>         defined networking capabilities of the Interface to Connected
>         Devices chapter through Cloud Hosting service interfaces" by
>         something like "Ability to elastically manage allocation of
>         network resources outside datacenter boundaries along the
>         whole communication path between the end user and the
>         applications backends, using interfaces produced in the I2ND
>         chapter"
>
> *
> I2ND Chapter:*
>
>   * NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR
>     LAST DISCUSSION !!
>
>
> *Security Chapter:*
>
>   * General comments:
>       o For the shake of consistency across all chapter contributions,
>         I wouldn't number the list of features, just use bullets.
>
>   * First Release:
>       o Explain what IDM stands for the first time the acronym appears
>         (Identity Management)
>       o I understand that the web interface that the IDM GE will
>         expose will be a Restful interface ...  therefore I would move
>         the reference to REST API to the first bullet of the General
>         Remarks subsection, which I would simply rewrite as follows:
>           + The IDM GE will provide a common Restful API to clients
>       o You should postpone optional Security GEs to the second
>         release as per discussion during our last joint WPLs/WPAs
>         follow-up confcall.   Only if UC projects requires any of them
>         explictly, we will evaluate how they can be delivered in
>         upgrades of the Testbed after delivery of the first release.
>       o Honestly speaking, I believe that it would be better if we
>         move the Context-based Security and Compliance GE to the
>         second release because my understanding is that it has to be
>         closely integrated within the architecture of the Apps Chapter
>         ... Has such integration been carefully designed ?  What are
>         we going to be able to provide in a first release if not ?   I
>         guess it makes sense to address such integration for the
>         second release, once the Architecture of the Apps chapter is
>         more consolidated.   Unless a UC projects requires this, let's
>         commit this for the second release.
>       o "offered for Release 1" to be dropped in the last bullet (point 5)
>
>   * Second Release:
>       o "offered for Release 2" should be dropped in many of the
>         points (just redundant, since the bullets are within a section
>         titled "Second Release")
>       o Integration with Data/Context Management GEs should be
>         addressed in the Data Handling GE for the Second Release
>         (include an additional point on the matter)
>
>   * Future Releases:
>       o For the sake of consistency across the different points, I
>         would re-title the first bullet as "Security Monitoring GE
>         functionalities"
>       o Merge the point on Ovalyzer with the corresponding sub-bullet,
>         making it just one bullet
>
>
> *Development Support Tools Chapter:*
>
>   * NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR
>     LAST DISCUSSION (i.e., moving testing tools to second release) !!
>
> -- Juanjo
>
> -------------
> Product Development and Innovation (PDI) - Telefonica Digital
> website:www.tid.es
> email:jhierro at tid.es
> twitter: twitter.com/JuanjoHierro
>
> FI-WARE (European Future Internet Core Platform) Chief Architect
>
> You can follow FI-WARE at:
>    website:http://www.fi-ware.eu
>    facebook:http://www.facebook.com/pages/FI-WARE/251366491587242
>    twitter:http://twitter.com/FIware
>    linkedIn:http://www.linkedin.com/groups/FIWARE-4239932
>
> ------------------------------------------------------------------------
> 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
>
>
> _______________________________________________
> Fiware-wpl mailing list
> Fiware-wpl at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware-wpl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120314/5d56b821/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: matteo_melideo.vcf
Type: text/x-vcard
Size: 354 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120314/5d56b821/attachment.vcf>

From jhierro at tid.es  Wed Mar 14 10:54:58 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Wed, 14 Mar 2012 10:54:58 +0100
Subject: [Fiware-wpa] [Fiware-wpl] Detailed comments on Technical
	Roadmap deliverable
In-Reply-To: <4F6056AC.1020904@eng.it>
References: <4F604722.1020703@tid.es> <4F6056AC.1020904@eng.it>
Message-ID: <4F606AF2.5040801@tid.es>


  This is my fault.   I thought that we already agreed that testing tools would be deferred to the second Release, but you are right that we finally agreed that I was going to review the contents anyway in order to make a concrete proposal (this basically to confirm whether testing tools were the points to be deferred or even some additional aspects should be postponed).

  Well, the point is that I have actually carried out the revision and do keep my position in favor of postponing delivering of testing tools to the second release.

  You can keep the rest regarding the First Release (first version of the IDE and catalogue)

  Cheers,

-- Juanjo


On 14/03/12 09:28, Matteo Melideo wrote:
Juanjo Hi,
why in capital letters the reminder to Wp9? Are there any problems?
I was honestly waiting for your inputs. Reading at the minutes the only point I can see is: "Development tools: Juanjo will check what is there and make a proposal on what items to be postponed for second release of FI-WARE"

Said that sorry if I missed this agreement!

M.


Il 14/03/2012 08:22, Juanjo Hierro ha scritto:
Hi,

  Here you have a list of issues/doubts that have came to my mind while reading the Technical Roadmap of each chapter.   I believe it would be worth solving them prior final publication.

  I'm still working on the comments for the IoT and Data/Context Management Chapter.   I couldn't bring comments on the I2ND and Development Support Tools chapters because changes recently agreed hadn't been incorporated yet and I prefer to make comments on a revised version.

Apps Chapter:

 *   First Release:
    *   You say ... "This is handled in conjunction with the 1st Open Call" ... But ... What is handled in conjunction with the 1st Open Call ?  The sentence that is below or the list of functions enumerated above the sentence ?   It was unclear.   Using a semicolon, it would be more clear.
    *   I will assume that what is handled in conjunction with the 1st Open Call ...  However, it is not that clear what do we intend to provide when we say that we will support the "Ability to expose a REST Service through SOAP protocol in order to enable a Compositor Editor supporting SOAP to compose REST Services".   My assumption is that you aim to rely on the ability to implement a service interface and describe it in a technology/protocol-neutral way using the IDL that the middleware to be developed as a result of the 1st Open Call will support.   Operations in the service interface will then be accessible through several protocols (i.e., REST, SOAP, IIOP, ...).    Is my assumption correct ?   If so, I would suggest explain it a bit better ... (I hope that the above description may help)
    *   It seems like there is some missing indentation in the last bullet list (the one after "These features will be ...")  ... I mean when you say "Basic interaction of the Composition Engine with the Marketplace regarding" ... shouldn't the two following items indented ?  how many of the following items ?
    *   I guess that when you say "Ability of the Composition Environment to read/write service description into the Repository using USDL" it would be more accurate to say "Ability of the Composition Environment to read/write service descriptions from/into the Repository that are described using USDL"
    *   It is not very clear what you mean when you say "Use of the Mediator Proxy generator through a Web Interface to generate a proxy to mediate SOAP to REST" ... what kind of Web interface are we talking about ?   I would suggest saying instead "ability to compose both SOAP and REST services using the capacities of a Mediator Proxy generator" but ... anything more clear
    *   We shouldn't refer to companies or products.  We are delivering what are going to be Open Specifications of FI-WARE GEs and a reference implementation of those specifications.  Therefore, it doesn't make sense to talk about the "DT Mashup Platform".
    *   What do we mean by "mediated SOAP services" ?   mediated through what ?   from where ?  to what ?
    *   typo: "die GEs" ... I guess should be "these GEs"
    *   Saying "The general integration between die GEs will not yet provided for the first release and will become a focus of the second release" may confuse a bit because there is some degree of integration between some of the GEs that will be achieved in the first release.   Please elaborate more on what will NOT be integrated.
 *   Second Release:
    *   Elaborate a bit on what new functions will come as a result of a closer integration of the store and the marketplace.  Add some "(e.g., xxx)" may help
    *   I don't understand what does "Adaptation of the service language USDL to the integrated technical setting" exactly means.
    *   You should elaborate (at least giving some examples) of how you intend to integrate Identity Management.
    *   You should elaborate (at least giving some examples) of how you intend to integrate aspects related to the Internet of Things
 *   Future releases:
    *   No particular comment

Cloud Chapter:

 *   General comments:
    *   Drop-out the text in bold coming from the guidelines

 *   First Release:
    *   I would shift the reference to the cloud portal to the beginning.  For instance, I would rewrite the first bullet as follows:
       *   Management of Individual virtual machines and associated resources in a datacenter through a set of standardized APIs as well as a Cloud Portal:
          *   Ability to automate the provision, as well as management of the lifecycle, of virtual machines and the associated compute, storage and network resources
          *   Ability to define and maintain a library of pre-configured virtual machine images that can be used for the automated provisioning of new virtual machines
    *   Is the concept of  "enhanced hardware-supported trust" described in the Architecture Description ?  If so, try to have a hyperlink to the proper section from here
    *   Same for the concept of "composite multi-VM services"
    *   Weren't we going to distinguish between what will be delivered at the beginning and at the end of 3Q2012 ?
 *   Second Release:
    *   We talk about "network bandwith" management in the first bullet ... do we mean it referred only to internal datacenter connectivity (i.e., VLANs) ?   Managing it end to end (i.e., from application clients to applications running on the backend hosted in a Cloud datacenter) would require using interfaces defined in the I2ND chapter ... and I wonder whether we are postponing management of those interfaces to future releases (this would be what makes sense IMHO).   We need to clarify this.
    *   While we focus on simple VMs allocation in the first release ... what about allocation of VLANs and virtual disk storage shared by several VMs ?   Wouldn't we support this level of allocation in the second release ?
    *   We talk about "federation" but we don't talk about cloudbursting - hybrids clouds.   If you consider them special cases of "federation", please explain that.
    *   What do we mean by "Image management for cloud edge appliances" ?
 *   Future Releases:
    *   I would reword the sentence saying "Exposing more software defined networking capabilities of the Interface to Connected Devices chapter through Cloud Hosting service interfaces" by something like "Ability to elastically manage allocation of network resources outside datacenter boundaries along the whole communication path between the end user and the applications backends, using interfaces produced in the I2ND chapter"

I2ND Chapter:


 *   NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR LAST DISCUSSION !!

Security Chapter:

 *   General comments:
    *   For the shake of consistency across all chapter contributions, I wouldn't number the list of features, just use bullets.

 *   First Release:
    *   Explain what IDM stands for the first time the acronym appears (Identity Management)
    *   I understand that the web interface that the IDM GE will expose will be a Restful interface ...  therefore I would move the reference to REST API to the first bullet of the General Remarks subsection, which I would simply rewrite as follows:
       *   The IDM GE will provide a common Restful API to clients
    *   You should postpone optional Security GEs to the second release as per discussion during our last joint WPLs/WPAs follow-up confcall.   Only if UC projects requires any of them explictly, we will evaluate how they can be delivered in upgrades of the Testbed after delivery of the first release.
    *   Honestly speaking, I believe that it would be better if we move the Context-based Security and Compliance GE to the second release because my understanding is that it has to be closely integrated within the architecture of the Apps Chapter ... Has such integration been carefully designed ?  What are we going to be able to provide in a first release if not ?   I guess it makes sense to address such integration for the second release, once the Architecture of the Apps chapter is more consolidated.   Unless a UC projects requires this, let's commit this for the second release.
    *   "offered for Release 1" to be dropped in the last bullet (point 5)

 *   Second Release:
    *   "offered for Release 2" should be dropped in many of the points (just redundant, since the bullets are within a section titled "Second Release")
    *   Integration with Data/Context Management GEs should be addressed in the Data Handling GE for the Second Release (include an additional point on the matter)

 *   Future Releases:
    *   For the sake of consistency across the different points, I would re-title the first bullet as "Security Monitoring GE functionalities"
    *   Merge the point on Ovalyzer with the corresponding sub-bullet, making it just one bullet


Development Support Tools Chapter:

 *   NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM OUR LAST DISCUSSION (i.e., moving testing tools to second release) !!

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________
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



_______________________________________________
Fiware-wpl mailing list
Fiware-wpl at lists.fi-ware.eu<mailto:Fiware-wpl at lists.fi-ware.eu>
http://lists.fi-ware.eu/listinfo/fiware-wpl


________________________________
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-wpa/attachments/20120314/7b8e69a0/attachment.html>

From matteo.melideo at eng.it  Wed Mar 14 11:19:38 2012
From: matteo.melideo at eng.it (Matteo Melideo)
Date: Wed, 14 Mar 2012 11:19:38 +0100
Subject: [Fiware-wpa] [Fiware-wpl] Detailed comments on Technical
	Roadmap deliverable
In-Reply-To: <4F606AF2.5040801@tid.es>
References: <4F604722.1020703@tid.es> <4F6056AC.1020904@eng.it>
	<4F606AF2.5040801@tid.es>
Message-ID: <4F6070BA.4010601@eng.it>

Juanjo,
thank you for the clarifications and this is fine with me then.

I only see an additional problem. What about the justifications vs. the 
EC (and the reviewers) for this delay?
According to the DoW, in my version Pag. 183 and 184, we should deliver 
at M12 Del. 9.4a - Application Testing and Deployment Support Tools as 
well as the methodology D9.2a.
We can definitely postpone both these deliverables with the methodology 
making more sense) but the reason why I claimed those things in the 
roadmap was just for this contractual obligations.

Let me know...

Best,

Matteo

Il 14/03/2012 10:54, Juanjo Hierro ha scritto:
>
>   This is my fault.   I thought that we already agreed that testing 
> tools would be deferred to the second Release, but you are right that 
> we finally agreed that I was going to review the contents anyway in 
> order to make a concrete proposal (this basically to confirm whether 
> testing tools were the points to be deferred or even some additional 
> aspects should be postponed).
>
>   Well, the point is that I have actually carried out the revision and 
> do keep my position in favor of postponing delivering of testing tools 
> to the second release.
>
>   You can keep the rest regarding the First Release (first version of 
> the IDE and catalogue)
>
>   Cheers,
>
> -- Juanjo
>
>
> On 14/03/12 09:28, Matteo Melideo wrote:
>> Juanjo Hi,
>> why in capital letters the reminder to Wp9? Are there any problems?
>> I was honestly waiting for your inputs. Reading at the minutes the 
>> only point I can see is: "Development tools: Juanjo will check what 
>> is there and make a proposal on what items to be postponed for second 
>> release of FI-WARE"
>>
>> Said that sorry if I missed this agreement!
>>
>> M.
>>
>>
>> Il 14/03/2012 08:22, Juanjo Hierro ha scritto:
>>> Hi,
>>>
>>>   Here you have a list of issues/doubts that have came to my mind 
>>> while reading the Technical Roadmap of each chapter.   I believe it 
>>> would be worth solving them prior final publication.
>>>
>>>   I'm still working on the comments for the IoT and Data/Context 
>>> Management Chapter.   I couldn't bring comments on the I2ND and 
>>> Development Support Tools chapters because changes recently agreed 
>>> hadn't been incorporated yet and I prefer to make comments on a 
>>> revised version.
>>>
>>> *Apps Chapter:*
>>>
>>>   * First Release:
>>>       o You say ... "This is handled in conjunction with the 1st
>>>         Open Call" ... But ... What is handled in conjunction with
>>>         the 1st Open Call ?  The sentence that is below or the list
>>>         of functions enumerated above the sentence ?   It was
>>>         unclear.   Using a semicolon, it would be more clear.
>>>       o I will assume that what is handled in conjunction with the
>>>         1st Open Call ...  However, it is not that clear what do we
>>>         intend to provide when we say that we will support the
>>>         "Ability to expose a REST Service through SOAP protocol in
>>>         order to enable a Compositor Editor supporting SOAP to
>>>         compose REST Services".   My assumption is that you aim to
>>>         rely on the ability to implement a service interface and
>>>         describe it in a technology/protocol-neutral way using the
>>>         IDL that the middleware to be developed as a result of the
>>>         1st Open Call will support.   Operations in the service
>>>         interface will then be accessible through several protocols
>>>         (i.e., REST, SOAP, IIOP, ...).    Is my assumption correct
>>>         ?   If so, I would suggest explain it a bit better ... (I
>>>         hope that the above description may help)
>>>       o It seems like there is some missing indentation in the last
>>>         bullet list (the one after "These features will be ...") 
>>>         ... I mean when you say "Basic interaction of the
>>>         Composition Engine with the Marketplace regarding" ...
>>>         shouldn't the two following items indented ?  how many of
>>>         the following items ?
>>>       o I guess that when you say "Ability of the Composition
>>>         Environment to read/write service description into the
>>>         Repository using USDL" it would be more accurate to say
>>>         "Ability of the Composition Environment to read/write
>>>         service descriptions from/into the Repository that are
>>>         described using USDL"
>>>       o It is not very clear what you mean when you say "Use of the
>>>         Mediator Proxy generator through a Web Interface to generate
>>>         a proxy to mediate SOAP to REST" ... what kind of Web
>>>         interface are we talking about ?   I would suggest saying
>>>         instead "ability to compose both SOAP and REST services
>>>         using the capacities of a Mediator Proxy generator" but ...
>>>         anything more clear
>>>       o We shouldn't refer to companies or products.  We are
>>>         delivering what are going to be Open Specifications of
>>>         FI-WARE GEs and a reference implementation of those
>>>         specifications.  Therefore, it doesn't make sense to talk
>>>         about the "DT Mashup Platform".
>>>       o What do we mean by "mediated SOAP services" ?   mediated
>>>         through what ?   from where ?  to what ?
>>>       o typo: "die GEs" ... I guess should be "these GEs"
>>>       o Saying "The general integration between die GEs will not yet
>>>         provided for the first release and will become a focus of
>>>         the second release" may confuse a bit because there is some
>>>         degree of integration between some of the GEs that will be
>>>         achieved in the first release.   Please elaborate more on
>>>         what will NOT be integrated.
>>>   * Second Release:
>>>       o Elaborate a bit on what new functions will come as a result
>>>         of a closer integration of the store and the marketplace. 
>>>         Add some "(e.g., xxx)" may help
>>>       o I don't understand what does "Adaptation of the service
>>>         language USDL to the integrated technical setting" exactly
>>>         means.
>>>       o You should elaborate (at least giving some examples) of how
>>>         you intend to integrate Identity Management.
>>>       o You should elaborate (at least giving some examples) of how
>>>         you intend to integrate aspects related to the Internet of
>>>         Things
>>>   * Future releases:
>>>       o No particular comment
>>>
>>>
>>> *Cloud Chapter:*
>>>
>>>   * General comments:
>>>       o Drop-out the text in bold coming from the guidelines
>>>
>>>   * First Release:
>>>       o I would shift the reference to the cloud portal to the
>>>         beginning.  For instance, I would rewrite the first bullet
>>>         as follows:
>>>           + Management of Individual virtual machines and associated
>>>             resources in a datacenter through a set of standardized
>>>             APIs as well as a Cloud Portal:
>>>               # Ability to automate the provision, as well as
>>>                 management of the lifecycle, of virtual machines and
>>>                 the associated compute, storage and network resources
>>>               # Ability to define and maintain a library of
>>>                 pre-configured virtual machine images that can be
>>>                 used for the automated provisioning of new virtual
>>>                 machines
>>>       o Is the concept of  "enhanced hardware-supported trust"
>>>         described in the Architecture Description ?  If so, try to
>>>         have a hyperlink to the proper section from here
>>>       o Same for the concept of "composite multi-VM services"
>>>       o Weren't we going to distinguish between what will be
>>>         delivered at the beginning and at the end of 3Q2012 ?
>>>   * Second Release:
>>>       o We talk about "network bandwith" management in the first
>>>         bullet ... do we mean it referred only to internal
>>>         datacenter connectivity (i.e., VLANs) ?   Managing it end to
>>>         end (i.e., from application clients to applications running
>>>         on the backend hosted in a Cloud datacenter) would require
>>>         using interfaces defined in the I2ND chapter ... and I
>>>         wonder whether we are postponing management of those
>>>         interfaces to future releases (this would be what makes
>>>         sense IMHO).   We need to clarify this.
>>>       o While we focus on simple VMs allocation in the first release
>>>         ... what about allocation of VLANs and virtual disk storage
>>>         shared by several VMs ?   Wouldn't we support this level of
>>>         allocation in the second release ?
>>>       o We talk about "federation" but we don't talk about
>>>         cloudbursting - hybrids clouds.   If you consider them
>>>         special cases of "federation", please explain that.
>>>       o What do we mean by "Image management for cloud edge
>>>         appliances" ?
>>>   * Future Releases:
>>>       o I would reword the sentence saying "Exposing more software
>>>         defined networking capabilities of the Interface to
>>>         Connected Devices chapter through Cloud Hosting service
>>>         interfaces" by something like "Ability to elastically manage
>>>         allocation of network resources outside datacenter
>>>         boundaries along the whole communication path between the
>>>         end user and the applications backends, using interfaces
>>>         produced in the I2ND chapter"
>>>
>>> *
>>> I2ND Chapter:*
>>>
>>>   * NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM
>>>     OUR LAST DISCUSSION !!
>>>
>>>
>>> *Security Chapter:*
>>>
>>>   * General comments:
>>>       o For the shake of consistency across all chapter
>>>         contributions, I wouldn't number the list of features, just
>>>         use bullets.
>>>
>>>   * First Release:
>>>       o Explain what IDM stands for the first time the acronym
>>>         appears (Identity Management)
>>>       o I understand that the web interface that the IDM GE will
>>>         expose will be a Restful interface ...  therefore I would
>>>         move the reference to REST API to the first bullet of the
>>>         General Remarks subsection, which I would simply rewrite as
>>>         follows:
>>>           + The IDM GE will provide a common Restful API to clients
>>>       o You should postpone optional Security GEs to the second
>>>         release as per discussion during our last joint WPLs/WPAs
>>>         follow-up confcall.   Only if UC projects requires any of
>>>         them explictly, we will evaluate how they can be delivered
>>>         in upgrades of the Testbed after delivery of the first release.
>>>       o Honestly speaking, I believe that it would be better if we
>>>         move the Context-based Security and Compliance GE to the
>>>         second release because my understanding is that it has to be
>>>         closely integrated within the architecture of the Apps
>>>         Chapter ... Has such integration been carefully designed ? 
>>>         What are we going to be able to provide in a first release
>>>         if not ?   I guess it makes sense to address such
>>>         integration for the second release, once the Architecture of
>>>         the Apps chapter is more consolidated.   Unless a UC
>>>         projects requires this, let's commit this for the second
>>>         release.
>>>       o "offered for Release 1" to be dropped in the last bullet
>>>         (point 5)
>>>
>>>   * Second Release:
>>>       o "offered for Release 2" should be dropped in many of the
>>>         points (just redundant, since the bullets are within a
>>>         section titled "Second Release")
>>>       o Integration with Data/Context Management GEs should be
>>>         addressed in the Data Handling GE for the Second Release
>>>         (include an additional point on the matter)
>>>
>>>   * Future Releases:
>>>       o For the sake of consistency across the different points, I
>>>         would re-title the first bullet as "Security Monitoring GE
>>>         functionalities"
>>>       o Merge the point on Ovalyzer with the corresponding
>>>         sub-bullet, making it just one bullet
>>>
>>>
>>> *Development Support Tools Chapter:*
>>>
>>>   * NO CHANGES HAVE BEEN YET IMPLEMENTED CAPTURING AGREEMENTS FROM
>>>     OUR LAST DISCUSSION (i.e., moving testing tools to second
>>>     release) !!
>>>
>>> -- Juanjo
>>>
>>> -------------
>>> Product Development and Innovation (PDI) - Telefonica Digital
>>> website:www.tid.es
>>> email:jhierro at tid.es
>>> twitter: twitter.com/JuanjoHierro
>>>
>>> FI-WARE (European Future Internet Core Platform) Chief Architect
>>>
>>> You can follow FI-WARE at:
>>>    website:http://www.fi-ware.eu
>>>    facebook:http://www.facebook.com/pages/FI-WARE/251366491587242
>>>    twitter:http://twitter.com/FIware
>>>    linkedIn:http://www.linkedin.com/groups/FIWARE-4239932
>>>
>>> ------------------------------------------------------------------------
>>> 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
>>>
>>>
>>> _______________________________________________
>>> Fiware-wpl mailing list
>>> Fiware-wpl at lists.fi-ware.eu
>>> http://lists.fi-ware.eu/listinfo/fiware-wpl
>
> ------------------------------------------------------------------------
> 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-wpa/attachments/20120314/5d5b2a17/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: matteo_melideo.vcf
Type: text/x-vcard
Size: 354 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120314/5d5b2a17/attachment.vcf>

From jhierro at tid.es  Wed Mar 14 11:36:28 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Wed, 14 Mar 2012 11:36:28 +0100
Subject: [Fiware-wpa] VERY IMPORTANT: Sync on what we have to capture in the
 Technical Roadmap
Message-ID: <4F6074AC.5050807@tid.es>

Hi all,

   A recent discussion in one of the chapters suggests that it would be
important to make the clarifications below.   I hope most of us where on
the same page ...

   What we intend to capture in the Technical Roadmap is what FI-WARE
will deliver that will be available on the FI-WARE Testbed and,
therefore, can be tested.   That is, working software.

   I want to emphasize that, according to the DoW, the Open
Specifications of a given GE are not delivered until at least a partial
reference implementation of that FI-WARE GE exists and is delivered
together with it.   In other words, FI-WARE GEs "fit in" or "become part
of" a given FI-WARE Release if there is a working reference
implementation of those specs (at least of partial one) that will become
part of the software linked to that FI-WARE Release, to be made
available on the FI-WARE Testbed three months later.    Therefore ,
whatever spec we deliver in month 12 should come accompanying an
implementation of it (at least a partial one) which will be working in
the FI-WARE Testbed at month 15.

   Of course, we will have to produce "preliminary" specs of the FI-WARE
GEs prior we can implement them.   But we haven't committed to deliver
them according to the DoW.   We may decide to publish these
"preliminary" specs whenever we want, even before an actual
implementation of them still doesn't exist, just for the benefit of UC
projects and the FI-WARE community as a whole.   But we will be able to
do so at our own discretion.    We will probably setup a space in the
"FI-WARE Open Specifications" corner we will create in the public wiki
where specs that are still pending of implementation can be published
(to gather feedback and provide more visibility of our plans, among
other things).

   Note that we find gaps or may need to introduce changes in a given
"preliminary" spec while we are developing a first reference
implementation of it.   That's why we do not commit to deliver the
FI-WARE GE Open Specifications until a reference implementation is
ready.   We have committed to deliver proven and stable specs.

   Cheers,

-- Juanjo


--

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es
email: jhierro at tid.es
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
   website:  http://www.fi-ware.eu
   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
   twitter:  http://twitter.com/FIware
   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


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


From ste.depanfilis at gmail.com  Wed Mar 14 11:50:10 2012
From: ste.depanfilis at gmail.com (ste.depanfilis at gmail.com)
Date: Wed, 14 Mar 2012 10:50:10 +0000
Subject: [Fiware-wpa] R: [Fiware-wpl] VERY IMPORTANT: Sync on what we have
	to capture in the Technical Roadmap
In-Reply-To: <4F6074AC.5050807@tid.es>
References: <4F6074AC.5050807@tid.es>
Message-ID: <70975156-1331722152-cardhu_decombobulator_blackberry.rim.net-27595037-@b1.c14.bise7.blackberry>

Dear juanjo,

Thank for restating it, but i made it very clear during testbed-chapters bilateral meetings in january in madrid!!!
However, saying it twice does not harm ;)
At this point it is clear i have to check the consistency between d10.1.a and d2.4!

Ciao,
Stefano

Le mail ti raggiungono ovunque con BlackBerry? from Vodafone!

-----Original Message-----
From: Juanjo Hierro <jhierro at tid.es>
Sender: fiware-wpl-bounces at lists.fi-ware.eu
Date: Wed, 14 Mar 2012 11:36:28 
To: fiware-wpl at lists.fi-ware.eu<fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<fiware-wpa at lists.fi-ware.eu>
Subject: [Fiware-wpl] VERY IMPORTANT: Sync on what we have to capture in the
 Technical Roadmap

Hi all,

   A recent discussion in one of the chapters suggests that it would be
important to make the clarifications below.   I hope most of us where on
the same page ...

   What we intend to capture in the Technical Roadmap is what FI-WARE
will deliver that will be available on the FI-WARE Testbed and,
therefore, can be tested.   That is, working software.

   I want to emphasize that, according to the DoW, the Open
Specifications of a given GE are not delivered until at least a partial
reference implementation of that FI-WARE GE exists and is delivered
together with it.   In other words, FI-WARE GEs "fit in" or "become part
of" a given FI-WARE Release if there is a working reference
implementation of those specs (at least of partial one) that will become
part of the software linked to that FI-WARE Release, to be made
available on the FI-WARE Testbed three months later.    Therefore ,
whatever spec we deliver in month 12 should come accompanying an
implementation of it (at least a partial one) which will be working in
the FI-WARE Testbed at month 15.

   Of course, we will have to produce "preliminary" specs of the FI-WARE
GEs prior we can implement them.   But we haven't committed to deliver
them according to the DoW.   We may decide to publish these
"preliminary" specs whenever we want, even before an actual
implementation of them still doesn't exist, just for the benefit of UC
projects and the FI-WARE community as a whole.   But we will be able to
do so at our own discretion.    We will probably setup a space in the
"FI-WARE Open Specifications" corner we will create in the public wiki
where specs that are still pending of implementation can be published
(to gather feedback and provide more visibility of our plans, among
other things).

   Note that we find gaps or may need to introduce changes in a given
"preliminary" spec while we are developing a first reference
implementation of it.   That's why we do not commit to deliver the
FI-WARE GE Open Specifications until a reference implementation is
ready.   We have committed to deliver proven and stable specs.

   Cheers,

-- Juanjo


--

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es
email: jhierro at tid.es
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
   website:  http://www.fi-ware.eu
   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
   twitter:  http://twitter.com/FIware
   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


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
_______________________________________________
Fiware-wpl mailing list
Fiware-wpl at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-wpl


From pascal.bisson at thalesgroup.com  Fri Mar 16 19:14:22 2012
From: pascal.bisson at thalesgroup.com (BISSON Pascal)
Date: Fri, 16 Mar 2012 19:14:22 +0100
Subject: [Fiware-wpa] FI-WARE - Open questions regarding M12 deliverables
Message-ID: <27871_1331921668_4F638303_27871_1909_1_06a1369c-f713-4798-83e4-7530fe62faae@THSONEA01HUB04P.one.grp>

Dear Juanjo,

So far no guidelines have been provided by you as CA regarding M12 deliverables that are common to each and every chapter. In the meantime it becomes quite urgent to gain access to those guidelines to align and harmonize right from the start our M12 deliverables. This even more than M12 is end of April !.
So question: Can you already provide us with some guidelines to follow for M12 deliverables (layout & content) or at least provide me/us with a date at which these guidelines (and accompanying templates) could be provided to us. Being said this guidance would be very much appreciated to me and colleagues in order to engage the work the sooner the better on the right direction. Hope you could provide us with such a guidance asap and by end of the month at the latest to stay compatible with the delivery date for M12 that so far remains unchanged (end of April).
Facing what we had faced with D2 deliverables I don't want to engage my team in doing work that wouldn't be aligned with what is expected and as such would have to be changed after (requesting some extra work from my people).
Of course and in case you would not be able to provide us with such guidance we would have to come up with our own proposal and follow it but this is something I would like to avoid since we loose harmonization.

So hearing from you on this important matter to not only Security chapter but all the Chapters (that's why I put my WPL/WPA colleagues in cc of this email).

Best Regards,
Pascal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120316/c5c20fd5/attachment.html>

From jhierro at tid.es  Sun Mar 18 23:48:13 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Sun, 18 Mar 2012 23:48:13 +0100
Subject: [Fiware-wpa] FI-WARE - Open questions regarding M12 deliverables
In-Reply-To: <27871_1331921668_4F638303_27871_1909_1_06a1369c-f713-4798-83e4-7530fe62faae@THSONEA01HUB04P.one.grp>
References: <27871_1331921668_4F638303_27871_1909_1_06a1369c-f713-4798-83e4-7530fe62faae@THSONEA01HUB04P.one.grp>
Message-ID: <4F66662D.30609@tid.es>

Hi Pascal and all

  I expect to provide such guidelines along this week.   Stay tuned.

  Anyways, any feedback, proposal you or any other WPL/WPA may have is more than welcome.   I would take them all into accounts in elaborating those guidelines.

  Cheers,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


On 16/03/12 19:14, BISSON Pascal wrote:
Dear Juanjo,

So far no guidelines have been provided by you as CA regarding M12 deliverables that are common to each and every chapter. In the meantime it becomes quite urgent to gain access to those guidelines to align and harmonize right from the start our M12 deliverables. This even more than M12 is end of April !.
So question: Can you already provide us with some guidelines to follow for M12 deliverables (layout & content) or at least provide me/us with a date at which these guidelines (and accompanying templates) could be provided to us. Being said this guidance would be very much appreciated to me and colleagues in order to engage the work the sooner the better on the right direction. Hope you could provide us with such a guidance asap and by end of the month at the latest to stay compatible with the delivery date for M12 that so far remains unchanged (end of April).
Facing what we had faced with D2 deliverables I don?t want to engage my team in doing work that wouldn?t be aligned with what is expected and as such would have to be changed after (requesting some extra work from my people).
Of course and in case you would not be able to provide us with such guidance we would have to come up with our own proposal and follow it but this is something I would like to avoid since we loose harmonization.

So hearing from you on this important matter to not only Security chapter but all the Chapters (that?s why I put my WPL/WPA colleagues in cc of this email).

Best Regards,
Pascal

________________________________
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-wpa/attachments/20120318/bf8cc2c7/attachment.html>

From mcp at tid.es  Wed Mar 21 18:10:35 2012
From: mcp at tid.es (Miguel Carrillo)
Date: Wed, 21 Mar 2012 18:10:35 +0100
Subject: [Fiware-wpa] Technical roadmap
Message-ID: <4F6A0B8B.9010009@tid.es>

Dear all,

I was looking into the Technical roadmap deliverable. I have
consolidated all the inputs from the private wiki in a dedicated page on
the public wiki. I assume that this is stable and closed but if anyone
needs to change anything, please let me know before doing so.

Best regards,

Miguel

--
----------------------------------------------------------------------
      _/          _/_/                     Miguel Carrillo Pacheco
     _/   _/     _/  _/   Telef?nica       Distrito Telef?nica
    _/ _/_/_/   _/   _/   Investigaci?n y  Edifico Oeste 1, Planta 9
   _/   _/     _/  _/     Desarrollo       Ronda de la Comunicaci?n S/N
  _/          _/_/                         28050 Madrid (Spain)
                                           Tel:  (+34) 91 483 26 77

                                           e-mail: mcp at tid.es

Follow FI-WARE on the net

        Website:  http://www.fi-ware.eu
        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
        Twitter:  http://twitter.com/Fiware
        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------


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


From mcp at tid.es  Thu Mar 22 17:10:29 2012
From: mcp at tid.es (Miguel Carrillo)
Date: Thu, 22 Mar 2012 17:10:29 +0100
Subject: [Fiware-wpa] Experts for evaluation of the 1st Open Call
Message-ID: <4F6B4EF5.20306@tid.es>

Dear all,

As you are aware, the 1st Open Call is ongoing and at some point we will have to send a number of experts to the Project Officer for his consideration & approval. From the coordination we will try to think of this but it is worth asking for your collaboration. Can any of you please put forward people who:

 *   Are mainly industry biased
 *   Have no direct links with FI-WARE
 *   Have a prestigious record in one of the two topics of the Open Call and/or a CV that could be easily "saleable" to the EC

If you have proposals please specify the topic in which he/she is an expert

Best regards,

Miguel
P.S.: Of course, those who submit proposals or have ties with the ones who do it will be immediately dismissed, but we cannot know that in advance!

--
----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telef?nica       Distrito Telef?nica
   _/ _/_/_/   _/   _/   Investigaci?n y  Edifico Oeste 1, Planta 9
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicaci?n S/N
 _/          _/_/                         28050 Madrid (Spain)
                                          Tel:  (+34) 91 483 26 77

                                          e-mail: mcp at tid.es<mailto:mcp at tid.es>

Follow FI-WARE on the net

        Website:  http://www.fi-ware.eu
        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
        Twitter:  http://twitter.com/Fiware
        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------

________________________________
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-wpa/attachments/20120322/0b203779/attachment.html>

From jhierro at tid.es  Mon Mar 26 07:17:10 2012
From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA)
Date: Mon, 26 Mar 2012 07:17:10 +0200
Subject: [Fiware-wpa] Joint FI-WARE WPLs/WPAs follow-up confcall
Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A9E@EXCLU2K7.hi.inet>

Cu?ndo: lunes, 26 de marzo de 2012 11:00-13:00. Hora est?ndar romance

*~*~*~*~*~*~*~*~*~*

We'll use powwownow.   PIN: 050662.   Local dial-in phone numbers at:

http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf

________________________________
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-wpa/attachments/20120326/df4c8e5b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 3524 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120326/df4c8e5b/attachment.ics>

From jhierro at tid.es  Mon Mar 26 11:07:54 2012
From: jhierro at tid.es (Juanjo Hierro)
Date: Mon, 26 Mar 2012 11:07:54 +0200
Subject: [Fiware-wpa] Shared google document with shared minutes
Message-ID: <4F7031EA.5070407@tid.es>


https://docs.google.com/document/d/1eTgdFucUJd054LuBitksMdV67q64BssvtSN1rNUfbQA/edit

   Cheers,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es
email: jhierro at tid.es
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
   website:  http://www.fi-ware.eu
   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
   twitter:  http://twitter.com/FIware
   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


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


From jhierro at tid.es  Tue Mar 27 19:27:06 2012
From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA)
Date: Tue, 27 Mar 2012 19:27:06 +0200
Subject: [Fiware-wpa] Joint FI-WARE WPLs/WPAs follow-up confcall
Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260AA0@EXCLU2K7.hi.inet>

Cu?ndo: martes, 10 de abril de 2012 11:00-12:30. Hora est?ndar romance

*~*~*~*~*~*~*~*~*~*

We'll use powwownow.   PIN: 050662.   Local dial-in phone numbers at:

http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf

________________________________
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-wpa/attachments/20120327/5eb48ebf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 3662 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120327/5eb48ebf/attachment.ics>