From jhierro at tid.es Thu Nov 3 07:06:56 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 03 Nov 2011 07:06:56 +0100 Subject: [Fiware-data] IMPORTANT AND URGENT: Fwd: Materializing Data/Context Management in FI-WARE In-Reply-To: <4EB17624.6030202@tid.es> References: <4EB17624.6030202@tid.es> Message-ID: <4EB22F80.3080807@tid.es> Hi all, We need to make the final push to get the "Materializing the FI-WARE Vision" chapter of the Wiki done. Note that this part is quite important since identification of baseline assets and the planning for those assets was one of the major differences between the second and first release of the FI-WARE High-level Description (Product Vision) deliverable. This work about description of baseline assets and creation of the different chapter/GE backlogs is also a fundamental step in our process. Please find bellow a message from Miguel Carrillo with detailed comments on things that are pending regarding Wiki contents. Please take a look to APs that are on your plate and get them done by EOB this Friday Nov 4th. They are not that complex, so I believe there is enough time to deal with all of them. Don't hesitate to ask any question you may have on the mailing list so that we can solve it asap. Note that contents of the "Materializing the FI-WARE Vision" chapter will be one of the elements that will be carefully evaluated by our reviewers (and keep in mind that the second release of the FI-WARE Product Vision should have been delivered by end of September so we are already running late). We need to get this finished now so that we can announce the official delivery next week. Best regards, -- Juanjo -------- Original Message -------- Subject: Materializing Data/Context Management in FI-WARE Date: Wed, 2 Nov 2011 17:56:04 +0100 From: MIGUEL CARRILLO PACHECO To: JUAN JOSE HIERRO SUREDA , CARLOS RALLI UCENDO Dear Juanjo & Carlos, I am sending private emails to all WPLs with further comments to the " Materializing the FI-WARE Vision" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. You have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) so you there is little more I have to tell you. General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. ?This product has IPR associated to it?, ?Open source?? To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artifacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Storys" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * Publish/Subscribe Broker * Context Awareness Platform (CAP) ? ok * Complex Event Processing * AMIT -Most of the fields empty (Programming artifacts, technologies used, Runtime pre-requisites and IPR) ? no changes since my last communication. * BigData Analysis * Hadoop - ok * MongoDB - ok * SAMSON Platform - Publicly Av. Info to be enriched * Multimedia Analysis * codoan ? ?Programming artifacts? and ?Publicly available documentation? are empty? no changes since my last communication. * 'White Diamond' ? ok * Unstructured Data Analysis * The format is ignored in the main page of ?Materializing Data/Context Management in FI-WARE?, it does not show the sections nor identifies ?Baseline Assets?, ?Themes?, ?Epics? ,?Features? & ?User-Stories? * Just links to external sites. No work here at all. * Meta-data Pre-processing * SinoVE Meta-data Processor - ?Runtime pre-requisites? still ?t.b.d.? * Location Platform o location server ? OK. o Location Provider ? OK * Query Broker * THESEUS QueryBroker ? Empty ?Programming artifacts? & ?Runtime pre-requisites?. The ?Tecnologies used? section seems somewhat poor(?The asset is implemented in Java. ?). * Semantic Annotation * TI's 'Semantic Annotator (SAnr)' ? ok * Semantic Application Support * NeOn Toolkit - ok (if it is an external tool, we should remove fields and go for the ?short? template) * Sesame - ok (if it is an external tool, as I believe, we should remove fields and go for the ?short? template) * OWLIM - ok (if it is an external tool, as I believe, we should remove fields and go for the ?short? template) 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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: From mcp at tid.es Thu Nov 3 13:41:29 2011 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 03 Nov 2011 13:41:29 +0100 Subject: [Fiware-data] IMPORTANT AND URGENT: Fwd: Materializing Data/Context Management in FI-WARE In-Reply-To: <4EB22F80.3080807@tid.es> References: <4EB17624.6030202@tid.es> <4EB22F80.3080807@tid.es> Message-ID: <4EB28BF9.2090401@tid.es> Hello again, As promised, my comments to the backlog follow. The deadline is tight (tomorrow) so please react promptly. General comments (for all WPs) ============================= You should review the full description of your backlog entries in the Wiki to make sure all fields are properly filled in. Despite we provided a spreadsheet explaining how to fill each fields and some examples when we started this exercise (the spreadsheet was distributed in mid August) we have found that that guidelines haven't been followed in many cases. We have enhanced the tutorial on the Wiki to include all the explanations now and to make sure that there is a place on the Wiki that you can check out in case of doubt. You can find it at: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki Particularly important is the style used for the text provided as "Goal" field. Please try to align with the patterns provided in the description of this field. Do not forget to visit the pages with instructions to handle the trackers: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_and_configure_trackers_in_FusionForge * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter Particular comments (for this WP) ============================= * Naming convention for naming (Id) user stories may be good to export to the rest of project * No backlog entries on the Wiki nor the tracker regarding the Unstructured Data Analysis GE ! * typos in Ids of metadata pre-processing GE ? * Backlog entries on the Wiki and tracker fully alligned except: * Location Platform: some entries on the Wiki have no ticket * There is functionality on the CEP that should be captured as Epic but still not there The deadline is tomorrow, Friday 4 EOB Best regards, Miguel El 03/11/2011 7:06, Juanjo Hierro escribi?: Hi all, We need to make the final push to get the "Materializing the FI-WARE Vision" chapter of the Wiki done. Note that this part is quite important since identification of baseline assets and the planning for those assets was one of the major differences between the second and first release of the FI-WARE High-level Description (Product Vision) deliverable. This work about description of baseline assets and creation of the different chapter/GE backlogs is also a fundamental step in our process. Please find bellow a message from Miguel Carrillo with detailed comments on things that are pending regarding Wiki contents. Please take a look to APs that are on your plate and get them done by EOB this Friday Nov 4th. They are not that complex, so I believe there is enough time to deal with all of them. Don't hesitate to ask any question you may have on the mailing list so that we can solve it asap. Note that contents of the "Materializing the FI-WARE Vision" chapter will be one of the elements that will be carefully evaluated by our reviewers (and keep in mind that the second release of the FI-WARE Product Vision should have been delivered by end of September so we are already running late). We need to get this finished now so that we can announce the official delivery next week. Best regards, -- Juanjo -------- Original Message -------- Subject: Materializing Data/Context Management in FI-WARE Date: Wed, 2 Nov 2011 17:56:04 +0100 From: MIGUEL CARRILLO PACHECO To: JUAN JOSE HIERRO SUREDA , CARLOS RALLI UCENDO Dear Juanjo & Carlos, I am sending private emails to all WPLs with further comments to the " Materializing the FI-WARE Vision" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. You have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) so you there is little more I have to tell you. General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. ?This product has IPR associated to it?, ?Open source?? To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artifacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Storys" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * Publish/Subscribe Broker * Context Awareness Platform (CAP) ? ok * Complex Event Processing * AMIT -Most of the fields empty (Programming artifacts, technologies used, Runtime pre-requisites and IPR) ? no changes since my last communication. * BigData Analysis * Hadoop - ok * MongoDB - ok * SAMSON Platform - Publicly Av. Info to be enriched * Multimedia Analysis * codoan ? ?Programming artifacts? and ?Publicly available documentation? are empty? no changes since my last communication. * 'White Diamond' ? ok * Unstructured Data Analysis * The format is ignored in the main page of ?Materializing Data/Context Management in FI-WARE?, it does not show the sections nor identifies ?Baseline Assets?, ?Themes?, ?Epics? ,?Features? & ?User-Stories? * Just links to external sites. No work here at all. * Meta-data Pre-processing * SinoVE Meta-data Processor - ?Runtime pre-requisites? still ?t.b.d.? * Location Platform o location server ? OK. o Location Provider ? OK * Query Broker * THESEUS QueryBroker ? Empty ?Programming artifacts? & ?Runtime pre-requisites?. The ?Tecnologies used? section seems somewhat poor(?The asset is implemented in Java. ?). * Semantic Annotation * TI's 'Semantic Annotator (SAnr)' ? ok * Semantic Application Support * NeOn Toolkit - ok (if it is an external tool, we should remove fields and go for the ?short? template) * Sesame - ok (if it is an external tool, as I believe, we should remove fields and go for the ?short? template) * OWLIM - ok (if it is an external tool, as I believe, we should remove fields and go for the ?short? template) 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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 -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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: From jhierro at tid.es Fri Nov 4 07:22:50 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 04 Nov 2011 07:22:50 +0100 Subject: [Fiware-data] DON'T MISS IT: FI-WARE Data/Context Management follow-up confcall TODAY Message-ID: <4EB384BA.2000808@tid.es> Hi all, We will celebrate the follow-up confcall today, starting at 09:30. Please don't miss it since we will address relevant topics. We will check the status regarding: * Description of assets * Backlog entries linked to Themes/Epics/Features/User-Stories * Selection of Features to be addressed in first minor release and planning of first Sprint While I believe that we are almost done with the first two bullets, we rather need to push and get the third finalized. We will also share recent decisions on how to handle activities within sprints, particularly introduction of "work items". If we still have time, we will address the issue about Open Calls. We will use powwownow for the confcall. PIN Code: 050662. Powwownow phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf Best regards, -- Juanjo ________________________________ 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: From jhierro at tid.es Fri Nov 4 09:34:37 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 04 Nov 2011 09:34:37 +0100 Subject: [Fiware-data] Fwd: Meeting invitation: FI-WARE Data/Context follow-up confcall In-Reply-To: <239640148.1320392689119.JavaMail.nobody@jsj2wl016.webex.com> References: <239640148.1320392689119.JavaMail.nobody@jsj2wl016.webex.com> Message-ID: <4EB3A39D.7050805@tid.es> -------- Original Message -------- Subject: Meeting invitation: FI-WARE Data/Context follow-up confcall Date: Fri, 4 Nov 2011 08:44:49 +0100 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE Data/Context follow-up confcall Date: Friday, November 4, 2011 Time: 9:30 am, Europe Time (Paris, GMT+01:00) Meeting Number: 962 583 818 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=187793017&UID=1258241497&PW=NYjI3NTI4YTRk&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=187793017&UID=1258241497&PW=NYjI3NTI4YTRk&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: Webex9100 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=187793017&UID=1258241497&ICS=MI&LD=1&RD=2&ST=1&SHA2=vfEVVxJHSIWTuzB6XRUpC4ctcSFPjyVEXps7S/F6JAc=&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: From jhierro at tid.es Sat Nov 5 00:08:08 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sat, 05 Nov 2011 00:08:08 +0100 Subject: [Fiware-data] Minutes of today's Data/Context Management follow-up confcall In-Reply-To: <2A6B76AF12C9794683898EA4B720C52E02F0B8F626BF@SRV-MADMX.mad.tecsidel.es> References: <2A6B76AF12C9794683898EA4B720C52E02F0B8F626BF@SRV-MADMX.mad.tecsidel.es> Message-ID: <4EB47058.6060905@tid.es> Hi all, These are the quick and dirty minutes from our confcall today. They are based on notes taken by Grant so I would like to thank him for his input ! ________________________________ 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: From jhierro at tid.es Sat Nov 5 00:11:04 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sat, 05 Nov 2011 00:11:04 +0100 Subject: [Fiware-data] Fwd: IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint In-Reply-To: <4EB3E27B.5070906@tid.es> References: <4EB3E27B.5070906@tid.es> Message-ID: <4EB47108.7020409@tid.es> Hi all, This is the email I sent to WPLs/WPAs today. Please read it carefully. It elaborates on what we already commented during our follow-up confcall this morning. Cheers, -- Juanjo -------- Original Message -------- Subject: IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint Date: Fri, 04 Nov 2011 14:02:51 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, We definitively need to close the selection of Features for the 1st Minor Release of FI-WARE as well as the planning of the 1st Sprint. We should have closed it by end of October but unfortunately we are delayed. Therefore, we have to take the necessary corrective actions. This mail is intended to put this actions in place so that we can recover these few days of delay and get back on track. Everything should be fixed by Nov 10th at the latest. We will do this at the price of making the first sprint a bit shorter, still planning it to finish by end of November. On Nov 10th, it should be clear what are the Features selected for the 1st Minor Release of FI-WARE and what are the backlog entries to be addressed in the 1st Sprint. That information should be visible on your tracker. Note that November 10th is the date at which we have told our PO that everything should be available on the Wiki and FusionForge environment. Now, following the actions/recommendations to implement/follow (some have already been tackled by some of you, but I'm summarizing them here for the convenience of all). Don't hesitate to raise any question or doubt that you may have. Please share them with your teams. Regarding Selection of Features for a given GE: Features may be considered just as a kind of Epic you believe you understand enough (i.e., you own enough detailed info describing the functionality of the Epic) as to feel confident that can be addressed in the duration of a release (duration of releases, also named as minor releases, are three months, don't confuse with usage of the term "release" in the DoW that comprises several releases and we have started to name as "major release"). You may hay identified a number of Features following the above criteria. However, some of you have only identified entries that you have labeled as Epic so far. If so, the first exercise I would ask you to do is to review the list of Epics you have and try to ask yourself the following question ... "Is this a functionality I really understand and have enough information about as to feel confident that could be addressed in 3 months ?" If your answer is "yes", then simply label the Epic as Feature and change the entry both at the Wiki and the tracker accordingly. It may happen that the Epics you have identified are still at a very high-level though. Therefore, you cannot guarantee that you will be able to address them in any. Thus, you need to refine them and this will be work to be done. Those Epics cannot be selected as Features, of course. I would suggest that you try to make some progress refining them until November 10th and try to find out whether you can derive more detailed entries from them and check whether some of them can be labeled as Features. But those entries you believe cannot qualify as Feature because they are still too high-level should be kept as Epics. The first minor release is scheduled to finish by end of January. I know that we have considered finishing it by end of February but after feedback from some of you, let's keep it to finish by end of January. Once you identify a number of Features, it's a matter of deciding whether you feel confident enough to assign it to a particular minor release within the first major release. If so, you should assign it a ReleaseId to the ticket associated to the Feature on the tracker. We will adopt the following convention for identifying minor releases in FI-WARE (i.e., for the values of ReleasesId fields on the tracker): FIWARE.Release.. Where is the number of the major release the minor release is associated to Where is the number of the minor release, within the major release Note that you may not yet feel confident about what release will be the release in which you will address a particular Feature. If so, simply don't assign a ReleaseId to the corresponding ticket. Anyway, bear in mind that, when referring to Features in releases other than the current minor release, you are just setting up an expectation. Expectations may change a bit and we may decide to update the list of Features we plan to address in the second minor release while developing the first minor release. Adapting the planning over time is what Agile is all about. If by November 10th you haven't identified any Feature and you still only have Epics, don't panic. See next section. Regarding planning of 1st Sprint: Some people have shared the feedback that they feel like they are not still in the position to identify a relevant list of User Stories or even Features. They still need to work on the set of Epics they had currently identified. How can we show we are doing some work in the course of the first sprint and be able to follow-up progress ? After thinking a bit on the matter, I have decided to introduce the concept of "Work Item". Work items refer to work to be done in the course of a sprint, trying to meet a concrete goal. It may relate to work to be done in order to refine an Epic (or a feature) and derive actual Features (or User-stories) derived from it. In general, any work you need to address to progress development but may be difficult to express in terms of "functionality supported by the product". This I hope will help you to declare things to be addressed in the first sprint (and subsequent sprints) in a more natural/intuitive way. "Work Items" is not something I had invented myself. It was already identified as a special kind of backlog entries by some Agile authors. Indeed was identified by Dean Leffingwell in the paper I had already sent to you some time ago. The reason why I feel reluctant to introduce these kind of entries in our definition of Backlog was that I was afraid about the explosion of entries in the Wiki. Besides, some of these work items may relate to activities that we may wish to keep at confidential level, just shared among FI-WARE partners. At the end of the day, users (application developers in our case) should just need to know about functionality we plan to develop in GEs. Now I see the advantages that introducing these "Work Items" will bring to some chapters, and definitively they will help us to move things forward and monitor progress. So let's go for their introduction. However, trying to minimize overhead what I believe we can adopt as a formula is that these Work Items just need to be registered on the tracker and we don't need to create a detailed entry on the Wiki. I feel like this is a good compromise and have the following advantages: * We will keep on the public Wiki only that information that is relevant in terms of description of the functionality to be supported by GEs. At the end of the day, this is what is relevant from an user (app developer) perspective, so there is no need to overflown the Wiki with additional, so fine-grained info. * Work Items would exist on the trackers (which is the place where you can get the complete view of a backlog) and trackers linked to chapters are private to chapter members. This will be helpful Given said the above, the task to be done until Nov 10th is to get a good list of User-Stories and Work Items that help to describe what you will do during the first sprint (ending Nov 30th). Hope that this will mean a more clear goal and then you will be able to provide some "meat to eat" by then. We will adopt the following convention for identifying Sprints in FI-WARE (i.e., for the values of SprintId fields on the tracker): FIWARE.Sprint... Where is the number of the major release where the sprint is planned Where is the number of the minor release, within the major release, where the sprint is planned Where is the number of the sprint ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: a-lean-and-scalable-requirements-information-model-for-agile-enterprises.pdf Type: application/pdf Size: 1463988 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Wed Nov 9 19:16:46 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 9 Nov 2011 19:16:46 +0100 Subject: [Fiware-data] Fwd: IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint In-Reply-To: <4EB47108.7020409@tid.es> References: <4EB3E27B.5070906@tid.es> <4EB47108.7020409@tid.es> Message-ID: Hi All, I've attentively read and reread the mail of Juanjo below and minutes from the last call, [for me the Open Call issues is still open in undiscussed , therefore reserve the right to still have it open and discuss] and have performed first exercise in tracker and wiki. However not sure if I have got it correctly as far as didn't see yet any other similar results from other performed there, therefore probably I've got something wrong. Anyway, after internal TI discussions and meetings I've converted 13 (if not wrong) EPICS to Features that should be ready by TI for 01/2012. Some of them maintained as is, some will be started from a minimum set (1st minor release). Some, especially the ones where a cooperation with other partners required, are still left as EPIC. Juanjo, please check this first attempt and give me a feedback if I have spent my time useless or less. Probably I will again miss the call this Friday, sorry so much. BR, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Saturday, November 05, 2011 12:11 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Fwd: IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint Hi all, This is the email I sent to WPLs/WPAs today. Please read it carefully. It elaborates on what we already commented during our follow-up confcall this morning. Cheers, -- Juanjo -------- Original Message -------- Subject: IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint Date: Fri, 04 Nov 2011 14:02:51 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, We definitively need to close the selection of Features for the 1st Minor Release of FI-WARE as well as the planning of the 1st Sprint. We should have closed it by end of October but unfortunately we are delayed. Therefore, we have to take the necessary corrective actions. This mail is intended to put this actions in place so that we can recover these few days of delay and get back on track. Everything should be fixed by Nov 10th at the latest. We will do this at the price of making the first sprint a bit shorter, still planning it to finish by end of November. On Nov 10th, it should be clear what are the Features selected for the 1st Minor Release of FI-WARE and what are the backlog entries to be addressed in the 1st Sprint. That information should be visible on your tracker. Note that November 10th is the date at which we have told our PO that everything should be available on the Wiki and FusionForge environment. Now, following the actions/recommendations to implement/follow (some have already been tackled by some of you, but I'm summarizing them here for the convenience of all). Don't hesitate to raise any question or doubt that you may have. Please share them with your teams. Regarding Selection of Features for a given GE: Features may be considered just as a kind of Epic you believe you understand enough (i.e., you own enough detailed info describing the functionality of the Epic) as to feel confident that can be addressed in the duration of a release (duration of releases, also named as minor releases, are three months, don't confuse with usage of the term "release" in the DoW that comprises several releases and we have started to name as "major release"). You may hay identified a number of Features following the above criteria. However, some of you have only identified entries that you have labeled as Epic so far. If so, the first exercise I would ask you to do is to review the list of Epics you have and try to ask yourself the following question ... "Is this a functionality I really understand and have enough information about as to feel confident that could be addressed in 3 months ?" If your answer is "yes", then simply label the Epic as Feature and change the entry both at the Wiki and the tracker accordingly. It may happen that the Epics you have identified are still at a very high-level though. Therefore, you cannot guarantee that you will be able to address them in any. Thus, you need to refine them and this will be work to be done. Those Epics cannot be selected as Features, of course. I would suggest that you try to make some progress refining them until November 10th and try to find out whether you can derive more detailed entries from them and check whether some of them can be labeled as Features. But those entries you believe cannot qualify as Feature because they are still too high-level should be kept as Epics. The first minor release is scheduled to finish by end of January. I know that we have considered finishing it by end of February but after feedback from some of you, let's keep it to finish by end of January. Once you identify a number of Features, it's a matter of deciding whether you feel confident enough to assign it to a particular minor release within the first major release. If so, you should assign it a ReleaseId to the ticket associated to the Feature on the tracker. We will adopt the following convention for identifying minor releases in FI-WARE (i.e., for the values of ReleasesId fields on the tracker): FIWARE.Release.. Where is the number of the major release the minor release is associated to Where is the number of the minor release, within the major release Note that you may not yet feel confident about what release will be the release in which you will address a particular Feature. If so, simply don't assign a ReleaseId to the corresponding ticket. Anyway, bear in mind that, when referring to Features in releases other than the current minor release, you are just setting up an expectation. Expectations may change a bit and we may decide to update the list of Features we plan to address in the second minor release while developing the first minor release. Adapting the planning over time is what Agile is all about. If by November 10th you haven't identified any Feature and you still only have Epics, don't panic. See next section. Regarding planning of 1st Sprint: Some people have shared the feedback that they feel like they are not still in the position to identify a relevant list of User Stories or even Features. They still need to work on the set of Epics they had currently identified. How can we show we are doing some work in the course of the first sprint and be able to follow-up progress ? After thinking a bit on the matter, I have decided to introduce the concept of "Work Item". Work items refer to work to be done in the course of a sprint, trying to meet a concrete goal. It may relate to work to be done in order to refine an Epic (or a feature) and derive actual Features (or User-stories) derived from it. In general, any work you need to address to progress development but may be difficult to express in terms of "functionality supported by the product". This I hope will help you to declare things to be addressed in the first sprint (and subsequent sprints) in a more natural/intuitive way. "Work Items" is not something I had invented myself. It was already identified as a special kind of backlog entries by some Agile authors. Indeed was identified by Dean Leffingwell in the paper I had already sent to you some time ago. The reason why I feel reluctant to introduce these kind of entries in our definition of Backlog was that I was afraid about the explosion of entries in the Wiki. Besides, some of these work items may relate to activities that we may wish to keep at confidential level, just shared among FI-WARE partners. At the end of the day, users (application developers in our case) should just need to know about functionality we plan to develop in GEs. Now I see the advantages that introducing these "Work Items" will bring to some chapters, and definitively they will help us to move things forward and monitor progress. So let's go for their introduction. However, trying to minimize overhead what I believe we can adopt as a formula is that these Work Items just need to be registered on the tracker and we don't need to create a detailed entry on the Wiki. I feel like this is a good compromise and have the following advantages: * We will keep on the public Wiki only that information that is relevant in terms of description of the functionality to be supported by GEs. At the end of the day, this is what is relevant from an user (app developer) perspective, so there is no need to overflown the Wiki with additional, so fine-grained info. * Work Items would exist on the trackers (which is the place where you can get the complete view of a backlog) and trackers linked to chapters are private to chapter members. This will be helpful Given said the above, the task to be done until Nov 10th is to get a good list of User-Stories and Work Items that help to describe what you will do during the first sprint (ending Nov 30th). Hope that this will mean a more clear goal and then you will be able to provide some "meat to eat" by then. We will adopt the following convention for identifying Sprints in FI-WARE (i.e., for the values of SprintId fields on the tracker): FIWARE.Sprint... Where is the number of the major release where the sprint is planned Where is the number of the minor release, within the major release, where the sprint is planned Where is the number of the sprint ________________________________ 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:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Thu Nov 10 07:50:40 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 10 Nov 2011 07:50:40 +0100 Subject: [Fiware-data] Fwd: On empty sections associated to Themes/Epics/Features/User-Stories on the Wiki In-Reply-To: <4EBB7387.2000606@tid.es> References: <4EBB7387.2000606@tid.es> Message-ID: <4EBB7440.4030908@tid.es> Hi, Please take care of this action point. Thanks, -- Juanjo -------- Original Message -------- Subject: On empty sections associated to Themes/Epics/Features/User-Stories on the Wiki Date: Thu, 10 Nov 2011 07:47:35 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi, There may be GEs for which some of the sections linked to Themes, Epics, Features or User-Stories may be empty. This is fine because our development in FI-WARE didn't start from the scratch but relies on the selection of a number of baseline assets. Thus, the FI-WARE backlog will contain Theme/Epic/Feature/User-Story entries that match "functionality to be supported but is not yet fully supported in its full extend" in the reference implementation we want to build based on selected assets (in other words, requires some development to be done on the assets). If we had gone for building a complete backlog that includes all "functionality to be supported" in the reference implementation of GEs, it would be a huge task since it had meant trying to perform a reverse engineering of many of the functionalities already supported in the baseline assets, many of which had taken years of development. We may had finished with a very nice and complete backlog, where just selecting the features we would get a detailed description of all GEs, but this would not provide so much added value to the development teams, who want to plan what they have to do rather that document what they already did, overall when at the end of the day we will produce a complete set of GE specifications where the complete functionality of GEs will be detailed documented for the sake of application programmers (and they will not want to check backlogs) Since having sections with empty bullets may lead to a wrong interpretation ("there is work pending"), you should review all the sections dealing with description of backlog entries on the Wiki and remove those "Themes", "Epics", "Features" or "User-Stories" sections that are empty. Please try to get this done for this milestone. It simply takes a few minutes. Best regards, -- Juanjo ________________________________ 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: From jhierro at tid.es Thu Nov 10 09:41:53 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 10 Nov 2011 09:41:53 +0100 Subject: [Fiware-data] Slides to be used in the internal FI-WARE workshop on Security Identity, Access Control and Privacy Management GEs Message-ID: <4EBB8E51.5030604@tid.es> Hi all, Slides that will be used in the workshop this morning have been uploaded to FusionForge and is available at: https://forge.fi-ware.eu/docman/view.php/7/584/Meeting_WP8-Use_Case_Projects_v05.ppt Best regards, -- Juanjo 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 Fri Nov 11 07:45:32 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 11 Nov 2011 07:45:32 +0100 Subject: [Fiware-data] Follow-up confcall today Message-ID: <4EBCC48C.2020503@tid.es> Hi, We are not going to have a follow-up confcall today. You should have dealed with the APs that were identified in the last confcall and it is also supposed that you had dealed with selection of features for the 1st minor release as well as the planning of the 1st sprint. I will devote this morning to review carefully what you have done and send you detailed instructions on how to deal with anything that I may find missing. Cheers, -- Juanjo 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 Mon Nov 14 19:03:42 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Nov 2011 19:03:42 +0100 Subject: [Fiware-data] New type of entries in the tracker associated to WorkItems Message-ID: <4EC157FE.6060604@tid.es> Hi, Just to let you know that I have added "WorkItem" as a new choice for the "FI-WARE Backlog Entry Type" field of tickets on the tracker. Regards, -- Juanjo 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 ralli at tid.es Thu Nov 17 12:12:13 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 17 Nov 2011 12:12:13 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpl] Fwd: Submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) References: <4EC46CA9.8010207@tid.es> Message-ID: <8AA2F873-6298-4FE8-BF31-7463ACCC7571@tid.es> Dear All, Find enclosed below, just FYI, our official communication/delivery of D2.2b (Product Vision) to the Fi-WARE Project officer and Reviewers. Thanks for your contributions to data/context section that enabled us to meet this deadline, Best regards, Inicio del mensaje reenviado: De: JUAN JOSE HIERRO SUREDA > Fecha: 17 de noviembre de 2011 03:08:41 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpl] Fwd: Submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) FYI. Feel free to share with your teams. Cheers, -- Juanjo -------- Original Message -------- Subject: Submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) Date: Thu, 17 Nov 2011 02:43:46 +0100 From: JUAN JOSE HIERRO SUREDA To: Arian.ZWEGERS at ec.europa.eu , dgr at whitestein.com , msli at icfocus.co.uk , rdifrancesco at ymail.com , bel.piet1 at gmail.com CC: FI-WARE project EC mailbox , JOSE JIMENEZ DELGADO , MIGUEL CARRILLO PACHECO , JUAN JOSE HIERRO SUREDA Dear PO and FI-WARE project reviewers, This is the official submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) deliverable of the FI-WARE project. You can download a .pdf version of this deliverable at: https://forge.fi-ware.eu/docman/view.php/7/624/FI-WARE+High-level+Description+Product+Vision+11-11-16.pdf The FI-WARE High-level Description (Product Vision) is a living document, constantly updated on the public Wiki of the FI-WARE project (http://wiki.fi-ware.eu). You can always get access it on line at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision The submitted D.2.2.b deliverable indeed correspond to a snapshot of the contents of the FI-WARE High-level Description (Product Vision) available on the Wiki. This snapshot has been produced using standard extensions of MediaWiki enabling to generate .pdf books from MediaWiki-based Wiki contents. Best regards, Juanjo Hierro Chief Architect & Technical Manager FI-WARE project www.fi-ware.eu ________________________________ 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 ________________________________ 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Nov 17 12:24:50 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Thu, 17 Nov 2011 12:24:50 +0100 Subject: [Fiware-data] Data/Context WP coordination Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A0E@EXCLU2K7.hi.inet> When: Occurs every Friday from 9:30 AM to 11:00 AM effective 6/3/2011. (GMT+01:00) Brussels, Copenhagen, Madrid, Paris *~*~*~*~*~*~*~*~*~* 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2802 bytes Desc: not available URL: From jhierro at tid.es Thu Nov 17 12:24:50 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Thu, 17 Nov 2011 12:24:50 +0100 Subject: [Fiware-data] Data/Context WP follow-up confcall Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A0F@EXCLU2K7.hi.inet> When: Friday, November 18, 2011 9:30 AM-11:00 AM. Romance Standard Time *~*~*~*~*~*~*~*~*~* 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2163 bytes Desc: not available URL: From jhierro at tid.es Thu Nov 17 12:25:36 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 17 Nov 2011 12:25:36 +0100 Subject: [Fiware-data] Follow-up confcall tomorrow (THIS TIME WE'LL HAVE) Message-ID: <4EC4EF30.3000500@tid.es> Dear colleagues, Tomorrow we should have a follow-up confcall. Goals are to review state of the backlog and confirm we are on track regarding start of the first sprint regarding all GEs. Besides, we have to start analyzing the requests being received by the UC projects. The target goal is to show a significant progress on this during next week. I will explain what is the process we will follow to handle this. As always, we'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf Details for the webex will be sent later by Carlos. Best regards, -- Juanjo 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 ralli at tid.es Thu Nov 17 18:00:52 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 17 Nov 2011 18:00:52 +0100 Subject: [Fiware-data] Follow-up confcall tomorrow (THIS TIME WE'LL HAVE) In-Reply-To: <4EC4EF30.3000500@tid.es> References: <4EC4EF30.3000500@tid.es> Message-ID: Hi All, Find enclosed here the Webex session details for tomorrow's call: Topic: FI-WARE, Data/Context WP follow up Call Conference Date: Friday, November 18, 2011 Time: 9:30 pm, Europe Time (Paris, GMT+01:00) Meeting Number: 965 983 156 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=188221702&UID=0&PW=NZjkwY2RmZWU4&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: 1234abcD 4. Click "Join Now". Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 17/11/2011, a las 12:25, Juanjo Hierro escribi?: Dear colleagues, Tomorrow we should have a follow-up confcall. Goals are to review state of the backlog and confirm we are on track regarding start of the first sprint regarding all GEs. Besides, we have to start analyzing the requests being received by the UC projects. The target goal is to show a significant progress on this during next week. I will explain what is the process we will follow to handle this. As always, we'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf Details for the webex will be sent later by Carlos. Best regards, -- Juanjo 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-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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: From ralli at tid.es Fri Nov 18 09:33:14 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 18 Nov 2011 09:33:14 +0100 Subject: [Fiware-data] Follow-up confcall tomorrow (THIS TIME WE'LL HAVE) In-Reply-To: References: <4EC4EF30.3000500@tid.es> Message-ID: <1759C106-BC63-4265-AC28-A886C6790669@tid.es> Dear All, Due to a misconfiguration on our Webex system, we will be starting with some 20 min delay. We'll be sending a new link for the Webex session over the e-mail before 9:50. Sorry for the inconveniences caused by this. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 17/11/2011, a las 18:00, CARLOS RALLI UCENDO escribi?: Hi All, Find enclosed here the Webex session details for tomorrow's call: Topic: FI-WARE, Data/Context WP follow up Call Conference Date: Friday, November 18, 2011 Time: 9:30 pm, Europe Time (Paris, GMT+01:00) Meeting Number: 965 983 156 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=188221702&UID=0&PW=NZjkwY2RmZWU4&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: 1234abcD 4. Click "Join Now". Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 17/11/2011, a las 12:25, Juanjo Hierro escribi?: Dear colleagues, Tomorrow we should have a follow-up confcall. Goals are to review state of the backlog and confirm we are on track regarding start of the first sprint regarding all GEs. Besides, we have to start analyzing the requests being received by the UC projects. The target goal is to show a significant progress on this during next week. I will explain what is the process we will follow to handle this. As always, we'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf Details for the webex will be sent later by Carlos. Best regards, -- Juanjo 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-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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: From jhierro at tid.es Fri Nov 18 09:52:11 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 18 Nov 2011 09:52:11 +0100 Subject: [Fiware-data] Fwd: URGENT: Slides for the review (status and more detailed template) In-Reply-To: <4EC55027.5050704@tid.es> References: <4EC55027.5050704@tid.es> Message-ID: <4EC61CBB.9060701@tid.es> Template of the presentation for the review 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: FI-WARE M6 Review chapter-template 11-11-17.ppt Type: application/vnd.ms-powerpoint Size: 701952 bytes Desc: not available URL: From ralli at tid.es Fri Nov 18 12:32:44 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 18 Nov 2011 12:32:44 +0100 Subject: [Fiware-data] Conference Call (Data/Context Follow up) - Notes Message-ID: Dear All, Find enclosed some notes collected by Grant and Myself with the main action points & tasks status as discussed before. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- 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: Notes_callconf20111118.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 40666 bytes Desc: Notes_callconf20111118.docx URL: From jhierro at tid.es Fri Nov 18 14:53:33 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 18 Nov 2011 14:53:33 +0100 Subject: [Fiware-data] Link to the tracker where UC projects are issuing their requests Message-ID: <4EC6635D.6090808@tid.es> https://forge.fi-ware.eu/tracker/?atid=163&group_id=7&func=browse You of course need to be log in for the link to work Cheers, -- Juanjo 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 Sun Nov 20 12:31:27 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 20 Nov 2011 12:31:27 +0100 Subject: [Fiware-data] Input for slides on Data/Context Management for the review Message-ID: <4EC8E50F.5010608@tid.es> Hi, We are still missing many of the contributions to the slides. I believe it was not that difficult, just few but carefully selected sentences. We have received only contributions from Siemens and Atos. Did we miss someone else's ? Please find enclosed a very early draft integrating the input so far and trying to elaborate how the slides about vision may look like. We have just put together, in susbsequent slides, your input on "target features for the first release" and we won't try to consolidate them into a single slide until we receive all your input, so please try to deliver it ASAP. Summary of requested input: @Telecom Italia: * Description of vision about Publish/Subscribe GE * Description of target features for the first release of the Publish/Subscribe GE * Input on Semmantic annotation. Try to make it short because we need to merge it with the Semmantic Application Support GE into a single slide @IBM: * Description of vision about CEP GE * Description of target features for the first release of the CEP GE @Telefonica: * Description of vision about BigData Analysis GE * Description of target features for the first release of the Publish/Subscribe GE @Thales: * Description of vision about Location Platform GE * Description of target features for the first release of the Location Platform GE @All: * Input for slide on "Early identification of Open Call Topics" Note that Carlos and me have to be at the airport no later than 18:30 ... so please send your contributions ASAP. If they arrive earlier than 17:00 Cheers, -- Juanjo ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE M6 Review Data_v3.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 1788440 bytes Desc: not available URL: From p.amon at siemens.com Sun Nov 20 15:46:23 2011 From: p.amon at siemens.com (Amon, Peter) Date: Sun, 20 Nov 2011 15:46:23 +0100 Subject: [Fiware-data] Input for slides on Data/Context Management for the review In-Reply-To: <4EC8E50F.5010608@tid.es> References: <4EC8E50F.5010608@tid.es> Message-ID: Dear Juanjo, all, just my two cents on the open call: In Torino, we discussed that we might miss technology on image analysis, since Siemens is focusing on video and Telecom Italia's focus is on the broker aspect. Kind regards Peter ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Sonntag, 20. November 2011 12:31 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Input for slides on Data/Context Management for the review Hi, We are still missing many of the contributions to the slides. I believe it was not that difficult, just few but carefully selected sentences. We have received only contributions from Siemens and Atos. Did we miss someone else's ? Please find enclosed a very early draft integrating the input so far and trying to elaborate how the slides about vision may look like. We have just put together, in susbsequent slides, your input on "target features for the first release" and we won't try to consolidate them into a single slide until we receive all your input, so please try to deliver it ASAP. Summary of requested input: @Telecom Italia: * Description of vision about Publish/Subscribe GE * Description of target features for the first release of the Publish/Subscribe GE * Input on Semmantic annotation. Try to make it short because we need to merge it with the Semmantic Application Support GE into a single slide @IBM: * Description of vision about CEP GE * Description of target features for the first release of the CEP GE @Telefonica: * Description of vision about BigData Analysis GE * Description of target features for the first release of the Publish/Subscribe GE @Thales: * Description of vision about Location Platform GE * Description of target features for the first release of the Location Platform GE @All: * Input for slide on "Early identification of Open Call Topics" Note that Carlos and me have to be at the airport no later than 18:30 ... so please send your contributions ASAP. If they arrive earlier than 17:00 Cheers, -- Juanjo ________________________________ 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: From jhierro at tid.es Sun Nov 20 16:06:08 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 20 Nov 2011 16:06:08 +0100 Subject: [Fiware-data] Input for slides on Data/Context Management for the review In-Reply-To: References: <4EC8E50F.5010608@tid.es> Message-ID: <4EC91760.9010101@tid.es> That's fine and I wouldn't be surprised if some of the UC project ask for that (I believe they have mentioned this in some of our AB meetings). Just a question mark ... Does Siemens already plan to provide video analysis capabilities together with the Multimedia Analysis GE as sort of "already pre-build/built-in" Video Analysis algorithms (such as "face recognition", for instance) ? What kind of video analysis would be those that will come along the Multimedia Analysis GE ? My understanding was that the asset provided by Siemens just provided the basic platform to program and run such analysis algorithms but developers had to indeed develop the algorithms on their own ... If we plan to provide a basic set of pre-build video analysis algorithms, it would be worth mentioning them ... Thanks in advance, -- Juanjo On 20/11/11 15:46, Amon, Peter wrote: Dear Juanjo, all, just my two cents on the open call: In Torino, we discussed that we might miss technology on image analysis, since Siemens is focusing on video and Telecom Italia's focus is on the broker aspect. Kind regards Peter ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Sonntag, 20. November 2011 12:31 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Input for slides on Data/Context Management for the review Hi, We are still missing many of the contributions to the slides. I believe it was not that difficult, just few but carefully selected sentences. We have received only contributions from Siemens and Atos. Did we miss someone else's ? Please find enclosed a very early draft integrating the input so far and trying to elaborate how the slides about vision may look like. We have just put together, in susbsequent slides, your input on "target features for the first release" and we won't try to consolidate them into a single slide until we receive all your input, so please try to deliver it ASAP. Summary of requested input: @Telecom Italia: * Description of vision about Publish/Subscribe GE * Description of target features for the first release of the Publish/Subscribe GE * Input on Semmantic annotation. Try to make it short because we need to merge it with the Semmantic Application Support GE into a single slide @IBM: * Description of vision about CEP GE * Description of target features for the first release of the CEP GE @Telefonica: * Description of vision about BigData Analysis GE * Description of target features for the first release of the Publish/Subscribe GE @Thales: * Description of vision about Location Platform GE * Description of target features for the first release of the Location Platform GE @All: * Input for slide on "Early identification of Open Call Topics" Note that Carlos and me have to be at the airport no later than 18:30 ... so please send your contributions ASAP. If they arrive earlier than 17:00 Cheers, -- Juanjo ________________________________ 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 ________________________________ 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: From p.amon at siemens.com Mon Nov 21 10:45:49 2011 From: p.amon at siemens.com (Amon, Peter) Date: Mon, 21 Nov 2011 10:45:49 +0100 Subject: [Fiware-data] Input for slides on Data/Context Management for the review In-Reply-To: <4EC91760.9010101@tid.es> References: <4EC8E50F.5010608@tid.es> <4EC91760.9010101@tid.es> Message-ID: We do not have face recognition in our asset. We will have change detection in a first release and object detection in a later release. Further feature extension of the asset is foreseen. In my understanding, the "basic platform" (for images) is more along the lines of TI's asset (MM broker). To me, it is still open, whether we will/should have two realizations of the GE (one for images, one for video) or not. The first option is probably easier to handle. Kind regards Peter ________________________________ From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Sonntag, 20. November 2011 16:06 To: Amon, Peter Cc: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Input for slides on Data/Context Management for the review That's fine and I wouldn't be surprised if some of the UC project ask for that (I believe they have mentioned this in some of our AB meetings). Just a question mark ... Does Siemens already plan to provide video analysis capabilities together with the Multimedia Analysis GE as sort of "already pre-build/built-in" Video Analysis algorithms (such as "face recognition", for instance) ? What kind of video analysis would be those that will come along the Multimedia Analysis GE ? My understanding was that the asset provided by Siemens just provided the basic platform to program and run such analysis algorithms but developers had to indeed develop the algorithms on their own ... If we plan to provide a basic set of pre-build video analysis algorithms, it would be worth mentioning them ... Thanks in advance, -- Juanjo On 20/11/11 15:46, Amon, Peter wrote: Dear Juanjo, all, just my two cents on the open call: In Torino, we discussed that we might miss technology on image analysis, since Siemens is focusing on video and Telecom Italia's focus is on the broker aspect. Kind regards Peter ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Sonntag, 20. November 2011 12:31 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Input for slides on Data/Context Management for the review Hi, We are still missing many of the contributions to the slides. I believe it was not that difficult, just few but carefully selected sentences. We have received only contributions from Siemens and Atos. Did we miss someone else's ? Please find enclosed a very early draft integrating the input so far and trying to elaborate how the slides about vision may look like. We have just put together, in susbsequent slides, your input on "target features for the first release" and we won't try to consolidate them into a single slide until we receive all your input, so please try to deliver it ASAP. Summary of requested input: @Telecom Italia: * Description of vision about Publish/Subscribe GE * Description of target features for the first release of the Publish/Subscribe GE * Input on Semmantic annotation. Try to make it short because we need to merge it with the Semmantic Application Support GE into a single slide @IBM: * Description of vision about CEP GE * Description of target features for the first release of the CEP GE @Telefonica: * Description of vision about BigData Analysis GE * Description of target features for the first release of the Publish/Subscribe GE @Thales: * Description of vision about Location Platform GE * Description of target features for the first release of the Location Platform GE @All: * Input for slide on "Early identification of Open Call Topics" Note that Carlos and me have to be at the airport no later than 18:30 ... so please send your contributions ASAP. If they arrive earlier than 17:00 Cheers, -- Juanjo ________________________________ 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 ________________________________ 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: From ralli at tid.es Mon Nov 21 12:17:05 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 21 Nov 2011 12:17:05 +0100 Subject: [Fiware-data] Latest Slides on Data/Context Management for the review In-Reply-To: References: <4EC8E50F.5010608@tid.es> <4EC91760.9010101@tid.es> Message-ID: <55F38830-238A-4B0F-8D7B-115F92948808@tid.es> Hi All, Find enclosed here the latest version of Data/Context Services (WP6) slides for the review. Your comments, mainly to your specific GE section, but also "Highs/lows" slide & "Open Calls" one, are very welcomed. Thanks in advance, Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- 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: FI-WARE M6 Review Data_v4.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 2479207 bytes Desc: FI-WARE M6 Review Data_v4.pptx URL: From ralli at tid.es Mon Nov 21 12:16:13 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 21 Nov 2011 12:16:13 +0100 Subject: [Fiware-data] Latest Slides on Data/Context Management for the review In-Reply-To: References: <4EC8E50F.5010608@tid.es> <4EC91760.9010101@tid.es> Message-ID: <8B533CCB-96E8-4164-A711-2E7CBFE8EFF3@tid.es> Hi All, Find enclosed here the latest version of Data/Context Services (WP6) slides for the review. Your comments, mainly to your specific GE section, but also "Highs/lows" slide & "Open Calls" one, are very welcomed. Thanks in advance, Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- 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: FI-WARE M6 Review Data_v4.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 2479207 bytes Desc: FI-WARE M6 Review Data_v4.pptx URL: From ralli at tid.es Mon Nov 21 15:48:54 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 21 Nov 2011 15:48:54 +0100 Subject: [Fiware-data] Latest Slides on Data/Context Management for the review - Version after overall Rehersal In-Reply-To: <8B533CCB-96E8-4164-A711-2E7CBFE8EFF3@tid.es> References: <4EC8E50F.5010608@tid.es> <4EC91760.9010101@tid.es> <8B533CCB-96E8-4164-A711-2E7CBFE8EFF3@tid.es> Message-ID: <1A4BB297-66F6-40EC-9E5C-9D5CF9505677@tid.es> Here we go, All comments during our review here in Brussels some minutes ago are included. I summarized (and gave a higher level description) the points on the slide describing the features expected for our first, release but I don't see easy to collapse the two slides in one without creating a misleading overcrowded slide. "Open calls" slide remains incomplete until we clarify how we deal with them. Thanks all for your comments and you are not late for some more whenever convenient ;-) Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 21/11/2011, a las 12:16, CARLOS RALLI UCENDO escribi?: > Hi All, > > Find enclosed here the latest version of Data/Context Services (WP6) slides for the review. > > Your comments, mainly to your specific GE section, but also "Highs/lows" slide & "Open Calls" one, are very welcomed. > > Thanks in advance, > Best regards, > -- > ------------------------------------------------------- > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Telef?nica I+D SAU > Madrid, Spain > ------------------------------------------------------- > > > 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: FI-WARE M6 Review Data_v6.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 2480405 bytes Desc: FI-WARE M6 Review Data_v6.pptx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From ralli at tid.es Mon Nov 21 18:54:00 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 21 Nov 2011 18:54:00 +0100 Subject: [Fiware-data] Latest Slides on Data/Context Management for the review - Version 7 In-Reply-To: <1A4BB297-66F6-40EC-9E5C-9D5CF9505677@tid.es> References: <4EC8E50F.5010608@tid.es> <4EC91760.9010101@tid.es> <8B533CCB-96E8-4164-A711-2E7CBFE8EFF3@tid.es> <1A4BB297-66F6-40EC-9E5C-9D5CF9505677@tid.es> Message-ID: Version 7 is ready and attached. Juanjo and myself will work out the latest version later, but this one is quite final thanks to your responsive support today and the previous days. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 21/11/2011, a las 15:48, CARLOS RALLI UCENDO escribi?: > Here we go, > > All comments during our review here in Brussels some minutes ago are included. > I summarized (and gave a higher level description) the points on the slide describing the features expected for our first, release but I don't see easy to collapse the two slides in one without creating a misleading overcrowded slide. > > "Open calls" slide remains incomplete until we clarify how we deal with them. > > Thanks all for your comments and you are not late for some more whenever convenient ;-) > Best regards, > -- > ------------------------------------------------------- > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Telef?nica I+D SAU > Madrid, Spain > ------------------------------------------------------- > > El 21/11/2011, a las 12:16, CARLOS RALLI UCENDO escribi?: > >> Hi All, >> >> Find enclosed here the latest version of Data/Context Services (WP6) slides for the review. >> >> Your comments, mainly to your specific GE section, but also "Highs/lows" slide & "Open Calls" one, are very welcomed. >> >> Thanks in advance, >> Best regards, >> -- >> ------------------------------------------------------- >> Carlos Ralli Ucendo (ralli at tid.es) >> Cell: +34696923588 >> Telef?nica I+D SAU >> Madrid, Spain >> ------------------------------------------------------- >> >> >> > 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: FI-WARE M6 Review Data_v7.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 2400257 bytes Desc: FI-WARE M6 Review Data_v7.pptx URL: From boris.moltchanov at telecomitalia.it Tue Nov 22 17:13:55 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 22 Nov 2011 17:13:55 +0100 Subject: [Fiware-data] Latest Slides on Data/Context Management for the review - Version 7 In-Reply-To: References: <4EC8E50F.5010608@tid.es> <4EC91760.9010101@tid.es> <8B533CCB-96E8-4164-A711-2E7CBFE8EFF3@tid.es> <1A4BB297-66F6-40EC-9E5C-9D5CF9505677@tid.es> Message-ID: Hi, finally was able to read ppt slides. Few comments, even if maybe too late: - don't we have a semantic annotation GE? In the slides I see meta-data preparation and meta-data annotator GEs; - do we have location or localization GE? I remember the localization GE, but maybe it was changed and I'm not updated. A part of the image recognition I believe that also semantic model creation could be another relevant topic for an OpenCall. Maybe also others, but for the moment I don't remember others and will contribute on this matter to the opencall preparation. Best Regards, Boris -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of CARLOS RALLI UCENDO Sent: Monday, November 21, 2011 6:54 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Latest Slides on Data/Context Management for the review - Version 7 Version 7 is ready and attached. Juanjo and myself will work out the latest version later, but this one is quite final thanks to your responsive support today and the previous days. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 21/11/2011, a las 15:48, CARLOS RALLI UCENDO escribi?: > Here we go, > > All comments during our review here in Brussels some minutes ago are included. > I summarized (and gave a higher level description) the points on the slide describing the features expected for our first, release but I don't see easy to collapse the two slides in one without creating a misleading overcrowded slide. > > "Open calls" slide remains incomplete until we clarify how we deal with them. > > Thanks all for your comments and you are not late for some more > whenever convenient ;-) Best regards, > -- > ------------------------------------------------------- > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Telef?nica I+D SAU > Madrid, Spain > ------------------------------------------------------- > > El 21/11/2011, a las 12:16, CARLOS RALLI UCENDO escribi?: > >> Hi All, >> >> Find enclosed here the latest version of Data/Context Services (WP6) slides for the review. >> >> Your comments, mainly to your specific GE section, but also "Highs/lows" slide & "Open Calls" one, are very welcomed. >> >> Thanks in advance, >> Best regards, >> -- >> ------------------------------------------------------- >> Carlos Ralli Ucendo (ralli at tid.es) >> Cell: +34696923588 >> Telef?nica I+D SAU >> Madrid, Spain >> ------------------------------------------------------- >> >> >> > 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. From jhierro at tid.es Fri Nov 25 09:21:24 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 25 Nov 2011 09:21:24 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpa] Fwd: RE: Review report In-Reply-To: <4ECD281C.6010505@tid.es> References: <4ECD281C.6010505@tid.es> Message-ID: <4ECF5004.1030800@tid.es> -------- Original Message -------- Subject: [Fiware-wpa] Fwd: RE: Review report Date: Wed, 23 Nov 2011 18:06:36 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, I asked Arian to send us at least a brief summary of the informal feedback given after the review meeting. Please find it below. Cheers, -- Juanjo -------- Original Message -------- Subject: RE: Review report Date: Wed, 23 Nov 2011 16:26:23 +0100 From: Arian.ZWEGERS at ec.europa.eu To: JUAN JOSE HIERRO SUREDA CC: INFSO-ICT-285248 at ec.europa.eu Dear Juanjo, As requested, see some points of the informal feedback given after the review meeting below. About deliverables: 1) the reviewers did not indicate that any deliverable would be rejected. This does not mean that all deliverables will be accepted. 2) regarding the prototype deliverables D9.1.1 and D12.1, there is the additional issue about the submission. I plan to address this only in 2012. Best regards, Arian. ======================================================== Informal feedback after FI-WARE first review * "This is a good FP7 project" * Commitment, focus on pragmatism. * The dialogue between the UCs and FI-WARE seems to be happening. * There is a focus on low-hanging fruits. Focus should be on tackling the difficult parts first. * Technology identified is OK. Technology is the easy part though. The softer issues (third party innovation enablement) are much more difficult and much more important. The success of the PPP is not so much dependent on the partners, but more on third party innovation. * The overall risk is not so much that the project does not do what it plans but that it does not do what is industrially and market-wise relevant. It is common for many projects to deliver technology, put it on the shelf, and deliver more technology. * How to make sure that the companies involved are solidly behind the work in the project? How to prevent that the work is carried out by a number of people in an organisation, without anybody else in the organisation knowing about it? The consortium should bring in other departments of the partners concerned in the project. * There was a slide with the project objective and the 'real objective', which focused on generating money. This is the correct starting point. The exploitation plan in month 12 should not only be about plans, but also about the actual activities within the partners, and also how different user communities are targeted. We expect to see such activities in that report. If FI-WARE is really one of the flagship projects, the companies should get behind the project. Now you have the UCs and the technology together in the PPP, the industries have to get squarely behind it. We don't want an exploitation plan like we see in a normal IP. We state again and again that results have to be useful. This can not be done by only research and technology people. * Results should get to the market quickly, within 3-5 years after the start of the project. The agile approach should result in having something available soon. Nowadays, software is in continuous beta-mode. It's a kind of direct marketing by the technologists, rapid and direct. IPR conditions are essential. This should not be blocking the fast provision of results. * It is also largely a matter of fud, fear/uncertainty/doubt: "trust us, we will deliver in a few months". It is also a marketing story. * Who is FI-WARE focusing on? The guys in the garage? Then compare with Apple and Google, but that is a maturing market, even though there is a lot of dynamism. As a new entrant, new unique selling points must be provided. Where is the selling point in FI-WARE? An opportunity might be in apps that can work together in a larger whole, services. Furthermore, apps are mostly for consumers, but businesses need something more, e.g. spanning the company boundary (which involves dealing with security issues, etc). These are perhaps not the traditional apps we are talking about now. * The distinction between Generic and Specific Enablers will be decided case by case. But you need rules, guidelines. This distinction has also an IPR dimension, and touches upon standardisation. GEs should be prime candidates for standardisation. The distinction is also relevant for the Open Call. Proposers need such kind of information. A 3-page document will not be enough. * It is not clear to us to what extent UCs have a voice in what is in the open call? Furthermore, Jose's comments about the very limited set of potential proposers are absolutely dangerous. There is more outside. Don't benchmark yourself with e.g. Bonfire. It's also a great opportunity to disseminate. Besides, half of the efforts in year 3 will be by partners that are not there at the moment. In short, take it more seriously. * At the moment, there is a lot of efforts on the leaders. Control and work should be spread a bit. If JJH hits a tree, the project stops. Peter Fatelnig: 150 people go to work for the PPP each day. 75 people go to work on FI-WARE every day. ________________________________ 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 ________________________________ 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: From ralli at tid.es Mon Nov 28 08:47:48 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 28 Nov 2011 08:47:48 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpl] Next steps References: <4ECFB12D.1050304@tid.es> Message-ID: Dear WP participants, Find enclosed below some tasks we plan to start with right after the review held last week. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- Inicio del mensaje reenviado: De: JUAN JOSE HIERRO SUREDA > Fecha: 25 de noviembre de 2011 16:15:57 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpl] Next steps Hi, We shouldn't get relaxed right after our official review. We had to work hard during last days to succeed in the review but now that we have overcome this milestone, we have to proceed with what comes next: a) Review of results of the first Sprint and planning of second Sprint. b) Deal with requests from UC projects. We will definitively push this in the next weeks and a number of agreements have been reached in the FI-PPP AB meeting that has just closed in Munich. c) Based on results of b) and our own analysis, come up with a first list of topics for the first Open Call d) Start activities regarding our next deliverable (Architecture Specifications) Along the weekend and Monday, I will forward you more concrete info about how to deal with these matters. Best regards, -- Juanjo 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: From mcp at tid.es Wed Nov 30 13:34:15 2011 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 30 Nov 2011 13:34:15 +0100 Subject: [Fiware-data] Need your help: vote for a submission from FI-WARE Message-ID: <4ED622C7.4030905@tid.es> Dear all, Acting on behalf of FI-WARE, Thierry Nagellen has just submitted a topic for workshop in the Future Internet Assembly to be celebrated in Aalborg. This topic could have the FI PPP as sponsor and we should have technical presentations (from FI-Ware partners but also from other contributors as Smart Santander or IoT-A projects) and some new Use Cases to improve the requirements picture We need your support to get there and there is very little time left. We would appreciate it if you could go to this link, login with a gmail user and vote if you like it: http://www.future-internet.eu/home/shape-fia.html?modSeries=111dab&modTopic=40&modSubmission=5c4fe7 Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- 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