Hi, Just an update on this. Based on the inputs received by several of you, we will go for creating this new WP/chapter but the activities considered in the FI-INMEDIA proposal will be integrated in the Data/Context Management chapter, where they will staty together with those linked to the Compressed-domain Video Analysis GE. Therefore, the new WP/chapter will be focused on Advanced Middleware and Web-based User Interfaces. Of course, we will incorporate references to the need to coordinate their work with that of other chapters. 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) Coordinator and 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 22/05/13 19:54, stefano de panfilis wrote: dear juanjo, i basically do agree, but for the sake of better consistency i do suggest to keep the two ges fi-inmedia and Compressed Domain Video Analysis together. in fact the fi-inmedia was born and agreed at the level of the fi-ppp ab to extend and complement with what already specified and provided by the Compressed Domain Video Analysis ge. keeping them separate, i mean in two different wps, migth generate inconsistencies and/or overlaps. so either both in the data chapter or both in the new wp. the argument of size of a wp you put forward is a bit articial in the sense that if we believe a new chapter needs to be in the overall fi-ware architecture than the size per se does not matter at all while keeping things together in an almost unconsistent way foir sure migth generate incomprehensions as well as communication and exploiation issues. so my proposal is to very much welcome the new wp, but also to keep together the content geis well defined in the data chapter. ciao, stefano 2013/5/22 Juanjo Hierro <jhierro at tid.es<mailto:jhierro at tid.es>> [Boxbe]<https://www.boxbe.com/overview> [http://www.boxbe.com/stfopen?tc_serial=14203782183&tc_rand=626565837&utm_source=stf&utm_medium=email&utm_campaign=ANNO_AFA&utm_content=001] You chose to allow Juanjo Hierro (jhierro at tid.es<mailto:jhierro at tid.es>) even though this message failed authentication Click to disallow<https://www.boxbe.com/anno?tc_serial=14203782183&tc_rand=626565837&utm_source=stf&utm_medium=email&utm_campaign=ANNO_AFA&utm_content=001&action=authfail&set=false&token=fzXrcpOSZSOrHfg%2BJ61dJiO1JK68IJ67ZeaYqquKqzqh%2FpqJrRz1OFCX8Lr9IAPJ&key=HkTaXJwIXdM3sz9w8Mp13UuThA%2FfgYp5%2B3SbtdkwY4U%3D> Hi all, As you perfectly know, a number of new partners will join the FI-WARE consortium as a result of the 2nd Open Call. I have given a careful thought to the way these new beneficiaries of the 2nd Open Call could be integrated in FI-WARE. Overall, looking for an approach that makes sense technically in the first place but also makes sense from an organizational perspective. It is obvious that Advanced Web-based User Interface GEs should fit within a new WP because existing WPs are not so much related. In a first approach, one may go for a design where there essentially the activities devised in the WeX proposal (dealing with the topic on Advanced Web-based User Interface in the 2nd Open Call) would go to that WP, while activities addressed in the FI-INMEDIA (dealing with the another topic on Stream-oriented GEs in the 2nd Open Call) may go to the WP on Data/Context Management. However, this would lead to a situation which is a bit unbalanced because the new WP will be very small compare to others. Besides, the Data/Context Management WP would become rather huge and difficult to manage. The solution that has came to my mind would consist in adding a new WP devoted to "Advanced Middleware, Web-based User Interface and Multimedia Enablers". This WP would concentrate tasks linked to specification and reference implementation of enablers targeted to: * support development of Web-based User Interfaces covering 3D and augmented reality and multimedia aspects * support multimedia enablers that may help to deal with stream processing and delivery of multimedia contents * advanced middleware technologies (i.e., KIARA) intended to help the above enablers to reach the best performance The Working Package Leader (WPL) would be ZHAW and I believe that the best idea would be to propose that DKFI becomes the Working Package Architect (WPA). Of course, all this under the necessary technical and overall coordination by TID and follow-up through the regular joint WPLs/WPAs follow-up confcalls. I see several advantages on this approach. Among others, moving KIARA to the new WP would help to better work on the details about how the KIARA middleware can be used to support the quite challenging requirements on performance that are expected for the other GEs to be provided by this WP. Besides, the approach would allow to concentrate the resources of DFKI in a single WP, thus easing their task as WPA. DFKI would not be only involved in the KIARA activities but also in the activities dealing with overall design of the architecture that supports advanced Web-based User Interfaces covering 3D and augmented reality capabilities and stream-related enablers dealing with processing and delivery of multimedia contents, contributing their know-how in both fields and also the fact that the proposed contributions for the first topic were relying on open source technologies developed at DFKI. I have already discussed this within TID (currently WPL in the Data/Context Management WP) in addition to ZHAW and DFKI (because they would become the WPL and WPA of this new WP, respectively) and they agree with this movement. Therefore, we will go for implementing the addition of this new WP in amendment 5 that for which the negotiation is going to start soon. Note that we intend to close this new amendment rather soon (targeting end of this month or first week of June). Therefore, we will proceed with this approach unless we receive an elaborated objection by any of you. I cannot imagine about any reason why there may be any objection to this but, formally, we had to ask :-) 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<http://twitter.com/JuanjoHierro> FI-WARE (European Future Internet Core Platform) Coordinator and 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-ga mailing list Fiware-ga at lists.fi-ware.eu<mailto:Fiware-ga at lists.fi-ware.eu> https://lists.fi-ware.eu/listinfo/fiware-ga -- 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 ________________________________ 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-ga/attachments/20130604/cb0bfd13/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy