From ralli at tid.es Thu Mar 1 09:44:49 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 01 Mar 2012 09:44:49 +0100 Subject: [Fiware-data] Today's Data/Context PhC at 10:30 Message-ID: <6CCF2A12-72CF-4FE1-B9C6-D428995E97B1@tid.es> Dear WP Colleagues, Find here some details for our today's call: - Google Doc: https://docs.google.com/document/d/1KKPpepj4HXVkqax_pfUlUV3oTzLiLeTY_Pk1r2rkQLs/edit - Powownow: We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf I will be providing in some minutes the .doc file with the agenda and so on. Best regards, ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx From e.fiware1 at tid.es Thu Mar 1 10:38:34 2012 From: e.fiware1 at tid.es (Grant Croker) Date: Thu, 01 Mar 2012 10:38:34 +0100 Subject: [Fiware-data] Screen sharing for 1-3-12 Message-ID: <000001ccf78f$1584a3e0$408deba0$%fiware1@tid.es> For those that cannot access the Google Doc with the meeting minutes can you try https://join.me/822-648-311 (you?ll need Adobe Flash). Thanks grant ________________________________ 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 Thu Mar 1 11:09:25 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 1 Mar 2012 11:09:25 +0100 Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE In-Reply-To: References: <4F4CC61B.2010806@tid.es> Message-ID: Missed fiware data list by iPhone in the previous message. B From: Moltchanov Boris Sent: Thursday, March 01, 2012 7:14 AM To: Guy Sharon Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE For example that adapters for CEP in C-CAST were developed by UASO. Great that you agree on this Guy! Thanks. Boris 29/feb/2012, ? 20:27, "Guy Sharon" > ???????(?): Hi all, "Third" module responsibility of conversion - this could be done by implementing specific input and output adapters of our CEP engine These adapters support JMS meaning we can subscribe to a topic or listen to a queue for incoming events and we can publish to a topic or send to a queue outgoing events \ complex events. These adapters also support REST as clients. Meaning we can REST GET events from a RESTfull service as incoming events to CEP and we can REST POST events to a RESTfull service as outgoing \ complex events Regards, Guy Sharon Manager, Event-based Middleware & Solutions Group IBM Research - Haifa ________________________________ Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: and within IBM on: Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Moltchanov Boris > To: Juanjo Hierro > Cc: "fiware-data at lists.fi-ware.eu" > Date: 29/02/2012 20:04 Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi Juanjo, Ok. Got your point and never used it differently. Sorry if sometimes seemed differently. I would confirm that the PubSub based on the context broker is unable to handle any request without an valuated entityID notation. Thus, as stated from very beginning and discussed with Guy and as you suggested (after conversation with Carlo during the last f2f) we have to comply with the context data structure (Within the vision document). Otherwise the query, subscription and entity resolution all based on the context broker will not work (confirmation from Telecom Italia developers). Therefore regarding the third point (Event Objects) of your email below the PubSub shall receive EventsObjects, and then eventually republishing them to the consumers, with an entityID and will provide to anyone CEP included the context data elements with entityIDs. You have suggested, if I?m not wrong, to put this enityID either fixed or fixed but configurable. I suggest, as discussed with Guy and tried to explain in the call, that we derive the entityID from the EO?s attributes if there is at least one. If there is no one a fixed entityID such as entityID=CEP shall be introduces. And viceversa an entityID coming from the PubSub into the CEP might be ?encoded? into the EO?s entity attribute element. However both such conversions are out of scope of the current components and shall be performed by a ?third? module that will accomplish an EO into the context element (EO(event,opt.entityID) -> context(entityID, scope=event) and viceversa will rebuild an EO from a context element (context(entityID,scope)->EO(scope+attr.entityID)). Moreover, the same ?third? module could perform subscription to the PubSub for the events/scopes that the CEP needs to derive the EO, as far as, if I remember well, the CEP is unable to perform the subscription and shall be feeded (pushed) by the events or contexts_as_events, Guy confirm? And the PubSub does not perform subscription on itself, but on behalf of a consumer. There may be no explicit specific consumer for feeding the CEP, thus this subscription task to the PubSub on behalf of the CEP will be taken by this ?third? component. Let?s have a closer look to this proposed architectural/functional vision in tomorrow AC. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Tuesday, February 28, 2012 1:19 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Hi Boris, PLEASE, while making your proposal for the solution on how to map concepts between the Pub/Sub Broker GE and CEP pleas DO FOLLOW the terms and definitions proposed in the FI-WARE Product Vision: * "Context Elements" (which certainly map to the concepts defined in OMA) * "Data Elements" (= Context Elements but without EntityId) * "Event Objects": the programming structure that will be used by the CEP into which Context Elements and Data Elements should be mapped. Let's try to avoid the term "Event" which may introduce confusion and doesn't add to much the technical discussion which is indeed about how to map between the data structures listed above (the term Event can be used but should then be under the definition provided in the FI-WARE Product Vision). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Thu Mar 1 12:37:28 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 1 Mar 2012 12:37:28 +0100 Subject: [Fiware-data] a proposal to optimize the effort in FI-WARE and respect the timing being efficient and stragihtfoward to the VALUES Message-ID: Juanjo, (I already had touched this discussion with Carlos, probably it was a wrong moment and place, sorry for that). Being here constructive and including at least our WP6 mailing list, I propose, that in each WP of FI-WARE we're: - Highlight and put clearly WHAT ARE THE VALUES OF OUR SINGLE COMPONENTS (GEs) exposing this VERY SIMPLE TABLE to: o Reciprocally within the FI-WARE WPs o Towards the UCPs This information is: - additionally to the documentation that we already have; - taking consideration the knowledge and info, which is perfectly known by all the asset (GE) owners (Companies); thus, this is FREE FOR EFFORT and has an IMMEDIATE implementation (this table could be created in a very short time). Why to do this and where is value? Here: 1. will be clear without reading a lot of details and among different document (too verbose) the documentation of the project, that become massively described (I mean the quantity) and sometime we are losing the look to the value of our components and instead concentrating onto the details 2. will stimulate the WPs and UCPs for creation of the scenarios that: a. will have even GREATRE VALUE that the single components; b. return back to us the FEEDBACK on their scenarios, which will be built ON OUR components' and values (no disruption to the GEs' specs, preserving our work and being efficient in time/effort consume) and will provide to us in FI-WARE a clear understanding about which COMPONENTs (GEs) WILL BE USED and IN WHICH COMBINATIONS, that will additionally provide requirements to us how the GEs have to cooperate. This is up to you to decide on such a table, I sincerely believe and strongly sure that such almost free (zero cost) effort worth its value. Of course then we will have requirements coming from the UCPs independently on our components and we will consider them, however anticipation of these reqs (maybe delayed they are started later, don't have clear ideas, wish to implement everything inside UCP because to high level FI-WARE vision or because feeling that is not supported by FI-WARE, etc.) will have of flavor of saying "Hello, We (a,b,c) are hear and value of each a=xxx, b=yyy, c=zzz)! Please say me, for you, which d is missing and how you wish to use these a,b,c and new d.". BR, B Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From boris.moltchanov at telecomitalia.it Thu Mar 1 13:18:07 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 1 Mar 2012 13:18:07 +0100 Subject: [Fiware-data] Screen sharing for 1-3-12 In-Reply-To: <000001ccf78f$1584a3e0$408deba0$%fiware1@tid.es> References: <000001ccf78f$1584a3e0$408deba0$%fiware1@tid.es> Message-ID: Thank you for pointing this tool out, Grant! If it will be demonstrated as a really good alternative (I?m sorry about some troubles on Siemen?s side) to webex, which is I suppose is not free for use, we might use also this one. B From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Grant Croker Sent: Thursday, March 01, 2012 10:39 AM To: 'fiware-data at lists.fi-ware.eu' Subject: [Fiware-data] Screen sharing for 1-3-12 For those that cannot access the Google Doc with the meeting minutes can you try https://join.me/822-648-311 (you?ll need Adobe Flash). Thanks grant ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From ralli at tid.es Tue Mar 6 17:40:08 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 06 Mar 2012 17:40:08 +0100 Subject: [Fiware-data] FI-WARE Technical Roadmap Deliverable (Needs per-asset owner review) References: <4F54F599.5040701@tid.es> Message-ID: Dear WP Colleagues, As discussed in our last week conference call, I was in charge of make a first version of our chapter contribution to the "Technical Roadmap" deliverable prior to your specific asset review. You can find it at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Data-Context I tried to summarize the 'Feature' tickets in the tracker for each Data/Context asset and the description that we displayed in the slides of the previous review in Brussels. For this deliverable we are trying to avoid repeating once more the contents in the Vision, materializing the Vision & Architecture. We also avoided to make sections per each asset, tough all points for an asset and feature (1st, 2nd and further) remain together. This way we better provide a vision of Data/Context integrated/synergic value. Please, note that at the end of 'Release 1' it is **VERY** important to state what we will not be actually delivering compared to what someone may expect as of reading the above mentioned documents (vision, materializing ..., architecture). Find in the mail below, some extra guidelines Juanjo provided to the rest of WPl/WPa. We should be able to provide the final version including your reviews by this Thursday EoB. Thanks in advance, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Inicio del mensaje reenviado: De: JUAN JOSE HIERRO SUREDA > Fecha: 5 de marzo de 2012 18:19:21 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpa] IMPORTANT REMARKS regarding the FI-WARE Technical Roadmap Deliverable Hi all, I guess you are dealing with the writing of the FI-WARE Technical Roadmap deliverable. I also guess that you would agree that, while the text we are going to produce here doesn't need to be long, it may be highly relevant because we are trying to fix there WHAT WE COMMIT TO DELIVER WHEN. Therefore, I would like to make a couple of remarks: * Please try to commit for the first release what we believe is strictly a MUST, that is, things we believe that, if not brought, FI-WARE will be useless to the UC projects (or, at least, they will blame of us :-) Note that we didn't specify what we were going to bring in the first release within the current signed DoW. Therefore, nobody will be able to make the point that we are not fulfilling the DoW if we do not deliver this or that. HOWEVER, we will JUDGED with respect to whatever we commit to deliver now: if we promise to deliver something in the first release now and then we fail to deliver it, then the reviewers will have the right to say we failed and reject acceptance of, among others, the FI-WARE Testbed deliverable. * It's not a matter of committing to deliver what we believe we can develop and have ready for integration by end of April based on selected baseline assets. Don't underestimate the integration efforts on the testbed. Also don't underestimate integration coordination efforts: just following up that a given GE is properly installed and configured in the Testbed will take its time not only to leaders of tasks in WP10, but also to you as chapters leads and myself ... so, why should we spent time in something that nobody would consider urgent/must ? It's better that we rather concentrate on integrating the less things possible for the first release and leave integration of things that can wait for later. We should just focus on what can be a STABLE integrated FI-WARE Release and then make it grow, adding new GEs or features in already integrated GEs. * Despite we talk just about Major Releases in the FI-WARE DoW or in the Technical Roadmap Deliverable, we should plan to be able to upgrade the testbed at our convenience every three months, so that new GE software or upgrades on existing GEs arrives end of July 2012, October 2012, January 2013, Abril 2013, July 2013, ... and then new releases of the testbed are published by end of October 2012, January 2013, Abril 2013, July 2013, October 2013 respectively (we typically book three months for integration testing in the testbed). So don't hesitate to defer things for the first or the second minor release within the second major release of FI-WARE in your planning. * I propose the following to handle what is planned in the different minor releases of the second major release. We will publish the Technical Roadmap deliverable just making the distinction on what goes in the first Major Release and what goes in the second Major Release of FI-WARE. And please be conservative promising things for the First Major Release. Then, what we will do is ask the UC projects: Is there anything planned for the Second Major Release you wish to have prioritized ? Then, based on their feedback, we will prioritize the features they highlight and will try to deliver then a little bit in advance, planning them in the first minor releases of the second major release (e.g., to get it ready in the FI-WARE Testbed either by end of October 2012 or end of January 2013). Doing so, we are showing we care about their priorities and show some flexibility. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 ralli at tid.es Wed Mar 7 11:31:30 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 07 Mar 2012 11:31:30 +0100 Subject: [Fiware-data] Data/Context Follow up Call (Thu March 8th, 10:30-12:00) Message-ID: Dear WP Colleagues, Find here some details (tentative Agenda included) for our today's call with - Google Doc: https://docs.google.com/document/d/1ZfAuQ4FyJtAFIgdBxApl6DGnVrV6yXi3vNtNWFPM5wA/edit (also attached the document file to this e-mail) Please, do not forget to register as "available" so we can easily monitor who is intending to attend. I will re-send once I get the Webex details & there are more updates. During the afternoon, I will check too if all previous minutes are in place (private Wiki). Volunteers for this week UC projects tickets discussion? (Peter, I have already included a slot for tickets splitting). Best regards, ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Thu Mar 8 10:40:00 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 08 Mar 2012 10:40:00 +0100 Subject: [Fiware-data] Fwd: Please join now, meeting in progress: FI-WARE Data/Context Conf Call (10:30 AM, no PM) References: <241995627.1330594787541.JavaMail.nobody@jsj2wl015.webex.com> Message-ID: <5213ACCA-1A19-4C46-AE70-49EC2BC77AEF@tid.es> Hello , Please join my meeting that is currently in progress. Topic: FI-WARE Data/Context Conf Call (10:30 AM, no PM) Date: Thursday, March 1, 2012 Time: 10:39 am, Europe Time (Paris, GMT+01:00) Meeting Number: 964 079 569 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/e.php?AT=MI&EventID=191276132&UID=1273918182&PW=NZmRhMGJjNGI2&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: 1234abcD 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://telefonica.webex.com/telefonica-en/e.php?AT=MI&EventID=191276132&UID=1273918182&PW=NZmRhMGJjNGI2&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 Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Thu Mar 8 11:34:28 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 08 Mar 2012 11:34:28 +0100 Subject: [Fiware-data] Minutes of Today as they are now Message-ID: Hi, Here you are. For comments, corrections & suggestions, please use the Googledoc. Those not able to access, drop an e-mail to me. https://docs.google.com/document/d/1ZfAuQ4FyJtAFIgdBxApl6DGnVrV6yXi3vNtNWFPM5wA/edit Tonight I will freeze the minutes and upload to the proper places in the Wiki. Thanks for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx From ralli at tid.es Thu Mar 8 11:35:48 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 08 Mar 2012 11:35:48 +0100 Subject: [Fiware-data] Minutes of Today as they are now (w/ attachment) In-Reply-To: References: Message-ID: <88B4D3CA-0822-4FBD-BFC8-4A5F62787649@tid.es> El 08/03/2012, a las 11:34, CARLOS RALLI UCENDO escribi?: > Hi, > > Here you are. > > For comments, corrections & suggestions, please use the Googledoc. Those not able to access, drop an e-mail to me. > > https://docs.google.com/document/d/1ZfAuQ4FyJtAFIgdBxApl6DGnVrV6yXi3vNtNWFPM5wA/edit > > Tonight I will freeze the minutes and upload to the proper places in the Wiki. > > Thanks for your cooperation. > Best regards, > -- > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > Product Development & Innovation (Telef?nica Digital) > Telef?nica I+D SAU > Madrid, Spain > ------------------------------------------------------------------------------------------------------------------------ > Follow FI-WARE project (Future Internet Services Core Platform): > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: @fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ------------------------------------------------------------------------------------------------------------------------ > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: 20120308_Data-Context_Minutes_v1 - Google Docs.webarchive Type: application/x-webarchive Size: 3073472 bytes Desc: 20120308_Data-Context_Minutes_v1 - Google Docs.webarchive URL: From Thomas.Riegel at siemens.com Tue Mar 13 09:58:11 2012 From: Thomas.Riegel at siemens.com (Riegel, Thomas) Date: Tue, 13 Mar 2012 09:58:11 +0100 Subject: [Fiware-data] Suggestion for Desktop-Sharing Application - Teamviewer Message-ID: <68C38D00FDECEA438AF874B71CF09170075AD01AB4@DEMCHP99E34MSX.ww902.siemens.net> Hi Carlos, As our Siemens firewall settings/regulations seem to be very strict may I suggest another desktop sharing tool , which is convenient and works for us (Siemens) too. It's Teamviewer (http://www.teamviewer.com/en/index.aspx). Everyone need to download that application (but it need not to be installed - just run it); The host (i.e. you) clicks on the tab "Meeting" and starts an instant one; then a Meeting ID is generated which will be distributed to the participants for accessing it. Carlos, please have a look at it and let us have a try next PhC (to share the minutes on google docs). CU Thomas __________________________________________ With best regards, Thomas Riegel Siemens AG Corporate Technology Corporate Research and Technologies CT T DE IT2 Otto-Hahn-Ring 6 81739 Munich, Germany Tel.: +49 89 636-41225 Fax: +49 89 636-51115 mailto:thomas.riegel at siemens.com Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer; Roland Busch, Brigitte Ederer, Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen, Michael Suess; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322 -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Tue Mar 13 11:18:00 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 13 Mar 2012 11:18:00 +0100 Subject: [Fiware-data] Suggestion for Desktop-Sharing Application - Teamviewer In-Reply-To: <68C38D00FDECEA438AF874B71CF09170075AD01AB4@DEMCHP99E34MSX.ww902.siemens.net> References: <68C38D00FDECEA438AF874B71CF09170075AD01AB4@DEMCHP99E34MSX.ww902.siemens.net> Message-ID: This service is forbidden by Telecom Italia. I don't know the reason but I suppose is the next: 1. All the sharing is passing through a German server for RSA handshake (thus the key could be known or shared with that server); 2. It uses channel encryption, thus other 3rd part (e.g. Telecom Italia doesn't know what is communication about). Obviously this pose a great security threat for Enterprises using this tool where someone else know about the communication but not the company itself. I tried, our proxy server even blocks its homepage. Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Riegel, Thomas Sent: Tuesday, March 13, 2012 9:58 AM To: CARLOS RALLI UCENDO Cc: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Suggestion for Desktop-Sharing Application - Teamviewer Hi Carlos, As our Siemens firewall settings/regulations seem to be very strict may I suggest another desktop sharing tool , which is convenient and works for us (Siemens) too. It's Teamviewer (http://www.teamviewer.com/en/index.aspx). Everyone need to download that application (but it need not to be installed - just run it); The host (i.e. you) clicks on the tab "Meeting" and starts an instant one; then a Meeting ID is generated which will be distributed to the participants for accessing it. Carlos, please have a look at it and let us have a try next PhC (to share the minutes on google docs). CU Thomas __________________________________________ With best regards, Thomas Riegel Siemens AG Corporate Technology Corporate Research and Technologies CT T DE IT2 Otto-Hahn-Ring 6 81739 Munich, Germany Tel.: +49 89 636-41225 Fax: +49 89 636-51115 mailto:thomas.riegel at siemens.com Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer; Roland Busch, Brigitte Ederer, Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen, Michael Suess; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From marcus.laumer.ext at siemens.com Tue Mar 13 11:37:49 2012 From: marcus.laumer.ext at siemens.com (Laumer, Marcus) Date: Tue, 13 Mar 2012 11:37:49 +0100 Subject: [Fiware-data] Splitting of UC Tickets Message-ID: <750211B1279EFC489DB5D8B39550E0741D6E71F64E@DEMCHP99E15MSX.ww902.siemens.net> Hi Carlos, while reviewing the minutes of our last PhC I noticed that you created the Split status in the backlog tracker of data/context, not in the global FI-WARE tracker for UC project requests. Unfortunately, I did not recognize this during our call. Shouldn't we have the Split status in the global tracker to be able to split the UC tickets directly, as already agreed upon in one of our previous PhC with Juanjo? Or did I get the idea wrong? I think the Split status in the backlog tracker should not be necessary since the UC projects do not issue any tickets there and we can handle them on our own, right? Best regards, Marcus PS: You sent the minutes of the last PhC as .webarchive file. We managed to open it with some effort, but we would prefer .doc or .pdf files :) -- Marcus Laumer External service provider at Siemens AG Corporate Technology Corporate Research and Technologies CT T DE IT2 Otto-Hahn-Ring 6 81739 Munich, Germany Tel.: +49 (89) 636-45149 mailto:marcus.laumer.ext at siemens.com Important notice: This e-mail and any attachment thereof contain corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Tue Mar 13 11:49:04 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 13 Mar 2012 11:49:04 +0100 Subject: [Fiware-data] Splitting of UC Tickets In-Reply-To: <750211B1279EFC489DB5D8B39550E0741D6E71F64E@DEMCHP99E15MSX.ww902.siemens.net> References: <750211B1279EFC489DB5D8B39550E0741D6E71F64E@DEMCHP99E15MSX.ww902.siemens.net> Message-ID: Hi Marcus, You are right. I did the changes first in the Data/Context tracker to test first, now it should be done in the global one too. Just make another try & let me know. Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ El 13/03/2012, a las 11:37, Laumer, Marcus escribi?: Hi Carlos, while reviewing the minutes of our last PhC I noticed that you created the Split status in the backlog tracker of data/context, not in the global FI-WARE tracker for UC project requests. Unfortunately, I did not recognize this during our call. Shouldn?t we have the Split status in the global tracker to be able to split the UC tickets directly, as already agreed upon in one of our previous PhC with Juanjo? Or did I get the idea wrong? I think the Split status in the backlog tracker should not be necessary since the UC projects do not issue any tickets there and we can handle them on our own, right? Best regards, Marcus PS: You sent the minutes of the last PhC as .webarchive file. We managed to open it with some effort, but we would prefer .doc or .pdf files :) -- Marcus Laumer External service provider at Siemens AG Corporate Technology Corporate Research and Technologies CT T DE IT2 Otto-Hahn-Ring 6 81739 Munich, Germany Tel.: +49 (89) 636-45149 mailto:marcus.laumer.ext at siemens.com Important notice: This e-mail and any attachment thereof contain corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank you. ________________________________ 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 Tue Mar 13 15:28:05 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 13 Mar 2012 15:28:05 +0100 Subject: [Fiware-data] Data/Context Architecture Diagram Message-ID: Dear Wp Colleagues, I have updated the diagram for the chapter section of D2.3 at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Data/Context_Management_Architecture_(PRELIMINARY) I introduced the Query Broker element and made the changes to CEP connections suggested by Tali. If there are more comments, please let me know. Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx From ralli at tid.es Wed Mar 14 10:55:31 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 14 Mar 2012 10:55:31 +0100 Subject: [Fiware-data] Tomorrow's follow up call is cancelled. Message-ID: <64C22498-93D0-4298-9457-EA9C106FBD66@tid.es> Dear WP Colleagues, We are making some final efforts to finish & deliver D2.3 and D2.4 so we've decided to cancel tomorrow's follow up. Therefore, our next call conf will be Thursday next week, March 22nd at 10:30. Should you have any relevant/urgent issue, please use the mailing list or just drop me an e-mail. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Fri Mar 16 07:23:02 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 16 Mar 2012 07:23:02 +0100 Subject: [Fiware-data] A new daddy among us Message-ID: <4F62DC46.10907@tid.es> Hi all, I'm glad to announce you that Carlos entered the selected club of daddys yesterday. His first child was born yesterday and weighed 3,4 Kg. Everything was Ok. Carlos will be around two weeks on paternity leave. He most probably join us again on March 2-3. Again ... Congratulations to Carlos and his (now bigger) family !! Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Fri Mar 16 07:30:16 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 16 Mar 2012 07:30:16 +0100 Subject: [Fiware-data] Revision of Data/Context Management Technical Roadmap Message-ID: <4F62DDF8.7060807@tid.es> Hi all, I will act as WPL while Carlos is on Paternity leave. So don't hesitate to contact me on any matter. I have carried out a revision of the contents of our chapter's contribution to the FI-WARE Technical Roadmap deliverable. A new version of it is available at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Data-Context Please take a few minutes to review that everything is ok with you. Besides a few changes to improve readability, I have added the following major clarifications: * Explain that all GEs will provide a Restful API for app developers * Explain that the Pub/Sub Broker GE will implement a subset of the operations defined in FI-WARE NGSI Restful API for the first release and the complete FI-WARE NGSI Restful API in the Second Release (A ContextML-based higher-level API will be supported also in the first release) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.amon at siemens.com Mon Mar 19 16:23:11 2012 From: p.amon at siemens.com (Amon, Peter) Date: Mon, 19 Mar 2012 16:23:11 +0100 Subject: [Fiware-data] Revision of Data/Context Management Technical Roadmap In-Reply-To: <4F62DDF8.7060807@tid.es> References: <4F62DDF8.7060807@tid.es> Message-ID: Dear Juanjo, I implemented some pending changes that were agreed on in the PhC on March 8 (see the minutes) and that Carlos planned to incorporate. Otherwise, the page seems fine to me. Kind regards Peter ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 16. M?rz 2012 07:30 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revision of Data/Context Management Technical Roadmap Hi all, I will act as WPL while Carlos is on Paternity leave. So don't hesitate to contact me on any matter. I have carried out a revision of the contents of our chapter's contribution to the FI-WARE Technical Roadmap deliverable. A new version of it is available at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Data-Context Please take a few minutes to review that everything is ok with you. Besides a few changes to improve readability, I have added the following major clarifications: * Explain that all GEs will provide a Restful API for app developers * Explain that the Pub/Sub Broker GE will implement a subset of the operations defined in FI-WARE NGSI Restful API for the first release and the complete FI-WARE NGSI Restful API in the Second Release (A ContextML-based higher-level API will be supported also in the first release) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From e.fiware1 at tid.es Thu Mar 22 10:52:32 2012 From: e.fiware1 at tid.es (Grant Croker) Date: Thu, 22 Mar 2012 10:52:32 +0100 Subject: [Fiware-data] Data/Context call cancelled - 22/03/12 Message-ID: <000301cd0811$80ae8680$820b9380$%fiware1@tid.es> Hi all, due to Carlos being out on paternity leave today?s WP call has been cancelled. We are looking to reschedule the call for next Monday. An agenda item will be the discussion is the definition/specification of the RESTful interface. If you have any other points you wish to bring up please let me know. Regards grant ________________________________ 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 Mon Mar 26 09:29:51 2012 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Mon, 26 Mar 2012 09:29:51 +0200 Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub BrokerGE and the CEP GE In-Reply-To: References: <4F4CC61B.2010806@tid.es> Message-ID: Thank for these details Guy, About the REST based interaction, in your description, the CEP is a REST client which synchronously GET events from an input event source (pull mode). Could CEP be viewed as a REST service to which a event source could act as a REST client POSTing events to CEP (push mode)? Regards, Fano ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: mercredi 29 f?vrier 2012 20:27 To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu; fiware-data-bounces at lists.fi-ware.eu Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub BrokerGE and the CEP GE Hi all, "Third" module responsibility of conversion - this could be done by implementing specific input and output adapters of our CEP engine These adapters support JMS meaning we can subscribe to a topic or listen to a queue for incoming events and we can publish to a topic or send to a queue outgoing events \ complex events. These adapters also support REST as clients. Meaning we can REST GET events from a RESTfull service as incoming events to CEP and we can REST POST events to a RESTfull service as outgoing \ complex events Regards, Guy Sharon Manager, Event-based Middleware & Solutions Group IBM Research - Haifa ________________________________ Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: and within IBM on: Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Moltchanov Boris To: Juanjo Hierro Cc: "fiware-data at lists.fi-ware.eu" Date: 29/02/2012 20:04 Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi Juanjo, Ok. Got your point and never used it differently. Sorry if sometimes seemed differently. I would confirm that the PubSub based on the context broker is unable to handle any request without an valuated entityID notation. Thus, as stated from very beginning and discussed with Guy and as you suggested (after conversation with Carlo during the last f2f) we have to comply with the context data structure (Within the vision document). Otherwise the query, subscription and entity resolution all based on the context broker will not work (confirmation from Telecom Italia developers). Therefore regarding the third point (Event Objects) of your email below the PubSub shall receive EventsObjects, and then eventually republishing them to the consumers, with an entityID and will provide to anyone CEP included the context data elements with entityIDs. You have suggested, if I'm not wrong, to put this enityID either fixed or fixed but configurable. I suggest, as discussed with Guy and tried to explain in the call, that we derive the entityID from the EO's attributes if there is at least one. If there is no one a fixed entityID such as entityID=CEP shall be introduces. And viceversa an entityID coming from the PubSub into the CEP might be "encoded" into the EO's entity attribute element. However both such conversions are out of scope of the current components and shall be performed by a "third" module that will accomplish an EO into the context element (EO(event,opt.entityID) -> context(entityID, scope=event) and viceversa will rebuild an EO from a context element (context(entityID,scope)->EO(scope+attr.entityID)). Moreover, the same "third" module could perform subscription to the PubSub for the events/scopes that the CEP needs to derive the EO, as far as, if I remember well, the CEP is unable to perform the subscription and shall be feeded (pushed) by the events or contexts_as_events, Guy confirm? And the PubSub does not perform subscription on itself, but on behalf of a consumer. There may be no explicit specific consumer for feeding the CEP, thus this subscription task to the PubSub on behalf of the CEP will be taken by this "third" component. Let's have a closer look to this proposed architectural/functional vision in tomorrow AC. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu ] On Behalf Of Juanjo Hierro Sent: Tuesday, February 28, 2012 1:19 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Hi Boris, PLEASE, while making your proposal for the solution on how to map concepts between the Pub/Sub Broker GE and CEP pleas DO FOLLOW the terms and definitions proposed in the FI-WARE Product Vision: * "Context Elements" (which certainly map to the concepts defined in OMA) * "Data Elements" (= Context Elements but without EntityId) * "Event Objects": the programming structure that will be used by the CEP into which Context Elements and Data Elements should be mapped. Let's try to avoid the term "Event" which may introduce confusion and doesn't add to much the technical discussion which is indeed about how to map between the data structures listed above (the term Event can be used but should then be under the definition provided in the FI-WARE Product Vision). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2305433.jpg Type: image/jpeg Size: 518 bytes Desc: ATT2305433.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2305434.jpg Type: image/jpeg Size: 467 bytes Desc: ATT2305434.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2305435.jpg Type: image/jpeg Size: 494 bytes Desc: ATT2305435.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2305436.gif Type: image/gif Size: 360 bytes Desc: ATT2305436.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2305437.gif Type: image/gif Size: 677 bytes Desc: ATT2305437.gif URL: From GUYSH at il.ibm.com Mon Mar 26 10:21:42 2012 From: GUYSH at il.ibm.com (Guy Sharon) Date: Mon, 26 Mar 2012 10:21:42 +0200 Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub BrokerGE and the CEP GE In-Reply-To: References: <4F4CC61B.2010806@tid.es> Message-ID: In essence CEP could provide the REST service - however - for the first test bed deployment we plan to deploy the CEP GE as a simple J2SE program. Meaning there is no web server or application server. So the only thing we want to provide at this point is the ability to GET events and POST derived events As we continue and want to provide scale etc. we should move away from the simple J2SE program and there we will have such capabilities based on the underlying infrastructure the CEP GE will run on. Regards, Guy Sharon Manager, Event-based Middleware & Solutions Group IBM Research - Haifa Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: and within IBM on: Haifa University, Mount Carmel Haifa, HA 31905 Israel From: To: Guy Sharon/Haifa/IBM at IBMIL, , Cc: , Date: 26/03/2012 09:29 Subject: RE: [Fiware-data] PLEASE: Regarding integration between Pub/Sub BrokerGE and the CEP GE Thank for these details Guy, About the REST based interaction, in your description, the CEP is a REST client which synchronously GET events from an input event source (pull mode). Could CEP be viewed as a REST service to which a event source could act as a REST client POSTing events to CEP (push mode)? Regards, Fano From: fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: mercredi 29 f?vrier 2012 20:27 To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu; fiware-data-bounces at lists.fi-ware.eu Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub BrokerGE and the CEP GE Hi all, "Third" module responsibility of conversion - this could be done by implementing specific input and output adapters of our CEP engine These adapters support JMS meaning we can subscribe to a topic or listen to a queue for incoming events and we can publish to a topic or send to a queue outgoing events \ complex events. These adapters also support REST as clients. Meaning we can REST GET events from a RESTfull service as incoming events to CEP and we can REST POST events to a RESTfull service as outgoing \ complex events Regards, Guy Sharon Manager, Event-based Middleware & Solutions Group IBM Research - Haifa Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: and within IBM on: Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Moltchanov Boris To: Juanjo Hierro Cc: "fiware-data at lists.fi-ware.eu" Date: 29/02/2012 20:04 Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Sent by: fiware-data-bounces at lists.fi-ware.eu Hi Juanjo, Ok. Got your point and never used it differently. Sorry if sometimes seemed differently. I would confirm that the PubSub based on the context broker is unable to handle any request without an valuated entityID notation. Thus, as stated from very beginning and discussed with Guy and as you suggested (after conversation with Carlo during the last f2f) we have to comply with the context data structure (Within the vision document). Otherwise the query, subscription and entity resolution all based on the context broker will not work (confirmation from Telecom Italia developers). Therefore regarding the third point (Event Objects) of your email below the PubSub shall receive EventsObjects, and then eventually republishing them to the consumers, with an entityID and will provide to anyone CEP included the context data elements with entityIDs. You have suggested, if I?m not wrong, to put this enityID either fixed or fixed but configurable. I suggest, as discussed with Guy and tried to explain in the call, that we derive the entityID from the EO?s attributes if there is at least one. If there is no one a fixed entityID such as entityID=CEP shall be introduces. And viceversa an entityID coming from the PubSub into the CEP might be ?encoded? into the EO?s entity attribute element. However both such conversions are out of scope of the current components and shall be performed by a ?third? module that will accomplish an EO into the context element (EO(event,opt.entityID) -> context(entityID, scope=event) and viceversa will rebuild an EO from a context element (context(entityID,scope)->EO(scope+attr.entityID)). Moreover, the same ?third? module could perform subscription to the PubSub for the events/scopes that the CEP needs to derive the EO, as far as, if I remember well, the CEP is unable to perform the subscription and shall be feeded (pushed) by the events or contexts_as_events, Guy confirm? And the PubSub does not perform subscription on itself, but on behalf of a consumer. There may be no explicit specific consumer for feeding the CEP, thus this subscription task to the PubSub on behalf of the CEP will be taken by this ?third? component. Let?s have a closer look to this proposed architectural/functional vision in tomorrow AC. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Tuesday, February 28, 2012 1:19 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Hi Boris, PLEASE, while making your proposal for the solution on how to map concepts between the Pub/Sub Broker GE and CEP pleas DO FOLLOW the terms and definitions proposed in the FI-WARE Product Vision: "Context Elements" (which certainly map to the concepts defined in OMA) "Data Elements" (= Context Elements but without EntityId) "Event Objects": the programming structure that will be used by the CEP into which Context Elements and Data Elements should be mapped. Let's try to avoid the term "Event" which may introduce confusion and doesn't add to much the technical discussion which is indeed about how to map between the data structures listed above (the term Event can be used but should then be under the definition provided in the FI-WARE Product Vision). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 518 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 467 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 494 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 360 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 518 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 467 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 494 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 360 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From ralli at tid.es Wed Mar 28 16:32:15 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 28 Mar 2012 16:32:15 +0200 Subject: [Fiware-data] Data/Context Follow up Call (Thu March 29th, 10:30-11:30) In-Reply-To: References: Message-ID: <0368B4FA-19C9-4F38-A239-1C2E8C0AD788@tid.es> Dear Wp Colleagues, Find here the googledoc that we will be using in tomorrow's Data/Context follow up. https://docs.google.com/document/d/1dPMVjTI6bhdEbjlgJVLMg_YDa9nVQU7vQryj_IAcHJI/edit I will be adding more details to the existing agenda in this file today in the evening. Please, do not forget to register as available and providing suggestions to the agenda if any. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: 20120329_Data-Context_Minutes_v1.doc Type: application/msword Size: 44032 bytes Desc: 20120329_Data-Context_Minutes_v1.doc URL: From boris.moltchanov at telecomitalia.it Wed Mar 28 17:02:05 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 28 Mar 2012 17:02:05 +0200 Subject: [Fiware-data] Data/Context Follow up Call (Thu March 29th, 10:30-11:30) In-Reply-To: <0368B4FA-19C9-4F38-A239-1C2E8C0AD788@tid.es> References: <0368B4FA-19C9-4F38-A239-1C2E8C0AD788@tid.es> Message-ID: Dear Carlos, All, unfortunately I'm not available this week, thus will not participate in the tomorrow audio-conference. Best Regards, Boris -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of CARLOS RALLI UCENDO Sent: Wednesday, March 28, 2012 4:32 PM To: Fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Data/Context Follow up Call (Thu March 29th, 10:30-11:30) Dear Wp Colleagues, Find here the googledoc that we will be using in tomorrow's Data/Context follow up. https://docs.google.com/document/d/1dPMVjTI6bhdEbjlgJVLMg_YDa9nVQU7vQryj_IAcHJI/edit I will be adding more details to the existing agenda in this file today in the evening. Please, do not forget to register as available and providing suggestions to the agenda if any. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. From ralli at tid.es Thu Mar 29 11:07:23 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 29 Mar 2012 11:07:23 +0200 Subject: [Fiware-data] Important-> Summary of Data/Context Follow up Call (Thu March 29th, 10:30-11:30) In-Reply-To: <0368B4FA-19C9-4F38-A239-1C2E8C0AD788@tid.es> References: <0368B4FA-19C9-4F38-A239-1C2E8C0AD788@tid.es> Message-ID: <97D9C815-0FC3-4D51-B26E-E4120405BAB1@tid.es> Dear WP Colleagues, At the end only Siemens, TI & TID provided an answer for the call today so I have decided to request the status information off line and make a new appointment for next week. As next week it will be easter, I propose to have our call on wednesday at 10:30-11:30. Please, confirm ASAP your availability. I would appreciate your efforts to participate as long as we have missed two weeks with this one and the feedback for today was really low. Data that you are expected to send to me so I can compile a WP report: - Status of your development tasks at this point (March'12, Sprint #5). Highlight deviations. - Plan ahead for Sprint #6 and also communicate if deviations will impact Release 1 (in this case, it should be documented in the technical roadmap). - Progress on the REST specs of your assets. Please send this information to me before the end of this week. Thanks for your cooperation, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ El 28/03/2012, a las 16:32, CARLOS RALLI UCENDO escribi?: > Dear Wp Colleagues, > > Find here the googledoc that we will be using in tomorrow's Data/Context follow up. > https://docs.google.com/document/d/1dPMVjTI6bhdEbjlgJVLMg_YDa9nVQU7vQryj_IAcHJI/edit > > I will be adding more details to the existing agenda in this file today in the evening. > > Please, do not forget to register as available and providing suggestions to the agenda if any. > > Best regards, > -- > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > Product Development & Innovation > Telef?nica I+D SAU > Madrid, Spain > ------------------------------------------------------------------------------------------------------------------------ > Follow FI-WARE project (Future Internet Services Core Platform): > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: @fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ------------------------------------------------------------------------------------------------------------------------ > > <20120329_Data-Context_Minutes_v1.doc> 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 Thu Mar 29 11:12:29 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 29 Mar 2012 11:12:29 +0200 Subject: [Fiware-data] Important-> Summary of Data/Context Follow up Call (Thu March 29th, 10:30-11:30) In-Reply-To: <97D9C815-0FC3-4D51-B26E-E4120405BAB1@tid.es> References: <0368B4FA-19C9-4F38-A239-1C2E8C0AD788@tid.es> <97D9C815-0FC3-4D51-B26E-E4120405BAB1@tid.es> Message-ID: I'm available for the proposed date/time (Wednesday, 10:30-11:30). Currently involved in the finalizing of IoT NSGI-like binding and hopefully as Juanjo promised we will have it closed by the END OF THIS MOTH because ONLY THEN TI will start with the development of the secondary Pub/Sub GE interface accordingly to the previous communication. BR, B -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of CARLOS RALLI UCENDO Sent: Thursday, March 29, 2012 11:07 AM To: Fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Important-> Summary of Data/Context Follow up Call (Thu March 29th, 10:30-11:30) Dear WP Colleagues, At the end only Siemens, TI & TID provided an answer for the call today so I have decided to request the status information off line and make a new appointment for next week. As next week it will be easter, I propose to have our call on wednesday at 10:30-11:30. Please, confirm ASAP your availability. I would appreciate your efforts to participate as long as we have missed two weeks with this one and the feedback for today was really low. Data that you are expected to send to me so I can compile a WP report: - Status of your development tasks at this point (March'12, Sprint #5). Highlight deviations. - Plan ahead for Sprint #6 and also communicate if deviations will impact Release 1 (in this case, it should be documented in the technical roadmap). - Progress on the REST specs of your assets. Please send this information to me before the end of this week. Thanks for your cooperation, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ El 28/03/2012, a las 16:32, CARLOS RALLI UCENDO escribi?: > Dear Wp Colleagues, > > Find here the googledoc that we will be using in tomorrow's Data/Context follow up. > https://docs.google.com/document/d/1dPMVjTI6bhdEbjlgJVLMg_YDa9nVQU7vQr > yj_IAcHJI/edit > > I will be adding more details to the existing agenda in this file today in the evening. > > Please, do not forget to register as available and providing suggestions to the agenda if any. > > Best regards, > -- > ---------------------------------------------------------------------- > -------------------------------------------------- > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > Product Development & Innovation > Telef?nica I+D SAU > Madrid, Spain > ---------------------------------------------------------------------- > -------------------------------------------------- > Follow FI-WARE project (Future Internet Services Core Platform): > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: @fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > -------------------------------------------------- > > <20120329_Data-Context_Minutes_v1.doc> 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.