From jhierro at tid.es Thu Dec 1 09:20:05 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Thu, 01 Dec 2011 09:20:05 +0100 Subject: [Fiware-data] Data/Context WP coordination Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A1B@EXCLU2K7.hi.inet> When: Friday, December 02, 2011 11:30 AM-1:00 PM. 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: 2407 bytes Desc: not available URL: From jhierro at tid.es Thu Dec 1 09:20:43 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Thu, 01 Dec 2011 09:20:43 +0100 Subject: [Fiware-data] Data/Context WP coordination Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A1C@EXCLU2K7.hi.inet> When: Monday, December 05, 2011 9:00 AM-10:30 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: 2407 bytes Desc: not available URL: From ralli at tid.es Thu Dec 1 10:51:02 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 01 Dec 2011 10:51:02 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpl] IMPORTANT: Approach for Architecture Specification Deliverable References: <4ED63FF2.6020400@tid.es> Message-ID: Dear WP colleagues, The first release of "FI-WARE Architecture & Technical Roadmap" deliverable is one of our remarkable tasks to start with at this point, so we will be able to deliver by end of January 2012 (M9) as stated in our contract/DoW. Find enclosed below the overall approach suggested by Juanjo to all WPs, so that we stand the more pragmatic we can by partially working out part of the GE Open specifications committed for M12. Basically, the proposal is to elaborate our architecture by describing in detail how each specific GE will actually interact with any other entities in terms of data type, operations and interfaces. Let me suggest you to read carefully Juanjo's proposal & analyze the attached file related to OMG's set of CORBA Services Specifications as a reference to the material to deliver per each specific GE. Feedback/comments or specific issues at our WP level are welcomed. Thanks in advance for your efforts. 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: 30 de noviembre de 2011 15:38:42 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpl] IMPORTANT: Approach for Architecture Specification Deliverable Hi all, As you know, we have to start working on the Architecture Specifications, which is one of the deliverables that is due in month 9, that is, end of January. My intention is to adopt a pragmatic approach, trying to generate something that can be integrated as part of the GE Open Specifications that we have to produce by month 12. My vision is that all GE Open Specifications should start with a chapter where an overview of the envisioned Architecture for the GE is described. While style would be narrative, the description should be enough concrete, i.e., formulated over actual data type, interface and operation names and elaborating on the base interaction scenarios involving the different entities exporting the defined interfaces. Then, after that chapter, the detailed specification of all data types and interfaces with their operations, are provided (this including signature of operations and accurate description of expected behaviour linked to operations) Then, the Architecture Specification deliverable would be just the result of developing this overview chapter. But nothing better than an example, so let me use one taken from OMG's set of CORBA Services Specifications. Along my many years involved in different standardization efforts, I have found that OMG CORBA Service specs are rather comprehensive and close to what programmers (our ultimate customers!) love to see. Please find enclosed the CORBA Event Service Specifications. What I would then select as the Architecture description are the contents of the following sections: * The whole chapter 1 * Section 2.2 and 2.4 (which some people may have argued should have been included in chapter 1 :-) Note that anyone who reads the mentioned sections would get a CLEAR picture of what is the Architecture of the service and what are going to be the entities and interfaces/operations that will be supported in a compliant implementation. The conceptual and programming model would be also rather clear from a programmer's perspective. Therefore, rather valuable information for an application developer perspective which is what really should matter to us. A side benefit is that what will remain as pending regarding GE Open Specifications will be less, that is, the detailed specification of data types and interfaces/operations. One thing that we will have to define is the set of conventions that we should all follow whenever we need to draw any figure, like figures 1-x or 2-x. For this, Thomas and me will come soon to you with a proposal in short time. Please take your time to analyze this carefully and formulate any question you may have. From now on, I assume that you will start planning activities in Sprint 2 and 3 dealing with development of these specifications within each of your chapters. This may well take the form of Work Items in the tracker. 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 ________________________________ 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: Event Service Specification 04-10-02.pdf Type: application/pdf Size: 515254 bytes Desc: Event Service Specification 04-10-02.pdf URL: -------------- 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 Dec 1 19:34:12 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 01 Dec 2011 19:34:12 +0100 Subject: [Fiware-data] Follow-up confcall Message-ID: <4ED7C8A4.3060902@tid.es> Hi all, We had to re-schedule the follow-up confcall because it would collide with a FI-WARE PCC meeting that has been allocated at the same time ... I have re-schedule it to happen on Monday Dec 5th from 09:00am to 10:30am. Dial-in and webex bridge details will be as always. You should have planned the Work Items and User Stories you plan to address during the second sprint (December), so one of the main topics we will review during our confcall will be that planning as well as the results of the first sprint. Please come to the meeting with these matters well prepared. In addition, we will elaborate on how to approach the Architecture Specifications (deliverable due on month 9) Sorry for the short notice about this change. Those that definitively cannot attend the confcall because of the change, please send an email elaborating on the sprints (results of the first one and planning for the second) and formulate any question you may have regarding the deliverable on Architecture Specifications. 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 boris.moltchanov at telecomitalia.it Fri Dec 2 09:17:03 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 2 Dec 2011 09:17:03 +0100 Subject: [Fiware-data] Follow-up confcall In-Reply-To: <4ED7C8A4.3060902@tid.es> References: <4ED7C8A4.3060902@tid.es> Message-ID: Dear All, unfortunately (specially for myself) I am unavailable for the Monday morning call. Sorry. 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 Juanjo Hierro Sent: Thursday, December 01, 2011 7:34 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Follow-up confcall Hi all, We had to re-schedule the follow-up confcall because it would collide with a FI-WARE PCC meeting that has been allocated at the same time ... I have re-schedule it to happen on Monday Dec 5th from 09:00am to 10:30am. Dial-in and webex bridge details will be as always. You should have planned the Work Items and User Stories you plan to address during the second sprint (December), so one of the main topics we will review during our confcall will be that planning as well as the results of the first sprint. Please come to the meeting with these matters well prepared. In addition, we will elaborate on how to approach the Architecture Specifications (deliverable due on month 9) Sorry for the short notice about this change. Those that definitively cannot attend the confcall because of the change, please send an email elaborating on the sprints (results of the first one and planning for the second) and formulate any question you may have regarding the deliverable on Architecture Specifications. 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 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 ralli at tid.es Fri Dec 2 10:06:39 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 02 Dec 2011 10:06:39 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpl] IMPORTANT: Handling tickets issued by the UC projects References: <4ED50329.4050600@tid.es> Message-ID: Dear WP colleagues, Be aware that Use-Case projects have already started to place requirements for the core platform by the means of tickets related to specific Theme/Epic/Feature requests. After a first round pre-processing, tickets are being assigned to WPLs and, possibly in turn to project members. The whole process workflow and how-to is now part of the project Handbook and available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_handle_FI-WARE_Theme/Epic/Feature_requests_issued_by_UC_projects Our target is to process as many tickets as possible before the next FI-PPP AB meeting, scheduled for December 15. Based on the analysis, we should be able to identify topics for the first Open Call. Thanks for your cooperation to meet our deadline. Should you have any comment or issue, please let us know. 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 -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Dec 5 08:29:10 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 05 Dec 2011 08:29:10 +0100 Subject: [Fiware-data] Little delay in starting our follow-up confcall Message-ID: <4EDC72C6.6020008@tid.es> Hi all, Please let's start at 09:15am instead of 09:00am ... Powwownow dial-in details as always. Apologizes for the inconvenience. 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 Mon Dec 5 09:01:39 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 05 Dec 2011 09:01:39 +0100 Subject: [Fiware-data] Webex Details FI-WARE Data/Context Conf Call References: <4EDC710E.20706@tid.es> Message-ID: Here you are, . Topic: FI-WARE Data/Context Conf Call Date: Monday, December 5, 2011 Time: 8:45 am, Europe Time (Paris, GMT+01:00) Meeting Number: 962 158 730 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=188727272&UID=0&PW=NY2QyN2M2NDVj&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=188727272&UID=0&PW=NY2QyN2M2NDVj&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 ________________________________ 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 Wed Dec 7 10:27:49 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 07 Dec 2011 10:27:49 +0100 Subject: [Fiware-data] Regular follow-up confcall this Friday Message-ID: <4EDF3195.5040400@tid.es> Hi, I would like to propose that we start earlier (09:00am) this Friday because I would need to close at 10:00am sharp ... I will update the calendar invitation accordingly. Hope this is not an issue on your side. If it is an issue, let me know and we'll try to find a solution. 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 Wed Dec 7 10:28:07 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 07 Dec 2011 10:28:07 +0100 Subject: [Fiware-data] Data/Context WP coordination Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A26@EXCLU2K7.hi.inet> When: Friday, December 16, 2011 9:00 AM-10:30 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: 2407 bytes Desc: not available URL: From jhierro at tid.es Wed Dec 7 10:28:26 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 07 Dec 2011 10:28:26 +0100 Subject: [Fiware-data] Data/Context WP coordination Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A27@EXCLU2K7.hi.inet> When: Friday, December 16, 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: 2407 bytes Desc: not available URL: From jhierro at tid.es Wed Dec 7 10:28:38 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 07 Dec 2011 10:28:38 +0100 Subject: [Fiware-data] Data/Context WP coordination Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A28@EXCLU2K7.hi.inet> When: Friday, December 09, 2011 9:00 AM-10:30 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: 2407 bytes Desc: not available URL: From jhierro at tid.es Wed Dec 7 10:58:12 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 07 Dec 2011 10:58:12 +0100 Subject: [Fiware-data] [Fiware-iot] Basic examples OGC- ETSI.M2M In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA58AA54558@EXMB05CMS.surrey.ac.uk> References: <4ED75D0E.1080506@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCA58AA54558@EXMB05CMS.surrey.ac.uk> Message-ID: <4EDF38B4.4080202@tid.es> Hi Tarek, The partners involved in development of the Publish/Subscribe Broker GE within the Data/Context Management chapter (Telecom Italia and Orange) are trying to deal with incorporation of semantic meta-data linked to events (context elements) and published through the Publish/Subscribe Broker GE. I copy Boris Moltchanov from Telecom Italia who is dealing with coordination of the developments linked to this GE. While I guess that having two implementations of the NGSI spec may be Ok (though we have to find out how to justify it) what certainly has to be achieved is that the final APIs finally offered to the application developer are the same, so that applications are not programmed in a different way depending on what Publish/Subscriber Broker GE it connects to. And this doesn't only affect number and name of operations but structure of data (which certainly affects the signature of operations). I would suggest that we setup a dedicated thread of discussion over the email where each can explain its respective approach and we can reach the necessary alignment. Would you believe that we should link that thread of discussion through both the fiware-data and fiware-iot mailing lists ? I guess not all members in that list want to get spammed ;-) My current thinking would be that of creating a dedicated mailing list for discussion about the NGSI interface implementation were partners involved in trying to implement this interface in both the FI-WARE IoT and FI-WARE Data chapters would be members, besides the respective WPLs, WPAs, the deputy chief architect of FI-WARE and myself. Your feedback is welcome. Best regards, -- Juanjo On 06/12/11 18:33, T.Elsaleh at surrey.ac.uk wrote: Hello All, I would like to describe the asset proposed by UniS and the activities we are currently conducting. We are working on developing an RDF representation of OMA-NGSI for IoT entities and resources. This will be done according to the information models that we have developed for the IoTA project. The following is a list of the planned and ongoing activities: ? Creating entity/resource templates in RDF format based on OMA-NGSI representation. ? Providing a repository for the RDF data based on our Linked Sensor Data Platform. ? Developing RESTful interfaces for publish/access/query ? Supporting SPARQL query over the representations ? We can also work with other partners to demonstrate mapping with other description models e.g. SensorML, by annotating SensorML using OMA-NGSI based RDF data. Please let us know if you have any concerns and comments. Best regards, Tarek Elsaleh Research Assistant Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: 01 December 2011 13:03 To: rheras at tid.es; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Basic examples OGC- ETSI.M2M Hi all, Some comments about our decisions and next steps : 1 ? Based on the collective work done in October we have decided to use for the time being OMA-NGSI and ETSI M2M for northbound and southbound API and to establish relationships with OGC but also with IoT-A and ETSI M2M to evaluate further improvements 2 ? We are working on Future Internet and it is not so risky to choose ETSI M2M based on ETSI M2M community which is very large and because this community has reached a first stable version of technical specifications. 3 ? Focusing today on OGC should be also a bad signal for UC projects which are not using OGC but some other standards. Typically, the existing structure in OGC is like the EPC Global structure and the 3 related projects would not adopt our GE if we have to encapsulate EPC in OGC, and this is the same concern for ONVIF regarding OGC. We have to provide an agnostic approach regarding existing standards. 4 ? OMA-NGSI provides a very high level description and we have to explain/comment this description to find a generic format valuable for all the other standards description (OGC, ONVIF, EPC?) which will provide this agnostic layer. 5 ? Some partners interested in some dedicated standards have to demonstrate, through NGSI and ETSI M2M implementation that the related standards could provide advanced features and and could propose NGSI and ETSI M2M improvements. 6 - In the same way, we could push improvements to the other standards for dedicated issues as security or nomadic things So at the end of November, we have to define these NGSI details (so provide your feedback regarding your knowledge in several standards) and to implement the first functions for ETSI M2M on the selected assets as provided by the task leaders. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Ricardo de las Heras Envoy? : jeudi 1 d?cembre 2011 11:55 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Basic examples OGC- ETSI.M2M Dear partners, as we agreed in the last conf. call, TID have prepared some examples about how we use the OGC standard (SensorML+ O&M) within the IDAS platform. Additionally I attach you a simple example about how the ETSI standard could work as a container of an OGC descriptive XML document, but this option is not implemented yet in the IDAS platform, although we are considering to include it in the medium-long term roadmap. Our main concert in this way is about how the industry will accept it, at this time we don't know any sensor/device ETSI compliant manufacturer, this is a critical point for the final success of the ETSI standard, so at present I think this would be a risky bet. Please provide any type of additional information you have about this issue. thanks, best regards, RHer at s. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1873 / Virus Database: 2102/4650 - Release Date: 12/01/11 ________________________________ 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 GUYSH at il.ibm.com Fri Dec 9 09:29:04 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Fri, 9 Dec 2011 10:29:04 +0200 Subject: [Fiware-data] Rescheduled: Data/Context WP coordination (16 Dec 09:00 CET) In-Reply-To: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A26@EXCLU2K7.hi.inet> References: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A26@EXCLU2K7.hi.inet> Message-ID: In case the list of numbers on web site doesnt work for POW WOW This number always works for me +44 844 4 73 73 73 PIN: 050662 Guy Sharon Manager Event-based Middleware & Solutions Group Event-based Middleware & Solutions phone : +972 4 8296587 mobile : +972 54 6976417 address : IBM R&D Labs in Israel, Haifa University Campus, Mount Carmel, Haifa, 31905, Israel email : guysh at il.ibm.com Rescheduled: Data/Context WP coordination Fri 16/12/2011 10:00 - 11:30 (Repeats) Attendance is required for Guy Sharon Chair: jhierro at tid.es Sent By: fiware-data-bounces at lists.fi-ware.eu No Location Information jhierro at tid.es jhierro has rescheduled this meeting. You have not yet responded. Repeats This entry repeats Required: ralli at tid.es, fiware-data at lists.fi-ware.eu Optional: Tali Yatzkar-Haham/Haifa/IBM, fano.ramparany at orange.com Time zones: This entry was created in a different time zone. The time in that time zone is: Fri 16/12/2011 9:00 CET10:30 CET When: Friday, December 16, 2011 9:00 AM-10:30 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 [attachment "" deleted by Guy Sharon/Haifa/IBM] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: From jhierro at tid.es Sun Dec 11 08:54:32 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 11 Dec 2011 08:54:32 +0100 Subject: [Fiware-data] IMPORTANT: Assignment of UC project tickets linked to the Complex Event Processing Engine Message-ID: <4EE461B8.6030203@tid.es> Dear all, I have started assigning you some of the tickets being issued by the UC projects. My understanding is that you should have received an email once a ticket has been assigned to you. Please confirm. Anyways, I will provide a list of assignment I have made later today (probably this evening). If you are not receiving emails, please go to the "FI-WARE Themes/Epic/Feature request" tracker linked to the FI-WARE tracker on FusionForge and check what tickets may have been assigned to you. In my opinion, most of the tickets correspond to functionality that either should be supported already in the baseline asset linked to the GE (at, least IMHO) or is currently in our plan to support it in FI-WARE. I have provided a first response to those tickets (based on the "Probably covered but requires further analysis" canned response) but passed them into the "Under Evaluation by FI-WARE" status and assigned them to you. Please quickly check them and decide whether they should be transitioned to the "Already Covered by Baseline Asset" or "Covered by FI-WARE Backlog Entries" Status. Before handling any ticket, please check the tutorial on How to handle FI-WARE Theme/Epic/Feature requests issued by UC projects at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_handle_FI-WARE_Theme/Epic/Feature_requests_issued_by_UC_projects IMPORTANT NOTE: I remind you that there is a serious bug currently on the tracker (under analysis by the FusionForge support team) which implies you SHOULD NOT make (or build) a query on the tracker asking for tickets assigned to some given person. If you establish a condition in the request about the assignee, then it will return an error, but more importantly, you won't be able to get access to the tracker any longer because that query (which returns an error message) will be your default query, so you get an error whenever you try to access the tracker :-( 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 Dec 11 09:24:47 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 11 Dec 2011 09:24:47 +0100 Subject: [Fiware-data] IMPORTANT: Assignment of UC project tickets linked to the Complex Event Processing Engine In-Reply-To: <4EE461B8.6030203@tid.es> References: <4EE461B8.6030203@tid.es> Message-ID: <4EE468CF.8060003@tid.es> I have added some comments to many of the tickets, so don't forget to revise them. If you have any doubt, don't hesitate to ask through this list before making any action. We need to handle tickets carefully so we don't deliver wrong messages to UC projects. Cheers, -- Juanjo On 11/12/11 08:54, Juanjo Hierro wrote: > Dear all, > > I have started assigning you some of the tickets being issued by the > UC projects. > > My understanding is that you should have received an email once a > ticket has been assigned to you. Please confirm. Anyways, I will > provide a list of assignment I have made later today (probably this > evening). If you are not receiving emails, please go to the "FI-WARE > Themes/Epic/Feature request" tracker linked to the FI-WARE tracker on > FusionForge and check what tickets may have been assigned to you. > > In my opinion, most of the tickets correspond to functionality that > either should be supported already in the baseline asset linked to the > GE (at, least IMHO) or is currently in our plan to support it in > FI-WARE. I have provided a first response to those tickets (based > on the "Probably covered but requires further analysis" canned > response) but passed them into the "Under Evaluation by FI-WARE" > status and assigned them to you. Please quickly check them and > decide whether they should be transitioned to the "Already Covered by > Baseline Asset" or "Covered by FI-WARE Backlog Entries" Status. > Before handling any ticket, please check the tutorial on How to handle > FI-WARE Theme/Epic/Feature requests issued by UC projects at: > > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_handle_FI-WARE_Theme/Epic/Feature_requests_issued_by_UC_projects > > > IMPORTANT NOTE: I remind you that there is a serious bug currently > on the tracker (under analysis by the FusionForge support team) which > implies you SHOULD NOT make (or build) a query on the tracker asking > for tickets assigned to some given person. If you establish a > condition in the request about the assignee, then it will return an > error, but more importantly, you won't be able to get access to the > tracker any longer because that query (which returns an error message) > will be your default query, so you get an error whenever you try to > access the tracker :-( > > > > 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 Dec 11 09:29:42 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 11 Dec 2011 09:29:42 +0100 Subject: [Fiware-data] IMPORTANT: Assignment of UC project tickets linked to the Complex Event Processing Engine In-Reply-To: <4EE468CF.8060003@tid.es> References: <4EE461B8.6030203@tid.es> <4EE468CF.8060003@tid.es> Message-ID: <4EE469F6.1090605@tid.es> Don't forget also to check the entry created by the UC project for he ticket on the FI-WARE Wiki. The link is provided as one of the fields of the ticket. Sometimes there is more detailed information provided there. Cheers, -- Juanjo On 11/12/11 09:24, Juanjo Hierro wrote: > > I have added some comments to many of the tickets, so don't forget > to revise them. > > If you have any doubt, don't hesitate to ask through this list > before making any action. We need to handle tickets carefully so we > don't deliver wrong messages to UC projects. > > Cheers, > > -- Juanjo > > On 11/12/11 08:54, Juanjo Hierro wrote: >> Dear all, >> >> I have started assigning you some of the tickets being issued by >> the UC projects. >> >> My understanding is that you should have received an email once a >> ticket has been assigned to you. Please confirm. Anyways, I will >> provide a list of assignment I have made later today (probably this >> evening). If you are not receiving emails, please go to the >> "FI-WARE Themes/Epic/Feature request" tracker linked to the FI-WARE >> tracker on FusionForge and check what tickets may have been assigned >> to you. >> >> In my opinion, most of the tickets correspond to functionality that >> either should be supported already in the baseline asset linked to >> the GE (at, least IMHO) or is currently in our plan to support it in >> FI-WARE. I have provided a first response to those tickets (based >> on the "Probably covered but requires further analysis" canned >> response) but passed them into the "Under Evaluation by FI-WARE" >> status and assigned them to you. Please quickly check them and >> decide whether they should be transitioned to the "Already Covered by >> Baseline Asset" or "Covered by FI-WARE Backlog Entries" Status. >> Before handling any ticket, please check the tutorial on How to >> handle FI-WARE Theme/Epic/Feature requests issued by UC projects at: >> >> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_handle_FI-WARE_Theme/Epic/Feature_requests_issued_by_UC_projects >> >> >> IMPORTANT NOTE: I remind you that there is a serious bug currently >> on the tracker (under analysis by the FusionForge support team) which >> implies you SHOULD NOT make (or build) a query on the tracker asking >> for tickets assigned to some given person. If you establish a >> condition in the request about the assignee, then it will return an >> error, but more importantly, you won't be able to get access to the >> tracker any longer because that query (which returns an error >> message) will be your default query, so you get an error whenever you >> try to access the tracker :-( >> >> >> >> 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 Thu Dec 15 19:59:16 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 15 Dec 2011 19:59:16 +0100 Subject: [Fiware-data] Follow-up confcall tomorrow - Guy and Boris important to read Message-ID: <4EEA4384.7060900@tid.es> Hi all, We will cancel the follow-up confcall tomorrow. I will setup a doodle to find a more suitable time slot on Monday/Tuesday/Wednesday. However, I want to use the slot IBM and Telecom Italia should have bookend in their agenda for tomorrow :-) The idea would be to devote the slot tomorrow to discuss about the issue of overlapping GEs with the IoT chapter. Please, Guy and Boris: confirm your availability. Apologizes to the rest for the short notice. Best regards, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro 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 Fri Dec 16 08:43:09 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 16 Dec 2011 08:43:09 +0100 Subject: [Fiware-data] Follow-up confcall tomorrow - Guy and Boris important to read In-Reply-To: <4EEA4384.7060900@tid.es> References: <4EEA4384.7060900@tid.es> Message-ID: Guy, Boris, Please, find enclosed the details to connect to the webex for today's meeting: Topic: Meeting with IBM/TI Date: Friday, December 16, 2011 Time: 9:15 am, Europe Time (Paris, GMT+01:00) Meeting Number: 966 611 709 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=189144427&UID=0&PW=NZjg4YWExZTJm&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=189144427&UID=0&PW=NZjg4YWExZTJm&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: Webex5000 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=189144427&UID=0&ICS=MI&LD=1&RD=2&ST=1&SHA2=9Th3bhbgR9CoVL/CEap4PkL0D3SESr7ayEufdyyMQrQ=&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. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 15/12/2011, a las 19:59, Juanjo Hierro escribi?: Hi all, We will cancel the follow-up confcall tomorrow. I will setup a doodle to find a more suitable time slot on Monday/Tuesday/Wednesday. However, I want to use the slot IBM and Telecom Italia should have bookend in their agenda for tomorrow :-) The idea would be to devote the slot tomorrow to discuss about the issue of overlapping GEs with the IoT chapter. Please, Guy and Boris: confirm your availability. Apologizes to the rest for the short notice. Best regards, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro 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 Dec 16 09:50:49 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 16 Dec 2011 09:50:49 +0100 Subject: [Fiware-data] Follow-up confcall tomorrow - Guy and Boris important to read In-Reply-To: References: <4EEA4384.7060900@tid.es> Message-ID: <4EEB0669.8060100@tid.es> As mentioned, only TI and Telefonica will meet taking advantage of the slot. Boris, please find the Webex details below. We will use it during our call. ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro On 16/12/11 08:43, CARLOS RALLI UCENDO wrote: Guy, Boris, Please, find enclosed the details to connect to the webex for today's meeting: Topic: Meeting with IBM/TI Date: Friday, December 16, 2011 Time: 9:15 am, Europe Time (Paris, GMT+01:00) Meeting Number: 966 611 709 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=189144427&UID=0&PW=NZjg4YWExZTJm&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=189144427&UID=0&PW=NZjg4YWExZTJm&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: Webex5000 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=189144427&UID=0&ICS=MI&LD=1&RD=2&ST=1&SHA2=9Th3bhbgR9CoVL/CEap4PkL0D3SESr7ayEufdyyMQrQ=&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. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 15/12/2011, a las 19:59, Juanjo Hierro escribi?: Hi all, We will cancel the follow-up confcall tomorrow. I will setup a doodle to find a more suitable time slot on Monday/Tuesday/Wednesday. However, I want to use the slot IBM and Telecom Italia should have bookend in their agenda for tomorrow :-) The idea would be to devote the slot tomorrow to discuss about the issue of overlapping GEs with the IoT chapter. Please, Guy and Boris: confirm your availability. Apologizes to the rest for the short notice. Best regards, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro 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 ________________________________ 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 Dec 16 13:30:30 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 16 Dec 2011 13:30:30 +0100 Subject: [Fiware-data] Fwd: [Fiware] IMPORTANT: FI-WARE General Assembly (Plenary) meeting in January References: <4EEB2F25.80708@tid.es> Message-ID: <801E1334-EB02-4DA2-8F8B-763EBDDC1713@tid.es> Please, see below the details on the next plenary meeting to be held in TID premises in Madrid on Jan 23-27th. 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: 16 de diciembre de 2011 12:44:37 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, "fiware at lists.fi-ware.eu" > Asunto: [Fiware] IMPORTANT: FI-WARE General Assembly (Plenary) meeting in January Hi all, This is to let you know that the next FI-WARE General Assembly (Plenary) meeting will take place in Madrid in Telefonica's facilities, from January 23rd until January 27th. Focus will be given in that the different chapter (WP) teams meet together face2face. Also to arrange joint meetings involving several chapters at convenience, in order to address cross-chapter issues. Thus, we will take advantage that we are meeting in the same venue. We may have a short plenary meeting of about 2-3 hours but not more than that. We have booked 9 rooms from January 23 starting at 14:30 until January 27th 14:00. We believe it should be enough to run all the parallel meetings that are needed. We will setup a google docs spreadsheet to help closing the concrete dates and times at which a) each chapter (WP) will meet alone and b) joint chapter meetings will take place (this, of course means they agree among themselves). Soon we will send you an email with more info about logistics but we wanted to share already this basic information so that you can start booking flights and accomodations. We couldn't make it before we got sure that we could book all the necessary rooms. WPLs and WPAs will meet from January 23 starting at 09:00am. Cheers, -- ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro 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 mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware ________________________________ 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 Dec 19 17:47:25 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 19 Dec 2011 17:47:25 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpl] We are on Facebook now! References: <4EEF616A.9000307@tid.es> Message-ID: <033DA9FF-32FF-44AD-B0F1-0253CCE103AB@tid.es> FYI Let me use this as a reminder to follow us on @fiware account too. All our tweets will be automatically posted in the facebook page described below. Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- Inicio del mensaje reenviado: De: MIGUEL CARRILLO PACHECO > Fecha: 19 de diciembre de 2011 17:08:10 GMT+01:00 Para: "fiware at lists.fi-ware.eu" > Cc: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpl] We are on Facebook now! Dear all, We have our Facebook page now. You can reach it on: WPL, can you please disseminate this within your respective WPs? http://www.facebook.com/pages/FI-WARE/251366491587242 Please tick on the "I like it" button to help us grow a reasonable number of votes on Facebook. Thanks 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 _______________________________________________ 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 ralli at tid.es Thu Dec 22 10:23:50 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 22 Dec 2011 10:23:50 +0100 Subject: [Fiware-data] Private wiki created + Logistics for Madrid meeting References: <4EF21786.3010500@tid.es> Message-ID: Dear WP Colleagues, We have just created a private wiki space linked to a private project to share information just relevant for project members. For instance, we have already uploaded there the logistics and location details of our forthcoming Madrid meeting in January. As a private project, it is not reachable from the "project list" menu in the forge, so you'll need to keep the following link in your records: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Main_Page I have subscribed to this Wiki all project members listed in the Data chapter Wiki. Should you have any access/usage trouble, just drop me an e-mail. Best regards + Merry Xmas and Happy 2012. -- ------------------------------------------------------- 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 -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Thu Dec 22 16:51:42 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 22 Dec 2011 16:51:42 +0100 Subject: [Fiware-data] Webex & other Details for tomorrow's Data/Context follow up Conference Call Message-ID: <0484E687-6054-4B26-8D17-683635671930@tid.es> Dear WP Colleagues, Here you are: 1) We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf 2) Webex: Topic: FIWARE Data/Context Conf Call Date: Friday, December 23, 2011 Time: 9:30 am, Europe Time (Paris, GMT+01:00) Meeting Number: 965 177 804 Meeting Password: 1234abcD Go to https://telefonica.webex.com/telefonica-en/j.php?ED=189319147&UID=1265577607&PW=NYzRiMDUwYWIx&RT=MiMyMw%3D%3D 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 -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Thu Dec 22 17:41:15 2011 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Thu, 22 Dec 2011 17:41:15 +0100 Subject: [Fiware-data] Webex & other Details for tomorrow's Data/Context follow up Conference Call In-Reply-To: <0484E687-6054-4B26-8D17-683635671930@tid.es> References: <0484E687-6054-4B26-8D17-683635671930@tid.es> Message-ID: Hi Carlos and all, I'm afraid I won't be able to participate to tomorrow FIWARE DATA PhC as I'll be on vacation up to next year. So a short status on our side: FT is progressing well on the extension of the PubSub GE semantic interface. I wish all of you a merry chrismas and the best for new year! Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de CARLOS RALLI UCENDO Envoy? : jeudi 22 d?cembre 2011 16:52 ? : Fiware-data at lists.fi-ware.eu Objet : [Fiware-data] Webex & other Details for tomorrow's Data/Context follow up Conference Call Dear WP Colleagues, Here you are: 1) We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf 2) Webex: Topic: FIWARE Data/Context Conf Call Date: Friday, December 23, 2011 Time: 9:30 am, Europe Time (Paris, GMT+01:00) Meeting Number: 965 177 804 Meeting Password: 1234abcD Go to https://telefonica.webex.com/telefonica-en/j.php?ED=189319147&UID=1265577607&PW=NYzRiMDUwYWIx&RT=MiMyMw%3D%3D 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 -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Dec 23 08:59:40 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 23 Dec 2011 08:59:40 +0100 Subject: [Fiware-data] Follow-up confcall In-Reply-To: <4EF42CEA.6030009@tid.es> References: <4EF42CEA.6030009@tid.es> Message-ID: <4EF434EC.5080104@tid.es> Hi, We will start 09:45am sharp. I would rather encourage you to read the message below in the 15mins between 09:30am and 09:45am. This will save us some time during the confcall. Carlos had distributed the dial-in and webex bridge details Cheers, -- Juanjo -------- Original Message -------- Subject: [Fiware-wpl] IMPORTANT TO SYNC: FI-WARE First Open Call Date: Fri, 23 Dec 2011 08:25:30 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, This is to report to you about the decisions taken regarding topics for the first Open Call in FI-WARE. Please share this info with your respective teams. Going through a sequence of three intensive dedicated confcalls, the FI-PPP AB has came to an agreement on how to handle the higher priority topics raised by the UC projects as well as what will be the topics to be addressed in the first Open Call (a number of topics proposed by FI-WARE have been incorporated in the analysis in respect to this last point). You can get a wrap-up of this exercise summarizing the agreements reached looking at the sheet titled "Wrapup" in the following shared Google docs spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE&hl=en_US#gid=1 As you will see, only two topics will be addressed in the first Open Call. Following the advice of our PO, Arian Zwegers, we have decided to split the original first Open Call into two Open Calls, therefore having a total of three Open Calls overall. We have also decided to go for a very short list of topics in this first Open Call. This is because: * Again, following our PO advice, we have to take the opportunity of this Open Call to learn about how to manage the Open Call process so it's better to make it a "small trial" * We had to face the challenge of describing in detail and in collaboration with the UC projects what we will ask for in the description of this first Open Call, which has to be issued by end of January 2012. We have little time/resources to do this for too many topics, overall taking into account that we need to face a number of deliverables by end of January. In addition, many of the high-priority topics that both UC projects and ourselves have in our list (some of them shared) are still described in a too high-level so clearly there is a need to work on further refining them as to distill the actual features we want to support in FI-WARE. This is something that makes sense to afford during Q1 of 2012. Regarding the two particular topics selected for the first Open Call, let me elaborate a bit on them: * Middleware for efficient and QoS/Security-aware invocation of services as well as exchange of messages. There were several UC projects that were asking for this, not just for implementing communication between different parts of the application but for invoking services exposed to applications by the FI-WARE GEs. Therefore, we will have to go for it definitively. However, I see here the opportunity to drive what has to be developed in a way it can become useful in FI-WARE to help a) solving some of the issues we had identified during our Security workshop on November that have to do with managing access control through credentials when handling requests to services, b) dealing with several accountability and traceability issues and c) enabling a technology-neutral definition of GE interfaces. I will elaborate more on what I believe we may push into the definition of requirements for such middleware in the "Glue Middleware" Task Force we agreed to launch in our last joint WPLs/WPAs follow-up confcall. * Business Models and Business Elements (BM & BE) Definition and Simulation This is leveraged in a request made by UC projects to have means for simulating how costs of deploying a given application on top of FI-WARE (not only hosting service costs but costs derived from using other FI-WARE GE services or even third-party application services) could be simulated. Here, I found the opportunity to map this to our critical need to address the development of a BM & BE definition support component in the context of the first Open Call since this will be a base component of the Business Framework Reference Architecture for which an asset hadn't been identified. On the other hand, from my point of view, merging the two things together makes a lot of sense because any party that is able to contribute a product that implements this sort of simulation (which is the ultimate need expressed by the UC projects) may have probably implemented its own tools for defining the basic BM & BE on which simulation is based. Therefore, it makes sense to me to go and adapt our basic BM & BE Model to the one such potential new partner may bring. Regarding the rest of topics some of you had proposed, they where discussed and we agreed that they may go for the second call after their functional description is further defined, which is something that should happen during Q1 2012. Regarding the rest of topics raised by the UC projects, I would like to highlight the following: * Augmented Reality and 3D User Interfaces were brought to the table. Fair enough, these topics are clearly something we were not covering but have to do a lot with the kind of User Experiences someone would expect to see supported in Future Internet Applications. Therefore, I find it rather suitable to cover them through Open Calls which may attract rather specialized partners on the topics. In my view, this may probably lead to definition of a Working Package on User Interface support where, BTW, we may explore whether multi-device and multi-channel access to applications (currently in WP3 and somehow lacking of support) may be collocated. * Many UC projects are looking for means in the platform that will enable them to assure certain QoS at infrastructure level not just at centralized Data Centers but end-to-end. This had been mapped into a number of requests assigned to the I2ND chapter. UC projects do not expect to manage QoS at communication level from the application themselves (other than through the basic middleware targeted in the 1st Open Call). What they expect is to be able to select, configure and contract the SLA linked to an application at configuration&deployment time. SLAs that I see would be expressed in terms of a number of SLOs (Service Level Objectives). In words of one UC project: What would be very nice to have is a service which I can ask: "I need connectivity from A to B", and the service will answer "OK, you have 10 possible paths, price is such, characteristics of connection are such". If this is done properly, my application can then choose the "most reliable", "least expensive", or "most secure" path (and this will be seutp automatically). Next thing would be monitoring to see if the promised characteristics were really delivered (otherwise I don't pay...) I agree this has to be a functionality that has to be provided by FI-WARE but will require a close coordination between the Cloud, I2ND and Apps (Business Framework) chapter, so let's really assign this a high priority in our discussions. BTW, this clearly matches one of the cross-chapter Task Forces we identified during our last joint WPLs/WPAs confcall (Network-aware Cloud Task Force) * Many UC projects also have requirements for distributing their applications partly in the centralized Data Centers and partly in cloud proxies at the network-edge. Many of them wish to see the concept of cloud-proxy generalized as to cover smartphones and other smart but small devices. This comes along the need to be able to describe this distributed taxonomy at the time applications are configured and deployed on FI-WARE as well as the need to define means for handling failures in communication between the Data Center clouds and cloud proxies (periodic synchronizations and the like). This doesn't come as something new to us, but confirms the need to afford the definition of the necessary components at the Cloud chapter that can deal with this and prepare this as a subject for the second Open Call. * Another common requirements have to do with a) being able to assign a level of certainty/trust to data being managed by the application and b) being able to manage access and views to data depending on credentials of the user on behalf of whom an application is trying to get access to data. Both requirements are clearly generic and probably useful for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Several UC projects also expressed the need for several kind of "data-stream-oriented" GEs. For instance, the notion of Publish/Subscribe but linked to streams rather than to atomic data units. Again, this seems to be something generic and useful enough for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Rest of requirements were about topics I believe most probably are already in our roadmap or should not be a big issue to include in our roadmap. We agreed to follow them during Q1 2012 as to confirm this or not. Hope this long summary gives you a clear picture. Next steps will mean working on the detailed development of Epics that will be published as part of the first Open Call and will provide an enough detailed description of what we are looking for there. In addition, setting up a number of Task Forces on the topics above, involving UC projects, where we will address identification of Features. Such features will either enrich our current FI-WARE backlog (because we find they would fit within the roadmap of already identified GEs) or will be used for describing what will be requested in the second Open Call. More details will follow in the first weeks of January. I take advantage of this email to wish you all a very nice Christmas and a Happy New Year. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ________________________________ 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 Fri Dec 23 09:11:15 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 23 Dec 2011 09:11:15 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpl] IMPORTANT TO SYNC: FI-WARE First Open Call References: <4EF42CEA.6030009@tid.es> Message-ID: <1D0E453D-FB85-44FF-B787-CEB689A3B931@tid.es> Dear WP Colleagues, Please, take some time for this mail where cooperation roadmap with UC projects and Open Calls is described in detail. It is also time to collect your feedback on this so Juanjo may address open issues or provide us with further explanations. Merry Xmas and Happy 2012. -- ------------------------------------------------------- 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: 23 de diciembre de 2011 08:25:30 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpl] IMPORTANT TO SYNC: FI-WARE First Open Call Hi all, This is to report to you about the decisions taken regarding topics for the first Open Call in FI-WARE. Please share this info with your respective teams. Going through a sequence of three intensive dedicated confcalls, the FI-PPP AB has came to an agreement on how to handle the higher priority topics raised by the UC projects as well as what will be the topics to be addressed in the first Open Call (a number of topics proposed by FI-WARE have been incorporated in the analysis in respect to this last point). You can get a wrap-up of this exercise summarizing the agreements reached looking at the sheet titled "Wrapup" in the following shared Google docs spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE&hl=en_US#gid=1 As you will see, only two topics will be addressed in the first Open Call. Following the advice of our PO, Arian Zwegers, we have decided to split the original first Open Call into two Open Calls, therefore having a total of three Open Calls overall. We have also decided to go for a very short list of topics in this first Open Call. This is because: * Again, following our PO advice, we have to take the opportunity of this Open Call to learn about how to manage the Open Call process so it's better to make it a "small trial" * We had to face the challenge of describing in detail and in collaboration with the UC projects what we will ask for in the description of this first Open Call, which has to be issued by end of January 2012. We have little time/resources to do this for too many topics, overall taking into account that we need to face a number of deliverables by end of January. In addition, many of the high-priority topics that both UC projects and ourselves have in our list (some of them shared) are still described in a too high-level so clearly there is a need to work on further refining them as to distill the actual features we want to support in FI-WARE. This is something that makes sense to afford during Q1 of 2012. Regarding the two particular topics selected for the first Open Call, let me elaborate a bit on them: * Middleware for efficient and QoS/Security-aware invocation of services as well as exchange of messages. There were several UC projects that were asking for this, not just for implementing communication between different parts of the application but for invoking services exposed to applications by the FI-WARE GEs. Therefore, we will have to go for it definitively. However, I see here the opportunity to drive what has to be developed in a way it can become useful in FI-WARE to help a) solving some of the issues we had identified during our Security workshop on November that have to do with managing access control through credentials when handling requests to services, b) dealing with several accountability and traceability issues and c) enabling a technology-neutral definition of GE interfaces. I will elaborate more on what I believe we may push into the definition of requirements for such middleware in the "Glue Middleware" Task Force we agreed to launch in our last joint WPLs/WPAs follow-up confcall. * Business Models and Business Elements (BM & BE) Definition and Simulation This is leveraged in a request made by UC projects to have means for simulating how costs of deploying a given application on top of FI-WARE (not only hosting service costs but costs derived from using other FI-WARE GE services or even third-party application services) could be simulated. Here, I found the opportunity to map this to our critical need to address the development of a BM & BE definition support component in the context of the first Open Call since this will be a base component of the Business Framework Reference Architecture for which an asset hadn't been identified. On the other hand, from my point of view, merging the two things together makes a lot of sense because any party that is able to contribute a product that implements this sort of simulation (which is the ultimate need expressed by the UC projects) may have probably implemented its own tools for defining the basic BM & BE on which simulation is based. Therefore, it makes sense to me to go and adapt our basic BM & BE Model to the one such potential new partner may bring. Regarding the rest of topics some of you had proposed, they where discussed and we agreed that they may go for the second call after their functional description is further defined, which is something that should happen during Q1 2012. Regarding the rest of topics raised by the UC projects, I would like to highlight the following: * Augmented Reality and 3D User Interfaces were brought to the table. Fair enough, these topics are clearly something we were not covering but have to do a lot with the kind of User Experiences someone would expect to see supported in Future Internet Applications. Therefore, I find it rather suitable to cover them through Open Calls which may attract rather specialized partners on the topics. In my view, this may probably lead to definition of a Working Package on User Interface support where, BTW, we may explore whether multi-device and multi-channel access to applications (currently in WP3 and somehow lacking of support) may be collocated. * Many UC projects are looking for means in the platform that will enable them to assure certain QoS at infrastructure level not just at centralized Data Centers but end-to-end. This had been mapped into a number of requests assigned to the I2ND chapter. UC projects do not expect to manage QoS at communication level from the application themselves (other than through the basic middleware targeted in the 1st Open Call). What they expect is to be able to select, configure and contract the SLA linked to an application at configuration&deployment time. SLAs that I see would be expressed in terms of a number of SLOs (Service Level Objectives). In words of one UC project: What would be very nice to have is a service which I can ask: "I need connectivity from A to B", and the service will answer "OK, you have 10 possible paths, price is such, characteristics of connection are such". If this is done properly, my application can then choose the "most reliable", "least expensive", or "most secure" path (and this will be seutp automatically). Next thing would be monitoring to see if the promised characteristics were really delivered (otherwise I don't pay...) I agree this has to be a functionality that has to be provided by FI-WARE but will require a close coordination between the Cloud, I2ND and Apps (Business Framework) chapter, so let's really assign this a high priority in our discussions. BTW, this clearly matches one of the cross-chapter Task Forces we identified during our last joint WPLs/WPAs confcall (Network-aware Cloud Task Force) * Many UC projects also have requirements for distributing their applications partly in the centralized Data Centers and partly in cloud proxies at the network-edge. Many of them wish to see the concept of cloud-proxy generalized as to cover smartphones and other smart but small devices. This comes along the need to be able to describe this distributed taxonomy at the time applications are configured and deployed on FI-WARE as well as the need to define means for handling failures in communication between the Data Center clouds and cloud proxies (periodic synchronizations and the like). This doesn't come as something new to us, but confirms the need to afford the definition of the necessary components at the Cloud chapter that can deal with this and prepare this as a subject for the second Open Call. * Another common requirements have to do with a) being able to assign a level of certainty/trust to data being managed by the application and b) being able to manage access and views to data depending on credentials of the user on behalf of whom an application is trying to get access to data. Both requirements are clearly generic and probably useful for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Several UC projects also expressed the need for several kind of "data-stream-oriented" GEs. For instance, the notion of Publish/Subscribe but linked to streams rather than to atomic data units. Again, this seems to be something generic and useful enough for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Rest of requirements were about topics I believe most probably are already in our roadmap or should not be a big issue to include in our roadmap. We agreed to follow them during Q1 2012 as to confirm this or not. Hope this long summary gives you a clear picture. Next steps will mean working on the detailed development of Epics that will be published as part of the first Open Call and will provide an enough detailed description of what we are looking for there. In addition, setting up a number of Task Forces on the topics above, involving UC projects, where we will address identification of Features. Such features will either enrich our current FI-WARE backlog (because we find they would fit within the roadmap of already identified GEs) or will be used for describing what will be requested in the second Open Call. More details will follow in the first weeks of January. I take advantage of this email to wish you all a very nice Christmas and a Happy New Year. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ________________________________ 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 Tanguy.Bourgault at thalesaleniaspace.com Fri Dec 23 11:23:44 2011 From: Tanguy.Bourgault at thalesaleniaspace.com (Tanguy.Bourgault at thalesaleniaspace.com) Date: Fri, 23 Dec 2011 11:23:44 +0100 Subject: [Fiware-data] =?iso-8859-1?q?R=E9f=2E_=3A__Follow-up_confcall?= In-Reply-To: <4EF434EC.5080104@tid.es> Message-ID: <28623_1324636224_4EF45840_28623_12119_1_OFE9CDFF2B.873B9409-ONC125796F.0037522C-C125796F.00391A8D@thalesaleniaspace.com> Dear All, I believe the tasks below are more related to "complex event processing" than "location platform": [#321] SMARTAGRIFOOD.Epic.data.MobilityAnalysis.ProcessOfUserLocation [#393] SAFECITY.Theme.Data/Context.Localisation Platform GE.Event Localization Please evaluate. Juanjo, fyi I have updated all other tickets assigned to R?mi. We both are on vacation until 2nd of January. Best regards and Merry Christmas ! Tanguy |---------+------------------------------------> | | Juanjo Hierro | | | | | | Envoy? par : | | | fiware-data-bounces at lists| | | .fi-ware.eu | | | | | | | | | 23/12/2011 08:59 | |---------+------------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | Pour : "fiware-data at lists.fi-ware.eu" | | cc : | | Objet : [Fiware-data] Follow-up confcall | >------------------------------------------------------------------------------------------------------------------------------| Hi, We will start 09:45am sharp. I would rather encourage you to read the message below in the 15mins between 09:30am and 09:45am. This will save us some time during the confcall. Carlos had distributed the dial-in and webex bridge details Cheers, -- Juanjo -------- Original Message -------- Subje [Fiware-wpl] IMPORTANT TO SYNC: FI-WARE First Open Call ct: Date: Fri, 23 Dec 2011 08:25:30 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, This is to report to you about the decisions taken regarding topics for the first Open Call in FI-WARE. Please share this info with your respective teams. Going through a sequence of three intensive dedicated confcalls, the FI-PPP AB has came to an agreement on how to handle the higher priority topics raised by the UC projects as well as what will be the topics to be addressed in the first Open Call (a number of topics proposed by FI-WARE have been incorporated in the analysis in respect to this last point). You can get a wrap-up of this exercise summarizing the agreements reached looking at the sheet titled "Wrapup" in the following shared Google docs spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE&hl=en_US#gid=1 As you will see, only two topics will be addressed in the first Open Call. Following the advice of our PO, Arian Zwegers, we have decided to split the original first Open Call into two Open Calls, therefore having a total of three Open Calls overall. We have also decided to go for a very short list of topics in this first Open Call. This is because: Again, following our PO advice, we have to take the opportunity of this Open Call to learn about how to manage the Open Call process so it's better to make it a "small trial" We had to face the challenge of describing in detail and in collaboration with the UC projects what we will ask for in the description of this first Open Call, which has to be issued by end of January 2012. We have little time/resources to do this for too many topics, overall taking into account that we need to face a number of deliverables by end of January. In addition, many of the high-priority topics that both UC projects and ourselves have in our list (some of them shared) are still described in a too high-level so clearly there is a need to work on further refining them as to distill the actual features we want to support in FI-WARE. This is something that makes sense to afford during Q1 of 2012. Regarding the two particular topics selected for the first Open Call, let me elaborate a bit on them: Middleware for efficient and QoS/Security-aware invocation of services as well as exchange of messages. There were several UC projects that were asking for this, not just for implementing communication between different parts of the application but for invoking services exposed to applications by the FI-WARE GEs. Therefore, we will have to go for it definitively. However, I see here the opportunity to drive what has to be developed in a way it can become useful in FI-WARE to help a) solving some of the issues we had identified during our Security workshop on November that have to do with managing access control through credentials when handling requests to services, b) dealing with several accountability and traceability issues and c) enabling a technology-neutral definition of GE interfaces. I will elaborate more on what I believe we may push into the definition of requirements for such middleware in the "Glue Middleware" Task Force we agreed to launch in our last joint WPLs/WPAs follow-up confcall. Business Models and Business Elements (BM & BE) Definition and Simulation This is leveraged in a request made by UC projects to have means for simulating how costs of deploying a given application on top of FI-WARE (not only hosting service costs but costs derived from using other FI-WARE GE services or even third-party application services) could be simulated. Here, I found the opportunity to map this to our critical need to address the development of a BM & BE definition support component in the context of the first Open Call since this will be a base component of the Business Framework Reference Architecture for which an asset hadn't been identified. On the other hand, from my point of view, merging the two things together makes a lot of sense because any party that is able to contribute a product that implements this sort of simulation (which is the ultimate need expressed by the UC projects) may have probably implemented its own tools for defining the basic BM & BE on which simulation is based. Therefore, it makes sense to me to go and adapt our basic BM & BE Model to the one such potential new partner may bring. Regarding the rest of topics some of you had proposed, they where discussed and we agreed that they may go for the second call after their functional description is further defined, which is something that should happen during Q1 2012. Regarding the rest of topics raised by the UC projects, I would like to highlight the following: Augmented Reality and 3D User Interfaces were brought to the table. Fair enough, these topics are clearly something we were not covering but have to do a lot with the kind of User Experiences someone would expect to see supported in Future Internet Applications. Therefore, I find it rather suitable to cover them through Open Calls which may attract rather specialized partners on the topics. In my view, this may probably lead to definition of a Working Package on User Interface support where, BTW, we may explore whether multi-device and multi-channel access to applications (currently in WP3 and somehow lacking of support) may be collocated. Many UC projects are looking for means in the platform that will enable them to assure certain QoS at infrastructure level not just at centralized Data Centers but end-to-end. This had been mapped into a number of requests assigned to the I2ND chapter. UC projects do not expect to manage QoS at communication level from the application themselves (other than through the basic middleware targeted in the 1st Open Call). What they expect is to be able to select, configure and contract the SLA linked to an application at configuration&deployment time. SLAs that I see would be expressed in terms of a number of SLOs (Service Level Objectives). In words of one UC project: What would be very nice to have is a service which I can ask: "I need connectivity from A to B", and the service will answer "OK, you have 10 possible paths, price is such, characteristics of connection are such". If this is done properly, my application can then choose the "most reliable", "least expensive", or "most secure" path (and this will be seutp automatically). Next thing would be monitoring to see if the promised characteristics were really delivered (otherwise I don't pay...) I agree this has to be a functionality that has to be provided by FI-WARE but will require a close coordination between the Cloud, I2ND and Apps (Business Framework) chapter, so let's really assign this a high priority in our discussions. BTW, this clearly matches one of the cross-chapter Task Forces we identified during our last joint WPLs/WPAs confcall (Network-aware Cloud Task Force) Many UC projects also have requirements for distributing their applications partly in the centralized Data Centers and partly in cloud proxies at the network-edge. Many of them wish to see the concept of cloud-proxy generalized as to cover smartphones and other smart but small devices. This comes along the need to be able to describe this distributed taxonomy at the time applications are configured and deployed on FI-WARE as well as the need to define means for handling failures in communication between the Data Center clouds and cloud proxies (periodic synchronizations and the like). This doesn't come as something new to us, but confirms the need to afford the definition of the necessary components at the Cloud chapter that can deal with this and prepare this as a subject for the second Open Call. Another common requirements have to do with a) being able to assign a level of certainty/trust to data being managed by the application and b) being able to manage access and views to data depending on credentials of the user on behalf of whom an application is trying to get access to data. Both requirements are clearly generic and probably useful for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. Several UC projects also expressed the need for several kind of "data-stream-oriented" GEs. For instance, the notion of Publish/Subscribe but linked to streams rather than to atomic data units. Again, this seems to be something generic and useful enough for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. Rest of requirements were about topics I believe most probably are already in our roadmap or should not be a big issue to include in our roadmap. We agreed to follow them during Q1 2012 as to confirm this or not. Hope this long summary gives you a clear picture. Next steps will mean working on the detailed development of Epics that will be published as part of the first Open Call and will provide an enough detailed description of what we are looking for there. In addition, setting up a number of Task Forces on the topics above, involving UC projects, where we will address identification of Features. Such features will either enrich our current FI-WARE backlog (because we find they would fit within the roadmap of already identified GEs) or will be used for describing what will be requested in the second Open Call. More details will follow in the first weeks of January. I take advantage of this email to wish you all a very nice Christmas and a Happy New Year. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro 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[rattachement "ATT00001..txt" supprim? par Tanguy Bourgault/FR/SPACE] _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data Tanguy Bourgault LBS Project Manager - Thales Alenia Space Tel. +33 5 34 35 34 92, Mob. +33 6 87 04 53 40 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pic00153.gif Type: image/gif Size: 1255 bytes Desc: not available URL: From ralli at tid.es Fri Dec 23 13:33:07 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 23 Dec 2011 13:33:07 +0100 Subject: [Fiware-data] Today's Follow-up confcall - Minutes In-Reply-To: <4EF37F1C.2080404@tid.es> References: <4EEA4384.7060900@tid.es> <4EF37F1C.2080404@tid.es> Message-ID: Hi, Find here the link to access the minutes of today's PhC: https://forge.fi-ware.eu/docman/view.php/9/713/20111223_Data-Context-Minutes.doc Please, note that you need to be logged in the forge prior to access through the above mentioned link. The overall template for the project minutes is available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Useful_document_templates Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 22/12/2011, a las 20:03, Juanjo Hierro escribi?: Hi, Actually the main goal of tomorrows' confcall is to go through UC requests and answer questions. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro On 22/12/11 19:21, Amon, Peter wrote: Dear Juanjo, the PhC this Friday comes a bit surprising. Nevertheless, Andreas will attend. :-) On the current status: We assessed the requirements from the usage area projects related our Siemens' GEs (see Excel sheet attached). Maybe you can elaborate a bit in tomorrow's PhC how we should answer to usage area projects in case a request will only be partially addressed (i.e., only part of the requested functionality will be implemented in the end). This is a case for the majority of requests we received. In case you think the comments written in the Excel sheet are appropriate, we can put them in/on the tracker. Kind regards and Merry X-mas to you and your team Peter -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Donnerstag, 15. Dezember 2011 19:59 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Follow-up confcall tomorrow - Guy and Boris important to read Hi all, We will cancel the follow-up confcall tomorrow. I will setup a doodle to find a more suitable time slot on Monday/Tuesday/Wednesday. However, I want to use the slot IBM and Telecom Italia should have bookend in their agenda for tomorrow :-) The idea would be to devote the slot tomorrow to discuss about the issue of overlapping GEs with the IoT chapter. Please, Guy and Boris: confirm your availability. Apologizes to the rest for the short notice. Best regards, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro 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 boris.moltchanov at telecomitalia.it Fri Dec 23 21:43:59 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 23 Dec 2011 21:43:59 +0100 Subject: [Fiware-data] Private wiki created + Logistics for Madrid meeting In-Reply-To: References: <4EF21786.3010500@tid.es> Message-ID: It worth to specify that in order to login that web-site area you have to be already logged in to project forge (not private). Otherwise, I've tried to login directly to the private area and my username was not recognized. Then tried to login first to the forge and then passed to the link indicated below . Not sure if this is a bug or my login doesn't work for the private site. Boris 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: Thursday, December 22, 2011 10:24 AM To: Fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Private wiki created + Logistics for Madrid meeting Dear WP Colleagues, We have just created a private wiki space linked to a private project to share information just relevant for project members. For instance, we have already uploaded there the logistics and location details of our forthcoming Madrid meeting in January. As a private project, it is not reachable from the "project list" menu in the forge, so you'll need to keep the following link in your records: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Main_Page I have subscribed to this Wiki all project members listed in the Data chapter Wiki. Should you have any access/usage trouble, just drop me an e-mail. Best regards + Merry Xmas and Happy 2012. -- ------------------------------------------------------- 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. [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: