From jhierro at tid.es Wed Jun 1 08:32:37 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Jun 2011 08:32:37 +0200 Subject: [Fiware-data] Fwd: Re: Timeslots for pending confcalls Message-ID: <4DE5DD05.9030408@tid.es> Hi all, These are the coordinates for the webex. https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&PW=NMDRhMGQ0MThl&RT=MTQjMjM%3D We may use the same powownow bridge that we used yesterday if there is no other bridge available: PIN 050662 dial-in phones in the attachment Cheers, -- Juanjo -------- Original Message -------- Subject: Invitaci?n a reuni?n: FI-WARE Query/Searching Access and Localization enablers Date: Wed, 1 Jun 2011 08:24:03 +0200 From: Gestor i-Reunion webex5000 Reply-To: Webex5000 at tid.es To: JUAN JOSE HIERRO SUREDA Hola , Gestor i-Reunion webex5000 lo invita a asistir a esta reuni?n en l?nea. Tema: FI-WARE Query/Searching Access and Localization enablers Fecha: mi?rcoles, 1 de junio de 2011 Hora: 9:00, Europa Verano Hora (Par?s, GMT+02:00) N?mero de la reuni?n: 965 726 400 Contrase?a de la reuni?n: 1234abcD ------------------------------------------------------- Para unirse a la reuni?n en l?nea (?Ahora tambi?n desde iPhones!) ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&PW=NMDRhMGQ0MThl&RT=MTQjMjM%3D 2. Introduzca su nombre y direcci?n de correo electr?nico. 3. Introduzca la contrase?a de la reuni?n: 1234abcD 4. Haga clic en "Entrar ahora". Para ver en otras zonas horarias o idiomas, haga clic en el enlace: https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&PW=NMDRhMGQ0MThl&ORT=MTQjMjM%3D ------------------------------------------------------- Para obtener ayuda ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/mc 2. En la barra de navegaci?n izquierda, haga clic en "Soporte". Puede ponerse en contacto conmigo en: Webex5000 at tid.es Para a?adir esta reuni?n al programa del calendario (por ejemplo Microsoft Outlook), haga clic en este enlace: https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&ICS=MI&LD=12&RD=14&ST=1&SHA2=dTXiizPxCjfgJTaoE3QQ7li/zfBMyzfd6r2pc7Yfcc4=&RT=MTQjMjM%3D La reproducci?n de archivos multimedia enriquecidos con formato universal de comunicaciones (UCF) necesita reproductores adecuados. Para ver este tipo de archivos multimedia enriquecidos en esta reuni?n, compruebe si tiene los reproductores instalados en la computadora. Vaya a https://telefonica.webex.com/telefonica/systemdiagnosis.php Inscr?base para disfrutar de la prueba gratuita de WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com ________________________________ 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: powownow-dial-in-numbers.pdf Type: application/pdf Size: 61661 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Wed Jun 1 08:33:09 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Jun 2011 08:33:09 +0200 Subject: [Fiware-data] Confcall on FI-WARE Query/Searching Access GEs Message-ID: <4DE5DD25.7090008@tid.es> Hi all, These are the coordinates for the webex. https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&PW=NMDRhMGQ0MThl&RT=MTQjMjM%3D We may use the same powownow bridge that we used yesterday if there is no other bridge available: PIN 050662 dial-in phones in the attachment Cheers, -- Juanjo -------- Original Message -------- Subject: Invitaci?n a reuni?n: FI-WARE Query/Searching Access and Localization enablers Date: Wed, 1 Jun 2011 08:24:03 +0200 From: Gestor i-Reunion webex5000 Reply-To: Webex5000 at tid.es To: JUAN JOSE HIERRO SUREDA Hola , Gestor i-Reunion webex5000 lo invita a asistir a esta reuni?n en l?nea. Tema: FI-WARE Query/Searching Access and Localization enablers Fecha: mi?rcoles, 1 de junio de 2011 Hora: 9:00, Europa Verano Hora (Par?s, GMT+02:00) N?mero de la reuni?n: 965 726 400 Contrase?a de la reuni?n: 1234abcD ------------------------------------------------------- Para unirse a la reuni?n en l?nea (?Ahora tambi?n desde iPhones!) ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&PW=NMDRhMGQ0MThl&RT=MTQjMjM%3D 2. Introduzca su nombre y direcci?n de correo electr?nico. 3. Introduzca la contrase?a de la reuni?n: 1234abcD 4. Haga clic en "Entrar ahora". Para ver en otras zonas horarias o idiomas, haga clic en el enlace: https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&PW=NMDRhMGQ0MThl&ORT=MTQjMjM%3D ------------------------------------------------------- Para obtener ayuda ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/mc 2. En la barra de navegaci?n izquierda, haga clic en "Soporte". Puede ponerse en contacto conmigo en: Webex5000 at tid.es Para a?adir esta reuni?n al programa del calendario (por ejemplo Microsoft Outlook), haga clic en este enlace: https://telefonica.webex.com/telefonica/j.php?ED=153706172&UID=1214279657&ICS=MI&LD=12&RD=14&ST=1&SHA2=dTXiizPxCjfgJTaoE3QQ7li/zfBMyzfd6r2pc7Yfcc4=&RT=MTQjMjM%3D La reproducci?n de archivos multimedia enriquecidos con formato universal de comunicaciones (UCF) necesita reproductores adecuados. Para ver este tipo de archivos multimedia enriquecidos en esta reuni?n, compruebe si tiene los reproductores instalados en la computadora. Vaya a https://telefonica.webex.com/telefonica/systemdiagnosis.php Inscr?base para disfrutar de la prueba gratuita de WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com ________________________________ 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: powownow-dial-in-numbers.pdf Type: application/pdf Size: 61661 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From fano.ramparany at orange-ftgroup.com Wed Jun 1 12:10:12 2011 From: fano.ramparany at orange-ftgroup.com (fano.ramparany at orange-ftgroup.com) Date: Wed, 1 Jun 2011 12:10:12 +0200 Subject: [Fiware-data] FI-WARE Data / PublishSubscribe GE / OL slides and article Message-ID: Dear all, I've uploaded OL slides presented at the yesterday concall meeting dedicated on Publish/Subscribe GE, with an article about OL approach to be published at a IE'2011 workshop next July. http://forge.fi-ware.eu/frs/download.php/3/2011-05-31OLPubSubPrez.pdf http://forge.fi-ware.eu/frs/download.php/4/WISHWellIE11midasFinal.pdf Let me know if there's any problem accessing it. Regards, Fano -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric.clavier at orange-ftgroup.com Wed Jun 1 16:52:06 2011 From: eric.clavier at orange-ftgroup.com (eric.clavier at orange-ftgroup.com) Date: Wed, 1 Jun 2011 16:52:06 +0200 Subject: [Fiware-data] : FT contributors on Personal Data Synchronization topic In-Reply-To: <4DE5DD25.7090008@tid.es> References: <4DE5DD25.7090008@tid.es> Message-ID: <2CAE5634D52E194BA393187E0568E1AC05F6B9EE@ftrdmel1> Hi Juanjo, Dany will replace me on the data synchronization topic aspects in the WP. Could you add him to the mailing-list ? We will get back to you to present our contribution Best regards Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Jun 1 18:01:49 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Jun 2011 18:01:49 +0200 Subject: [Fiware-data] Consolidated version of the Context/Data Management Chapter in the FI-WARE High-level Description Message-ID: <4DE6626D.1080103@tid.es> Dear Colleagues, You can find a first consolidated draft of the Context/Data Management Chapter in the FI-WARE High-Level Description Document. Some remarks: * Overall, the description of GEs still require quite some work. Without entering into the actual contents, the description of GEs provided by Siemens (multimedia analysis to gather multi-media metadata, preprocesing of metadata after/during gathering and Searching/Quering Access) are very good examples of the level of detail and style of description we should intend to achieve. Going more into details for each of the GEs: * Big Data Processing Enabler: We have to provide much more level of detail. It would be rather relevant to describe what operations will be offered to programmers going beyond the simple map-reduce operations that existing products such as Hadoop currently offer. * Regarding the Complex Event Processing Enabler, you should elaborate on the architecture of the implementation we are currently envisioning a little bit (concept of network of processing nodes). You, of course, have to point out that this would be considered a potential implementation but not the only one that could be valid. Besides, it would be worth providing a vision and description of operations (API) that the GE will offer to the programmer of how a given application will invoke those operations at runtime. * Regarding the GEs whose description was provided by Siemens, once again they are in a very good shape. However, we have to still work on some of them: a) we have to find out whether we need something like the "preprocesing of metadata after/during gathering" enabler of this same functionality can be achieved through the CEP generic enabler; b) we have to probably review the GE on "Searching/Quering Access" under the light of the discussion this morning * Regarding Intelligent Services, some of them requires further elaboration, most of them are in a good shape. * Regarding the Pub/Sub GE, figures are very nice but more explanations have to be given. While reading it, the description of the CORBA Event Service came to my mind ... we need sections like the ones that were included in that spec describing what a consumer or a supplier was, what a channel was and how one entities interact with the others. You may elaborate on the way these entities interact by simply describing the pictures you have already provided (suggestion: assign some numbering to operations in the figures and then describe the interaction following steps with the same numbering. * In generating a new draft of your contribution, please take this document as the starting point (this is because I had to make some changes in the template I wouldn't like to miss in next drafts) * I haven't yet added the contribution from ATOS because they were too preliminary. Please take a look at the examples from Siemens and deliver something more elaborated. Next steps: * I expect a new take from your side by tuesday June 7th EOB at the latest. One action on you would have to do with adding points to the Security subsection I have added in section 3.1.3. * I will send my notes from the rather relevant confcalls we had both yesterday (Publish/Subscribe Broker) and today (Query/Searching Access). There will be some points in which I will try to describe the agreement we reached. Authors of the sections describing the corresponding GEs will have to review these notes and try to implement the necessary changes in their descriptions to capture what we have agreed. There will be other points that will still remain as points for further discussion. Let's try to keep a thread of discussion over the email and see how much progress we achieve. In general terms, agreements we reach should go to the description of GEs (or the Overview section) while points that remain open will finally go to the Question Marks section. * I will start identifying the terms we should describe in a precise way. I may also try to provide some definitions to incorporate in the next draft. Don't hesitate to send your comments/feedback to this planning. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE_High-Level_Description_11-06-1 Data-Context Management v1.0 11-06-01.doc Type: application/msword Size: 2912768 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Wed Jun 1 18:09:00 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Jun 2011 18:09:00 +0200 Subject: [Fiware-data] Consolidated version of the Context/Data Management Chapter in the FI-WARE High-level Description In-Reply-To: <4DE6626D.1080103@tid.es> References: <4DE6626D.1080103@tid.es> Message-ID: <4DE6641C.4060201@tid.es> Hi, I forgot to send a link instead of an attachment :-) For your convenience, I have uploaded the document also at the server: http://forge.fi-ware.eu/docman/view.php/9/91/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.0+11-06-01.doc Best regards, -- Juanjo On 01/06/11 18:01, Juanjo Hierro wrote: Dear Colleagues, You can find a first consolidated draft of the Context/Data Management Chapter in the FI-WARE High-Level Description Document. Some remarks: * Overall, the description of GEs still require quite some work. Without entering into the actual contents, the description of GEs provided by Siemens (multimedia analysis to gather multi-media metadata, preprocesing of metadata after/during gathering and Searching/Quering Access) are very good examples of the level of detail and style of description we should intend to achieve. Going more into details for each of the GEs: * Big Data Processing Enabler: We have to provide much more level of detail. It would be rather relevant to describe what operations will be offered to programmers going beyond the simple map-reduce operations that existing products such as Hadoop currently offer. * Regarding the Complex Event Processing Enabler, you should elaborate on the architecture of the implementation we are currently envisioning a little bit (concept of network of processing nodes). You, of course, have to point out that this would be considered a potential implementation but not the only one that could be valid. Besides, it would be worth providing a vision and description of operations (API) that the GE will offer to the programmer of how a given application will invoke those operations at runtime. * Regarding the GEs whose description was provided by Siemens, once again they are in a very good shape. However, we have to still work on some of them: a) we have to find out whether we need something like the "preprocesing of metadata after/during gathering" enabler of this same functionality can be achieved through the CEP generic enabler; b) we have to probably review the GE on "Searching/Quering Access" under the light of the discussion this morning * Regarding Intelligent Services, some of them requires further elaboration, most of them are in a good shape. * Regarding the Pub/Sub GE, figures are very nice but more explanations have to be given. While reading it, the description of the CORBA Event Service came to my mind ... we need sections like the ones that were included in that spec describing what a consumer or a supplier was, what a channel was and how one entities interact with the others. You may elaborate on the way these entities interact by simply describing the pictures you have already provided (suggestion: assign some numbering to operations in the figures and then describe the interaction following steps with the same numbering. * In generating a new draft of your contribution, please take this document as the starting point (this is because I had to make some changes in the template I wouldn't like to miss in next drafts) * I haven't yet added the contribution from ATOS because they were too preliminary. Please take a look at the examples from Siemens and deliver something more elaborated. Next steps: * I expect a new take from your side by tuesday June 7th EOB at the latest. One action on you would have to do with adding points to the Security subsection I have added in section 3.1.3. * I will send my notes from the rather relevant confcalls we had both yesterday (Publish/Subscribe Broker) and today (Query/Searching Access). There will be some points in which I will try to describe the agreement we reached. Authors of the sections describing the corresponding GEs will have to review these notes and try to implement the necessary changes in their descriptions to capture what we have agreed. There will be other points that will still remain as points for further discussion. Let's try to keep a thread of discussion over the email and see how much progress we achieve. In general terms, agreements we reach should go to the description of GEs (or the Overview section) while points that remain open will finally go to the Question Marks section. * I will start identifying the terms we should describe in a precise way. I may also try to provide some definitions to incorporate in the next draft. Don't hesitate to send your comments/feedback to this planning. 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Wed Jun 1 18:21:28 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Jun 2011 18:21:28 +0200 Subject: [Fiware-data] Reviewing security issues in first draft of the Context/Data Management Message-ID: <4DE66708.7060609@tid.es> Hi, First of all, I have updated the first draft in the server so, please downloading it again if you were too fast and already did it before reading this email :-) I have just updated the section on question marks as to assign a section for Security and subsections for topics regarding Security, instead of a subsection for Security with a bullet list of topics. The link is still the same: http://forge.fi-ware.eu/docman/view.php/9/91/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.0+11-06-01.doc The rest of this message is specifically targeted to our colleagues from the Security WP who I'm sure are monitoring what we are doing ;-) Now that we have a first draft (though still this needs quite more work) I would suggest that you carry out a first overall revision identifying security issues that should be taken into account. I would encourage you to contribute a description of such issues in the section about Security Issues I have created in section 3.1.3. Please confirm that you have read and understood this message. Your contributions are due on June 7, EOB like for the rest of the WP team. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Thu Jun 2 18:12:52 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 02 Jun 2011 18:12:52 +0200 Subject: [Fiware-data] Cancelation of follow-up confcall tomorrow Message-ID: <4DE7B684.2060305@tid.es> Hi all, I believe it doesn't make so much sense to have a confcall tomorrow. Besides, some of you mentioned that today was bank holiday in your country and therefore would also have holidays tomorrow. You should have already received instructions about next steps (contributions for next draft due on June 7 EOB) I'm still working on the notes and thoughts from our previous confcall this week (Publish/Subscribe Broker and Query Access GE). It is preferable that you spend the time of the confcall tomorrow to review these notes and provide any comment. Let's iterate through the mailing list. Best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Thu Jun 2 23:27:03 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 2 Jun 2011 23:27:03 +0200 Subject: [Fiware-data] FI-WARE Data / PublishSubscribe GE / OL slides and article In-Reply-To: References: Message-ID: Dear All, I've added the slides TI have presented for Pub/Sub and Search/Query interface http://forge.fi-ware.eu/docman/view.php/9/99/FI-WARE_ContextQuery-CQL_v3.pdf. Juanjo, may you please check if this document is marked as private? I didn't find a way to explicit it creating the directory and uploading the document. Thank you. Best Regards, Boris From: fano.ramparany at orange-ftgroup.com [mailto:fano.ramparany at orange-ftgroup.com] Sent: Wednesday, June 01, 2011 12:10 PM To: jhierro at tid.es; Moltchanov Boris; sabine.zander at orange-ftgroup.com Cc: fiware-data at lists.fi-ware.eu Subject: FI-WARE Data / PublishSubscribe GE / OL slides and article Dear all, I've uploaded OL slides presented at the yesterday concall meeting dedicated on Publish/Subscribe GE, with an article about OL approach to be published at a IE'2011 workshop next July. http://forge.fi-ware.eu/frs/download.php/3/2011-05-31OLPubSubPrez.pdf http://forge.fi-ware.eu/frs/download.php/4/WISHWellIE11midasFinal.pdf Let me know if there's any problem accessing it. Regards, Fano Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Fri Jun 3 05:46:17 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 Jun 2011 05:46:17 +0200 Subject: [Fiware-data] FI-WARE Data / PublishSubscribe GE / OL slides and article In-Reply-To: References: Message-ID: <4DE85909.9020905@tid.es> Dear Boris, I have labeled it as private. Unfortunately, you have to make this in two steps. You have to upload (submit) the document first. The document will be labeled as "active" at that point, which means, among other things, that it is publicly available. Therefore, right afterwards, you have to navigate to it through the Admin page and when you click on the document, you will be provided a form where you can label it as "private". I would consider reasonable that you could select the state as "private" at the form where you create the request for submitting the doc, but for some strange reason, the docman system doesn't allow to do this. Anyway, most probably I will announce availability of subversion next week for all projects in FusionForge. Indeed, it is already there, but I would like to play first a bit with it to doublecheck everything is OK. Probably then what makes sense is to switch to subversion for uploading/sharing/downloading docs. Best regards, -- Juanjo On 02/06/11 23:27, Moltchanov Boris wrote: Dear All, I?ve added the slides TI have presented for Pub/Sub and Search/Query interface http://forge.fi-ware.eu/docman/view.php/9/99/FI-WARE_ContextQuery-CQL_v3.pdf. Juanjo, may you please check if this document is marked as private? I didn?t find a way to explicit it creating the directory and uploading the document. Thank you. Best Regards, Boris From: fano.ramparany at orange-ftgroup.com [mailto:fano.ramparany at orange-ftgroup.com] Sent: Wednesday, June 01, 2011 12:10 PM To: jhierro at tid.es; Moltchanov Boris; sabine.zander at orange-ftgroup.com Cc: fiware-data at lists.fi-ware.eu Subject: FI-WARE Data / PublishSubscribe GE / OL slides and article Dear all, I've uploaded OL slides presented at the yesterday concall meeting dedicated on Publish/Subscribe GE, with an article about OL approach to be published at a IE'2011 workshop next July. http://forge.fi-ware.eu/frs/download.php/3/2011-05-31OLPubSubPrez.pdf http://forge.fi-ware.eu/frs/download.php/4/WISHWellIE11midasFinal.pdf Let me know if there's any problem accessing it. Regards, Fano 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:part1.07030609.03070407 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Sun Jun 5 09:37:00 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 05 Jun 2011 09:37:00 +0200 Subject: [Fiware-data] Notes and thoughts on Publish/Subscribe GE and Query Access GE Message-ID: <4DEB321C.1020801@tid.es> Dear colleagues, I have uploaded on the following link: http://forge.fi-ware.eu/docman/view.php/9/108/Notes+and+Thoughts+on+Pub-Sub+Broker+and+Query+Access+GEs.doc a short document with notes and derived thoughts from our previous calls on the Publish/Subscribe GE and Query Access GE. I hope you all can endorse them so that we can make progress. I plan to use this document as basis for a post in our blog. It might be a reference of the kind of posts we may publish on progress of our activities in our blog (serving as an example for other WPs). Don't hesitate to make any comment. For your convenience, I have also attached its contents in plain text below. This may be helpful in any discussion. Best regards, -- Juanjo ======= 1. Motivation This document intends to summarize some notes and thoughts that may help to progress on the discussion about features that the Notification (Publish/Subscribe) Broker and the Query Access GE should support. They should be taken into consideration when writing the sections describing both GEs in the FI-WARE High-level Description document. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. About the Notification (Publish/Subscribe) Broker Enabler There are essentially two products on the table regarding this GE that may be considered as baseline for our work: * One from Telecom Italia, see [1] * Another one from Orange, see, see [2] and [3] The very basic concepts and operations in both proposals are similar, so probably it's not difficult to reach a consensus on entities/interfaces and operations. Actually, we may define the Notification (Publish/Subscribe) GE based on the following interfaces and operations (additional operations may be added): * The Notification Consumer interface, which would map to the Context Consumer interface in both the Telecom Italia's and Orange's proposal. This interface would support the notify operation (which may take the form of a post operation if the interface is implemented as a RESTful interface). It may also support a subscription_ended operation. * The Notification Broker interface, which would map to the Context Broker interface in Telecom Italia's proposal or to the Context Source interface in Orange's proposal. This interface would support the subscribe/unsubscribe operations. Querying of new data following a pull style of communication would be supported through a get operation exported by the Query Access GE as explained in section 4 of this report. * The Notification Broker Finder, which would map to the Context Broker interface in Orange's proposal. Note that this interface doesn't exist in Telecom Italia's proposal but this doesn't imply any conflict. This interface would support the discoverNB operation enabling to locate a Notification Broker Finder based on criteria (see discussion below). * The Notification Supplier interface, which would map to the Context Provider in Telecom Italia's proposal. This interface doesn't exist in Orange's proposal because sources of notifications directly export operations enabling multiple Consumers to subscribe. In other words, both the role of Notification Supplier and Notification Consumer are played by entities exporting the Context Source interface in Orange's proposal. This interface would support a get operation in order to support retrieval of new data complying with a given query, thus supporting a pull style of communication. This operation should follow the same signature as the get operation supported by the Query Access GE. A first conclusion and action point would be that we can describe the Notification (Publish/Subscribe) GE elaborating on this common set of entities/interfaces (i.e., product vision) and the operations they support. We would include a disclaimer at the beginning of the section explaining that the final set and signature of operations may change during final specification of the GE but it will be along the lines of what is described here. Given said the above, a fundamental difference of the two proposals has to do with the format of data being handled and notified (Telecom Italia supports a XML-based ContextML language while Orange supports RDFs). There are at least two aspects that strongly depend on the selected format for obvious reasons: * The kind of repository where data is stored (no matter whether it is located in a memory cache or in disk, the notion of repository is there) * The query language used to define subscriptions 3. Is a Universal Query language feasible? The conclusion of the team is that probably not. Even if it were feasible, it would imply to define "yet another query language" which certainly would impose severe barriers of adoption by the developers community. Something that would be feasible is to support multiple query languages and ask the programmer to declare what particular query language he/she wishes to use. This will determine the format/structure used to store data in the repository and the repository itself. Thus, a programmer may declare he/she wishes to use SPARQL while another may declare he/she wishes to use MPQF, CQL, Mongo DB's document-based query language or any other Query Language as long it is supported by the platform. Selection of the query language is a first step we may require the programmer to perform prior getting access to a particular Notification Broker, as illustrated in Figure 1. The complete list of steps to be followed by a Notification Consumer for subscribing to messages that comply with a given Query Language may be the following: 1. The Notification Consumer (NC) sends a request to the Notification Broker Finder (NBF) looking for a Notification Broker (NB) that supports a given Query Language specified as parameter in the request. 2. The NBF returns a reference to a NB supporting the specified Query Language 3. The NC subscribes to reception of data complying with a particular query by issuing a request to the NB. Note that in this model, the Notification Broker Finder plays a similar role to the Context Broker in Orange's Publish/Subscribe service. [cid:part1.00040104.00010200 at tid.es] Figure 1. Steps in connecting to a Publish/Subscribe Broker 4. Relationship between the Publish/Subscribe Broker GE and the Query Access GE The Context Broker component proposed by Telecom Italia, similarly to the Context Source component proposed by Orange, exported operations that would allow Consumers to query for context data. On the other hand, we have identified the need for a Query Access GE that allows to access to data stored in the FI-WARE Data/Context Management Platform. How should both means for quering data be related? After some discussion, we came to the conclusion that the Notification Broker interface to be defined in the Publish/Subscribe Broker GE should just export an operation that would return the access point to the interface offered by the Query Access GE. This interface should offer a get operation that enables to retrieve data that complies with a given query statement and has been stored in the platform after the last call to the same operation made by the same entity. This way, we would avoid duplicated interfaces. Note that a particular product may be providing the implementation of components implementing the Notification Broker interface and the Query Access interface for a particular query language (i.e., format for representing/storing data). This is illustrated in Figure 2. [cid:part2.07020607.09010509 at tid.es] Figure 2. Two products implementing the Publish/Subscribe Broker and Query Access interface for two different query languages 5. Abstract Query Language Families Two given query languages may have some common constructions/components and this may allow that a given query, formulated based on common constructions, can be executed by the corresponding Query Engines. Therefore, we may consider supporting the concept of "abstract query languages" in FI-WARE, each defined based on minimum common denominators of existing query languages. A question mark is what to do when abstract query languages are declared at the connection to the Publish/Subscribe Broker or the Query Access GEs. How are then queries executed? It seems like the solution may consist in performing a parallel execution of the query in compatible repositories (the query may be transferred to the query engines linked to each repository and then results gathered together in the response sent back to the application). However, there are still some open questions like, for example, what would be the actual format in which data results would be returned to the applications. We need to find out a solution or position on the matter. 6. Availability of data in different repositories Finally, there is still a big question mark regarding the following issue: what to do when some particular data is of interest to many applications but the query language each application uses to access data is different. Let's illustrate this scenario with an example. One data that may be of interest to several applications may be the ambient temperature measured in a given street. However, while a given application may wish to use Query Language "A" to subscribe for receiving such data through the Publish/Subscribe Broker GE, another application may wish to use Query Language "B". This would typically imply that the underlying engine is linked to a different Repository based on a different storage format. Then ... are both applications going to receive the data? Is the data going to be replicated in both repositories We need to find out a solution or position on the matter. 7. References [1] - http://forge.fi-ware.eu/docman/view.php/9/99/FI-WARE_ContextQuery-CQL_v3.pdf [2] - http://forge.fi-ware.eu/frs/download.php/3/2011-05-31OLPubSubPrez.pdf [3] - http://forge.fi-ware.eu/frs/download.php/4/WISHWellIE11midasFinal.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: clip_image002.gif Type: image/gif Size: 9036 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: clip_image004.gif Type: image/gif Size: 24189 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Sun Jun 5 09:50:44 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 05 Jun 2011 09:50:44 +0200 Subject: [Fiware-data] Pending action on Telecom Italia Message-ID: <4DEB3554.5040108@tid.es> Hi, I believe that one action point from our last telco was that Telecom Italia was going to send us a copy of the specs publishd in OMA regarding a Publish/Subscribe service. That would be helpful indeed. Best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Sun Jun 5 23:30:36 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Sun, 5 Jun 2011 23:30:36 +0200 Subject: [Fiware-data] Notes and thoughts on Publish/Subscribe GE and Query Access GE In-Reply-To: <4DEB321C.1020801@tid.es> References: <4DEB321C.1020801@tid.es> Message-ID: Dear All, Under the following link http://www.openmobilealliance.org/Technical/release_program/NGSI_v1_0.aspx you may find and download publicly available documents regarding the Next Generation Service Interface Enabler defined within OMA. Context management is represented there by NGSI-9/10 specifications. Among the documents you might be interested in the following documents: - OMA-RD-NGSI-V1_0-20100803-C.pdf - requirements considered for this Enabler; - OMA-AD-NGSI-V1_0-20100803-C.pdf - reference architecture of the Enabler; - OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf - context management interface description (NGSI-9 and NGSI-10). Moreover I recommend to take a look at the presentation http://www.ict-ccast.eu/workshops/2nd/13%20-%20OMA%20-%20Kovacs%20-%20OMA_ServiceAPI_Standardisation.pdf, which describes the Enabler at high-level. I preferred to give you the links to external documents on their respective web-sites instead of putting into our FI-WARE server or even worse sending via email. However if we need I may upload them to the server. 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: Sunday, June 05, 2011 9:37 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Notes and thoughts on Publish/Subscribe GE and Query Access GE Dear colleagues, I have uploaded on the following link: http://forge.fi-ware.eu/docman/view.php/9/108/Notes+and+Thoughts+on+Pub-Sub+Broker+and+Query+Access+GEs.doc a short document with notes and derived thoughts from our previous calls on the Publish/Subscribe GE and Query Access GE. I hope you all can endorse them so that we can make progress. I plan to use this document as basis for a post in our blog. It might be a reference of the kind of posts we may publish on progress of our activities in our blog (serving as an example for other WPs). Don't hesitate to make any comment. For your convenience, I have also attached its contents in plain text below. This may be helpful in any discussion. Best regards, -- Juanjo ======= 1. Motivation This document intends to summarize some notes and thoughts that may help to progress on the discussion about features that the Notification (Publish/Subscribe) Broker and the Query Access GE should support. They should be taken into consideration when writing the sections describing both GEs in the FI-WARE High-level Description document. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. About the Notification (Publish/Subscribe) Broker Enabler There are essentially two products on the table regarding this GE that may be considered as baseline for our work: * One from Telecom Italia, see [1] * Another one from Orange, see, see [2] and [3] The very basic concepts and operations in both proposals are similar, so probably it's not difficult to reach a consensus on entities/interfaces and operations. Actually, we may define the Notification (Publish/Subscribe) GE based on the following interfaces and operations (additional operations may be added): * The Notification Consumer interface, which would map to the Context Consumer interface in both the Telecom Italia's and Orange's proposal. This interface would support the notify operation (which may take the form of a post operation if the interface is implemented as a RESTful interface). It may also support a subscription_ended operation. * The Notification Broker interface, which would map to the Context Broker interface in Telecom Italia's proposal or to the Context Source interface in Orange's proposal. This interface would support the subscribe/unsubscribe operations. Querying of new data following a pull style of communication would be supported through a get operation exported by the Query Access GE as explained in section 4 of this report. * The Notification Broker Finder, which would map to the Context Broker interface in Orange's proposal. Note that this interface doesn't exist in Telecom Italia's proposal but this doesn't imply any conflict. This interface would support the discoverNB operation enabling to locate a Notification Broker Finder based on criteria (see discussion below). * The Notification Supplier interface, which would map to the Context Provider in Telecom Italia's proposal. This interface doesn't exist in Orange's proposal because sources of notifications directly export operations enabling multiple Consumers to subscribe. In other words, both the role of Notification Supplier and Notification Consumer are played by entities exporting the Context Source interface in Orange's proposal. This interface would support a get operation in order to support retrieval of new data complying with a given query, thus supporting a pull style of communication. This operation should follow the same signature as the get operation supported by the Query Access GE. A first conclusion and action point would be that we can describe the Notification (Publish/Subscribe) GE elaborating on this common set of entities/interfaces (i.e., product vision) and the operations they support. We would include a disclaimer at the beginning of the section explaining that the final set and signature of operations may change during final specification of the GE but it will be along the lines of what is described here. Given said the above, a fundamental difference of the two proposals has to do with the format of data being handled and notified (Telecom Italia supports a XML-based ContextML language while Orange supports RDFs). There are at least two aspects that strongly depend on the selected format for obvious reasons: * The kind of repository where data is stored (no matter whether it is located in a memory cache or in disk, the notion of repository is there) * The query language used to define subscriptions 3. Is a Universal Query language feasible? The conclusion of the team is that probably not. Even if it were feasible, it would imply to define "yet another query language" which certainly would impose severe barriers of adoption by the developers community. Something that would be feasible is to support multiple query languages and ask the programmer to declare what particular query language he/she wishes to use. This will determine the format/structure used to store data in the repository and the repository itself. Thus, a programmer may declare he/she wishes to use SPARQL while another may declare he/she wishes to use MPQF, CQL, Mongo DB's document-based query language or any other Query Language as long it is supported by the platform. Selection of the query language is a first step we may require the programmer to perform prior getting access to a particular Notification Broker, as illustrated in Figure 1. The complete list of steps to be followed by a Notification Consumer for subscribing to messages that comply with a given Query Language may be the following: 1. The Notification Consumer (NC) sends a request to the Notification Broker Finder (NBF) looking for a Notification Broker (NB) that supports a given Query Language specified as parameter in the request. 2. The NBF returns a reference to a NB supporting the specified Query Language 3. The NC subscribes to reception of data complying with a particular query by issuing a request to the NB. Note that in this model, the Notification Broker Finder plays a similar role to the Context Broker in Orange's Publish/Subscribe service. [cid:image001.gif at 01CC23D7.E4557B90] Figure 1. Steps in connecting to a Publish/Subscribe Broker 4. Relationship between the Publish/Subscribe Broker GE and the Query Access GE The Context Broker component proposed by Telecom Italia, similarly to the Context Source component proposed by Orange, exported operations that would allow Consumers to query for context data. On the other hand, we have identified the need for a Query Access GE that allows to access to data stored in the FI-WARE Data/Context Management Platform. How should both means for quering data be related? After some discussion, we came to the conclusion that the Notification Broker interface to be defined in the Publish/Subscribe Broker GE should just export an operation that would return the access point to the interface offered by the Query Access GE. This interface should offer a get operation that enables to retrieve data that complies with a given query statement and has been stored in the platform after the last call to the same operation made by the same entity. This way, we would avoid duplicated interfaces. Note that a particular product may be providing the implementation of components implementing the Notification Broker interface and the Query Access interface for a particular query language (i.e., format for representing/storing data). This is illustrated in Figure 2. [cid:image002.gif at 01CC23D7.E4557B90] Figure 2. Two products implementing the Publish/Subscribe Broker and Query Access interface for two different query languages 5. Abstract Query Language Families Two given query languages may have some common constructions/components and this may allow that a given query, formulated based on common constructions, can be executed by the corresponding Query Engines. Therefore, we may consider supporting the concept of "abstract query languages" in FI-WARE, each defined based on minimum common denominators of existing query languages. A question mark is what to do when abstract query languages are declared at the connection to the Publish/Subscribe Broker or the Query Access GEs. How are then queries executed? It seems like the solution may consist in performing a parallel execution of the query in compatible repositories (the query may be transferred to the query engines linked to each repository and then results gathered together in the response sent back to the application). However, there are still some open questions like, for example, what would be the actual format in which data results would be returned to the applications. We need to find out a solution or position on the matter. 6. Availability of data in different repositories Finally, there is still a big question mark regarding the following issue: what to do when some particular data is of interest to many applications but the query language each application uses to access data is different. Let's illustrate this scenario with an example. One data that may be of interest to several applications may be the ambient temperature measured in a given street. However, while a given application may wish to use Query Language "A" to subscribe for receiving such data through the Publish/Subscribe Broker GE, another application may wish to use Query Language "B". This would typically imply that the underlying engine is linked to a different Repository based on a different storage format. Then ... are both applications going to receive the data? Is the data going to be replicated in both repositories We need to find out a solution or position on the matter. 7. References [1] - http://forge.fi-ware.eu/docman/view.php/9/99/FI-WARE_ContextQuery-CQL_v3.pdf [2] - http://forge.fi-ware.eu/frs/download.php/3/2011-05-31OLPubSubPrez.pdf [3] - http://forge.fi-ware.eu/frs/download.php/4/WISHWellIE11midasFinal.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 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: image001.gif Type: image/gif Size: 9036 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 24189 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Tue Jun 7 09:40:08 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 07 Jun 2011 09:40:08 +0200 Subject: [Fiware-data] Details about bridge for our confcall on Localization Services Message-ID: <4DEDD5D8.50800@tid.es> Hi, We can use powonow for our confcall on Localization Services scheduled at 10:00am. powwownow PIN 050662: [cid:part1.06030708.09090701 at tid.es] If needed, we can use also webex (please find the details below) Best regards, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE confcall Localization Services Date: Tue, 7 Jun 2011 09:00:03 +0200 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE confcall Localization Services Date: Tuesday, June 7, 2011 Time: 9:30 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 965 296 726 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&PW=NZWQwZDliMDZk&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=153875242&UID=1214893992&PW=NZWQwZDliMDZk&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&ICS=MI&LD=1&RD=2&ST=1&SHA2=ugQgU0hJRBkb5PSE-99OZm0hOMfEhKyR05gOCwQldGY=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: moz-screenshot-27.png Type: image/png Size: 65941 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From remi.challamel at thalesaleniaspace.com Tue Jun 7 09:52:25 2011 From: remi.challamel at thalesaleniaspace.com (remi.challamel at thalesaleniaspace.com) Date: Tue, 7 Jun 2011 09:52:25 +0200 Subject: [Fiware-data] =?iso-8859-1?q?R=E9f=2E_=3A__Details_about_bridge_f?= =?iso-8859-1?q?or_our_confcall_on_Localization=09Services?= In-Reply-To: <4DEDD5D8.50800@tid.es> Message-ID: <15906_1307434383_4DEDDD8F_15906_2904_1_OFE56E74F2.E7D27482-ONC12578A8.002A8BEA-C12578A8.002B40A4@thalesaleniaspace.com> Dear Juanjo Here are the support slides for the teleconf at 10h. (See attached file: Internet of Future - KOM TAS v2a.ppt) |---------+------------------------------------> | | Juanjo Hierro | | | | | | Envoy? par : | | | fiware-data-bounces at lists| | | .fi-ware.eu | | | | | | | | | 07/06/2011 09:40 | |---------+------------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | Pour : "fiware-data at lists.fi-ware.eu" | | cc : | | Objet : [Fiware-data] Details about bridge for our confcall on Localization Services | >------------------------------------------------------------------------------------------------------------------------------| Hi, We can use powonow for our confcall on Localization Services scheduled at 10:00am. powwownow PIN 050662: If needed, we can use also webex (please find the details below) Best regards, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE confcall Localization Services Date: Tue, 7 Jun 2011 09:00:03 +0200 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE confcall Localization Services Date: Tuesday, June 7, 2011 Time: 9:30 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 965 296 726 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&PW=NZWQwZDliMDZk&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=153875242&UID=1214893992&PW=NZWQwZDliMDZk&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&ICS=MI&LD=1&RD=2&ST=1&SHA2=ugQgU0hJRBkb5PSE-99OZm0hOMfEhKyR05gOCwQldGY=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx(See attached file: jhierro.vcf)_______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data Meilleures salutations/Cordiali saluti/Best regards Sales&Marketing -- Project Manager Tel : fixed: +33 5 34 35 68 21 - cell: +33 6 74 33 82 58 / Fax : +33 5 34 35 43 39 Porte : P501 / E-Mail : remi.challamel at thalesaleniaspace.com -------------- 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: pic28253.gif Type: image/gif Size: 1255 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Internet of Future - KOM TAS v2a.ppt Type: application/vnd.ms-powerpoint Size: 1442304 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: application/octet-stream Size: 443 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 7 12:11:30 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 07 Jun 2011 12:11:30 +0200 Subject: [Fiware-data] IMPORTANT Reminder Message-ID: <4DEDF952.10405@tid.es> Hi all, This is a reminder to all of you in order to send a revised version of your contributions to the High-level Description document. Please don't forget to make it today EOB. Thanks, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Tue Jun 7 12:16:57 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 7 Jun 2011 12:16:57 +0200 Subject: [Fiware-data] Details about bridge for our confcall on Localization Services In-Reply-To: <4DEDD5D8.50800@tid.es> References: <4DEDD5D8.50800@tid.es> Message-ID: Location platform may use www.opencellid.org Just to have it send over all interested and traced in email exchange ?. 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, June 07, 2011 9:40 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Details about bridge for our confcall on Localization Services Hi, We can use powonow for our confcall on Localization Services scheduled at 10:00am. powwownow PIN 050662: [cid:image001.png at 01CC250B.C070FD00] If needed, we can use also webex (please find the details below) Best regards, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE confcall Localization Services Date: Tue, 7 Jun 2011 09:00:03 +0200 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE confcall Localization Services Date: Tuesday, June 7, 2011 Time: 9:30 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 965 296 726 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&PW=NZWQwZDliMDZk&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=153875242&UID=1214893992&PW=NZWQwZDliMDZk&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&ICS=MI&LD=1&RD=2&ST=1&SHA2=ugQgU0hJRBkb5PSE-99OZm0hOMfEhKyR05gOCwQldGY=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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: image001.png Type: image/png Size: 65941 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Tue Jun 7 12:46:28 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 07 Jun 2011 12:46:28 +0200 Subject: [Fiware-data] Notes from the confcall on Location Services Message-ID: <4DEE0184.5010904@tid.es> Hi all, We just finished our confcall on Location Services. I believe it was a very fruitful discussion. Let's include a section describing the Location Services GE in the Context-Data Management chapter of the FI-WARE High-level description deliverable. Thales will be in charge of writing this section. We can continue the discussion of what this GE should include or not include, or even need to add, as a result of reviewing the section. Thales may obtain the template for writing this section from the previous consolidated draft they can find at: http://forge.fi-ware.eu/docman/view.php/9/91/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.0+11-06-01.doc Best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 7 14:20:30 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 07 Jun 2011 14:20:30 +0200 Subject: [Fiware-data] Notes and thoughts on Publish/Subscribe GE and Query Access GE In-Reply-To: References: <4DEB321C.1020801@tid.es> Message-ID: <4DEE178E.4000804@tid.es> Dear Boris, Thanks for bringing this. In my more than 20 years in this bussiness of developing software, I have seen several attempts to define a Notification (Publish/Subscribe) service. Many times just re-inventing the wheel. So I would like to re-invent the wheel and define "Yet another Notification Service specification". From my point of view, the OMA specification has most of the ingredients that a Notification Service should have, so I would propose to take it as the basis of our work and make our GE specs compliant with those from OMA. But this means that the interfaces+operations to be defined for the FI-WARE Notification GE be those specified by OMA instead of those defined in Telecom Italia's or Orange's implementation. I would be more than happy with that approach and I see a value in FI-WARE providing a reference implementation of OMA specs. We may extend or deal with aspects not covered in the OMA specs by adding aspects related to support of multiple Query Languages and data formats along the lines of what I recently distributed as notes+thoughts. Could then Telecom Italia review the description of the Notification GE to align it with OMA specs ? Best regards, -- Juanjo On 05/06/11 23:30, Moltchanov Boris wrote: Dear All, Under the following link http://www.openmobilealliance.org/Technical/release_program/NGSI_v1_0.aspx you may find and download publicly available documents regarding the Next Generation Service Interface Enabler defined within OMA. Context management is represented there by NGSI-9/10 specifications. Among the documents you might be interested in the following documents: - OMA-RD-NGSI-V1_0-20100803-C.pdf ? requirements considered for this Enabler; - OMA-AD-NGSI-V1_0-20100803-C.pdf ? reference architecture of the Enabler; - OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf ? context management interface description (NGSI-9 and NGSI-10). Moreover I recommend to take a look at the presentation http://www.ict-ccast.eu/workshops/2nd/13%20-%20OMA%20-%20Kovacs%20-%20OMA_ServiceAPI_Standardisation.pdf, which describes the Enabler at high-level. I preferred to give you the links to external documents on their respective web-sites instead of putting into our FI-WARE server or even worse sending via email. However if we need I may upload them to the server. 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: Sunday, June 05, 2011 9:37 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Notes and thoughts on Publish/Subscribe GE and Query Access GE Dear colleagues, I have uploaded on the following link: http://forge.fi-ware.eu/docman/view.php/9/108/Notes+and+Thoughts+on+Pub-Sub+Broker+and+Query+Access+GEs.doc a short document with notes and derived thoughts from our previous calls on the Publish/Subscribe GE and Query Access GE. I hope you all can endorse them so that we can make progress. I plan to use this document as basis for a post in our blog. It might be a reference of the kind of posts we may publish on progress of our activities in our blog (serving as an example for other WPs). Don't hesitate to make any comment. For your convenience, I have also attached its contents in plain text below. This may be helpful in any discussion. Best regards, -- Juanjo ======= 1. Motivation This document intends to summarize some notes and thoughts that may help to progress on the discussion about features that the Notification (Publish/Subscribe) Broker and the Query Access GE should support. They should be taken into consideration when writing the sections describing both GEs in the FI-WARE High-level Description document. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. About the Notification (Publish/Subscribe) Broker Enabler There are essentially two products on the table regarding this GE that may be considered as baseline for our work: ? One from Telecom Italia, see [1] ? Another one from Orange, see, see [2] and [3] The very basic concepts and operations in both proposals are similar, so probably it?s not difficult to reach a consensus on entities/interfaces and operations. Actually, we may define the Notification (Publish/Subscribe) GE based on the following interfaces and operations (additional operations may be added): ? The Notification Consumer interface, which would map to the Context Consumer interface in both the Telecom Italia?s and Orange?s proposal. This interface would support the notify operation (which may take the form of a post operation if the interface is implemented as a RESTful interface). It may also support a subscription_ended operation. ? The Notification Broker interface, which would map to the Context Broker interface in Telecom Italia?s proposal or to the Context Source interface in Orange?s proposal. This interface would support the subscribe/unsubscribe operations. Querying of new data following a pull style of communication would be supported through a get operation exported by the Query Access GE as explained in section 4 of this report. ? The Notification Broker Finder, which would map to the Context Broker interface in Orange?s proposal. Note that this interface doesn?t exist in Telecom Italia?s proposal but this doesn?t imply any conflict. This interface would support the discoverNB operation enabling to locate a Notification Broker Finder based on criteria (see discussion below). ? The Notification Supplier interface, which would map to the Context Provider in Telecom Italia?s proposal. This interface doesn?t exist in Orange?s proposal because sources of notifications directly export operations enabling multiple Consumers to subscribe. In other words, both the role of Notification Supplier and Notification Consumer are played by entities exporting the Context Source interface in Orange?s proposal. This interface would support a get operation in order to support retrieval of new data complying with a given query, thus supporting a pull style of communication. This operation should follow the same signature as the get operation supported by the Query Access GE. A first conclusion and action point would be that we can describe the Notification (Publish/Subscribe) GE elaborating on this common set of entities/interfaces (i.e., product vision) and the operations they support. We would include a disclaimer at the beginning of the section explaining that the final set and signature of operations may change during final specification of the GE but it will be along the lines of what is described here. Given said the above, a fundamental difference of the two proposals has to do with the format of data being handled and notified (Telecom Italia supports a XML-based ContextML language while Orange supports RDFs). There are at least two aspects that strongly depend on the selected format for obvious reasons: ? The kind of repository where data is stored (no matter whether it is located in a memory cache or in disk, the notion of repository is there) ? The query language used to define subscriptions 3. Is a Universal Query language feasible? The conclusion of the team is that probably not. Even if it were feasible, it would imply to define ?yet another query language? which certainly would impose severe barriers of adoption by the developers community. Something that would be feasible is to support multiple query languages and ask the programmer to declare what particular query language he/she wishes to use. This will determine the format/structure used to store data in the repository and the repository itself. Thus, a programmer may declare he/she wishes to use SPARQL while another may declare he/she wishes to use MPQF, CQL, Mongo DB?s document-based query language or any other Query Language as long it is supported by the platform. Selection of the query language is a first step we may require the programmer to perform prior getting access to a particular Notification Broker, as illustrated in Figure 1. The complete list of steps to be followed by a Notification Consumer for subscribing to messages that comply with a given Query Language may be the following: 1. The Notification Consumer (NC) sends a request to the Notification Broker Finder (NBF) looking for a Notification Broker (NB) that supports a given Query Language specified as parameter in the request. 2. The NBF returns a reference to a NB supporting the specified Query Language 3. The NC subscribes to reception of data complying with a particular query by issuing a request to the NB. Note that in this model, the Notification Broker Finder plays a similar role to the Context Broker in Orange?s Publish/Subscribe service. [cid:part1.06050708.02010100 at tid.es] Figure 1. Steps in connecting to a Publish/Subscribe Broker 4. Relationship between the Publish/Subscribe Broker GE and the Query Access GE The Context Broker component proposed by Telecom Italia, similarly to the Context Source component proposed by Orange, exported operations that would allow Consumers to query for context data. On the other hand, we have identified the need for a Query Access GE that allows to access to data stored in the FI-WARE Data/Context Management Platform. How should both means for quering data be related? After some discussion, we came to the conclusion that the Notification Broker interface to be defined in the Publish/Subscribe Broker GE should just export an operation that would return the access point to the interface offered by the Query Access GE. This interface should offer a get operation that enables to retrieve data that complies with a given query statement and has been stored in the platform after the last call to the same operation made by the same entity. This way, we would avoid duplicated interfaces. Note that a particular product may be providing the implementation of components implementing the Notification Broker interface and the Query Access interface for a particular query language (i.e., format for representing/storing data). This is illustrated in Figure 2. [cid:part2.04060904.03050207 at tid.es] Figure 2. Two products implementing the Publish/Subscribe Broker and Query Access interface for two different query languages 5. Abstract Query Language Families Two given query languages may have some common constructions/components and this may allow that a given query, formulated based on common constructions, can be executed by the corresponding Query Engines. Therefore, we may consider supporting the concept of ?abstract query languages? in FI-WARE, each defined based on minimum common denominators of existing query languages. A question mark is what to do when abstract query languages are declared at the connection to the Publish/Subscribe Broker or the Query Access GEs. How are then queries executed? It seems like the solution may consist in performing a parallel execution of the query in compatible repositories (the query may be transferred to the query engines linked to each repository and then results gathered together in the response sent back to the application). However, there are still some open questions like, for example, what would be the actual format in which data results would be returned to the applications. We need to find out a solution or position on the matter. 6. Availability of data in different repositories Finally, there is still a big question mark regarding the following issue: what to do when some particular data is of interest to many applications but the query language each application uses to access data is different. Let?s illustrate this scenario with an example. One data that may be of interest to several applications may be the ambient temperature measured in a given street. However, while a given application may wish to use Query Language ?A? to subscribe for receiving such data through the Publish/Subscribe Broker GE, another application may wish to use Query Language ?B?. This would typically imply that the underlying engine is linked to a different Repository based on a different storage format. Then ? are both applications going to receive the data? Is the data going to be replicated in both repositories We need to find out a solution or position on the matter. 7. References [1] - http://forge.fi-ware.eu/docman/view.php/9/99/FI-WARE_ContextQuery-CQL_v3.pdf [2] - http://forge.fi-ware.eu/frs/download.php/3/2011-05-31OLPubSubPrez.pdf [3] - http://forge.fi-ware.eu/frs/download.php/4/WISHWellIE11midasFinal.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 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:part3.09070402.01000705 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/gif Size: 9036 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 24189 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From p.amon at siemens.com Tue Jun 7 19:46:53 2011 From: p.amon at siemens.com (Amon, Peter) Date: Tue, 7 Jun 2011 19:46:53 +0200 Subject: [Fiware-data] IMPORTANT Reminder In-Reply-To: <4DEDF952.10405@tid.es> References: <4DEDF952.10405@tid.es> Message-ID: Dear Juanjo, all, I just uploaded the description of the three Siemens GEs on the document server. Kind regards 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: Dienstag, 7. Juni 2011 12:12 > To: fiware-data at lists.fi-ware.eu > Subject: [Fiware-data] IMPORTANT Reminder > > Hi all, > > This is a reminder to all of you in order to send a revised version > of your contributions to the High-level Description document. > > Please don't forget to make it today EOB. > > Thanks, > > -- 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 jose.fuentesl at atosresearch.eu Tue Jun 7 20:17:47 2011 From: jose.fuentesl at atosresearch.eu (Jose Maria Fuentes Lopez) Date: Tue, 7 Jun 2011 20:17:47 +0200 Subject: [Fiware-data] IMPORTANT Reminder In-Reply-To: References: <4DEDF952.10405@tid.es> Message-ID: Dear Juanjo, all, I have also uploaded a new version of the ATOS GE description on the document server. You can find them at: https://forge.fi-ware.eu/docman/view.php/9/117/FI-WARE_High-Level_Description_11-06-1_ATOS_SemanticWeb.docx https://forge.fi-ware.eu/docman/view.php/9/118/FI-WARE_High-Level_Description_11-06-1_ATOS_Unstruc+-+Draft_2.docx Best regards, Chema Fuentes. -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Amon, Peter Sent: martes, 07 de junio de 2011 19:47 To: Juanjo Hierro; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] IMPORTANT Reminder Dear Juanjo, all, I just uploaded the description of the three Siemens GEs on the document server. Kind regards 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: Dienstag, 7. Juni 2011 12:12 > To: fiware-data at lists.fi-ware.eu > Subject: [Fiware-data] IMPORTANT Reminder > > Hi all, > > This is a reminder to all of you in order to send a revised version > of your contributions to the High-level Description document. > > Please don't forget to make it today EOB. > > Thanks, > > -- 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 ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ From pascal.bisson at thalesgroup.com Wed Jun 8 15:09:17 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 8 Jun 2011 15:09:17 +0200 Subject: [Fiware-data] Reviewing security issues in first draft of the Context/Data Management In-Reply-To: <4DE66708.7060609@tid.es> References: <4DE66708.7060609@tid.es> Message-ID: <13186_1307538562_4DEF7482_13186_1439_1_638e9cc9-5496-4958-8573-65fe85381331@THSONEA01HUB02P.one.grp> Dear Juanjo, I understand your demand and will work on it together with my WP8 colleagues (in cc) appointed to monitor and answer demands coming from your WP6 side for what concerns Security topic. Unfortunately we would not be able to answer you on the topic prior to Friday 10/06 at the earliest. Good news is that since we have a WP8 meeting I could put your demand also on the agenda of our meeting. Which might contribute to speed up a little bit our answer (being said also WP8 people appointed will do some preparatory work before) In any case will keep you posted and be back to you on the topic asap. Regards, Pascal De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mercredi 1 juin 2011 18:21 ? : fiware-data at lists.fi-ware.eu Cc : BISSON Pascal; jhierro >> "Juan J. Hierro" Objet : Reviewing security issues in first draft of the Context/Data Management Hi, First of all, I have updated the first draft in the server so, please downloading it again if you were too fast and already did it before reading this email :-) I have just updated the section on question marks as to assign a section for Security and subsections for topics regarding Security, instead of a subsection for Security with a bullet list of topics. The link is still the same: http://forge.fi-ware.eu/docman/view.php/9/91/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.0+11-06-01.doc The rest of this message is specifically targeted to our colleagues from the Security WP who I'm sure are monitoring what we are doing ;-) Now that we have a first draft (though still this needs quite more work) I would suggest that you carry out a first overall revision identifying security issues that should be taken into account. I would encourage you to contribute a description of such issues in the section about Security Issues I have created in section 3.1.3. Please confirm that you have read and understood this message. Your contributions are due on June 7, EOB like for the rest of the WP team. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From GUYSH at il.ibm.com Thu Jun 9 20:47:19 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Thu, 9 Jun 2011 21:47:19 +0300 Subject: [Fiware-data] CEP next version uploaded Message-ID: Hi, The next version can be found here: https://forge.fi-ware.eu/docman/view.php/9/133/FI-WARE_High-Level_Description_Data-Context+Management+v2.0+IBM.doc 1. Some terminology and definitions are just before "GE Description" - may need to move it elsewhere 2. Stream vs. Event processing - I just dropped a few lines from reference and some additional thoughts - for discussion 3. I have not referred to all comments in the functional description as I will revise and remove some of those functions - some of them as commented don't fit to well also in my opinion 4. There is an elaboration on the EPN (event processing network) and the type of operations you may apply on events - this as a possible implementation of the functionality that existed in the doc until now - and one IBM provides with its asset See you all tomorrow 9:30 CET Use the following bridge Participant Code: 8188850 France Caller Paid 0-170911580 France Toll-Free 0800-94-0558 Israel Toll-Free 1-809-417-783 USA Caller Paid 215-861-6239 USA Toll-Free 888-426-6840 For Other Countries: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=8188850&accessNumber=1809417783 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 -------------- 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 GUYSH at il.ibm.com Thu Jun 9 20:59:27 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Thu, 9 Jun 2011 21:59:27 +0300 Subject: [Fiware-data] some security issues that didnt make the document Message-ID: Issue 1 Trust the source of data Issue 2 Trust the data a source provides (even if the source is trusted) ? besides establishing trust, in processing, how do we treat trusted data in combination with less trusted data Issue 3 Privacy in providing and accessing data ? in processing, how do we process data with access rights combined with data without access rights? Disregarding it may lead to inconsistency or wrong conclusions. On the other hand the requestor is not allowed to access this data and therefore will have unauthorized view on information if this data is regarded in the processing 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 -------------- 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 Fri Jun 10 09:02:13 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Jun 2011 09:02:13 +0200 Subject: [Fiware-data] We will start at 09:45am Message-ID: <4DF1C175.2080409@tid.es> Hi all, Please take note that we will start a little bit later, that is 09:45am. Find enclosed the webex details. Guy, may you circulate the dial-in details ? Thanks, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE WP6 Data/Context weekly confcall Date: Fri, 10 Jun 2011 08:39:47 +0200 From: Gestor i-Reunion webex6100 Reply-To: Webex6100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex6100 invites you to attend this online meeting. Topic: FI-WARE WP6 Data/Context weekly confcall Date: Friday, 10 June 2011 Time: 9:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 965 346 754 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=154007832&UID=1215370707&PW=NOTVmNDJlZjk5&RT=MTgjMjM%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=154007832&UID=1215370707&PW=NOTVmNDJlZjk5&ORT=MTgjMjM%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex6100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=154007832&UID=1215370707&ICS=MI&LD=1&RD=18&ST=1&SHA2=q5KAu-7CYdmmms-1SSd0zn6pOHSZddSWQKrwuRBj7Sg=&RT=MTgjMjM%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From GUYSH at il.ibm.com Fri Jun 10 09:20:09 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Fri, 10 Jun 2011 10:20:09 +0300 Subject: [Fiware-data] Call details Message-ID: Participant Code: 8188850 France Caller Paid 0-170911580 France Toll-Free 0800-94-0558 Israel Toll-Free 1-809-417-783 USA Caller Paid 215-861-6239 USA Toll-Free 888-426-6840 For Other Countries: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=8188850&accessNumber=1809417783 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 ----- Forwarded by Guy Sharon/Haifa/IBM on 10/06/2011 10:19 ----- From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 10/06/2011 10:02 Subject: [Fiware-data] We will start at 09:45am Sent by: fiware-data-bounces at lists.fi-ware.eu Hi all, Please take note that we will start a little bit later, that is 09:45am. Find enclosed the webex details. Guy, may you circulate the dial-in details ? Thanks, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE WP6 Data/Context weekly confcall Date: Fri, 10 Jun 2011 08:39:47 +0200 From: Gestor i-Reunion webex6100 Reply-To: Webex6100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex6100 invites you to attend this online meeting. Topic: FI-WARE WP6 Data/Context weekly confcall Date: Friday, 10 June 2011 Time: 9:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 965 346 754 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=154007832&UID=1215370707&PW=NOTVmNDJlZjk5&RT=MTgjMjM%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=154007832&UID=1215370707&PW=NOTVmNDJlZjk5&ORT=MTgjMjM%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex6100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=154007832&UID=1215370707&ICS=MI&LD=1&RD=18&ST=1&SHA2=q5KAu-7CYdmmms-1SSd0zn6pOHSZddSWQKrwuRBj7Sg=&RT=MTgjMjM%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: application/octet-stream Size: 443 bytes Desc: not available URL: From fano.ramparany at orange-ftgroup.com Fri Jun 10 09:57:10 2011 From: fano.ramparany at orange-ftgroup.com (fano.ramparany at orange-ftgroup.com) Date: Fri, 10 Jun 2011 09:57:10 +0200 Subject: [Fiware-data] Notes and thoughts on Publish/Subscribe GE andQuery Access GE In-Reply-To: <4DEE178E.4000804@tid.es> References: <4DEB321C.1020801@tid.es> <4DEE178E.4000804@tid.es> Message-ID: Hi Juanjo, Starting from an existing OMA specification and extending it to cover our specific requirements seems indeed a reasonable approach. About your interesting notes+thoughts report. We would like to comment on the following points. * The Notification Supplier interface, which would map to the Context Provider in Telecom Italia's proposal. This interface doesn't exist in Orange's proposal because sources of notifications directly export operations enabling multiple Consumers to subscribe. In other words, both the role of Notification Supplier and Notification Consumer are played by entities exporting the Context Source interface in Orange's proposal. This interface would support a get operation in order to support retrieval of new data complying with a given query, thus supporting a pull style of communication. This operation should follow the same signature as the get operation supported by the Query Access GE. Although I agree with the parallel you draw between the Context Provider in TI asset and the possibility in OL asset to implement a component with both the CC and the CS interface, However I find the naming "Notification Supplier" misleading as it can be mixed up with the Notification broker. I understand the function of a Context Provider is to supply the Context Broker with high level context based on low level context provided by the same Context Broker. If my understanding is correct, may be we could find a name which closely relate to this function. Is a Universal Query language feasible? The conclusion of the team is that probably not. Even if it were feasible, it would imply to define "yet another query language" which certainly would impose severe barriers of adoption by the developers community. Something that would be feasible is to support multiple query languages and ask the programmer to declare what particular query language he/she wishes to use. This will determine the format/structure used to store data in the repository and the repository itself. We back this approach which makes the GE flexible enough to support: - multiple data representation languages - multiple query languages - multiple response languages and to accept futures ones. As you noted, in principle these languages go by 3. what to do when some particular data is of interest to many applications but the query language each application uses to access data is different. One approach is to have the application use the query language of the CB. This approach contrasts with the one where the application imposing its query language to the CB (which is what you seem to consider in your notes). Please feel free to react to this. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mardi 7 juin 2011 14:21 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Notes and thoughts on Publish/Subscribe GE andQuery Access GE Dear Boris, Thanks for bringing this. In my more than 20 years in this bussiness of developing software, I have seen several attempts to define a Notification (Publish/Subscribe) service. Many times just re-inventing the wheel. So I would like to re-invent the wheel and define "Yet another Notification Service specification". From my point of view, the OMA specification has most of the ingredients that a Notification Service should have, so I would propose to take it as the basis of our work and make our GE specs compliant with those from OMA. But this means that the interfaces+operations to be defined for the FI-WARE Notification GE be those specified by OMA instead of those defined in Telecom Italia's or Orange's implementation. I would be more than happy with that approach and I see a value in FI-WARE providing a reference implementation of OMA specs. We may extend or deal with aspects not covered in the OMA specs by adding aspects related to support of multiple Query Languages and data formats along the lines of what I recently distributed as notes+thoughts. Could then Telecom Italia review the description of the Notification GE to align it with OMA specs ? Best regards, -- Juanjo On 05/06/11 23:30, Moltchanov Boris wrote: Dear All, Under the following link http://www.openmobilealliance.org/Technical/release_program/NGSI_v1_0.aspx you may find and download publicly available documents regarding the Next Generation Service Interface Enabler defined within OMA. Context management is represented there by NGSI-9/10 specifications. Among the documents you might be interested in the following documents: - OMA-RD-NGSI-V1_0-20100803-C.pdf - requirements considered for this Enabler; - OMA-AD-NGSI-V1_0-20100803-C.pdf - reference architecture of the Enabler; - OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf - context management interface description (NGSI-9 and NGSI-10). Moreover I recommend to take a look at the presentation http://www.ict-ccast.eu/workshops/2nd/13%20-%20OMA%20-%20Kovacs%20-%20OMA_ServiceAPI_Standardisation.pdf, which describes the Enabler at high-level. I preferred to give you the links to external documents on their respective web-sites instead of putting into our FI-WARE server or even worse sending via email. However if we need I may upload them to the server. 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: Sunday, June 05, 2011 9:37 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Notes and thoughts on Publish/Subscribe GE and Query Access GE Dear colleagues, I have uploaded on the following link: http://forge.fi-ware.eu/docman/view.php/9/108/Notes+and+Thoughts+on+Pub-Sub+Broker+and+Query+Access+GEs.doc a short document with notes and derived thoughts from our previous calls on the Publish/Subscribe GE and Query Access GE. I hope you all can endorse them so that we can make progress. I plan to use this document as basis for a post in our blog. It might be a reference of the kind of posts we may publish on progress of our activities in our blog (serving as an example for other WPs). Don't hesitate to make any comment. For your convenience, I have also attached its contents in plain text below. This may be helpful in any discussion. Best regards, -- Juanjo ======= 1. Motivation This document intends to summarize some notes and thoughts that may help to progress on the discussion about features that the Notification (Publish/Subscribe) Broker and the Query Access GE should support. They should be taken into consideration when writing the sections describing both GEs in the FI-WARE High-level Description document. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. About the Notification (Publish/Subscribe) Broker Enabler There are essentially two products on the table regarding this GE that may be considered as baseline for our work: * One from Telecom Italia, see [1] * Another one from Orange, see, see [2] and [3] The very basic concepts and operations in both proposals are similar, so probably it's not difficult to reach a consensus on entities/interfaces and operations. Actually, we may define the Notification (Publish/Subscribe) GE based on the following interfaces and operations (additional operations may be added): * The Notification Consumer interface, which would map to the Context Consumer interface in both the Telecom Italia's and Orange's proposal. This interface would support the notify operation (which may take the form of a post operation if the interface is implemented as a RESTful interface). It may also support a subscription_ended operation. * The Notification Broker interface, which would map to the Context Broker interface in Telecom Italia's proposal or to the Context Source interface in Orange's proposal. This interface would support the subscribe/unsubscribe operations. Querying of new data following a pull style of communication would be supported through a get operation exported by the Query Access GE as explained in section 4 of this report. * The Notification Broker Finder, which would map to the Context Broker interface in Orange's proposal. Note that this interface doesn't exist in Telecom Italia's proposal but this doesn't imply any conflict. This interface would support the discoverNB operation enabling to locate a Notification Broker Finder based on criteria (see discussion below). * The Notification Supplier interface, which would map to the Context Provider in Telecom Italia's proposal. This interface doesn't exist in Orange's proposal because sources of notifications directly export operations enabling multiple Consumers to subscribe. In other words, both the role of Notification Supplier and Notification Consumer are played by entities exporting the Context Source interface in Orange's proposal. This interface would support a get operation in order to support retrieval of new data complying with a given query, thus supporting a pull style of communication. This operation should follow the same signature as the get operation supported by the Query Access GE. A first conclusion and action point would be that we can describe the Notification (Publish/Subscribe) GE elaborating on this common set of entities/interfaces (i.e., product vision) and the operations they support. We would include a disclaimer at the beginning of the section explaining that the final set and signature of operations may change during final specification of the GE but it will be along the lines of what is described here. Given said the above, a fundamental difference of the two proposals has to do with the format of data being handled and notified (Telecom Italia supports a XML-based ContextML language while Orange supports RDFs). There are at least two aspects that strongly depend on the selected format for obvious reasons: * The kind of repository where data is stored (no matter whether it is located in a memory cache or in disk, the notion of repository is there) * The query language used to define subscriptions 3. Is a Universal Query language feasible? The conclusion of the team is that probably not. Even if it were feasible, it would imply to define "yet another query language" which certainly would impose severe barriers of adoption by the developers community. Something that would be feasible is to support multiple query languages and ask the programmer to declare what particular query language he/she wishes to use. This will determine the format/structure used to store data in the repository and the repository itself. Thus, a programmer may declare he/she wishes to use SPARQL while another may declare he/she wishes to use MPQF, CQL, Mongo DB's document-based query language or any other Query Language as long it is supported by the platform. Selection of the query language is a first step we may require the programmer to perform prior getting access to a particular Notification Broker, as illustrated in Figure 1. The complete list of steps to be followed by a Notification Consumer for subscribing to messages that comply with a given Query Language may be the following: 1. The Notification Consumer (NC) sends a request to the Notification Broker Finder (NBF) looking for a Notification Broker (NB) that supports a given Query Language specified as parameter in the request. 2. The NBF returns a reference to a NB supporting the specified Query Language 3. The NC subscribes to reception of data complying with a particular query by issuing a request to the NB. Note that in this model, the Notification Broker Finder plays a similar role to the Context Broker in Orange's Publish/Subscribe service. Figure 1. Steps in connecting to a Publish/Subscribe Broker 4. Relationship between the Publish/Subscribe Broker GE and the Query Access GE The Context Broker component proposed by Telecom Italia, similarly to the Context Source component proposed by Orange, exported operations that would allow Consumers to query for context data. On the other hand, we have identified the need for a Query Access GE that allows to access to data stored in the FI-WARE Data/Context Management Platform. How should both means for quering data be related? After some discussion, we came to the conclusion that the Notification Broker interface to be defined in the Publish/Subscribe Broker GE should just export an operation that would return the access point to the interface offered by the Query Access GE. This interface should offer a get operation that enables to retrieve data that complies with a given query statement and has been stored in the platform after the last call to the same operation made by the same entity. This way, we would avoid duplicated interfaces. Note that a particular product may be providing the implementation of components implementing the Notification Broker interface and the Query Access interface for a particular query language (i.e., format for representing/storing data). This is illustrated in Figure 2. Figure 2. Two products implementing the Publish/Subscribe Broker and Query Access interface for two different query languages 5. Abstract Query Language Families Two given query languages may have some common constructions/components and this may allow that a given query, formulated based on common constructions, can be executed by the corresponding Query Engines. Therefore, we may consider supporting the concept of "abstract query languages" in FI-WARE, each defined based on minimum common denominators of existing query languages. A question mark is what to do when abstract query languages are declared at the connection to the Publish/Subscribe Broker or the Query Access GEs. How are then queries executed? It seems like the solution may consist in performing a parallel execution of the query in compatible repositories (the query may be transferred to the query engines linked to each repository and then results gathered together in the response sent back to the application). However, there are still some open questions like, for example, what would be the actual format in which data results would be returned to the applications. We need to find out a solution or position on the matter. 6. Availability of data in different repositories Finally, there is still a big question mark regarding the following issue: what to do when some particular data is of interest to many applications but the query language each application uses to access data is different. Let's illustrate this scenario with an example. One data that may be of interest to several applications may be the ambient temperature measured in a given street. However, while a given application may wish to use Query Language "A" to subscribe for receiving such data through the Publish/Subscribe Broker GE, another application may wish to use Query Language "B". This would typically imply that the underlying engine is linked to a different Repository based on a different storage format. Then ... are both applications going to receive the data? Is the data going to be replicated in both repositories We need to find out a solution or position on the matter. 7. References [1] - http://forge.fi-ware.eu/docman/view.php/9/99/FI-WARE_ContextQuery-CQL_v3.pdf [2] - http://forge.fi-ware.eu/frs/download.php/3/2011-05-31OLPubSubPrez.pdf [3] - http://forge.fi-ware.eu/frs/download.php/4/WISHWellIE11midasFinal.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 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. ________________________________ 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: ATT683547.gif Type: image/gif Size: 9036 bytes Desc: ATT683547.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT683548.gif Type: image/gif Size: 24189 bytes Desc: ATT683548.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT683549.jpg Type: image/jpeg Size: 677 bytes Desc: ATT683549.jpg URL: From jhierro at tid.es Fri Jun 10 09:57:54 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Jun 2011 09:57:54 +0200 Subject: [Fiware-data] I'm having problems connecting ... please wait Message-ID: <4DF1CE82.80903@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 -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From remi.challamel at thalesaleniaspace.com Fri Jun 10 10:28:01 2011 From: remi.challamel at thalesaleniaspace.com (remi.challamel at thalesaleniaspace.com) Date: Fri, 10 Jun 2011 10:28:01 +0200 Subject: [Fiware-data] FI-WARE WP6 - description of GE "localisation platform" Message-ID: <30998_1307694434_4DF1D562_30998_10501_1_OFEAEE942C.EB5A2115-ONC12578AB.002BBB2F-C12578AB.002E82D4@thalesaleniaspace.com> Dear JuanJo Here is the GE "localisation platform" description: https://forge.fi-ware.eu/docman/view.php/9/134/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.0+LOC_S.doc Best regards. Meilleures salutations/Cordiali saluti/Best regards Sales&Marketing -- Project Manager Tel : fixed: +33 5 34 35 68 21 - cell: +33 6 74 33 82 58 / Fax : +33 5 34 35 43 39 Porte : P501 / E-Mail : remi.challamel at thalesaleniaspace.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Fri Jun 10 12:02:24 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 10 Jun 2011 12:02:24 +0200 Subject: [Fiware-data] Minutes of the confcall 11-05-27 References: <4DDF672D.3050304@tid.es> Message-ID: Dear All, I don't remember if we have already conf-call planned, probably not yet. Sorry my IoT(houghts) in my brain is in a completely and truly MASH configuration with a lot of race conditions and collisions (not saying about faulting)... ;-). As I've mentioned during the just terminated conf-call and with regard to the attached email, please find uploaded two new contributions by TI as: - Semantic Annotation Enabler https://forge.fi-ware.eu/docman/view.php/9/136/FI-WARE_High-Level_Description_Semantic_Annotation_Enabler_TI.docx for integration with ATOS; - Multimedia Recognition Brokering https://forge.fi-ware.eu/docman/view.php/9/135/FI-WARE_High-Level_Description_Multimedia_Recognition_Brokering_Enabler_TI.docx for integration with Siemens. For sure if would be much better if the documents by default will be market as private and only then manually activated as public. Best Regards, Boris TI From: Moltchanov Boris Sent: Friday, May 27, 2011 4:16 PM To: 'Juanjo Hierro'; fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Minutes of the confcall 11-05-27 Dear All, TI in Turin will be closed on Thursday and Friday of next week, therefore we will be unable to participate in the next WP6 call. However we're very interested to be a part of the discussions regarding the following two aspects: - Semantic web annotation tools (with ATOS); - Multimedia analysis (with Siemens); as far as we have active assets in these areas as demonstrated during the kick-off meeting. I will share the documents from the docman with my colleagues, and would like to check with you if you're planning dedicated calls for these 2 topics in the beginning of the next week (30/05-01/05 incl.). Thank you. 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: Friday, May 27, 2011 10:56 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of the confcall 11-05-27 Dear colleagues, Please find enclosed the minutes I have taken during our weekly confcall. Comments are welcome. I assign a numbering to the different actions of the Action Plan we agreed. Note that action 3 was an action you didn't have time to see written in the shared desktop during the confcall but was indeed discussed. To Telecom Italia: please note that we agreed on the timeslots for celebrating the pending confcalls on Publish/Subscribe Broker as well as on Search/Quering Access (point 1 in the agenda). We beared in mind the timeslots of availability you provided to me in a separate mail. The only one for which we have yet to agree is the one on the Localization GE. Unfortunately, Thales didn't attend the confcall. Best regards, -- Juanjo Attendees: TID: Juanjo IBM: Guy Telecom Italia: ATOS: Tomas and Chema Orange: Fano Ramparany Siemens: Andreas, Thomas, Peter Thales: UPM: Agenda: 1. Review of actions from previous call 2. Status of contributions to deliverable (High-level Description) 3. Planning of next steps 1. Review of actions from previous call + confcall on Publish/Subscribe: Tuesday May 31, 11:30 - 13:00 + confcall Query/Siemens: Wednesday June 1, 09:30 - 11:00 + confcall on Localization GE: still ACTION pending Rest of actions had been done or had to do with contributions (therefore reviewed in next point of the agenda) 2. Status of contributions Action: The editor of each subsection in section 2, have to consider and hightlight whatever aspect related to Security is relevant for the GE description * Off-line Big Data analysis-processing/mining platform (TID) * Big Data stream processing based on map-reduce (TID) These two indeed match to a single GE. I have retitled the second aspect. Description was uploaded to the server ACTION: IBM and Telefonica to hold a confcall on monday May 31 starting 15:30 to reach full alignment on architecture of the processing part and combination/integration of TID's and IBM's assets. * Intelligent Services Plug-ins (TID) Uploaded to the docs server * Real-time stream processing based on CPE (IBM) Uploaded to the docs server * Preprocessing of meta-data during/after gathering (Siemens) Uploaded to the docs server * Preprocessing of unstructured data during/after gathering (ATOS) Uploaded to the docs server - very preliminary * Data/Context Pub/Sub Broker (TI) - note: Orange have brought also some asset here and TID wish to incorporate some requirements uploaded to the docs server * Semantic Web annotation tools (ATOS) uploaded to the docs server - very preliminary * Searching/Query-access (???) there is something contributed by Siemens. Will be considered input for the confcall on wednesday. * Multimedia analysis to gather multimedia meta-data (Siemens) uploaded to the docs server 3. Planning of next steps Agreed ACTION-PLAN: 1. Juanjo to consolidate all inputs in a single document to be distributed on monday: - revised template - concrete recomendations on the different sections 2. Editors of the different GE description sections will work from the single document distributed by Juanjo from monday till Thursday EOB: - trying to implement the recomendations - delivering a contribution with only the specific section they have edited (different files per section, not per company) - identify security issues to be address together with Security WP (Juanjo will come with a recommendation on how to provide this input) 3. Partners are welcome to perform an overall review the document distributed by Juanjo and upload a commented version (just comments using the tools for comments on MS Word) by Wednesday EOB. Editors of the different GE sections are then invited to check comments from other partners 4. On next confcall, we should plan on: - how to carry out peer review of existing section in the following week - how to fill rest of sections (particularly, how to generate the section on definitions) ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Fri Jun 10 15:59:16 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 10 Jun 2011 15:59:16 +0200 Subject: [Fiware-data] conference call per semantic techniques Message-ID: Dear Juanjo and Semantic Parthers, Would it be possible to set a doodle poll for the subject? I had checked with the team working in this matter and at 13:30 Monday none will be available. However our contribution is in FI-WARE repository as mentioned in one of the previous email in case you would analyze it in "off-line" first. Best Regards, Boris Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Fri Jun 10 19:26:33 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Jun 2011 19:26:33 +0200 Subject: [Fiware-data] Minutes of weekly followup confcall 11-06-10 Message-ID: <4DF253C9.1030804@tid.es> Hi, Quick and dirty, but hopefully clear and useful :-) Cheers, -- Juanjo Minutes: During the follow-up confcall we reviewed the status of contributions to the Context/Data Management Chapter in the FI-WARE High-level Description (product vision) deliverable. 1. Contribution by Siemen Uploaded on the server. Action on Juanjo to review whether it is now consistent with the conclusions from our debate on the Publish/Subscribe GE and its relationship to the Query Access GE. 2. Contributions regarding Management of Data semantics ATOS has updated their contribution and uploaded it on the server. Telecom Italia has also uploaded a contribution on the matter. We will setup an initial confcall regarding discussion on overall approach regarding Semantic Technology. First confcall on monday 13th, 13:30 pm and then there will be an additional one on tuesday 14 starting at 18:30. Juanjo to send the dial-in and webex details. 3. Contribution on CEP by IBM Action on Juanjo to review new draft produced by Guy. To send comments before sunday (working day in Israel) Action on All to review initial definition of Data vs Event provided IBM in their contribution and send comments to the list. In this respect, we need a definition of three concepts: - data element (data record) - event - context element The structure of data/event/context elements has to be common to several GEs, at least in respect to how such elements are going to be passed from one GE to another and to final applications. In this respect: - We should be able to subscribe to and notify plain data through the Publish/Subscribe Broker, not just context elements. Same for events. - We should be able to connect the output of the CEP GE to the Publish/Subscribe Broker GE and viceversa Action: Juanjo to make a proposal trying to start from Guy's proposal and the OMA model and send it to the list before sunday or sunday morning. We'll setup a confcall on Wednesday and in the meantime let's discuss over the email. Juanjo to make a doodle to find the right time. Juanjo: the OMA Publish/Subscribe Service may give some hints on a model that accomodates the three. Boris: agreed. Due to this linkage with the OMA model, we seamlessly continue addressing status of the description of the Publish/Subscribe Broker GE. 4. Contribution on the Publish/Subscribe Broker GE General agreement in that it would be feasible to define the interfaces and entities that would be supported in the FI-WARE Publish/Subscribe Broker GE along the lines of the OMA Model. But probably we may have to deal with particularities when dealing with the details of defining types linked to arguments to operation requests/responses in FI-WARE if we want to address the requirements mentioned in the previous point. General agreement that we should try to be as closer to the OMA spec as possible, trying to keep as much compliance as possible. Ideally, an implementation of the Publish/Subscribe Broker in compliance with the FI-WARE spec should be able to interact with client programs making use of the mandatory parts of OMA. We may be more relaxed and not require compliance with non-mandatory parts of the OMA specs (even if that means that we would not be able to claim compliance with OMA, but what really matters is that a relevant % of client programs that were able to work against OMA-compliant servers can port to use a FI-WARE-compliant implementation without not too much burden). Once we get a solid and tested spec, we would determine how to fastrack its adoption in OMA (as an update o the existing spec ? probably difficult ... as a variant of the existing one might be reasonable) Boris will start re-writing of Publish/Subscribe GE asap. Goal to get it done for review in following weekly confcall. 4. AOB Boris to send proposal on how to manage integration of contributions through SVN. ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Fri Jun 10 19:46:01 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 10 Jun 2011 19:46:01 +0200 Subject: [Fiware-data] Minutes of weekly followup confcall 11-06-10 In-Reply-To: <4DF253C9.1030804@tid.es> References: <4DF253C9.1030804@tid.es> Message-ID: *Starting from 4 point* that will take very short time (I'm in a short time-constraints now). the rest is next week: *Problem statement*: we need a shared SVN to join all our works into the same result - document and avoid trashing with multiple uncontrolled versions. *Possible solution* and steps: - SVN (with control versioning solution); - template of document (deliverables) are ready and published in SVN (with all styles and fonts already provided); 1. one (leader of deliverable or first initiative contributor) "instantiate" a document (deliverable) in its first (draft) version, that even might be empty but has the reference name, and assign to this a reasonable name (index or name or both of the document/deliverable); 2. a contributor (may act in parallel) download that document into local filesystem and perform changes regarding their respective sections (might be a new section or tracked review of an existing section); 3. once the contribution is ready the contributor lock the file, download the current already locked version, and insert his/her insertion or changes. This operation shall be relatively fast (question of minutes) in order to do not block the document more then necessarily for insertion; 4. [*optional*, and I hope this operation would be avoided] if contributor discover that the downloaded version is different from the one downloaded before starting the integration, a "merge" function of the MS World might be used (not always successful because only MS (probably) knows what happens insider their systems; 5. after the insertion or changes are done the contributor upload the file to the server under the same name and unlock the file. Some subversioning systems combines the download/lock and upload/unlock in the one operation respectively edit and release. In this case any user shall have its unique name within SVN and it would be really nice if the same name is used also for MS Word tracking inside the file in case of editing. Any document deliverable *MUST* have its responsible Editor who is leader of that document, solve race condition and eventual integration issues asking required actions directly to tracked (in SVN and in the document body) contributors. I hope this would help to our cooperation. If I missed something please integrate, improve, change or constructively suggest. 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: Friday, June 10, 2011 7:27 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of weekly followup confcall 11-06-10 Hi, Quick and dirty, but hopefully clear and useful :-) Cheers, -- Juanjo Minutes: During the follow-up confcall we reviewed the status of contributions to the Context/Data Management Chapter in the FI-WARE High-level Description (product vision) deliverable. 1. Contribution by Siemen Uploaded on the server. Action on Juanjo to review whether it is now consistent with the conclusions from our debate on the Publish/Subscribe GE and its relationship to the Query Access GE. 2. Contributions regarding Management of Data semantics ATOS has updated their contribution and uploaded it on the server. Telecom Italia has also uploaded a contribution on the matter. We will setup an initial confcall regarding discussion on overall approach regarding Semantic Technology. First confcall on monday 13th, 13:30 pm and then there will be an additional one on tuesday 14 starting at 18:30. Juanjo to send the dial-in and webex details. 3. Contribution on CEP by IBM Action on Juanjo to review new draft produced by Guy. To send comments before sunday (working day in Israel) Action on All to review initial definition of Data vs Event provided IBM in their contribution and send comments to the list. In this respect, we need a definition of three concepts: - data element (data record) - event - context element The structure of data/event/context elements has to be common to several GEs, at least in respect to how such elements are going to be passed from one GE to another and to final applications. In this respect: - We should be able to subscribe to and notify plain data through the Publish/Subscribe Broker, not just context elements. Same for events. - We should be able to connect the output of the CEP GE to the Publish/Subscribe Broker GE and viceversa Action: Juanjo to make a proposal trying to start from Guy's proposal and the OMA model and send it to the list before sunday or sunday morning. We'll setup a confcall on Wednesday and in the meantime let's discuss over the email. Juanjo to make a doodle to find the right time. Juanjo: the OMA Publish/Subscribe Service may give some hints on a model that accomodates the three. Boris: agreed. Due to this linkage with the OMA model, we seamlessly continue addressing status of the description of the Publish/Subscribe Broker GE. 4. Contribution on the Publish/Subscribe Broker GE General agreement in that it would be feasible to define the interfaces and entities that would be supported in the FI-WARE Publish/Subscribe Broker GE along the lines of the OMA Model. But probably we may have to deal with particularities when dealing with the details of defining types linked to arguments to operation requests/responses in FI-WARE if we want to address the requirements mentioned in the previous point. General agreement that we should try to be as closer to the OMA spec as possible, trying to keep as much compliance as possible. Ideally, an implementation of the Publish/Subscribe Broker in compliance with the FI-WARE spec should be able to interact with client programs making use of the mandatory parts of OMA. We may be more relaxed and not require compliance with non-mandatory parts of the OMA specs (even if that means that we would not be able to claim compliance with OMA, but what really matters is that a relevant % of client programs that were able to work against OMA-compliant servers can port to use a FI-WARE-compliant implementation without not too much burden). Once we get a solid and tested spec, we would determine how to fastrack its adoption in OMA (as an update o the existing spec ? probably difficult ... as a variant of the existing one might be reasonable) Boris will start re-writing of Publish/Subscribe GE asap. Goal to get it done for review in following weekly confcall. 4. AOB Boris to send proposal on how to manage integration of contributions through SVN. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From tomas.parientelobo at atosresearch.eu Mon Jun 13 09:23:25 2011 From: tomas.parientelobo at atosresearch.eu (Tomas PAriente Lobo) Date: Mon, 13 Jun 2011 09:23:25 +0200 Subject: [Fiware-data] conference call per semantic techniques In-Reply-To: References: Message-ID: <9DA3EC560FF1564DB032154AC290954B0552FA85@INTMAIL01.es.int.atosorigin.com> Dear Juanjo, As Boris cannot make it today to the call to discuss about semantics, could you please set up a doodle to decide on an alternative time? We are available mostly in the morning (before 15:00 CET). For your information, in this week I have already appointments on Tuesday, Wednesday and Thursday from around 10 to 11:30 approx. Best regards Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: viernes, 10 de junio de 2011 15:59 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] conference call per semantic techniques Dear Juanjo and Semantic Parthers, Would it be possible to set a doodle poll for the subject? I had checked with the team working in this matter and at 13:30 Monday none will be available. However our contribution is in FI-WARE repository as mentioned in one of the previous email in case you would analyze it in "off-line" first. Best Regards, Boris 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. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 566 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: From jhierro at tid.es Mon Jun 13 12:09:30 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 Jun 2011 12:09:30 +0200 Subject: [Fiware-data] Confcall at 13:30 on Semantics Message-ID: <4DF5E1DA.7090604@tid.es> Hi, Just to make sure we arrive with the right expectations to the confcall scheduled at 13:30pm. What I expect is that ATOS will elaborate on their proposal regarding this matter. It would be nice that they can provide us with some hints on how they envision their proposed GEs could be integrated with the rest of GEs we have in this chapter. I hope that we will have a webex session ready for that time, but I have to confess that I haven't still received the electronic invitation (despite I asked for it last friday :-( We would use the powwownow bridge: PIN: 050662 Dial-in phone numbers in the attachment Cheers, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: Powwownow-dial-in-numbers.pdf Type: application/pdf Size: 61516 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From tomas.parientelobo at atosresearch.eu Mon Jun 13 12:45:37 2011 From: tomas.parientelobo at atosresearch.eu (Tomas PAriente Lobo) Date: Mon, 13 Jun 2011 12:45:37 +0200 Subject: [Fiware-data] Confcall at 13:30 on Semantics In-Reply-To: <4DF5E1DA.7090604@tid.es> References: <4DF5E1DA.7090604@tid.es> Message-ID: <9DA3EC560FF1564DB032154AC290954B055803FC@INTMAIL01.es.int.atosorigin.com> Hi Juanjo, >From your email I understand that we keep our call at 13:30. Am I correct? A couple of things: - When you refer to webex, from who are you expecting the invitation? - We plan to show a couple of slides about our idea of what we can provide on semantics according to what we promised in the DoW. We can explain what we will offer as GE to the WP6 and the rest of the WPs (and usage areas of the PPP), but we are not in the position of knowing how the rest of the GEs of WP6 would use semantics. As a matter of example, WP3 people already communicate to us that they will use our GE to store and retrieve semantic descriptions of WS. I would like the rest of the partners involved in our WP to express if they have some requirements in this matter. Best regards Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu -----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: lunes, 13 de junio de 2011 12:10 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Confcall at 13:30 on Semantics Hi, Just to make sure we arrive with the right expectations to the confcall scheduled at 13:30pm. What I expect is that ATOS will elaborate on their proposal regarding this matter. It would be nice that they can provide us with some hints on how they envision their proposed GEs could be integrated with the rest of GEs we have in this chapter. I hope that we will have a webex session ready for that time, but I have to confess that I haven't still received the electronic invitation (despite I asked for it last friday :-( We would use the powwownow bridge: PIN: 050662 Dial-in phone numbers in the attachment 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 ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ From tomas.parientelobo at atosresearch.eu Mon Jun 13 13:26:33 2011 From: tomas.parientelobo at atosresearch.eu (Tomas PAriente Lobo) Date: Mon, 13 Jun 2011 13:26:33 +0200 Subject: [Fiware-data] Confcall at 13:30 on Semantics In-Reply-To: <9DA3EC560FF1564DB032154AC290954B055803FC@INTMAIL01.es.int.atosorigin.com> References: <4DF5E1DA.7090604@tid.es> <9DA3EC560FF1564DB032154AC290954B055803FC@INTMAIL01.es.int.atosorigin.com> Message-ID: <9DA3EC560FF1564DB032154AC290954B05580438@INTMAIL01.es.int.atosorigin.com> Dear all, See attached a couple of slides for our confcall in 5 minutes. Cheers Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Tomas PAriente Lobo Sent: lunes, 13 de junio de 2011 12:46 To: Juanjo Hierro; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Confcall at 13:30 on Semantics Hi Juanjo, >From your email I understand that we keep our call at 13:30. Am I correct? A couple of things: - When you refer to webex, from who are you expecting the invitation? - We plan to show a couple of slides about our idea of what we can provide on semantics according to what we promised in the DoW. We can explain what we will offer as GE to the WP6 and the rest of the WPs (and usage areas of the PPP), but we are not in the position of knowing how the rest of the GEs of WP6 would use semantics. As a matter of example, WP3 people already communicate to us that they will use our GE to store and retrieve semantic descriptions of WS. I would like the rest of the partners involved in our WP to express if they have some requirements in this matter. Best regards Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu -----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: lunes, 13 de junio de 2011 12:10 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Confcall at 13:30 on Semantics Hi, Just to make sure we arrive with the right expectations to the confcall scheduled at 13:30pm. What I expect is that ATOS will elaborate on their proposal regarding this matter. It would be nice that they can provide us with some hints on how they envision their proposed GEs could be integrated with the rest of GEs we have in this chapter. I hope that we will have a webex session ready for that time, but I have to confess that I haven't still received the electronic invitation (despite I asked for it last friday :-( We would use the powwownow bridge: PIN: 050662 Dial-in phone numbers in the attachment 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 ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- A non-text attachment was scrubbed... Name: Semantic Technologies in WP6.pptx Type: application/octet-stream Size: 119532 bytes Desc: Semantic Technologies in WP6.pptx URL: From jhierro at tid.es Mon Jun 13 13:27:11 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 Jun 2011 13:27:11 +0200 Subject: [Fiware-data] Webex for our FI-WARE confcall on Data Semantics Message-ID: <4DF5F40F.10606@tid.es> Sorry but I couldn't foward it to you before. Talk to you in some minutes. Best regards, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE confcall Data Semantics Date: Mon, 13 Jun 2011 12:59:15 +0200 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE confcall Data Semantics Date: Monday, June 13, 2011 Time: 1:30 pm, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 677 350 298 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=11644103&UID=103812568&PW=NOGVkZjI0ZTY3&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=11644103&UID=103812568&PW=NOGVkZjI0ZTY3&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=11644103&UID=103812568&ICS=MI&LD=1&RD=2&ST=1&SHA2=1NGoA0eTonIEWNq6X99n6MGY2schrK-AjiJagw1vLTQ=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From frederic.pichon at thalesgroup.com Mon Jun 13 15:44:25 2011 From: frederic.pichon at thalesgroup.com (PICHON Frederic) Date: Mon, 13 Jun 2011 15:44:25 +0200 Subject: [Fiware-data] FI-WARE WP6 - description of an intelligent service focused on information evaluation In-Reply-To: <30998_1307694434_4DF1D562_30998_10501_1_OFEAEE942C.EB5A2115-ONC12578AB.002BBB2F-C12578AB.002E82D4@thalesaleniaspace.com> References: <30998_1307694434_4DF1D562_30998_10501_1_OFEAEE942C.EB5A2115-ONC12578AB.002BBB2F-C12578AB.002E82D4@thalesaleniaspace.com> Message-ID: <24529_1307972667_4DF6143B_24529_4343_1_908CBC9017354841B2F32BBEC70A05A101C35575431D@THSONEA01CMS01P.one.grp> Dear Juanjo, Here is the description of the "Information Evaluation" plug-in that we propose to add to the Intelligent Services algorithms : https://forge.fi-ware.eu/docman/view.php/9/139/FI-WARE_High-Level_Description+Data-Context+Management+Intelligent+Services+algorithms+Information+Evaluation+plug-in+Thales.doc Best regards, Fr?d?ric -- Fr?d?ric Pichon Decision Technologies & Mathematics Lab Thales Research & Technology Campus Polytechnique 1 avenue Augustin Fresnel 91767 Palaiseau cedex France tel: +33 1.69.41.57.02 fax: +33 1.69.41.60.01 mailto:frederic.pichon at thalesgroup.com -- The information contained in this e-mail/fax and any attachments are the property of THALES and may be confidential. If you are not the intended recipient, please notify us immediately, send this message back to us and destroy it. You are hereby notified that any review, dissemination, distribution, copying or otherwise use of this e-mail/fax is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thomas.DELAVALLADE at fr.thalesgroup.com Mon Jun 13 16:39:42 2011 From: Thomas.DELAVALLADE at fr.thalesgroup.com (Thomas.DELAVALLADE at fr.thalesgroup.com) Date: Mon, 13 Jun 2011 16:39:42 +0200 Subject: [Fiware-data] FI-WARE WP6 - description of an intelligent ser vice focused on information evaluation Message-ID: <24529_1307975982_4DF6212E_24529_7142_1_F9415610929D5E4EB9213E0770A0C5000469C46D@helios2.clb.tcfr.thales> Dear Juanjo, you'll find hereafter the description of the "Intelligent Data Exploration" plug-in we also propose to add to the Intelligent Services Algorithms https://forge.fi-ware.eu/docman/view.php/9/140/FI-WARE_High-Level_Descriptio n_11-06-1+Data-Context+Management+v1.011-06-01+Thales+OLAP+plugin.doc Best regards, Thomas _____ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de PICHON Frederic Envoy? : lundi 13 juin 2011 15:44 ? : jhierro at tid.es Cc : fiware-data at lists.fi-ware.eu Objet : [Fiware-data] FI-WARE WP6 - description of an intelligent service focused on information evaluation Dear Juanjo, Here is the description of the "Information Evaluation" plug-in that we propose to add to the Intelligent Services algorithms : https://forge.fi-ware.eu/docman/view.php/9/139/FI-WARE_High-Level_Descriptio n+Data-Context+Management+Intelligent+Services+algorithms+Information+Evalua tion+plug-in+Thales.doc Best regards, Fr?d?ric -- Fr?d?ric Pichon Decision Technologies & Mathematics Lab Thales Research & Technology Campus Polytechnique 1 avenue Augustin Fresnel 91767 Palaiseau cedex France tel: +33 1.69.41.57.02 fax: +33 1.69.41.60.01 mailto:frederic.pichon at thalesgroup.com -- The information contained in this e-mail/fax and any attachments are the property of THALES and may be confidential. If you are not the intended recipient, please notify us immediately, send this message back to us and destroy it. You are hereby notified that any review, dissemination, distribution, copying or otherwise use of this e-mail/fax is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jun 14 12:57:49 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 14 Jun 2011 12:57:49 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Message-ID: <4DF73EAD.2090001@tid.es> Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:part1.03010906.08070301 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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: 0clip_image002.gif Type: image/gif Size: 7137 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From GUYSH at il.ibm.com Tue Jun 14 15:54:23 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Tue, 14 Jun 2011 16:54:23 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <4DF73EAD.2090001@tid.es> References: <4DF73EAD.2090001@tid.es> Message-ID: My only comment is regarding events I think our statement can be stronger about how an event object looks like - that we know what we want as a basic and things can be added ontop. The very basic is that an event object must have a type name. (one of the major distinctions from data), e.g rightMouseClick, buyStock The properties (or better yet use what we already defined ... data element) could be multiple ones BUT the basis must contain like you have written the detection time which is the time the event object was created. With these two pieces of information we can start creating event processing logic - without these you can't. 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 From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 14:00 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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 "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 14 16:30:25 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 14 Jun 2011 16:30:25 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: <4DF77081.5080909@tid.es> On 14/06/11 15:54, Guy Sharon wrote: My only comment is regarding events I think our statement can be stronger about how an event object looks like - that we know what we want as a basic and things can be added ontop. The very basic is that an event object must have a type name. (one of the major distinctions from data), e.g rightMouseClick, buyStock Note that a "data element" has an EntityId as well as a Type name. So the type name you are asking for is there: matches the name of the type linked to the data element. The properties (or better yet use what we already defined ... data element) could be multiple ones BUT the basis must contain like you have written the detection time which is the time the event object was created. With these two pieces of information we can start creating event processing logic - without these you can't. Data elements have a set of properties, but I believe we should not force data elements to have a property corresponding to "detection time" if we want to process them as events. We want to be able to read a given data element (as an example, as result of retrieving a data record from a data base) and be able to push it to the CEP GE or the Publish/Subscribe Broker GE. This would mean adding a timestamp actually, but that would go as a part of a sort of "header" of the event object wrapping the data element which would be created by the CEP GE internally to ease event processing. That's why I have declared that event objects are made of data element plus some associated properties relevant for event processing (timestamp and maybe others we may find useful). I feel like we should precisely add that those event objects will be created at the time a data element arrives to the CEP GE (and I would add ven to the Publish/Subscribe Broker GE). We don't need to attach a type name as part of the header in the event object wrapping a data element because the data element structure already contains the type name. I believe that the descriptions I provided were compatible with those you provided initially. I just wanted to formulate them in a way that: * any sort of data elements could be transformed into event objects (would be just a matter of attaching info relevant to event processing) * the definition of data elements and context elements allow us to go for a model which is close or compliant to the model defined in the OMA standard Please think about it carefully and with an open mind, not having a concrete product in mind. Best regards, -- Juanjo Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:part1.02090004.05050803 at tid.es] 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 From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 14:00 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:part2.07010108.09000800 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Tue Jun 14 17:51:37 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 14 Jun 2011 17:51:37 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <4DF73EAD.2090001@tid.es> References: <4DF73EAD.2090001@tid.es> Message-ID: Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image001.gif at 01CC2AAC.FAE1DF30] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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: image001.gif Type: image/gif Size: 7137 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Tue Jun 14 17:51:39 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 14 Jun 2011 17:51:39 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: I share this view. As I have said the event consist of two elements: event (name as data value) and time. Other references are implicit (under-intended) and meta-data (optional). Adding the entity reference we obtain the context. Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Tuesday, June 14, 2011 3:54 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events My only comment is regarding events I think our statement can be stronger about how an event object looks like - that we know what we want as a basic and things can be added ontop. The very basic is that an event object must have a type name. (one of the major distinctions from data), e.g rightMouseClick, buyStock The properties (or better yet use what we already defined ... data element) could be multiple ones BUT the basis must contain like you have written the detection time which is the time the event object was created. With these two pieces of information we can start creating event processing logic - without these you can't. Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2AAD.D6A7C610] 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 From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 14:00 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image002.gif at 01CC2AAD.D6A7C610] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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. [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: image001.gif Type: image/gif Size: 2558 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 7137 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Tue Jun 14 18:06:33 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 14 Jun 2011 18:06:33 +0200 Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) Message-ID: <4DF78709.9000204@tid.es> Hi all, We would use the powwownow bridge: PIN: 050662 Dial-in phone numbers in the attachment. The main goal of this confcall is that Telecom Italia explains their contribution in the field. We will also brief those who didn't attend the confcall on monday about results of that meeting. I will check whether I can setup a webex, but I'm not pretty sure I will be able to make it. Cheers, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: Powwownow-dial-in-numbers.pdf Type: application/pdf Size: 61516 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 14 18:26:16 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 14 Jun 2011 18:26:16 +0200 Subject: [Fiware-data] Webex details Message-ID: <4DF78BA8.7040409@tid.es> Tema: FI-WARE confcall Data Semantics Fecha: martes, 14 de junio de 2011 Hora: 18:19, Europa Verano Hora (Par?s, GMT+02:00) Nzmero de la reunisn: 672 239 869 Contraseqa de la reunisn: 1234abcD ------------------------------------------------------- Para unirse a la reuni?n en l?nea (?Ahora tambi?n desde iPhones!) ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/e.php?AT=MI&EventID=11800233&UID=104256523&PW=NOTZkYjk0ZDJl&RT=MTQjMjM%3D 2. Introduzca su nombre y direcci?n de correo electr?nico. 3. Introduzca la contrase?a de la reuni?n: 1234abcD 4. Haga clic en "Entrar ahora". 5. Siga las instrucciones que aparecen en pantalla. Para ver en otras zonas horarias o idiomas, haga clic en el enlace: https://telefonica.webex.com/telefonica/e.php?AT=MI&EventID=11800233&UID=104256523&PW=NOTZkYjk0ZDJl&ORT=MTQjMjM%3D ------------------------------------------------------- Para obtener ayuda ------------------------------------------------------- 1. Vaya a https://telefonica.webex.com/telefonica/mc 2. En la barra de navegaci?n izquierda, haga clic en "Soporte". Puede ponerse en contacto conmigo en: Webex7000 at tid.es Inscr?base para disfrutar de la prueba gratuita de WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com AVISO IMPORTANTE: Este servicio de WebEx incluye una funci?n que permite ver e intercambiar audio, documentos y otros materiales durante la sesi?n que va a grabarse. Al unirse a esta sesi?n, autom?ticamente da permiso para realizar dichas grabaciones. Si no est? de acuerdo con la grabaci?n, no se una a la sesi?n. ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 14 18:32:02 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 14 Jun 2011 18:32:02 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: <4DF78D02.2010300@tid.es> Sorry Boris but I have hardly understood your comments ... let me comment between lines of your email to point out what I don't understand ... On 14/06/11 17:51, Moltchanov Boris wrote: Dear Juajo, I would put the event definition before the Context. You mean the section ? Don't have any problem with that. But the point is that I believe that the definition of "Context" should not rely on the definition of "Event" As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. I do not understand why you talk here about "numbers" ... I also don't understand the text I put in read what you mean when you say "the data ... is a most generic case where only number (value) is the must" Can you be more precise about what are you referring to when you say "everything else" ? meta-data linked to data element attributes are indeed optional. It was said in the proposed text: "existence of meta-data linked to a data element attribute is optional." I believe that the type in a data element attribute is not something you can make it optional ... how would you be able to analyze what is the type of the value ? Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Actually, we say that event = data-element + "time when happened" ... but I don't clearly understand the meaning of what you wrote in parenthesis: "the object referred by the data is implicit therefore could be omitted" ... did you try to mean "the type associated to the data-element is implicit (is part of its description), therefore does not need to be added" ? This is actually what I tried to explain to Guy in my mail before. But please confirm. Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. Note that in the definitions that I proposed, there would be the concept of "context element" and the concept of event linked to a context element. In other words, there will be events of the form: event = context-element (which is a special kind of data-element) + "time when happened" If the Publish/Subscribe Broker GE is something that will enable programmers to do things like subscribing to "context elements received after some time" or "context element not older than this particular time", then we just need to declare that the Publish/Subscribe Broker GE deals with events. Best regards, -- Juanjo I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:part1.01020509.06020808 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:part2.04000709.06090804 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/gif Size: 7137 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From GUYSH at il.ibm.com Tue Jun 14 18:38:03 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Tue, 14 Jun 2011 19:38:03 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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 GUYSH at il.ibm.com Tue Jun 14 18:46:00 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Tue, 14 Jun 2011 19:46:00 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <4DF77081.5080909@tid.es> References: <4DF73EAD.2090001@tid.es> <4DF77081.5080909@tid.es> Message-ID: OK Juanjo That should work - as later stated in the definition there needs to be an explicit or implicit identification of event object from data Meaning that (taking your example of a DB record) The event type (name of the event) - could either come from some column\field in the record OR the name of the table (metadata) is the event type for all records. In both cases these still would be data elements so your explanation below I think covers this. On top of that though - we would need someone to explicitly 'map' the appropriate data element to the name of the event OR in some cases we could implicitly do this. 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 From: Juanjo Hierro To: fiware-data at lists.fi-ware.eu Date: 14/06/2011 17:30 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu On 14/06/11 15:54, Guy Sharon wrote: My only comment is regarding events I think our statement can be stronger about how an event object looks like - that we know what we want as a basic and things can be added ontop. The very basic is that an event object must have a type name. (one of the major distinctions from data), e.g rightMouseClick, buyStock Note that a "data element" has an EntityId as well as a Type name. So the type name you are asking for is there: matches the name of the type linked to the data element. The properties (or better yet use what we already defined ... data element) could be multiple ones BUT the basis must contain like you have written the detection time which is the time the event object was created. With these two pieces of information we can start creating event processing logic - without these you can't. Data elements have a set of properties, but I believe we should not force data elements to have a property corresponding to "detection time" if we want to process them as events. We want to be able to read a given data element (as an example, as result of retrieving a data record from a data base) and be able to push it to the CEP GE or the Publish/Subscribe Broker GE. This would mean adding a timestamp actually, but that would go as a part of a sort of "header" of the event object wrapping the data element which would be created by the CEP GE internally to ease event processing. That's why I have declared that event objects are made of data element plus some associated properties relevant for event processing (timestamp and maybe others we may find useful). I feel like we should precisely add that those event objects will be created at the time a data element arrives to the CEP GE (and I would add ven to the Publish/Subscribe Broker GE). We don't need to attach a type name as part of the header in the event object wrapping a data element because the data element structure already contains the type name. I believe that the descriptions I provided were compatible with those you provided initially. I just wanted to formulate them in a way that: any sort of data elements could be transformed into event objects (would be just a matter of attaching info relevant to event processing) the definition of data elements and context elements allow us to go for a model which is close or compliant to the model defined in the OMA standard Please think about it carefully and with an open mind, not having a concrete product in mind. Best regards, -- Juanjo 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 From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 14:00 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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 "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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[attachment "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 14 19:46:31 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 14 Jun 2011 19:46:31 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: <4DF79E77.9030407@tid.es> Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:part1.05010609.09000806 at tid.es] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:part2.07030402.08010907 at tid.es] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:part3.01090101.04030306 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:part4.08030103.04000702 at tid.es]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 ________________________________ 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: image/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Wed Jun 15 11:59:04 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Jun 2011 11:59:04 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: Hi Guy, No, entity only is not sufficient, the context must have the time-stamp (in order to check its real-timeness) and could have a type as well (context scope name). Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Tuesday, June 14, 2011 6:38 PM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Tentative definition of basic concepts: data, context and events Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:image001.gif at 01CC2B53.9F46D0C0] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image002.gif at 01CC2B53.9F46D0C0] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image003.gif at 01CC2B53.9F46D0C0] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:image004.gif at 01CC2B53.9F46D0C0]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 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: image001.gif Type: image/gif Size: 4203 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 2558 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From GUYSH at il.ibm.com Wed Jun 15 12:13:27 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Wed, 15 Jun 2011 13:13:27 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: Hi, OK but timestamp and scope name still dont make it an event - although the concepts have similar structural needs (context has a bit more) - it doesnt make sense to 'inherit' the structure. Although context can be interpreted from data or from events 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL Cc: "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 12:59 Subject: RE: Tentative definition of basic concepts: data, context and events Hi Guy, No, entity only is not sufficient, the context must have the time-stamp (in order to check its real-timeness) and could have a type as well (context scope name). Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Tuesday, June 14, 2011 6:38 PM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Tentative definition of basic concepts: data, context and events Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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 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. -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Wed Jun 15 12:28:03 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Jun 2011 12:28:03 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: Hi, It depends what type of the data and data itself you put in the context. For example: The data = 5 (value) The event is The data + The meta-data -> event_type = "rain conditions" (so there 5 is the rain (or raining) with the rate 5 (mm/hours); The context is The event+EntityID or The data+context_type+EntityID and Entity ID="Turin (city or location) (so there is rain of 5 force in the city Turin). I'm not discussing here about the types and values, I'm speaking about the data structure. Generally speaking, everything is a data (values) + metadata (types), however we may go deeper and define that adding the time-stamp and saying that the meta-data is an event-type we obtain an event, adding to that the EntityID we obtain a context. This vision is also in line with the OMA data structure definition, which goes even deeper, so it is not only saying that the data could have the meta-data but saying that also the data meta-data (context) could also have a nestled meta-data as context-type and so on. Please think about this, about the structure and have a look at the OMA specification. I will try to answer to Juanjo mails. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Wednesday, June 15, 2011 12:13 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, OK but timestamp and scope name still dont make it an event - although the concepts have similar structural needs (context has a bit more) - it doesnt make sense to 'inherit' the structure. Although context can be interpreted from data or from events Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2B57.259DCEF0] 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL Cc: "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 12:59 Subject: RE: Tentative definition of basic concepts: data, context and events ________________________________ Hi Guy, No, entity only is not sufficient, the context must have the time-stamp (in order to check its real-timeness) and could have a type as well (context scope name). Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Tuesday, June 14, 2011 6:38 PM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Tentative definition of basic concepts: data, context and events Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:image002.gif at 01CC2B57.259DCEF0] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2B57.259DCEF0] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image003.gif at 01CC2B57.259DCEF0] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:image004.gif at 01CC2B57.259DCEF0]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 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:image004.gif at 01CC2B57.259DCEF0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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: image001.gif Type: image/gif Size: 2558 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4203 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From GUYSH at il.ibm.com Wed Jun 15 13:16:43 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Wed, 15 Jun 2011 14:16:43 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: I think we are aligned - I agree with you - my point that I was trying to make is that not every data with time-stamp is necessarily an event e.g - you get the same piece of data multiple times during different time-stamps - this could be a repeated broadcast of a location of some device which has not changed over this time - there is no event here. But still you have context. 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL, "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 13:28 Subject: RE: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, It depends what type of the data and data itself you put in the context. For example: The data = 5 (value) The event is The data + The meta-data -> event_type = ?rain conditions? (so there 5 is the rain (or raining) with the rate 5 (mm/hours); The context is The event+EntityID or The data+context_type+EntityID and Entity ID=?Turin (city or location) (so there is rain of 5 force in the city Turin). I?m not discussing here about the types and values, I?m speaking about the data structure. Generally speaking, everything is a data (values) + metadata (types), however we may go deeper and define that adding the time-stamp and saying that the meta-data is an event-type we obtain an event, adding to that the EntityID we obtain a context. This vision is also in line with the OMA data structure definition, which goes even deeper, so it is not only saying that the data could have the meta-data but saying that also the data meta-data (context) could also have a nestled meta-data as context-type and so on. Please think about this, about the structure and have a look at the OMA specification. I will try to answer to Juanjo mails. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Wednesday, June 15, 2011 12:13 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, OK but timestamp and scope name still dont make it an event - although the concepts have similar structural needs (context has a bit more) - it doesnt make sense to 'inherit' the structure. Although context can be interpreted from data or from events 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL Cc: "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 12:59 Subject: RE: Tentative definition of basic concepts: data, context and events Hi Guy, No, entity only is not sufficient, the context must have the time-stamp (in order to check its real-timeness) and could have a type as well (context scope name). Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Tuesday, June 14, 2011 6:38 PM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Tentative definition of basic concepts: data, context and events Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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 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. 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. -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 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 boris.moltchanov at telecomitalia.it Wed Jun 15 13:17:39 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Jun 2011 13:17:39 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <4DF79E77.9030407@tid.es> References: <4DF73EAD.2090001@tid.es> <4DF79E77.9030407@tid.es> Message-ID: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number "5") is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named "data_type" is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more - EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don't need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don't know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the "owner" if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo's mail followed the same thoughts, that I've tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:image001.gif at 01CC2B57.D3ABE9F0] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image002.gif at 01CC2B57.D3ABE9F0] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image003.gif at 01CC2B57.D3ABE9F0] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:image004.gif at 01CC2B57.D3ABE9F0]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 ________________________________ 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: image001.gif Type: image/gif Size: 4203 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 2558 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Wed Jun 15 13:19:54 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Jun 2011 13:19:54 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: "make is that not every data with time-stamp is necessarily an event" - exactly, but the structure if of that of an event. The question whether it is event or not will depend not on the structure but on the context of that structure (data_types and names). And no, it is still not a context - we have to add to it EntityID (actor, subject, owner, object, whatever we call it) and we will get a context. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Wednesday, June 15, 2011 1:17 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events I think we are aligned - I agree with you - my point that I was trying to make is that not every data with time-stamp is necessarily an event e.g - you get the same piece of data multiple times during different time-stamps - this could be a repeated broadcast of a location of some device which has not changed over this time - there is no event here. But still you have context. Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2B5E.EA3DF170] 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL, "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 13:28 Subject: RE: [Fiware-data] Tentative definition of basic concepts: data, context and events ________________________________ Hi, It depends what type of the data and data itself you put in the context. For example: The data = 5 (value) The event is The data + The meta-data -> event_type = "rain conditions" (so there 5 is the rain (or raining) with the rate 5 (mm/hours); The context is The event+EntityID or The data+context_type+EntityID and Entity ID="Turin (city or location) (so there is rain of 5 force in the city Turin). I'm not discussing here about the types and values, I'm speaking about the data structure. Generally speaking, everything is a data (values) + metadata (types), however we may go deeper and define that adding the time-stamp and saying that the meta-data is an event-type we obtain an event, adding to that the EntityID we obtain a context. This vision is also in line with the OMA data structure definition, which goes even deeper, so it is not only saying that the data could have the meta-data but saying that also the data meta-data (context) could also have a nestled meta-data as context-type and so on. Please think about this, about the structure and have a look at the OMA specification. I will try to answer to Juanjo mails. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Wednesday, June 15, 2011 12:13 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, OK but timestamp and scope name still dont make it an event - although the concepts have similar structural needs (context has a bit more) - it doesnt make sense to 'inherit' the structure. Although context can be interpreted from data or from events Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2B5E.EA3DF170] 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL Cc: "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 12:59 Subject: RE: Tentative definition of basic concepts: data, context and events ________________________________ Hi Guy, No, entity only is not sufficient, the context must have the time-stamp (in order to check its real-timeness) and could have a type as well (context scope name). Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Tuesday, June 14, 2011 6:38 PM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Tentative definition of basic concepts: data, context and events Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:image002.gif at 01CC2B5E.EA3DF170] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2B5E.EA3DF170] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image003.gif at 01CC2B5E.EA3DF170] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:image004.gif at 01CC2B5E.EA3DF170]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 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:image004.gif at 01CC2B5E.EA3DF170]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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:image004.gif at 01CC2B5E.EA3DF170]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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: image001.gif Type: image/gif Size: 2558 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4203 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From GUYSH at il.ibm.com Wed Jun 15 13:22:58 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Wed, 15 Jun 2011 14:22:58 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> Message-ID: Ups - correct left that out. So we agree - we are talking about structure not interpretation of the structure to event or context 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL, "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 14:20 Subject: RE: [Fiware-data] Tentative definition of basic concepts: data, context and events ?make is that not every data with time-stamp is necessarily an event? ? exactly, but the structure if of that of an event. The question whether it is event or not will depend not on the structure but on the context of that structure (data_types and names). And no, it is still not a context ? we have to add to it EntityID (actor, subject, owner, object, whatever we call it) and we will get a context. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Wednesday, June 15, 2011 1:17 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events I think we are aligned - I agree with you - my point that I was trying to make is that not every data with time-stamp is necessarily an event e.g - you get the same piece of data multiple times during different time-stamps - this could be a repeated broadcast of a location of some device which has not changed over this time - there is no event here. But still you have context. 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL, "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 13:28 Subject: RE: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, It depends what type of the data and data itself you put in the context. For example: The data = 5 (value) The event is The data + The meta-data -> event_type = ?rain conditions? (so there 5 is the rain (or raining) with the rate 5 (mm/hours); The context is The event+EntityID or The data+context_type+EntityID and Entity ID=?Turin (city or location) (so there is rain of 5 force in the city Turin). I?m not discussing here about the types and values, I?m speaking about the data structure. Generally speaking, everything is a data (values) + metadata (types), however we may go deeper and define that adding the time-stamp and saying that the meta-data is an event-type we obtain an event, adding to that the EntityID we obtain a context. This vision is also in line with the OMA data structure definition, which goes even deeper, so it is not only saying that the data could have the meta-data but saying that also the data meta-data (context) could also have a nestled meta-data as context-type and so on. Please think about this, about the structure and have a look at the OMA specification. I will try to answer to Juanjo mails. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Wednesday, June 15, 2011 12:13 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, OK but timestamp and scope name still dont make it an event - although the concepts have similar structural needs (context has a bit more) - it doesnt make sense to 'inherit' the structure. Although context can be interpreted from data or from events 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 From: Moltchanov Boris To: Guy Sharon/Haifa/IBM at IBMIL Cc: "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 12:59 Subject: RE: Tentative definition of basic concepts: data, context and events Hi Guy, No, entity only is not sufficient, the context must have the time-stamp (in order to check its real-timeness) and could have a type as well (context scope name). Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Tuesday, June 14, 2011 6:38 PM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Tentative definition of basic concepts: data, context and events Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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 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. 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. 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. -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From jhierro at tid.es Wed Jun 15 15:56:15 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 15 Jun 2011 15:56:15 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> <4DF79E77.9030407@tid.es> Message-ID: <4DF8B9FF.1000807@tid.es> Hi Boris, Guy, I believe the picture is getting clear and we can reach soon a consensus here ... Thanks Boris for clarifying the meaning of the EntityId field in the description of a Context Element in OMA specs. This is helpful to close the final model. Let's use then EntityId as a field identifying the entity to which a given Context Element is relevant. That's fine. Then this field would be specific to Context Element and would not be present in Data Elements. I guess we would agree here. One thing I wouldn't agree with Boris is that EntityId and timestamp can be used as the Id in a DB. There might be two Context Elements produced at the very exact time (this might be not than frequent but still possible.) Therefore, the combination of the two fields cannot be used as a unique id. I believe that issue can be solved in a simpler manner. We may just say that Data Elements have no id. In case that is needed, for storage purpose as an example, it's up to the application to generate it (of course, value of some property in the Data Element can be used for that purpose.) A similar thing applies to the "EntityType" field defined in OMA. I guess this actually refers to the Type associated to the Entity identified by the "EntityId" field. Therefore, it doesn't match to the name of the type linked to the Data. I would handle this field similarly to the "EntityId" field in OMA. We may just say that Data Elements have no data type id (name). In this case, the only exception that I would made is that I would make it an optional field. Based on the above, I believe that we may define a model where: * Data Elements exist and have: * an optional "DataType" associated (universal name used to identify the type linked to the data) * a sequence of attributes, defined as triplets * per each attribute, a sequence of meta-data, each meta-data defined as * (note: value is a basic data value or a data element * Context Elements inherit from Data Elements (that is, are a specialized case of Data Elements) where: * they have an additional mandatory "EntityId" associated which referes to the entity the context element is related to * they have an additional mandatory "EntityType" associated which refers to the type of the entity identified by the previous "EntityId" * certain attributes (to be defined in the FI-WARE specification) will be mandatory * Events are objects that contain a Data Element (therefore, may also contain a Context Element) and have associated a timestamp relevant for event processing. What I believe it is not appropriate is to say that the Context are special kind of events. I see Context Elements as a special case of Data Elements. Both being able to be treated as events, that is, being able to be pushed into the CEP Generic Enabler or the Publish/Subscribe Broker GE. A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number ?5?) is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named ?data_type? is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more ? EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don?t need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don?t know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the ?owner? if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo?s mail followed the same thoughts, that I?ve tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:part1.06030909.09090002 at tid.es] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:part2.06090307.01020005 at tid.es] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:part3.03030603.02000302 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:part4.04030708.00020209 at tid.es]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 ________________________________ 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:part5.07040501.08040405 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From fano.ramparany at orange-ftgroup.com Wed Jun 15 17:08:47 2011 From: fano.ramparany at orange-ftgroup.com (fano.ramparany at orange-ftgroup.com) Date: Wed, 15 Jun 2011 17:08:47 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <4DF8B9FF.1000807@tid.es> References: <4DF73EAD.2090001@tid.es><4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number "5") is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named "data_type" is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more - EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don't need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don't know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the "owner" if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo's mail followed the same thoughts, that I've tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu ) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ 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: ATT2275411.gif Type: image/gif Size: 4203 bytes Desc: ATT2275411.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2275412.gif Type: image/gif Size: 2558 bytes Desc: ATT2275412.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2275413.gif Type: image/gif Size: 7137 bytes Desc: ATT2275413.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2275414.gif Type: image/gif Size: 677 bytes Desc: ATT2275414.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT2275415.jpg Type: image/jpeg Size: 677 bytes Desc: ATT2275415.jpg URL: From GUYSH at il.ibm.com Wed Jun 15 19:36:50 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Wed, 15 Jun 2011 20:36:50 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <4DF8B9FF.1000807@tid.es> References: <4DF73EAD.2090001@tid.es> <4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: I'll leave the context element to Boris As for the last part about the event and timestamp - this is exactly how I see it and what you are able to distinguish in our asset We call the time the event object is generated by the middleware - "detection time" We call the data element that can be interpreted (rules\mapping) as the time of the event creation - "occurrence time" Using the occurrence time is of course much harder as now events may be detected in a different order than they actually occurred. - We deal with this. Finally - the crucial point Juanjo mentions at the end not being in the thread - it goes without saying - I believe we all agree on this point - at least Juanjo and I discussed this at one point and its obvious that CEP asset can support but there needs to be additional support for specific formats if they are used. Thus we dont depend on one standard or another. 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 From: Juanjo Hierro To: Moltchanov Boris Cc: "fiware-data at lists.fi-ware.eu" Date: 15/06/2011 16:56 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Hi Boris, Guy, I believe the picture is getting clear and we can reach soon a consensus here ... Thanks Boris for clarifying the meaning of the EntityId field in the description of a Context Element in OMA specs. This is helpful to close the final model. Let's use then EntityId as a field identifying the entity to which a given Context Element is relevant. That's fine. Then this field would be specific to Context Element and would not be present in Data Elements. I guess we would agree here. One thing I wouldn't agree with Boris is that EntityId and timestamp can be used as the Id in a DB. There might be two Context Elements produced at the very exact time (this might be not than frequent but still possible.) Therefore, the combination of the two fields cannot be used as a unique id. I believe that issue can be solved in a simpler manner. We may just say that Data Elements have no id. In case that is needed, for storage purpose as an example, it's up to the application to generate it (of course, value of some property in the Data Element can be used for that purpose.) A similar thing applies to the "EntityType" field defined in OMA. I guess this actually refers to the Type associated to the Entity identified by the "EntityId" field. Therefore, it doesn't match to the name of the type linked to the Data. I would handle this field similarly to the "EntityId" field in OMA. We may just say that Data Elements have no data type id (name). In this case, the only exception that I would made is that I would make it an optional field. Based on the above, I believe that we may define a model where: Data Elements exist and have: an optional "DataType" associated (universal name used to identify the type linked to the data) a sequence of attributes, defined as triplets per each attribute, a sequence of meta-data, each meta-data defined as (note: value is a basic data value or a data element Context Elements inherit from Data Elements (that is, are a specialized case of Data Elements) where: they have an additional mandatory "EntityId" associated which referes to the entity the context element is related to they have an additional mandatory "EntityType" associated which refers to the type of the entity identified by the previous "EntityId" certain attributes (to be defined in the FI-WARE specification) will be mandatory Events are objects that contain a Data Element (therefore, may also contain a Context Element) and have associated a timestamp relevant for event processing. What I believe it is not appropriate is to say that the Context are special kind of events. I see Context Elements as a special case of Data Elements. Both being able to be treated as events, that is, being able to be pushed into the CEP Generic Enabler or the Publish/Subscribe Broker GE. A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: We comply with OMA specs We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number ?5?) is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named ?data_type? is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more ? EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don?t need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don?t know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the ?owner? if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo?s mail followed the same thoughts, that I?ve tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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 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. 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 "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From GUYSH at il.ibm.com Wed Jun 15 19:45:12 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Wed, 15 Jun 2011 20:45:12 +0300 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es><4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: Fano - I think its also important to see if the RDF can be mapped to the model we discuss (the other way around) I think its symmetric in probably all cases of formats - but something to consider 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 From: To: , Cc: fiware-data at lists.fi-ware.eu Date: 15/06/2011 19:20 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: We comply with OMA specs We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number ?5?) is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named ?data_type? is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more ? EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don?t need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don?t know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the ?owner? if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo?s mail followed the same thoughts, that I?ve tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. 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 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. 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 -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 4203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7137 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Wed Jun 15 20:55:58 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Jun 2011 20:55:58 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <4DF8B9FF.1000807@tid.es> References: <4DF73EAD.2090001@tid.es> <4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: <7E8F4654-93F8-4655-83EE-A076C8EF6A36@telecomitalia.it> Hi Everyone, First of all for this attempt trying to understand what I meant in emails, is not easy neither to express nor to understand for the persons getting first knowledge about the context matter. I put my comments in the body of below email. 15/giu/2011, ? 15:56, "Juanjo Hierro" > ???????(?): Hi Boris, Guy, I believe the picture is getting clear and we can reach soon a consensus here ... Thanks Boris for clarifying the meaning of the EntityId field in the description of a Context Element in OMA specs. This is helpful to close the final model. Let's use then EntityId as a field identifying the entity to which a given Context Element is relevant. That's fine. Then this field would be specific to Context Element and would not be present in Data Elements. I guess we would agree here. Fine. One thing I wouldn't agree with Boris is that EntityId and timestamp can be used as the Id in a DB. There might be two Context Elements produced at the very exact time (this might be not than frequent but still possible.) Therefore, the combination of the two fields cannot be used as a unique id. Sorry, probably I made an explanation mistake here, the DataID - unique identifier for the context might be obtained by combination of EntityID+context_scope+timestamp. it must be univocal as far as the same context must come from the same context source at the same time for the same EntityID. Otherwise it creates an uncertainty in the data. However, as you correctly said, we don't need this element for the context at all. It was just a suggestion in a case we need a specific reference key. I believe that issue can be solved in a simpler manner. We may just say that Data Elements have no id. In case that is needed, for storage purpose as an example, it's up to the application to generate it (of course, value of some property in the Data Element can be used for that purpose.) Yes, agree. A similar thing applies to the "EntityType" field defined in OMA. I guess this actually refers to the Type associated to the Entity identified by the "EntityId" field. Therefore, it doesn't match to the name of the type linked to the Data. I would handle this field similarly to the "EntityId" field in OMA. We may just say that Data Elements have no data type id (name). In this case, the only exception that I would made is that I would make it an optional field. Your understanding is correct. The people dealing with the data would decide if have a metadata such as data type or data name or less. Based on the above, I believe that we may define a model where: * Data Elements exist and have: * an optional "DataType" associated (universal name used to identify the type linked to the data) * a sequence of attributes, defined as triplets * per each attribute, a sequence of meta-data, each meta-data defined as * (note: value is a basic data value or a data element Ok * * Context Elements inherit from Data Elements (that is, are a specialized case of Data Elements) where: * they have an additional mandatory "EntityId" associated which referes to the entity the context element is related to * they have an additional mandatory "EntityType" associated which refers to the type of the entity identified by the previous "EntityId" * certain attributes (to be defined in the FI-WARE specification) will be mandatory Correct. * * * Events are objects that contain a Data Element (therefore, may also contain a Context Element) and have associated a timestamp relevant for event processing. I would inverse it in sense to say that the event element inherits a data element plus some meta-data and attributes plus a timestamp And then that context element inherits event element and extending it with entityID, entityID type and some other elements to be defined. * What I believe it is not appropriate is to say that the Context are special kind of events. I see Context Elements as a special case of Data Elements. Both being able to be treated as events, that is, being able to be pushed into the CEP Generic Enabler or the Publish/Subscribe Broker GE. Probably we may say that a context element is extended version of data element as well as of data element but I don't exist:). A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. Context cannot be without EntityID therefore an event cannot be a context as is but shall be provided with EntityID and type to become a context. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) If we are not losing the meaning of triplets during this representation and triplets, it may be truth. The advantages for the model I have described so far is: * We comply with OMA specs Not complete maybe because only part of threaten spec is compliant, the rest will not, therefore not compliant formally. * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements These two points seem to be ok. Best regards, Boris Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number ?5?) is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named ?data_type? is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more ? EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don?t need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don?t know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the ?owner? if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo?s mail followed the same thoughts, that I?ve tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris <boris.moltchanov at telecomitalia.it> To: Juanjo Hierro <jhierro at tid.es>, "fiware-data at lists.fi-ware.eu" <fiware-data at lists.fi-ware.eu> Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Wed Jun 15 23:58:00 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Jun 2011 23:58:00 +0200 Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) In-Reply-To: <4DF78709.9000204@tid.es> References: <4DF78709.9000204@tid.es> Message-ID: Dear Juanjo and Siemens and ATOS (and eventually other) partners, TI is able to participate in order to discuss this topic (subject) on this Friday, starting from 15:00CET and later. Please let me know in time if this is feasible for you. Sorry for lost last communications, indeed the last email (below) received very late to organize an operative action. 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: Tuesday, June 14, 2011 6:07 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) Hi all, We would use the powwownow bridge: PIN: 050662 Dial-in phone numbers in the attachment. The main goal of this confcall is that Telecom Italia explains their contribution in the field. We will also brief those who didn't attend the confcall on monday about results of that meeting. I will check whether I can setup a webex, but I'm not pretty sure I will be able to make it. 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 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 boris.moltchanov at telecomitalia.it Thu Jun 16 00:24:50 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 16 Jun 2011 00:24:50 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es><4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: Dear Fano, Why do you believe we need another value among the context creation (generation) timestamp. The context is real or near real-time, therefore shall have a timestamp and a validity period or expiration time for this context. I believe in your mentioned use-case with the sensor the data collected during a day and sent in a bunch as a "sporadic packet" are not the context anymore. Only the last, more fresh one, could be taken as a context (if it still valid and reasonable). The rest of that sensor collected data are the context history, so is not the context anymore and could be treated at the "application" level, for example, adding a new context_scope=increasing order. For example, a sensor collecting temperature reading its onboard sensor each 5 minutes: 1. 10dgC 2. 11dgC 3. 12dgC 4. Opening TX window to send the data and sending the data to gateway or broker. 5. Only final value 12dgC is set as context, the rest 2 are recorder into the history as "previous" context from timestamp "a", when previous TX window was opened, or with a Context_scope= and context_type = previous context. Or a gateway or broker could know that that context was collected by the sensor each 5minutes and calculate back the timestamp in the history. 6. Reset the context in the sensor and again: 7. 12dgC 8. 11dgC 9. ... until the next TX window Otherwise I'm afraid we will "encode" generic data representation scheme with too much "application" dependent (particularity of that sensor) and, again, formally speaking, collected previous data, is not the context, but the history of previous, already passed and overwritten, reality. Best Regards, Boris From: fano.ramparany at orange-ftgroup.com [mailto:fano.ramparany at orange-ftgroup.com] Sent: Wednesday, June 15, 2011 5:09 PM To: jhierro at tid.es; Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Tentative definition of basic concepts: data,context and events Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number "5") is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named "data_type" is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more - EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don't need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don't know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the "owner" if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo's mail followed the same thoughts, that I've tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:image001.gif at 01CC2BBA.E678F560] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image002.gif at 01CC2BBA.E678F560] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image003.gif at 01CC2BBA.E678F560] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:image004.gif at 01CC2BBA.E678F560]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 ________________________________ 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:image004.gif at 01CC2BBA.E678F560]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image001.gif Type: image/gif Size: 4203 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 2558 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Thu Jun 16 00:27:28 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 16 Jun 2011 00:27:28 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es><4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: This is what I also thought - both schemas ContextML and RDF are triplets but one is based on a straightforward context data encoding: object-context_name-value, while other is related to semantic and ontology. I'm not sure about the final decision but the model shall be evaluated also for RDF. Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Wednesday, June 15, 2011 7:45 PM To: fano.ramparany at orange-ftgroup.com Cc: Moltchanov Boris; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Fano - I think its also important to see if the RDF can be mapped to the model we discuss (the other way around) I think its symmetric in probably all cases of formats - but something to consider Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2BBC.2C2A2FB0] 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 From: To: , Cc: fiware-data at lists.fi-ware.eu Date: 15/06/2011 19:20 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number "5") is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named "data_type" is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more - EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don't need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don't know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the "owner" if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo's mail followed the same thoughts, that I've tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this [cid:image002.gif at 01CC2BBC.2C2A2FB0] Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2BBC.2C2A2FB0] 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. [cid:image003.gif at 01CC2BBC.2C2A2FB0] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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:image004.gif at 01CC2BBC.2C2A2FB0]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 ________________________________ 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:image004.gif at 01CC2BBC.2C2A2FB0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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. [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: image001.gif Type: image/gif Size: 2558 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4203 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From p.amon at siemens.com Thu Jun 16 09:54:56 2011 From: p.amon at siemens.com (Amon, Peter) Date: Thu, 16 Jun 2011 09:54:56 +0200 Subject: [Fiware-data] Minutes of the confcall 11-05-27 In-Reply-To: References: <4DDF672D.3050304@tid.es> Message-ID: Dear Boris, all, the GE "Multimedia Recognition Brokering" is in line with the description of our "Multimedia Analysis" GE, especially the "Detectors" and "Recognizer" part. Some other features like "Feedback" and "Provisioning" would be complementary to the functionality we offer at the moment. Boris/Juanjo, did we already decide about merging the two. For the moment, I see two options: 1. Merge them in D2.2a already. 2. Keep them separate in D2.2a and decide about a merge for D2.2b later. I can offer to volunteer to do the editing. (I am equivalently fine with TI doing the integration. :-) Kind regards Peter ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: Freitag, 10. Juni 2011 12:02 To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Minutes of the confcall 11-05-27 Dear All, I don't remember if we have already conf-call planned, probably not yet. Sorry my IoT(houghts) in my brain is in a completely and truly MASH configuration with a lot of race conditions and collisions (not saying about faulting)... ;-). As I've mentioned during the just terminated conf-call and with regard to the attached email, please find uploaded two new contributions by TI as: - Semantic Annotation Enabler https://forge.fi-ware.eu/docman/view.php/9/136/FI-WARE_High-Level_Description_Semantic_Annotation_Enabler_TI.docx for integration with ATOS; - Multimedia Recognition Brokering https://forge.fi-ware.eu/docman/view.php/9/135/FI-WARE_High-Level_Description_Multimedia_Recognition_Brokering_Enabler_TI.docx for integration with Siemens. For sure if would be much better if the documents by default will be market as private and only then manually activated as public. Best Regards, Boris TI From: Moltchanov Boris Sent: Friday, May 27, 2011 4:16 PM To: 'Juanjo Hierro'; fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Minutes of the confcall 11-05-27 Dear All, TI in Turin will be closed on Thursday and Friday of next week, therefore we will be unable to participate in the next WP6 call. However we're very interested to be a part of the discussions regarding the following two aspects: - Semantic web annotation tools (with ATOS); - Multimedia analysis (with Siemens); as far as we have active assets in these areas as demonstrated during the kick-off meeting. I will share the documents from the docman with my colleagues, and would like to check with you if you're planning dedicated calls for these 2 topics in the beginning of the next week (30/05-01/05 incl.). Thank you. 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: Friday, May 27, 2011 10:56 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of the confcall 11-05-27 Dear colleagues, Please find enclosed the minutes I have taken during our weekly confcall. Comments are welcome. I assign a numbering to the different actions of the Action Plan we agreed. Note that action 3 was an action you didn't have time to see written in the shared desktop during the confcall but was indeed discussed. To Telecom Italia: please note that we agreed on the timeslots for celebrating the pending confcalls on Publish/Subscribe Broker as well as on Search/Quering Access (point 1 in the agenda). We beared in mind the timeslots of availability you provided to me in a separate mail. The only one for which we have yet to agree is the one on the Localization GE. Unfortunately, Thales didn't attend the confcall. Best regards, -- Juanjo Attendees: TID: Juanjo IBM: Guy Telecom Italia: ATOS: Tomas and Chema Orange: Fano Ramparany Siemens: Andreas, Thomas, Peter Thales: UPM: Agenda: 1. Review of actions from previous call 2. Status of contributions to deliverable (High-level Description) 3. Planning of next steps 1. Review of actions from previous call + confcall on Publish/Subscribe: Tuesday May 31, 11:30 - 13:00 + confcall Query/Siemens: Wednesday June 1, 09:30 - 11:00 + confcall on Localization GE: still ACTION pending Rest of actions had been done or had to do with contributions (therefore reviewed in next point of the agenda) 2. Status of contributions Action: The editor of each subsection in section 2, have to consider and hightlight whatever aspect related to Security is relevant for the GE description * Off-line Big Data analysis-processing/mining platform (TID) * Big Data stream processing based on map-reduce (TID) These two indeed match to a single GE. I have retitled the second aspect. Description was uploaded to the server ACTION: IBM and Telefonica to hold a confcall on monday May 31 starting 15:30 to reach full alignment on architecture of the processing part and combination/integration of TID's and IBM's assets. * Intelligent Services Plug-ins (TID) Uploaded to the docs server * Real-time stream processing based on CPE (IBM) Uploaded to the docs server * Preprocessing of meta-data during/after gathering (Siemens) Uploaded to the docs server * Preprocessing of unstructured data during/after gathering (ATOS) Uploaded to the docs server - very preliminary * Data/Context Pub/Sub Broker (TI) - note: Orange have brought also some asset here and TID wish to incorporate some requirements uploaded to the docs server * Semantic Web annotation tools (ATOS) uploaded to the docs server - very preliminary * Searching/Query-access (???) there is something contributed by Siemens. Will be considered input for the confcall on wednesday. * Multimedia analysis to gather multimedia meta-data (Siemens) uploaded to the docs server 3. Planning of next steps Agreed ACTION-PLAN: 1. Juanjo to consolidate all inputs in a single document to be distributed on monday: - revised template - concrete recomendations on the different sections 2. Editors of the different GE description sections will work from the single document distributed by Juanjo from monday till Thursday EOB: - trying to implement the recomendations - delivering a contribution with only the specific section they have edited (different files per section, not per company) - identify security issues to be address together with Security WP (Juanjo will come with a recommendation on how to provide this input) 3. Partners are welcome to perform an overall review the document distributed by Juanjo and upload a commented version (just comments using the tools for comments on MS Word) by Wednesday EOB. Editors of the different GE sections are then invited to check comments from other partners 4. On next confcall, we should plan on: - how to carry out peer review of existing section in the following week - how to fill rest of sections (particularly, how to generate the section on definitions) ________________________________ 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:983463807 at 16062011-0A44]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From fano.ramparany at orange-ftgroup.com Thu Jun 16 10:27:29 2011 From: fano.ramparany at orange-ftgroup.com (fano.ramparany at orange-ftgroup.com) Date: Thu, 16 Jun 2011 10:27:29 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es><4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: Dear Boris, I was perhaps too extrem with the daily sporadic connection. But they are some lowpower WSN protocols which make it possible to set the sensors radio component idle most of the time, and synchronize their wakening during short period to have all communication occur during that period. If the sensor is able to date its measurements, it might make sense to use this date for event processing (my concern was more on event processing than on context management). Maybe one solution (introduced in an earlier document or discussion) is to distinguish the event object creation time from the event occurence time. The event creation time being the default one and the event occurence time being the one the real event occured. May be concrete use-cases analysis (from UA scenarios) could determine if this is necessary or not. Fano ________________________________ De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] Envoy? : jeudi 16 juin 2011 00:25 ? : RAMPARANY Fano RD-TECH-GRE; jhierro at tid.es Cc : fiware-data at lists.fi-ware.eu Objet : RE: [Fiware-data] Tentative definition of basic concepts: data,context and events Dear Fano, Why do you believe we need another value among the context creation (generation) timestamp. The context is real or near real-time, therefore shall have a timestamp and a validity period or expiration time for this context. I believe in your mentioned use-case with the sensor the data collected during a day and sent in a bunch as a "sporadic packet" are not the context anymore. Only the last, more fresh one, could be taken as a context (if it still valid and reasonable). The rest of that sensor collected data are the context history, so is not the context anymore and could be treated at the "application" level, for example, adding a new context_scope=increasing order. For example, a sensor collecting temperature reading its onboard sensor each 5 minutes: 1. 10dgC 2. 11dgC 3. 12dgC 4. Opening TX window to send the data and sending the data to gateway or broker. 5. Only final value 12dgC is set as context, the rest 2 are recorder into the history as "previous" context from timestamp "a", when previous TX window was opened, or with a Context_scope= and context_type = previous context. Or a gateway or broker could know that that context was collected by the sensor each 5minutes and calculate back the timestamp in the history. 6. Reset the context in the sensor and again: 7. 12dgC 8. 11dgC 9. ... until the next TX window Otherwise I'm afraid we will "encode" generic data representation scheme with too much "application" dependent (particularity of that sensor) and, again, formally speaking, collected previous data, is not the context, but the history of previous, already passed and overwritten, reality. Best Regards, Boris From: fano.ramparany at orange-ftgroup.com [mailto:fano.ramparany at orange-ftgroup.com] Sent: Wednesday, June 15, 2011 5:09 PM To: jhierro at tid.es; Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Tentative definition of basic concepts: data,context and events Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number "5") is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named "data_type" is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more - EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don't need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don't know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the "owner" if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo's mail followed the same thoughts, that I've tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu ) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 4203 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 2558 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Thu Jun 16 10:32:04 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 16 Jun 2011 10:32:04 +0200 Subject: [Fiware-data] Minutes of the confcall 11-05-27 In-Reply-To: References: <4DDF672D.3050304@tid.es> Message-ID: <717919DA-838E-4E80-8575-4057BD215F15@telecomitalia.it> Dear Amon, I'm glad that you've found it in line. This requested by me phone call is very important for me to put in contact for FIWARE right persons working on this technology and be sure from they are sharing this point of view that everything is fine there. I'm sorry that this insertion has taken so long time from our side and I believe that this requested phone call conference will take very short time, especially if we're really aligned. However I cannot evaluate and decide it on myself and need an inclusion of the right people, just after the requested confcall. I really hope it will be fast and "painless". Thank you very much. Best regards, Boris 16/giu/2011, ? 09:55, "Amon, Peter" > ???????(?): Dear Boris, all, the GE "Multimedia Recognition Brokering" is in line with the description of our "Multimedia Analysis" GE, especially the "Detectors" and "Recognizer" part. Some other features like "Feedback" and "Provisioning" would be complementary to the functionality we offer at the moment. Boris/Juanjo, did we already decide about merging the two. For the moment, I see two options: 1. Merge them in D2.2a already. 2. Keep them separate in D2.2a and decide about a merge for D2.2b later. I can offer to volunteer to do the editing. (I am equivalently fine with TI doing the integration. :-) Kind regards Peter ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: Freitag, 10. Juni 2011 12:02 To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Minutes of the confcall 11-05-27 Dear All, I don?t remember if we have already conf-call planned, probably not yet. Sorry my IoT(houghts) in my brain is in a completely and truly MASH configuration with a lot of race conditions and collisions (not saying about faulting)? ;-). As I?ve mentioned during the just terminated conf-call and with regard to the attached email, please find uploaded two new contributions by TI as: - Semantic Annotation Enabler https://forge.fi-ware.eu/docman/view.php/9/136/FI-WARE_High-Level_Description_Semantic_Annotation_Enabler_TI.docx for integration with ATOS; - Multimedia Recognition Brokering https://forge.fi-ware.eu/docman/view.php/9/135/FI-WARE_High-Level_Description_Multimedia_Recognition_Brokering_Enabler_TI.docx for integration with Siemens. For sure if would be much better if the documents by default will be market as private and only then manually activated as public. Best Regards, Boris TI From: Moltchanov Boris Sent: Friday, May 27, 2011 4:16 PM To: 'Juanjo Hierro'; fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Minutes of the confcall 11-05-27 Dear All, TI in Turin will be closed on Thursday and Friday of next week, therefore we will be unable to participate in the next WP6 call. However we?re very interested to be a part of the discussions regarding the following two aspects: - Semantic web annotation tools (with ATOS); - Multimedia analysis (with Siemens); as far as we have active assets in these areas as demonstrated during the kick-off meeting. I will share the documents from the docman with my colleagues, and would like to check with you if you?re planning dedicated calls for these 2 topics in the beginning of the next week (30/05-01/05 incl.). Thank you. 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: Friday, May 27, 2011 10:56 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of the confcall 11-05-27 Dear colleagues, Please find enclosed the minutes I have taken during our weekly confcall. Comments are welcome. I assign a numbering to the different actions of the Action Plan we agreed. Note that action 3 was an action you didn't have time to see written in the shared desktop during the confcall but was indeed discussed. To Telecom Italia: please note that we agreed on the timeslots for celebrating the pending confcalls on Publish/Subscribe Broker as well as on Search/Quering Access (point 1 in the agenda). We beared in mind the timeslots of availability you provided to me in a separate mail. The only one for which we have yet to agree is the one on the Localization GE. Unfortunately, Thales didn't attend the confcall. Best regards, -- Juanjo Attendees: TID: Juanjo IBM: Guy Telecom Italia: ATOS: Tomas and Chema Orange: Fano Ramparany Siemens: Andreas, Thomas, Peter Thales: UPM: Agenda: 1. Review of actions from previous call 2. Status of contributions to deliverable (High-level Description) 3. Planning of next steps 1. Review of actions from previous call + confcall on Publish/Subscribe: Tuesday May 31, 11:30 - 13:00 + confcall Query/Siemens: Wednesday June 1, 09:30 - 11:00 + confcall on Localization GE: still ACTION pending Rest of actions had been done or had to do with contributions (therefore reviewed in next point of the agenda) 2. Status of contributions Action: The editor of each subsection in section 2, have to consider and hightlight whatever aspect related to Security is relevant for the GE description * Off-line Big Data analysis-processing/mining platform (TID) * Big Data stream processing based on map-reduce (TID) These two indeed match to a single GE. I have retitled the second aspect. Description was uploaded to the server ACTION: IBM and Telefonica to hold a confcall on monday May 31 starting 15:30 to reach full alignment on architecture of the processing part and combination/integration of TID's and IBM's assets. * Intelligent Services Plug-ins (TID) Uploaded to the docs server * Real-time stream processing based on CPE (IBM) Uploaded to the docs server * Preprocessing of meta-data during/after gathering (Siemens) Uploaded to the docs server * Preprocessing of unstructured data during/after gathering (ATOS) Uploaded to the docs server - very preliminary * Data/Context Pub/Sub Broker (TI) - note: Orange have brought also some asset here and TID wish to incorporate some requirements uploaded to the docs server * Semantic Web annotation tools (ATOS) uploaded to the docs server - very preliminary * Searching/Query-access (???) there is something contributed by Siemens. Will be considered input for the confcall on wednesday. * Multimedia analysis to gather multimedia meta-data (Siemens) uploaded to the docs server 3. Planning of next steps Agreed ACTION-PLAN: 1. Juanjo to consolidate all inputs in a single document to be distributed on monday: - revised template - concrete recomendations on the different sections 2. Editors of the different GE description sections will work from the single document distributed by Juanjo from monday till Thursday EOB: - trying to implement the recomendations - delivering a contribution with only the specific section they have edited (different files per section, not per company) - identify security issues to be address together with Security WP (Juanjo will come with a recommendation on how to provide this input) 3. Partners are welcome to perform an overall review the document distributed by Juanjo and upload a commented version (just comments using the tools for comments on MS Word) by Wednesday EOB. Editors of the different GE sections are then invited to check comments from other partners 4. On next confcall, we should plan on: - how to carry out peer review of existing section in the following week - how to fill rest of sections (particularly, how to generate the section on definitions) ________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From tomas.parientelobo at atosresearch.eu Thu Jun 16 10:43:44 2011 From: tomas.parientelobo at atosresearch.eu (Tomas PAriente Lobo) Date: Thu, 16 Jun 2011 10:43:44 +0200 Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) In-Reply-To: References: <4DF78709.9000204@tid.es> Message-ID: <9DA3EC560FF1564DB032154AC290954B055810D9@INTMAIL01.es.int.atosorigin.com> Hi Boris, Sorry, but we cannot make it this Friday. Cheers Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: mi?rcoles, 15 de junio de 2011 23:58 To: Juanjo Hierro; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics (second part) Dear Juanjo and Siemens and ATOS (and eventually other) partners, TI is able to participate in order to discuss this topic (subject) on this Friday, starting from 15:00CET and later. Please let me know in time if this is feasible for you. Sorry for lost last communications, indeed the last email (below) received very late to organize an operative action. 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: Tuesday, June 14, 2011 6:07 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) Hi all, We would use the powwownow bridge: PIN: 050662 Dial-in phone numbers in the attachment. The main goal of this confcall is that Telecom Italia explains their contribution in the field. We will also brief those who didn't attend the confcall on monday about results of that meeting. I will check whether I can setup a webex, but I'm not pretty sure I will be able to make it. 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 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. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ From fano.ramparany at orange-ftgroup.com Thu Jun 16 10:44:41 2011 From: fano.ramparany at orange-ftgroup.com (fano.ramparany at orange-ftgroup.com) Date: Thu, 16 Jun 2011 10:44:41 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es><4DF79E77.9030407@tid.es><4DF8B9FF.1000807@tid.es> Message-ID: With respect to the original data model: ________________________________ De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] Envoy? : jeudi 16 juin 2011 00:27 ? : Guy Sharon; RAMPARANY Fano RD-TECH-GRE Cc : fiware-data at lists.fi-ware.eu Objet : RE: [Fiware-data] Tentative definition of basic concepts: data,context and events This is what I also thought - both schemas ContextML and RDF are triplets but one is based on a straightforward context data encoding: object-context_name-value, while other is related to semantic and ontology. I'm not sure about the final decision but the model shall be evaluated also for RDF. Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Wednesday, June 15, 2011 7:45 PM To: fano.ramparany at orange-ftgroup.com Cc: Moltchanov Boris; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Fano - I think its also important to see if the RDF can be mapped to the model we discuss (the other way around) I think its symmetric in probably all cases of formats - but something to consider 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 From: To: , Cc: fiware-data at lists.fi-ware.eu Date: 15/06/2011 19:20 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu ] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number "5") is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named "data_type" is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more - EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don't need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don't know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the "owner" if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo's mail followed the same thoughts, that I've tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu ) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ 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. 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: image001.gif Type: image/gif Size: 2558 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4203 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From p.amon at siemens.com Thu Jun 16 10:52:25 2011 From: p.amon at siemens.com (Amon, Peter) Date: Thu, 16 Jun 2011 10:52:25 +0200 Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) In-Reply-To: <9DA3EC560FF1564DB032154AC290954B055810D9@INTMAIL01.es.int.atosorigin.com> References: <4DF78709.9000204@tid.es> <9DA3EC560FF1564DB032154AC290954B055810D9@INTMAIL01.es.int.atosorigin.com> Message-ID: Hi Boris, hi Tom?s, Friday is also not perfect for me. I would be available Mon/Tue/Wed next week (except some appointments at lunch time). (This concerns the confcall on "Multimedia Recognition" / "Multimedia Analysis".) Kind regards Peter > -----Original Message----- > From: fiware-data-bounces at lists.fi-ware.eu > [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of > Tomas PAriente Lobo > Sent: Donnerstag, 16. Juni 2011 10:44 > To: Moltchanov Boris; Juanjo Hierro; fiware-data at lists.fi-ware.eu > Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics > (second part) > > Hi Boris, > > Sorry, but we cannot make it this Friday. > > Cheers > > Tom?s > > Tom?s Pariente Lobo > Knowledge Lab > Atos Research and Innovation > C/Albarrac?n 25, 28037 Madrid (SPAIN) > Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 > http://www.atosresearch.eu > > > > -----Original Message----- > From: fiware-data-bounces at lists.fi-ware.eu > [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of > Moltchanov Boris > Sent: mi?rcoles, 15 de junio de 2011 23:58 > To: Juanjo Hierro; fiware-data at lists.fi-ware.eu > Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics > (second part) > > Dear Juanjo and Siemens and ATOS (and eventually other) partners, > > TI is able to participate in order to discuss this topic > (subject) on this Friday, starting from 15:00CET and later. > > Please let me know in time if this is feasible for you. > > Sorry for lost last communications, indeed the last email > (below) received very late to organize an operative action. > > 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: Tuesday, June 14, 2011 6:07 PM > To: fiware-data at lists.fi-ware.eu > Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) > > Hi all, > > We would use the powwownow bridge: > > PIN: 050662 > > Dial-in phone numbers in the attachment. > > The main goal of this confcall is that Telecom Italia > explains their > contribution in the field. We will also brief those who > didn't attend > the confcall on monday about results of that meeting. > > I will check whether I can setup a webex, but I'm not > pretty sure I will be able to make it. > > 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 > > 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. > > _______________________________________________ > Fiware-data mailing list > Fiware-data at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-data > ------------------------------------------------------------------ > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately > and destroy it. > As its integrity cannot be secured on the Internet, the Atos Origin > group liability cannot be triggered for the message content. Although > the sender endeavours to maintain a computer virus-free network, > the sender does not warrant that this transmission is virus-free and > will not be liable for any damages resulting from any virus > transmitted. > > Este mensaje y los ficheros adjuntos pueden contener > informacion confidencial > destinada solamente a la(s) persona(s) mencionadas anteriormente > pueden estar protegidos por secreto profesional. > Si usted recibe este correo electronico por error, gracias > por informar > inmediatamente al remitente y destruir el mensaje. > Al no estar asegurada la integridad de este mensaje sobre la > red, Atos Origin > no se hace responsable por su contenido. Su contenido no > constituye ningun > compromiso para el grupo Atos Origin, salvo ratificacion > escrita por ambas partes. > Aunque se esfuerza al maximo por mantener su red libre de > virus, el emisor > no puede garantizar nada al respecto y no sera responsable de > cualesquiera > danos que puedan resultar de una transmision de virus. > ------------------------------------------------------------------ > > _______________________________________________ > Fiware-data mailing list > Fiware-data at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-data > From boris.moltchanov at telecomitalia.it Thu Jun 16 10:56:38 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 16 Jun 2011 10:56:38 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> <4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: <969EEB54-6BAC-4A7F-8E61-944194FAECDD@telecomitalia.it> Dear Fano, I got perfectly you use-case from the previous email. I would ensure you that I have some certain inside understanding of WSN tech and apps;). I'm not sure if we really need to include another timestamps, even partials, within the data structure we are defining. You're right saying that the event occurrence is not the context unless this is sent immediately therefore become a context generation by the event occurrence. Moreover we are going to handle the event streams in a real-time. Then, for a WSN device communications stand-by-wake-up-send/receive-stand-by-again we may threat the event time generation on a higher data structure true layer, saying that once events (more then one collected within radio-silent WSN device) are sent to the gateway or application this is the context of that decide and inside we may have more events with probably their respective timestamps. Then, if an application requires them: - as pure events, even if stored and not real-time we have the structure right data structure for that (all of them stored). If device doesn't have an internal clock it should be higher level application or gateway handle the conversion issue; - as a context, we have a right data structure also for this, and only the last one, fresher and if still valid data will be taken into consideration; - a mix of two or conversions, it should be handled at application/service layer outside of enabler, or, you said, if we will have STRONG and CLEAR requirement from our FIWARE IoT or UA FI-Projects, we could embed it into our FI-FARE WP6 enabler. Let wait and see what others think about this matter. Best Regards, Boris 16/giu/2011, ? 10:28, "fano.ramparany at orange.com" > ???????(?): Dear Boris, I was perhaps too extrem with the daily sporadic connection. But they are some lowpower WSN protocols which make it possible to set the sensors radio component idle most of the time, and synchronize their wakening during short period to have all communication occur during that period. If the sensor is able to date its measurements, it might make sense to use this date for event processing (my concern was more on event processing than on context management). Maybe one solution (introduced in an earlier document or discussion) is to distinguish the event object creation time from the event occurence time. The event creation time being the default one and the event occurence time being the one the real event occured. May be concrete use-cases analysis (from UA scenarios) could determine if this is necessary or not. Fano ________________________________ De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] Envoy? : jeudi 16 juin 2011 00:25 ? : RAMPARANY Fano RD-TECH-GRE; jhierro at tid.es Cc : fiware-data at lists.fi-ware.eu Objet : RE: [Fiware-data] Tentative definition of basic concepts: data,context and events Dear Fano, Why do you believe we need another value among the context creation (generation) timestamp. The context is real or near real-time, therefore shall have a timestamp and a validity period or expiration time for this context. I believe in your mentioned use-case with the sensor the data collected during a day and sent in a bunch as a ?sporadic packet? are not the context anymore. Only the last, more fresh one, could be taken as a context (if it still valid and reasonable). The rest of that sensor collected data are the context history, so is not the context anymore and could be treated at the ?application? level, for example, adding a new context_scope=increasing order. For example, a sensor collecting temperature reading its onboard sensor each 5 minutes: 1. 10dgC 2. 11dgC 3. 12dgC 4. Opening TX window to send the data and sending the data to gateway or broker. 5. Only final value 12dgC is set as context, the rest 2 are recorder into the history as ?previous? context from timestamp ?a?, when previous TX window was opened, or with a Context_scope= and context_type = previous context. Or a gateway or broker could know that that context was collected by the sensor each 5minutes and calculate back the timestamp in the history. 6. Reset the context in the sensor and again: 7. 12dgC 8. 11dgC 9. ? until the next TX window Otherwise I?m afraid we will ?encode? generic data representation scheme with too much ?application? dependent (particularity of that sensor) and, again, formally speaking, collected previous data, is not the context, but the history of previous, already passed and overwritten, reality. Best Regards, Boris From: fano.ramparany at orange-ftgroup.com [mailto:fano.ramparany at orange-ftgroup.com] Sent: Wednesday, June 15, 2011 5:09 PM To: jhierro at tid.es; Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Tentative definition of basic concepts: data,context and events Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number ?5?) is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named ?data_type? is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more ? EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don?t need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don?t know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the ?owner? if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo?s mail followed the same thoughts, that I?ve tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris <boris.moltchanov at telecomitalia.it> To: Juanjo Hierro <jhierro at tid.es>, "fiware-data at lists.fi-ware.eu" <fiware-data at lists.fi-ware.eu> Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From fano.ramparany at orange-ftgroup.com Thu Jun 16 11:26:14 2011 From: fano.ramparany at orange-ftgroup.com (fano.ramparany at orange-ftgroup.com) Date: Thu, 16 Jun 2011 11:26:14 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es><4DF79E77.9030407@tid.es><4DF8B9FF.1000807@tid.es> Message-ID: With respect to the original data schema, and with a quick (and dirty) thinking: the above could be transformed into the following RDF model triplets: EntityId rdf:type Data_element.type, EntityId Data_element_attributes_i.Name Data_element_attributes_i.Value, (i from 1 to n) - if Data_element_attributes.Value is not a litteral (litteral are instances of basic types such as integer, float, double, string,...) Data_element_attributes_i.Value Meta-data_k.Name Meta-data_k.Value, (k from 1 to n') - if Data_element_attributes_i.Value is a litteral value and Meta-data is attached to Data_element_attribute_i, an intermediary node should be created with a generated URI say URIgen_i which will represent the Data_element_attribute. This node will be the subject of the the triplet representing the Meta_data. URIgen_i Meta-data_k.Name Meta-data_k.Value, With the ongoing discussion about how EntityId should be used, this might require some adjustment. For the reverse mapping (from RDF to the data schema). I think this is more complicated and requires more thinking. The main issues I foresee revolves around how to express triplets which capture the ontologies? ________________________________ De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] Envoy? : jeudi 16 juin 2011 00:27 ? : Guy Sharon; RAMPARANY Fano RD-TECH-GRE Cc : fiware-data at lists.fi-ware.eu Objet : RE: [Fiware-data] Tentative definition of basic concepts: data,context and events This is what I also thought - both schemas ContextML and RDF are triplets but one is based on a straightforward context data encoding: object-context_name-value, while other is related to semantic and ontology. I'm not sure about the final decision but the model shall be evaluated also for RDF. Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Wednesday, June 15, 2011 7:45 PM To: fano.ramparany at orange-ftgroup.com Cc: Moltchanov Boris; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Fano - I think its also important to see if the RDF can be mapped to the model we discuss (the other way around) I think its symmetric in probably all cases of formats - but something to consider 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 From: To: , Cc: fiware-data at lists.fi-ware.eu Date: 15/06/2011 19:20 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu ] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number "5") is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named "data_type" is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more - EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don't need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don't know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the "owner" if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo's mail followed the same thoughts, that I've tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I've said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must - explicit object or subject (entity) making it the context. I hope I've succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu ) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ 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. 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: image003.gif Type: image/gif Size: 7137 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 2558 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4203 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Thu Jun 16 11:36:06 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Jun 2011 11:36:06 +0200 Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) In-Reply-To: References: <4DF78709.9000204@tid.es> <9DA3EC560FF1564DB032154AC290954B055810D9@INTMAIL01.es.int.atosorigin.com> Message-ID: <4DF9CE86.3020307@tid.es> Boris, May you try to setup a doodle on this ? Monday will be hard for me if earlier that 16:30. Tuesday (whole day), wednesday morning (until 13:00) or wednesday evening (after 17:00) would also work for me. Best regards, -- Juanjo On 16/06/11 10:52, Amon, Peter wrote: > Hi Boris, hi Tom?s, > > Friday is also not perfect for me. I would be available Mon/Tue/Wed next week (except some appointments at lunch time). > > (This concerns the confcall on "Multimedia Recognition" / "Multimedia Analysis".) > > Kind regards > Peter > > > >> -----Original Message----- >> From: fiware-data-bounces at lists.fi-ware.eu >> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of >> Tomas PAriente Lobo >> Sent: Donnerstag, 16. Juni 2011 10:44 >> To: Moltchanov Boris; Juanjo Hierro; fiware-data at lists.fi-ware.eu >> Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics >> (second part) >> >> Hi Boris, >> >> Sorry, but we cannot make it this Friday. >> >> Cheers >> >> Tom?s >> >> Tom?s Pariente Lobo >> Knowledge Lab >> Atos Research and Innovation >> C/Albarrac?n 25, 28037 Madrid (SPAIN) >> Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 >> http://www.atosresearch.eu >> >> >> >> -----Original Message----- >> From: fiware-data-bounces at lists.fi-ware.eu >> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of >> Moltchanov Boris >> Sent: mi?rcoles, 15 de junio de 2011 23:58 >> To: Juanjo Hierro; fiware-data at lists.fi-ware.eu >> Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics >> (second part) >> >> Dear Juanjo and Siemens and ATOS (and eventually other) partners, >> >> TI is able to participate in order to discuss this topic >> (subject) on this Friday, starting from 15:00CET and later. >> >> Please let me know in time if this is feasible for you. >> >> Sorry for lost last communications, indeed the last email >> (below) received very late to organize an operative action. >> >> 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: Tuesday, June 14, 2011 6:07 PM >> To: fiware-data at lists.fi-ware.eu >> Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) >> >> Hi all, >> >> We would use the powwownow bridge: >> >> PIN: 050662 >> >> Dial-in phone numbers in the attachment. >> >> The main goal of this confcall is that Telecom Italia >> explains their >> contribution in the field. We will also brief those who >> didn't attend >> the confcall on monday about results of that meeting. >> >> I will check whether I can setup a webex, but I'm not >> pretty sure I will be able to make it. >> >> 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 >> >> 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. >> >> _______________________________________________ >> Fiware-data mailing list >> Fiware-data at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-data >> ------------------------------------------------------------------ >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive >> this e-mail in error, please notify the sender immediately >> and destroy it. >> As its integrity cannot be secured on the Internet, the Atos Origin >> group liability cannot be triggered for the message content. Although >> the sender endeavours to maintain a computer virus-free network, >> the sender does not warrant that this transmission is virus-free and >> will not be liable for any damages resulting from any virus >> transmitted. >> >> Este mensaje y los ficheros adjuntos pueden contener >> informacion confidencial >> destinada solamente a la(s) persona(s) mencionadas anteriormente >> pueden estar protegidos por secreto profesional. >> Si usted recibe este correo electronico por error, gracias >> por informar >> inmediatamente al remitente y destruir el mensaje. >> Al no estar asegurada la integridad de este mensaje sobre la >> red, Atos Origin >> no se hace responsable por su contenido. Su contenido no >> constituye ningun >> compromiso para el grupo Atos Origin, salvo ratificacion >> escrita por ambas partes. >> Aunque se esfuerza al maximo por mantener su red libre de >> virus, el emisor >> no puede garantizar nada al respecto y no sera responsable de >> cualesquiera >> danos que puedan resultar de una transmision de virus. >> ------------------------------------------------------------------ >> >> _______________________________________________ >> 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 -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Thu Jun 16 12:05:31 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 16 Jun 2011 12:05:31 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: References: <4DF73EAD.2090001@tid.es> <4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> Message-ID: <043F497C-F675-4725-B38A-2A31841F4E97@telecomitalia.it> "The main issues I foresee revolves around how to express triplets which capture the ontologies?" this exactly was (and is) my doubt about usage of RDF for the context. The context is very bad served with the ontology (more events or parameters then semantic meaning), therefore It is not considered (not within) the OMA specs and I could only wander whether it could be represented from RDF to our (Oma based) specs without loosing that onthology meaning. Fano,ay you eventually perform an excersize based on you experience? Best regards, Boris 16/giu/2011, ? 11:26, "fano.ramparany at orange-ftgroup.com" <fano.ramparany at orange-ftgroup.com> ???????(?): With respect to the original data schema, and with a quick (and dirty) thinking: the above could be transformed into the following RDF model triplets: EntityId rdf:type Data_element.type, EntityId Data_element_attributes_i.Name Data_element_attributes_i.Value, (i from 1 to n) - if Data_element_attributes.Value is not a litteral (litteral are instances of basic types such as integer, float, double, string,...) Data_element_attributes_i.Value Meta-data_k.Name Meta-data_k.Value, (k from 1 to n') - if Data_element_attributes_i.Value is a litteral value and Meta-data is attached to Data_element_attribute_i, an intermediary node should be created with a generated URI say URIgen_i which will represent the Data_element_attribute. This node will be the subject of the the triplet representing the Meta_data. URIgen_i Meta-data_k.Name Meta-data_k.Value, With the ongoing discussion about how EntityId should be used, this might require some adjustment. For the reverse mapping (from RDF to the data schema). I think this is more complicated and requires more thinking. The main issues I foresee revolves around how to express triplets which capture the ontologies? ________________________________ De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] Envoy? : jeudi 16 juin 2011 00:27 ? : Guy Sharon; RAMPARANY Fano RD-TECH-GRE Cc : fiware-data at lists.fi-ware.eu Objet : RE: [Fiware-data] Tentative definition of basic concepts: data,context and events This is what I also thought ? both schemas ContextML and RDF are triplets but one is based on a straightforward context data encoding: object-context_name-value, while other is related to semantic and ontology. I?m not sure about the final decision but the model shall be evaluated also for RDF. Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Wednesday, June 15, 2011 7:45 PM To: fano.ramparany at orange-ftgroup.com Cc: Moltchanov Boris; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Fano - I think its also important to see if the RDF can be mapped to the model we discuss (the other way around) I think its symmetric in probably all cases of formats - but something to consider 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 From: <fano.ramparany at orange-ftgroup.com> To: <jhierro at tid.es>, <boris.moltchanov at telecomitalia.it> Cc: fiware-data at lists.fi-ware.eu Date: 15/06/2011 19:20 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number ?5?) is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named ?data_type? is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more ? EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don?t need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don?t know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the ?owner? if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo?s mail followed the same thoughts, that I?ve tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ 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. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From tomas.parientelobo at atosresearch.eu Thu Jun 16 12:07:14 2011 From: tomas.parientelobo at atosresearch.eu (Tomas PAriente Lobo) Date: Thu, 16 Jun 2011 12:07:14 +0200 Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) In-Reply-To: <4DF9CE86.3020307@tid.es> References: <4DF78709.9000204@tid.es> <9DA3EC560FF1564DB032154AC290954B055810D9@INTMAIL01.es.int.atosorigin.com> <4DF9CE86.3020307@tid.es> Message-ID: <9DA3EC560FF1564DB032154AC290954B055811B0@INTMAIL01.es.int.atosorigin.com> Hi, In the slots Juanjo provided, I'm free on Tuesday before 10AM and from 12 to 15:30 and o on Wednesday morning as well. Best regards Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: jueves, 16 de junio de 2011 11:36 To: Amon, Peter Cc: Tomas PAriente Lobo; Moltchanov Boris; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics (second part) Boris, May you try to setup a doodle on this ? Monday will be hard for me if earlier that 16:30. Tuesday (whole day), wednesday morning (until 13:00) or wednesday evening (after 17:00) would also work for me. Best regards, -- Juanjo On 16/06/11 10:52, Amon, Peter wrote: > Hi Boris, hi Tom?s, > > Friday is also not perfect for me. I would be available Mon/Tue/Wed next week (except some appointments at lunch time). > > (This concerns the confcall on "Multimedia Recognition" / "Multimedia > Analysis".) > > Kind regards > Peter > > > >> -----Original Message----- >> From: fiware-data-bounces at lists.fi-ware.eu >> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Tomas >> PAriente Lobo >> Sent: Donnerstag, 16. Juni 2011 10:44 >> To: Moltchanov Boris; Juanjo Hierro; fiware-data at lists.fi-ware.eu >> Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics (second >> part) >> >> Hi Boris, >> >> Sorry, but we cannot make it this Friday. >> >> Cheers >> >> Tom?s >> >> Tom?s Pariente Lobo >> Knowledge Lab >> Atos Research and Innovation >> C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. >> (+34) 91 754 3252 >> http://www.atosresearch.eu >> >> >> >> -----Original Message----- >> From: fiware-data-bounces at lists.fi-ware.eu >> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov >> Boris >> Sent: mi?rcoles, 15 de junio de 2011 23:58 >> To: Juanjo Hierro; fiware-data at lists.fi-ware.eu >> Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics (second >> part) >> >> Dear Juanjo and Siemens and ATOS (and eventually other) partners, >> >> TI is able to participate in order to discuss this topic >> (subject) on this Friday, starting from 15:00CET and later. >> >> Please let me know in time if this is feasible for you. >> >> Sorry for lost last communications, indeed the last email >> (below) received very late to organize an operative action. >> >> 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: Tuesday, June 14, 2011 6:07 PM >> To: fiware-data at lists.fi-ware.eu >> Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) >> >> Hi all, >> >> We would use the powwownow bridge: >> >> PIN: 050662 >> >> Dial-in phone numbers in the attachment. >> >> The main goal of this confcall is that Telecom Italia explains >> their >> contribution in the field. We will also brief those who >> didn't attend >> the confcall on monday about results of that meeting. >> >> I will check whether I can setup a webex, but I'm not pretty >> sure I will be able to make it. >> >> 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 >> >> 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. >> >> _______________________________________________ >> Fiware-data mailing list >> Fiware-data at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-data >> ------------------------------------------------------------------ >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive >> this e-mail in error, please notify the sender immediately and >> destroy it. >> As its integrity cannot be secured on the Internet, the Atos Origin >> group liability cannot be triggered for the message content. Although >> the sender endeavours to maintain a computer virus-free network, the >> sender does not warrant that this transmission is virus-free and will >> not be liable for any damages resulting from any virus transmitted. >> >> Este mensaje y los ficheros adjuntos pueden contener informacion >> confidencial destinada solamente a la(s) persona(s) mencionadas >> anteriormente pueden estar protegidos por secreto profesional. >> Si usted recibe este correo electronico por error, gracias por >> informar inmediatamente al remitente y destruir el mensaje. >> Al no estar asegurada la integridad de este mensaje sobre la red, >> Atos Origin no se hace responsable por su contenido. Su contenido no >> constituye ningun compromiso para el grupo Atos Origin, salvo >> ratificacion escrita por ambas partes. >> Aunque se esfuerza al maximo por mantener su red libre de virus, el >> emisor no puede garantizar nada al respecto y no sera responsable de >> cualesquiera danos que puedan resultar de una transmision de virus. >> ------------------------------------------------------------------ >> >> _______________________________________________ >> 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 ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ From jhierro at tid.es Thu Jun 16 12:59:43 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Jun 2011 12:59:43 +0200 Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events In-Reply-To: <043F497C-F675-4725-B38A-2A31841F4E97@telecomitalia.it> References: <4DF73EAD.2090001@tid.es> <4DF79E77.9030407@tid.es> <4DF8B9FF.1000807@tid.es> <043F497C-F675-4725-B38A-2A31841F4E97@telecomitalia.it> Message-ID: <4DF9E21F.7010304@tid.es> Folks, I will produce a new version of the notes I sent where I believe I will be able to consolidated much of the discussion so far. Therefore, we can just concentrate in minor details for which a final conclusion seems to be not reached. I would kindly ask all you to stop discussion for the time being and wait until we can resume it from a consolidated base. Best regards, -- Juanjo On 16/06/11 12:05, Moltchanov Boris wrote: "The main issues I foresee revolves around how to express triplets which capture the ontologies?" this exactly was (and is) my doubt about usage of RDF for the context. The context is very bad served with the ontology (more events or parameters then semantic meaning), therefore It is not considered (not within) the OMA specs and I could only wander whether it could be represented from RDF to our (Oma based) specs without loosing that onthology meaning. Fano,ay you eventually perform an excersize based on you experience? Best regards, Boris 16/giu/2011, ? 11:26, "fano.ramparany at orange-ftgroup.com" > ???????(?): With respect to the original data schema, and with a quick (and dirty) thinking: the above could be transformed into the following RDF model triplets: EntityId rdf:type Data_element.type, EntityId Data_element_attributes_i.Name Data_element_attributes_i.Value, (i from 1 to n) - if Data_element_attributes.Value is not a litteral (litteral are instances of basic types such as integer, float, double, string,...) Data_element_attributes_i.Value Meta-data_k.Name Meta-data_k.Value, (k from 1 to n') - if Data_element_attributes_i.Value is a litteral value and Meta-data is attached to Data_element_attribute_i, an intermediary node should be created with a generated URI say URIgen_i which will represent the Data_element_attribute. This node will be the subject of the the triplet representing the Meta_data. URIgen_i Meta-data_k.Name Meta-data_k.Value, With the ongoing discussion about how EntityId should be used, this might require some adjustment. For the reverse mapping (from RDF to the data schema). I think this is more complicated and requires more thinking. The main issues I foresee revolves around how to express triplets which capture the ontologies? ________________________________ De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] Envoy? : jeudi 16 juin 2011 00:27 ? : Guy Sharon; RAMPARANY Fano RD-TECH-GRE Cc : fiware-data at lists.fi-ware.eu Objet : RE: [Fiware-data] Tentative definition of basic concepts: data,context and events This is what I also thought ? both schemas ContextML and RDF are triplets but one is based on a straightforward context data encoding: object-context_name-value, while other is related to semantic and ontology. I?m not sure about the final decision but the model shall be evaluated also for RDF. Best Regards, Boris From: Guy Sharon [mailto:GUYSH at il.ibm.com] Sent: Wednesday, June 15, 2011 7:45 PM To: fano.ramparany at orange-ftgroup.com Cc: Moltchanov Boris; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Fano - I think its also important to see if the RDF can be mapped to the model we discuss (the other way around) I think its symmetric in probably all cases of formats - but something to consider 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 From: > To: >, > Cc: fiware-data at lists.fi-ware.eu Date: 15/06/2011 19:20 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear all, I agree with the first part of your message which state the consensual view. Here is my feedback on the second part where Juanjo request our opinion: - I agree with the process of assigning the time of creation of the event to the timestamp value by default, but making it possible to set the timestamp with another value. Use case: a sensor with sporadic connection (e.g. daily connection) but which store locally its measurement with the date of measure. - I second the approach making it possible to choose your preferred representation language (XML, RDF,...) for all GEs which will process data (data, event, context). As I'm personnally a supporter of RDF, I've checked that the data model discussed so far can be easily mapped onto RDF. Regards, Fano ________________________________ De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 15 juin 2011 15:56 ? : Moltchanov Boris Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Tentative definition of basic concepts: data,context and events ... A point about which we have to agree is that of the right interpretation of the timestamp for event processing. The way I see it is as follows: * Data Elements (or Context Elements since they would be a special case of Data Elements) will be treated as events at the time at which they are pushed into any of the Event-oriented Generic Enablers we will provide: the CEP GE and the Publish/Subscribe Broker GE. So, in other words, event objects become created and are kind of a internal structure used for both GEs to wrap the Data Elements they receive and be able to perform part of their processing. * The event object created when a Data Element arrives at the CEP GE or the Publish/Subscribe Broker GE, includes of course the Data Element itself but additional info is added (like if it were a kind of a header). One info that is added is the time at which the event "is created". By default, this time would match the time at which the Data Element arrived the GE (i.e., the time at which the event object that wraps it was created). However, the programmer would be able to setup rules that would allow him/her to establish that the value of a given attribute is used instead. * The internal structure used for represent event objects in memory would be hidden to the application programmer but he/she would know that a timestamp would be linked to the Data Element and, therefore, he may use that info in its formulas for conditions in the programming of the CEP GE or in subscriptions to the Publish/Subscribe Broker GE. A crucial point not raised in this thread of discussion but introduced in the document I send is that the description of Data Elements and Context Elements doesn't prescribe a particular format for transfering or storing them. There might be multiple XML document formats that could be defined for sending Data Elements or Context Elements in messages. In addition, a given Data Element or Context Element can be stored in different ways (e.g., as RDF triplets in an RDF repository, as entries in MongoDB, as entries in a RDBMS, etc.) The advantages for the model I have described so far is: * We comply with OMA specs * We can treat as events both Data Elements and Context Elements. Data Elements and Context Elements can be processed by the CEP GE and can be distributed by the Publish/Subscribe GE * It's generic. We do not mandate a particular format to represent Data Elements and Context Elements Hope that we can agree in all the above and close a definition for this basic concepts. Best regards, -- Juanjo On 15/06/11 13:17, Moltchanov Boris wrote: Hi Juanjo, Let me first answer the simpler email (simpler questions without complexity or ambiguity): I think both a) and b) interpretations are correct, with mentioning that: 1. EntityID for the context is not the data key reference number (just like in a DB in case a) in order to retrieve a data and make the references to that ID from other DBs or tables), but this is ID of an Entity to whom those data (context) belong to, so a person, a device (owner or the data = Entity and this owner has its own EntityID as in case b)). 2. An key reference EntityID (as in DB, case a)) might be built for the context data taking EntityID of the context and adding time-stamp, in that case you obtain Data ID for referencing as a unique key. I think the same could be done for the event, but not sure, Guy might correct me. Again, as in my email to Guy, I am speaking about the data structure, that will have the data and the meta-data. 1. the Data VALUE (as part of the structure, thus just like a number ?5?) is a must for the DATA; we may add Data ID as another must to work over Data in DBs; so we have Data_Value<->Data_ID; 2. the Data meta-data named ?data_type? is a must for both the events (data_type=event_name) and for the context (data _type=context_scope). Here we obtain EVENT and CONTEXT increasing of complexity of DATA by the same structural element data_type. And in both cases EVENT and CONTEXT we need a time-stamp, therefove we have still the same data-structure. So we have: Data_Value<->Data_ID && Data_Type<->context_scope||event_name && timestamp; 3. but the structure above is not sufficient for the context, we need one more ? EntityID (data owner or object to whom the data are referred to). Therefore we have Data_Value<->Data_ID && Data_Type=context_scope||event_name && timestamp && EntityID<->data_owner/actor/subject/object then vice versa: event element may have more data elements inside; context element may have more data and events inside; in the 3. case we don?t need Data_ID therefore we may omit is saying that it could be built based on EntityID+timestamp+context_name. I think also in event structure something similar may be done. I mean that DataID is not the EntityID for the context therefore e.g. in context we may loose DataID as far as that is not needed, and the data may be univocally identified by the triplet (EntityID, context_scope, timestamp). Probably in order to avoid mixing and merging for the moment something that we are not let sure if it will be useful, we may just say that everything is a data and it has meta-data and then go deeper defining the structure model for the events and for the context putting mandatory and optional, similar as OMA defines. What I was trying to explain in my previous emails is: the Data Value is must everywhere in data, events and context, otherwise the data become metadata only, therefore semantic or ontology, which is knowledge but I don?t know if to call it then data or events, for sure not context. And if the Data Value is provided with event_name and timestamp it become and Event, if you add there EntitID (not DataID, but the ?owner? if that data) it become Context. That was the matter of my previous communications. TI follows OMA context definition however some Mandatory structure elements defined there are omitted for sake of simplicity and because there are implicity, or because we are missing them, such as quality of context data meta-data. Therefore those, as quality of context meta-data, shall be marked as optional in FI-WARE. What do you think? As far as another Juanjo?s mail followed the same thoughts, that I?ve tried to clarify know I will wait for your opinion before answering that email, and avoid useless if not harmful confusion. 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, June 14, 2011 7:47 PM To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Hi, This is a crucial point with respect to which, a clarification from Boris would help. In the OMA specification of the Context Management (Publish/Subscribe) Service, Context Elements have a field called "EntityId". There are two interpretations of what this "EntityId" means. Depending on which one is the correct one, we need to adjust our definitions: a) "EntityId" is just a "key" or "identifier" of the Context Element (for instance, used as key in a RDBMS). This was the interpretation I give in my document, so I Just explained that a Data Element had an "EntityId" associated to it. b) "EntityId" is an id of an entity the Context Element provides some information about. So, for example, "EntityId" in a Context Element could be "MyVillage" and then, there could be several ContextElements describing aspects about "Prado Museum". For example, I may have a Context Element describing Location (with attributes latitude and altitude) while another Context Element may have Temperature (with attributes temperature, and time at which the temperature was measured). If a) is the right interpretation, Context Elements would just be a special case of Data Element and, therefore, they would have an "EntityId" associated to them. As simple as that. If b) is the right interpretation, then I believe that "EntityId" and "EntityType" would not make sense in Data Elements. I still believe that we should link an "Id" and "DataType" to Data Elements. Then Context Elements would "extend" Data Elements so that they also add "EntityId" and "EntityType". What is rather clear to me is that events are just things that wrap data/context and link a time to them. In this respect, it makes sense to talk about data events or context events if we want to precise when an event is linked to a data element or a context element. Feedback from Boris about what is the right interpretation (a) or b) above) would allow us to perform the next iteration in this definition. Best regards, -- Juanjo On 14/06/11 18:38, Guy Sharon wrote: Boris - wouldn't it be also true to be able to obtain context by associating data with entity? i.e. No need to go through an event to get to context? So something like this 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 14/06/2011 18:51 Subject: Re: [Fiware-data] Tentative definition of basic concepts: data, context and events Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Juajo, I would put the event definition before the Context. As I?ve said during the last conf-call, the data (including everything related to numbers and values) is a most generic case where only number (value) is the must. Everything else (meta-data, types, etc.) is optional. Then we would have an event as data + time when happened (the object referred by the data is implicit therefore could be omitted). Then adding the subject or object (referenced entity) we obtain the context, which inherit legacy properties of both the data (value) and event (when happened) as must and adding another must ? explicit object or subject (entity) making it the context. I hope I?ve succeeded to explain my point of view. Thank you. 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, June 14, 2011 12:58 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tentative definition of basic concepts: data, context and events Dear all, As you know, one of the action points from our last confcall had to do with providing a tentative definition of basic concepts in our chapter like data, context and event. Please find the document I have produced on the matter at: https://forge.fi-ware.eu/docman/view.php/9/141/Notes+and+Thoughts+on+definition+of+data-context-event.doc Just in case you believe it would be more easy to run a discussion via email following this email, I have attached the text of this document below. Hope you find it useful. Your feedback is welcome. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Any data element has an entity in any FI-WARE Instance and, as such, it has an associated EntityId which universally and unequivocally indentifies the data element among the whole set of existing data elements. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format. They can be transferred as an XML document or in some sort of efficient binary representation and then be stored in a Relational Database or as entries in a noSQL data base like MongoDB. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element is just a particular case of data element. However, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are defined as a data element to which a number of standard event object properties (similar to a header) are associated. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object was created. The data element and the standard properties linked to an event are used to describe, as mentioned above, something that has happened or is contemplated as having happened in a given domain. A context event The relationship (or difference) of the terms data and event is continuously debated. One summary of the philosophical and technical aspects of such debates is included in the background section of [Grove 06] with several references to the different opinions and definitions. For the purpose of FI-WARE and in specifically of the Context and Data Management Generic Enablers, we need to distinguish between the semantic level and the technical level of such a relationship that FI-WARE wishes to adopt, communicate, through its interfaces, and implement. Semantically speaking, the term data subsumes the term event meaning that some data can be semantically interpreted as events. From a technical perspective data is the way information is communicated in FI-WARE and it needs to be explicitly or implicitly identified as an event object and vice versa for processing the data as event. ________________________________ 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 ________________________________ 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. ________________________________ 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. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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:part1.09020703.06000803 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Thu Jun 16 20:29:10 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Jun 2011 20:29:10 +0200 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Message-ID: <4DFA4B76.8010602@tid.es> Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. [cid:part1.03080703.00060200 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. [cid:part2.08010600.07020100 at tid.es] Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. ________________________________ 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: clip_image002.gif Type: image/gif Size: 7104 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: clip_image004.gif Type: image/gif Size: 8023 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Revised Notes and Thoughts on definition of data-context-event.doc Type: application/msword Size: 240128 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Fri Jun 17 02:18:18 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 17 Jun 2011 02:18:18 +0200 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events In-Reply-To: <4DFA4B76.8010602@tid.es> References: <4DFA4B76.8010602@tid.es> Message-ID: Dear Juanjo and rest of the Folk, Please find attached the document, which might be already included as a part of our FI-WARE spec. I, personally, agree with our thoughts that Juanjo has expressed and have just tailored the below text to a specification style, excluding eventual verbosity (and somewhere correcting English, however I don't pretend here). If you agree we may already use it as a part of official specification. I still need to improve the reference high-level pub/sub spec, not difficult job, however not sure if will have time. Let speak tomorrow morning. 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: Thursday, June 16, 2011 8:29 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. [cid:image001.gif at 01CC2C94.C2470D00] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. [cid:image002.gif at 01CC2C94.C2470D00] Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. ________________________________ 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: image001.gif Type: image/gif Size: 7104 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 8023 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Revised Notes and Thoughts on definition of data-context-event Boris.doc Type: application/msword Size: 248832 bytes Desc: Revised Notes and Thoughts on definition of data-context-event Boris.doc URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Fri Jun 17 03:31:15 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 17 Jun 2011 03:31:15 +0200 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events References: <4DFA4B76.8010602@tid.es> Message-ID: Dear All, please find here https://forge.fi-ware.eu/docman/view.php/9/158/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.1+17-06-01-2.doc the file with reviewed pub/sub high-level description. It is private. I'm safe for your mail boxes not attaching to this email, the size is more than 2MB. Best Regards, Boris From: Moltchanov Boris Sent: Friday, June 17, 2011 2:18 AM To: 'Juanjo Hierro'; fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Dear Juanjo and rest of the Folk, Please find attached the document, which might be already included as a part of our FI-WARE spec. I, personally, agree with our thoughts that Juanjo has expressed and have just tailored the below text to a specification style, excluding eventual verbosity (and somewhere correcting English, however I don't pretend here). If you agree we may already use it as a part of official specification. I still need to improve the reference high-level pub/sub spec, not difficult job, however not sure if will have time. Let speak tomorrow morning. 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: Thursday, June 16, 2011 8:29 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. [cid:image001.gif at 01CC2C9E.2ED72B90] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. [cid:image002.gif at 01CC2C9E.2ED72B90] Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. ________________________________ 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: image001.gif Type: image/gif Size: 7104 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 8023 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From GUYSH at il.ibm.com Fri Jun 17 06:31:11 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Fri, 17 Jun 2011 07:31:11 +0300 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events In-Reply-To: References: <4DFA4B76.8010602@tid.es> Message-ID: I disagree with some of the comments Boris has on events. In particular... "An event is a particular case of the context element that does not have the EntityId and EntityType components" Why tie it to context - an event can stand on its own! - you may want to refer to the meaning of the event as some contextual information but it is not a must. I think we can live without this sentence We need to distinguish how we identify events vs. how we deal with events. The processing doesnt care how you identified an event from the origin (data element). I therefore think that we shouldnt event mention any context in the event definition section. The data elements can be identified as events if.... , the data element can be identified as context if... - sometimes the data element can be identified as both - thats all. Please see my comments here... Once we agree on the content I offer to go through this for correcting the English (and there will be a lot there) 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 From: Moltchanov Boris To: Juanjo Hierro , "fiware-data at lists.fi-ware.eu" Date: 17/06/2011 03:18 Subject: Re: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Juanjo and rest of the Folk, Please find attached the document, which might be already included as a part of our FI-WARE spec. I, personally, agree with our thoughts that Juanjo has expressed and have just tailored the below text to a specification style, excluding eventual verbosity (and somewhere correcting English, however I don?t pretend here). If you agree we may already use it as a part of official specification. I still need to improve the reference high-level pub/sub spec, not difficult job, however not sure if will have time. Let speak tomorrow morning. 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: Thursday, June 16, 2011 8:29 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu ( http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. 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. [attachment "Revised Notes and Thoughts on definition of data-context-event Boris.doc" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 7104 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 8023 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Revised Notes and Thoughts on definition of data-context-event Guy.doc Type: application/octet-stream Size: 250368 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 17 08:12:14 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 17 Jun 2011 08:12:14 +0200 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events In-Reply-To: References: <4DFA4B76.8010602@tid.es> Message-ID: <4DFAF03E.7060202@tid.es> Hi, I have taken a look at the changes proposed by Boris over the document I sent. I believe almost 90% of them can be accepted regarding the sections on which we describe data elements and context elements. I'll try to produce a revised version with some of the changes accepted prior to our confcall today. However, there is a fundamental difference in what respect to definition of events and I would like to point it out here because it's a matter for discussion (indeed, I rather disagree with the changes Boris made in the section on events) Boris essentially argues that event objects can only wrap data elements and, by the way, with certain mandatory attributes and meta-data. Indeed, Boris says that "An event is a particular case of the context element that does not have the EntityId and EntityType components". But that equals to a data element with certain mandatory attributes and meta-data. I believe, that approach has severe limitations: * It wouldn't allow the programmer to use the CEP GE or the Publish/Subscribe Broker GE with data elements that do not have the mandatory attributes and meta-data that will be defined by context elements. Why should we try to impose those attributes and metadata to any type of data handled in our system ? I do not believe there is no reason why the implementation of the CEP GE or the Publish/Subscribe Broker GE cannot handle data elements as well as context elements in general. * It wouldn't allow the programmer to use the CEP GE (or the Publish/Subscribe Broker GE) establishing conditions on ECA rules that rely on the EntityId or the EntityType (subscription formulas in the case of the Publish/Subscribe Broker). Why should we impose that limitation ? I believe that an applications subscribing to reception of context elements linked to a particular EntityId or to reception of context elements of a particular EntityType would be rather common ... Since you propose that EntityId and EntityType be dropped from the structure an event object is wrapping ... How can you establish conditions on EntityId and/or EntityType in ECA-rules/subscription-formulas ? I believe the model is much cleaner, while at the same time more powerful, by simply saying that an event object is something that wraps a data element or a context element. Such wrapping takes place at the time the data element or context element is received (arrives) at the GE, either the CEP GE or the Publish/Subscribe Broker GE. And such wrapping implies adding some components (such as detection time) which, like a header, accompany the data/context element while it is being processed by the GE. Applications can use values of those components in the conditions they program (ECA rules in the CEP GE or subscription formulas in the Publish/Subscribe Broker GE). Last but not least, this wrapping would disappear when processing by the GE is finished. If it helps to understand this model, you may just assume that data elements are like context elements with the EntityId and EntityType set to null (because data elements do not necessarily be associated to an EntityId and EntityType). Then an event object wraps a context element (either a true context element with assigned EntityId and EntityType values, or a data element, that is, a context element with EntityId and EntityType components set to null). That simple. In this model, none of the above mentioned limitations exist. It might be the case that a particular asset, brought by partner as a baseline for the reference implementation of a given GE, isn't able to process any sort of data element or context element format but a predefined one. However, this shouldn't impede us to specify the GEs in FI-WARE in a more open and flexible way. The implementation may need to be enhanced to support multiple formats (I don't see so much difficult since the definition of data and context element we are introducing here probably already adapts very well to the kind of structure these concrete GEs are today using to represent context/data in memory. That would be in our roadmap (FI-WARE backlog). Besides, we may claim that there might exist particular GE implementations tied to a particular case of data element and context element format representation for performance reasons. Those GEs would be partial implementations of the GE spec. Best regards, -- Juanjo On 17/06/11 02:18, Moltchanov Boris wrote: Dear Juanjo and rest of the Folk, Please find attached the document, which might be already included as a part of our FI-WARE spec. I, personally, agree with our thoughts that Juanjo has expressed and have just tailored the below text to a specification style, excluding eventual verbosity (and somewhere correcting English, however I don?t pretend here). If you agree we may already use it as a part of official specification. I still need to improve the reference high-level pub/sub spec, not difficult job, however not sure if will have time. Let speak tomorrow morning. 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: Thursday, June 16, 2011 8:29 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. [cid:part1.00060705.09030001 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. [cid:part2.07050407.02010205 at tid.es] Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. ________________________________ 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:part3.06030003.00030905 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/gif Size: 7104 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 8023 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 17 09:29:13 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 17 Jun 2011 09:29:13 +0200 Subject: [Fiware-data] Fwd: Meeting invitation: FI-WARE WP6 Data/Context weekly confcall Message-ID: <4DFB0249.4040700@tid.es> Folks, This is the info about webex for our confcall today. Dial-in details for the confcall bridge would be the same that Guy distributed last friday. Talk to you in a minute, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE WP6 Data/Context weekly confcall Date: Fri, 17 Jun 2011 09:04:16 +0200 From: Gestor i-Reunion webex6000 Reply-To: Webex6000 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex6000 invites you to attend this online meeting. Topic: FI-WARE WP6 Data/Context weekly confcall Date: Friday, June 17, 2011 Time: 9:30 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 675 324 069 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=12102963&UID=105956788&PW=NOGVhNWZiYmZm&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=12102963&UID=105956788&PW=NOGVhNWZiYmZm&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: Webex6000 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=12102963&UID=105956788&ICS=MI&LD=1&RD=2&ST=1&SHA2=SRzFFTo4vIGFII8Qg1G5sZaXy41HaiLo/HBMO5wQwUw=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 17 11:35:45 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 17 Jun 2011 11:35:45 +0200 Subject: [Fiware-data] Minutes of our confcall Message-ID: <4DFB1FF1.5070304@tid.es> Hi, Quick and dirty but hopefully complete :-) Thanks IBM for hosting the bridge and all for attending this fruitful meeting. Regards, -- Juanjo Attendees: Guy (IBM) Andreas (Siemens) Federico (UPM) Tom?s and Chema (ATOS) Juanjo (TID) Boris (Telecom Italia) Fano (Orange) - I didn't hear him in the confcall but I saw him on the webex ... Discussion about basic concepts: After some discussion we reach agreement. Juanjo to produce a final document compiling all the final definitions. This would go to the Overview part which would consist in these definitions, together with an explanation of the overall target architecture where each of the GEs are represented. Review status of contributions regarding GE descriptions: Juanjo explained that the planning at global level for this deliverable (FI-WARE High-level Description) has been updated. Now planning is as follows: + June 22 will be the new milestone for reception of contributions by each Chapter + From June 23 until June 30 we will carry out peer reviews. Aim is to produce a draft that is consolidated/complete enough as to be sent to representatives of the FI PPP Architecture Board by end of June. This will allow Use Case projects to start making comments and producing features requests we may evaluate for integration in our backlog + On July 11-12, there is a meeting of the FI PPP AB where we have to present the FI-WARE High-level Description. We should plan to distribute a final version of the deliverable at that date and then officially issue it to the EC by July 15 BigData Analysis GE Delayed but the team working at TID would produce a version on Wednesday. Guy will provide comments on the current draft. CEP GE Guy uploaded an update. Juanjo to make a second revision but in general believes it's almost Ok. Others are welcome to review it. Publish/Subscribe Broker GE Now that basic concepts have been settle, Boris will finalize writing this GE description section. Boris has upload a first draft of this. Partners entitled to review it and provide comments so that Boris can take all considerations in mind while writing the next consolidated version (due by Wednesday) Mutimedia analysis GE It is unchanged since last time Siemens uploaded it. Monday a confcall was setup at 16:30 pm. Juanjo to provide powwownow and web details. Query GE Andreas to take a look at the description of the Publish/Subscribe Broker GE to ensure that the proper linkage between the Query and the Publish/Subscribe Broker GE is kept as we agreed several weeks ago (document notes distributed by Juanjo after several confcalls discussion on the matter) Meta-data processing GE Still discussing with IBM whether this GE should be indeed a part of the CEP GE or not. Discussion to be taken by email using the WP mailing list. Andreas to start thread of discussion Meta-data (semantic) annotation tool Last uploaded version from ATOS. We need to have a more detailed description. Localization GE Should be reviewed under the light of the discussion we had during our conference on the matter. Intelligente Services GE There is still some work to be done. Partners entitled to review more stable parts. Revision of Security issues All entitled to identify security issues and provide them as input to the Question Marks section (check format in last template for the chapter distributed by Juanjo). Nevertheless, it was decided at global level to run a task force per chapter starting on June 23 where people from each WP will work together with people from the Security WP trying to finalize detection/analysis of security issues. We have to provide names of people who would be part of this task force on our side, reviewing our chapter together with people from the security team ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From andreas.hutter at siemens.com Fri Jun 17 11:59:08 2011 From: andreas.hutter at siemens.com (Hutter, Andreas) Date: Fri, 17 Jun 2011 11:59:08 +0200 Subject: [Fiware-data] On the relation of the Metadata Processing GE (Siemens) and the CEP GE (IBM) In-Reply-To: <4DFA4B76.8010602@tid.es> References: <4DFA4B76.8010602@tid.es> Message-ID: Dear Guy, all, as agreed during the telco, I am taking up the discussion on the relation between the Metadata Processing GE (Siemens) and the CEP GE (IBM). The question to be discussed is whether the CEP GE would already cover the functionalities of the Metadata Processing GE and, therefore, the latter one could be discarded. My current understanding is the following: a) The functionality of the (Meta)data Processing GE is to: - manage the incoming streaming / data connections - prepare the incoming data for further consumption in the analytics platform (e.g. transforming an XML document into JavaClasses, performing simple filtering operations, attaching reception time stamp, ...). There are no complex processing steps involved (e.g. correlations) - provide the prepared data to the target consuming GE b) These functions have corresponding functions that are provided inside the CEP GE. Hence we need to answer two questions: 1. Do we provide an stand-alone GE to provide the functions currently proposed for the (Meta)data Processing GE ? --> I believe that this would be beneficial because the tasks addressed by these functions are required all consuming GEs in the analytics platform. At the same time GE's like the CEP GE could provide their own internal "preprocessing components" to provide these functions, i.e. there is always the option to bypass the (Meta)data Processing GE. 2. Should we use the (Meta)data Processing GE proposed by Siemens or should we carve out the corresponding functions from the CEP GE by defining the appropriate interfaces and asking IBM to provide their implementation with these APIs attiached ? --> I do not have a strong opinion here. Either way is fine. Best regards, Andreas -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange-ftgroup.com Fri Jun 17 16:35:31 2011 From: fano.ramparany at orange-ftgroup.com (fano.ramparany at orange-ftgroup.com) Date: Fri, 17 Jun 2011 16:35:31 +0200 Subject: [Fiware-data] Some comment on the CEP GE Message-ID: Hi Guy, Here are some comments from my collegue Yvon Lopinto who reviewed your document. - The section introducting "the designer of the event processing logic" would deserve more details. - The Design component would better be moved to the the Tools GE. - Is this high level specification compatible with a CEP distributed deployement? Our experience favours a design approach where CEP operates at different levels including local CEP which generate "higher-level" events to be processed on eventually more centralized server. Kind regards, Fano -------------- next part -------------- An HTML attachment was scrubbed... URL: From GUYSH at il.ibm.com Fri Jun 17 17:30:16 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Fri, 17 Jun 2011 18:30:16 +0300 Subject: [Fiware-data] Some comment on the CEP GE In-Reply-To: References: Message-ID: I should upload the latest version - there is significantly more detail on the design - Juanjo commented on the latest version which he got directly from me. As for Tool - Juanjo mentioned a general comment - the Tools GE (WP9) is not going to implement tools for the GEs rather each GE that needs tools should implement it and make sure it is integratable into the framework WP9 will provide. As for deployment - I have not discussed it in the document. The latest version discusses how the CEP application a user would program is of a network of individual CEP processing instructions connected to an entire network. This network may be deployed from entirely on a single centralized engine to entirely distributed each processing instruction running on its own in a different server\device - anywhere you can think of that has compute power for that particular processing instruction. Here it is https://forge.fi-ware.eu/docman/view.php/9/133/FI-WARE_High-Level_Description_Data-Context+Management+v3.0+IBM.doc 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 From: To: Guy Sharon/Haifa/IBM at IBMIL Cc: , Date: 17/06/2011 17:35 Subject: Some comment on the CEP GE Hi Guy, Here are some comments from my collegue Yvon Lopinto who reviewed your document. - The section introducting ?the designer of the event processing logic? would deserve more details. - The Design component would better be moved to the the Tools GE. - Is this high level specification compatible with a CEP distributed deployement? Our experience favours a design approach where CEP operates at different levels including local CEP which generate "higher-level" events to be processed on eventually more centralized server. Kind regards, Fano -------------- 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 boris.moltchanov at telecomitalia.it Fri Jun 17 19:10:31 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 17 Jun 2011 19:10:31 +0200 Subject: [Fiware-data] Some comment on the CEP GE In-Reply-To: References: Message-ID: <730BA8DC-BC3B-4CD3-B115-8BC9449CB065@telecomitalia.it> Maximally uncoupled architecture for most components reusability especially where same component could be needed for one or more other components or application. Reduce embedding, only in special cases where it is strictly needed (performance) and not create redundancy. Avoid redundancy increasing the cost, complexity and killing efficiency. That is what I'm thinking as generic rules of a good architectural design. Then, if a component provides not core-business but some supporting feature or functionality and as well as we have tools GE it should be there. This is without entering into the components peculiarity that i'm not familiar with. Have a nice week-end, Boris 17/giu/2011, ?? 17:30, "Guy Sharon" > ??????????????(??): I should upload the latest version - there is significantly more detail on the design - Juanjo commented on the latest version which he got directly from me. As for Tool - Juanjo mentioned a general comment - the Tools GE (WP9) is not going to implement tools for the GEs rather each GE that needs tools should implement it and make sure it is integratable into the framework WP9 will provide. As for deployment - I have not discussed it in the document. The latest version discusses how the CEP application a user would program is of a network of individual CEP processing instructions connected to an entire network. This network may be deployed from entirely on a single centralized engine to entirely distributed each processing instruction running on its own in a different server\device - anywhere you can think of that has compute power for that particular processing instruction. Here it is https://forge.fi-ware.eu/docman/view.php/9/133/FI-WARE_High-Level_Description_Data-Context+Management+v3.0+IBM.doc 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 From: > To: Guy Sharon/Haifa/IBM at IBMIL Cc: >, > Date: 17/06/2011 17:35 Subject: Some comment on the CEP GE ________________________________ Hi Guy, Here are some comments from my collegue Yvon Lopinto who reviewed your document. - The section introducting ???the designer of the event processing logic??? would deserve more details. - The Design component would better be moved to the the Tools GE. - Is this high level specification compatible with a CEP distributed deployement? Our experience favours a design approach where CEP operates at different levels including local CEP which generate "higher-level" events to be processed on eventually more centralized server. Kind regards, Fano _______________________________________________ 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. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From GUYSH at il.ibm.com Sun Jun 19 20:33:14 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Sun, 19 Jun 2011 21:33:14 +0300 Subject: [Fiware-data] On the relation of the Metadata Processing GE (Siemens) and the CEP GE (IBM) In-Reply-To: References: <4DFA4B76.8010602@tid.es> Message-ID: Hi, I will comment in the order Andreas listed his understanding - "manage incoming connections" - in my understanding this is the role for the gathering data GE. CEP GE is configured with the events it should process and not too focused on the connections and where the events come from. Although IBM's asset includes an adapter for introducing new types of connections, it is not the focus of the asset and the thoughts were to support adapters only for internal purposes of the Data\Context management. - "prepare for further consumption" - CEP GEs should support simple (better term is stateless) operations as well (as IBM's asset does) such as filter-in\out and transformations. As for XML to Java Classes - we want to abstract this part in the entire chapter, meaning there will be no constraint on the structure and method of representing data, events and context (a part from what is of basic as in the discussions between Juanjo, Boris and myself). So - if you get metadata in other format than XML we should be able to support that as well. -"provide to consuming GE" - any processing GE should support this Therefore it initially looks very similar but before concluding I would ask the following questions as well: 1. What does it mean the metadata of streamed data? Are you analyzing the metadata separately? How is this then combined with the data? Or is your assumption that you 'propagate' the same stream with additional information or a slightly different stream? 2. How different is the processing on the metadata from the data? If you had the data in XML and need to convert to Java Classes and attach detection time - whats the difference? Is there something at the level of the filter or transformation that is semantical and you need someone to set this up in such a way that could never be done on data? 3. Not all data is events, CEP deals with events, what would be the issues of handling the metadata as events in order to process with CEP? 4. How do you configure such instructions\processing on metadata? Who does this and how? Could they be happy with a CEP like tooling\management? Perhaps there are additional questions to help us understanding what are the differences and breaking points in processing for metadata 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 From: "Hutter, Andreas" To: "fiware-data at lists.fi-ware.eu" Date: 17/06/2011 12:59 Subject: [Fiware-data] On the relation of the Metadata Processing GE (Siemens) and the CEP GE (IBM) Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Guy, all, as agreed during the telco, I am taking up the discussion on the relation between the Metadata Processing GE (Siemens) and the CEP GE (IBM). The question to be discussed is whether the CEP GE would already cover the functionalities of the Metadata Processing GE and, therefore, the latter one could be discarded. My current understanding is the following: a) The functionality of the (Meta)data Processing GE is to: - manage the incoming streaming / data connections - prepare the incoming data for further consumption in the analytics platform (e.g. transforming an XML document into JavaClasses, performing simple filtering operations, attaching reception time stamp, ...). There are no complex processing steps involved (e.g. correlations) - provide the prepared data to the target consuming GE b) These functions have corresponding functions that are provided inside the CEP GE. Hence we need to answer two questions: 1. Do we provide an stand-alone GE to provide the functions currently proposed for the (Meta)data Processing GE ? --> I believe that this would be beneficial because the tasks addressed by these functions are required all consuming GEs in the analytics platform. At the same time GE's like the CEP GE could provide their own internal "preprocessing components" to provide these functions, i.e. there is always the option to bypass the (Meta)data Processing GE. 2. Should we use the (Meta)data Processing GE proposed by Siemens or should we carve out the corresponding functions from the CEP GE by defining the appropriate interfaces and asking IBM to provide their implementation with these APIs attiached ? --> I do not have a strong opinion here. Either way is fine. Best regards, Andreas_______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Mon Jun 20 10:58:37 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Mon, 20 Jun 2011 10:58:37 +0200 Subject: [Fiware-data] On the relation of the Metadata Processing GE (Siemens) and the CEP GE (IBM) In-Reply-To: References: <4DFA4B76.8010602@tid.es> Message-ID: Dear All, me few thoughts to some aspects of this discussion (we may have a lot of metadata in the Context Data as well): - Meta-data are also the data, just let's say not of the first importance of not core business (describe the data itself and not directivity involved into the business), therefore has a "right to exist" as any other type of data; - Say that above the events could represent a value of meta-data, e.g. in my context of my presence (now) I'd include a location context meta-data saying just entered, which is an event; therefore we need a mechanism processing meta-data as part of the context meta-data, and event could be a context meta-data as an example before); events and other contexts could be an input for meta-data processing for a richer context; - Therefore concluding the last sequence meta-data could form events hence the context or context meta-data as an output of the meta-data processing mechanism, e.g. I have an accuracy in location context and would need put in the meta-data of the context not only the precision grade but also a parameter saying "increasing resolution" or "degrade quality", etc. Sorry for a complicate explanation, I believe the meta-data are just other data and could be anything as such. The difference is only in the purpose (secondary) and usage (for main data processing). Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Guy Sharon Sent: Sunday, June 19, 2011 8:33 PM To: Hutter, Andreas Cc: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] On the relation of the Metadata Processing GE (Siemens) and the CEP GE (IBM) Hi, I will comment in the order Andreas listed his understanding - "manage incoming connections" - in my understanding this is the role for the gathering data GE. CEP GE is configured with the events it should process and not too focused on the connections and where the events come from. Although IBM's asset includes an adapter for introducing new types of connections, it is not the focus of the asset and the thoughts were to support adapters only for internal purposes of the Data\Context management. - "prepare for further consumption" - CEP GEs should support simple (better term is stateless) operations as well (as IBM's asset does) such as filter-in\out and transformations. As for XML to Java Classes - we want to abstract this part in the entire chapter, meaning there will be no constraint on the structure and method of representing data, events and context (a part from what is of basic as in the discussions between Juanjo, Boris and myself). So - if you get metadata in other format than XML we should be able to support that as well. -"provide to consuming GE" - any processing GE should support this Therefore it initially looks very similar but before concluding I would ask the following questions as well: 1. What does it mean the metadata of streamed data? Are you analyzing the metadata separately? How is this then combined with the data? Or is your assumption that you 'propagate' the same stream with additional information or a slightly different stream? 2. How different is the processing on the metadata from the data? If you had the data in XML and need to convert to Java Classes and attach detection time - whats the difference? Is there something at the level of the filter or transformation that is semantical and you need someone to set this up in such a way that could never be done on data? 3. Not all data is events, CEP deals with events, what would be the issues of handling the metadata as events in order to process with CEP? 4. How do you configure such instructions\processing on metadata? Who does this and how? Could they be happy with a CEP like tooling\management? Perhaps there are additional questions to help us understanding what are the differences and breaking points in processing for metadata Guy Sharon Manager Event-based Middleware & Solutions Group ________________________________ [cid:image001.gif at 01CC2F37.F454D9D0] 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 From: "Hutter, Andreas" To: "fiware-data at lists.fi-ware.eu" Date: 17/06/2011 12:59 Subject: [Fiware-data] On the relation of the Metadata Processing GE (Siemens) and the CEP GE (IBM) Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Dear Guy, all, as agreed during the telco, I am taking up the discussion on the relation between the Metadata Processing GE (Siemens) and the CEP GE (IBM). The question to be discussed is whether the CEP GE would already cover the functionalities of the Metadata Processing GE and, therefore, the latter one could be discarded. My current understanding is the following: a) The functionality of the (Meta)data Processing GE is to: - manage the incoming streaming / data connections - prepare the incoming data for further consumption in the analytics platform (e.g. transforming an XML document into JavaClasses, performing simple filtering operations, attaching reception time stamp, ...). There are no complex processing steps involved (e.g. correlations) - provide the prepared data to the target consuming GE b) These functions have corresponding functions that are provided inside the CEP GE. Hence we need to answer two questions: 1. Do we provide an stand-alone GE to provide the functions currently proposed for the (Meta)data Processing GE ? --> I believe that this would be beneficial because the tasks addressed by these functions are required all consuming GEs in the analytics platform. At the same time GE's like the CEP GE could provide their own internal "preprocessing components" to provide these functions, i.e. there is always the option to bypass the (Meta)data Processing GE. 2. Should we use the (Meta)data Processing GE proposed by Siemens or should we carve out the corresponding functions from the CEP GE by defining the appropriate interfaces and asking IBM to provide their implementation with these APIs attiached ? --> I do not have a strong opinion here. Either way is fine. Best regards, Andreas_______________________________________________ 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. [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: image001.gif Type: image/gif Size: 2558 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Mon Jun 20 15:52:08 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 20 Jun 2011 15:52:08 +0200 Subject: [Fiware-data] Bridges for our confcall this afternoon on multimedia analysis Message-ID: <4DFF5088.5050109@tid.es> Folks, We can use powwownow for the confcall scheduled at 16:30 ... Dial-in phone numbers are in the attachment. The PIN: 050662 Regarding webex, please find enclosed the details. Cheers, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE session Date: Mon, 20 Jun 2011 15:39:00 +0200 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE session Date: Monday, June 20, 2011 Time: 4:30 pm, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 962 873 717 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=154069027&UID=1215565962&PW=NNTkwY2YwOTE1&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=154069027&UID=1215565962&PW=NNTkwY2YwOTE1&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=154069027&UID=1215565962&ICS=MI&LD=1&RD=2&ST=1&SHA2=14GhT-rTH85-e2my5v9Qn-d/yFAOpBbkgr1PdeWhRCw=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Powwownow-dial-in-numbers.pdf Type: application/pdf Size: 61516 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Tue Jun 21 18:09:11 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 21 Jun 2011 18:09:11 +0200 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events In-Reply-To: References: <4DFA4B76.8010602@tid.es> Message-ID: Dear All, Considering Juanjo's comments and making the document more readable, simpler and better structured I've edited the P/S document with the following changes: 1. Reserved the section dedicated to the data structures just before starting the GE descriptions (we have to introduce what we're going to address by those GEs and then describe the GEs; 2. As first GE introduced P/S GE simplifying and clarifying the text and rendering it adopted for any type of data, context or events; 3. Change the name leaving just high-level description data/context management. The document URI is https://forge.fi-ware.eu/docman/admin/index.php?editdoc=1&docid=184&group_id=9 . Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: Friday, June 17, 2011 3:31 AM To: Juanjo Hierro; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Dear All, please find here https://forge.fi-ware.eu/docman/view.php/9/158/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.1+17-06-01-2.doc the file with reviewed pub/sub high-level description. It is private. I'm safe for your mail boxes not attaching to this email, the size is more than 2MB. Best Regards, Boris From: Moltchanov Boris Sent: Friday, June 17, 2011 2:18 AM To: 'Juanjo Hierro'; fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Dear Juanjo and rest of the Folk, Please find attached the document, which might be already included as a part of our FI-WARE spec. I, personally, agree with our thoughts that Juanjo has expressed and have just tailored the below text to a specification style, excluding eventual verbosity (and somewhere correcting English, however I don't pretend here). If you agree we may already use it as a part of official specification. I still need to improve the reference high-level pub/sub spec, not difficult job, however not sure if will have time. Let speak tomorrow morning. 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: Thursday, June 16, 2011 8:29 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like '2', '7' or '365' that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. [cid:image001.gif at 01CC303C.E2EB3C60] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. [cid:image002.gif at 01CC303C.E2EB3C60] Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. ________________________________ 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:image003.gif at 01CC303C.E2EB3C60]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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: image001.gif Type: image/gif Size: 7104 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 8023 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 677 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From tomas.parientelobo at atosresearch.eu Wed Jun 22 13:57:32 2011 From: tomas.parientelobo at atosresearch.eu (Tomas PAriente Lobo) Date: Wed, 22 Jun 2011 13:57:32 +0200 Subject: [Fiware-data] ATOS contibutions uploaded Message-ID: <9DA3EC560FF1564DB032154AC290954B0560847C@INTMAIL01.es.int.atosorigin.com> Dear Juanjo, all, I have uploaded a new version of the ATOS contributions. Some comments: - Part of our GE based on the FIRST asset is quite similar to what is described within the Intelligent Service Plugins section under the "Opinion mining" part. o However, I believe that this Intelligent service described there should be divided in two parts: Data gathering and Opinion mining. The data gathering should be part of the Massive data gathering enabler, while the extraction of opinions and sentiments from "clean" text is really the intelligent algorithm. o I don't see the Massive data gathering enabler described anywhere, but it seems that the data gathering is somehow scattered in the description of some of the rest of the GEs. Is this going to remain this way? o So, I have uploaded a version of our GE (https://forge.fi-ware.eu/docman/view.php/9/188/FI-WARE_High-Level_Description_21-06-01_preprocessing_unstructured_data_enabler.doc), but I would recommend in future versions to try to merge the data gathering parts of all GEs in a single GE (Massive Data Gathering) with different approaches. Our data gathering from unstructured web resources would be part of that GE, while the sentiment analysis part of our GE could then be joined to the Opinion mining plugin GE (although probably there are differences in the way the assets for opinion mining are implemented). - Regarding the Semantic Annotation enabler, I see that there is a description of the GE already submitted by TI. This is OK, but our enabler is different in the sense that is not providing semantic annotation capabilities, but the necessary infrastructure to enable semantic apps (including annotations, ontology engineering and SPARQL search, among others). This is the Semantic infrastructure enabler. We have uploaded a new version at https://forge.fi-ware.eu/docman/view.php/9/187/FI-WARE_High-Level_Description_21-06-01_semantic_app_enabler.doc. Best regards Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 566 bytes Desc: image001.gif URL: From boris.moltchanov at telecomitalia.it Wed Jun 22 17:50:05 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 22 Jun 2011 17:50:05 +0200 Subject: [Fiware-data] TI will not be in the Friday call Message-ID: Dear Partners, TI will not be able to participate in this Friday's audio-conference due to local holiday. I will check the minutes and proceed with our contributions as agreed during the last calls. Best Regards, Boris Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Wed Jun 22 22:45:26 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 Jun 2011 22:45:26 +0200 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events In-Reply-To: References: <4DFA4B76.8010602@tid.es> Message-ID: <4E025466.2060808@tid.es> Boris, The URL you have copied in your message is not an URL to an entry in the folder/files tree displayed at: https://forge.fi-ware.eu/docman/index.php?group_id=9# Are you referring to the following one ? https://forge.fi-ware.eu/docman/view.php/9/184/FI-WARE_High-Level_Description_Data-Context+Management+v1.3+21-06-01.doc If not, please go to the above page, explode the folders and while putting the cursor mouse in the proper entry, click on the right button of your mouse and then copy the link location. That should allow you to get the real URI that will allow us to download the file. Please clarify. Thanks, -- Juanjo On 21/06/11 18:09, Moltchanov Boris wrote: Dear All, Considering Juanjo?s comments and making the document more readable, simpler and better structured I?ve edited the P/S document with the following changes: 1. Reserved the section dedicated to the data structures just before starting the GE descriptions (we have to introduce what we?re going to address by those GEs and then describe the GEs; 2. As first GE introduced P/S GE simplifying and clarifying the text and rendering it adopted for any type of data, context or events; 3. Change the name leaving just high-level description data/context management. The document URI is https://forge.fi-ware.eu/docman/admin/index.php?editdoc=1&docid=184&group_id=9 . Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: Friday, June 17, 2011 3:31 AM To: Juanjo Hierro; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Dear All, please find here https://forge.fi-ware.eu/docman/view.php/9/158/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.1+17-06-01-2.doc the file with reviewed pub/sub high-level description. It is private. I?m safe for your mail boxes not attaching to this email, the size is more than 2MB. Best Regards, Boris From: Moltchanov Boris Sent: Friday, June 17, 2011 2:18 AM To: 'Juanjo Hierro'; fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Dear Juanjo and rest of the Folk, Please find attached the document, which might be already included as a part of our FI-WARE spec. I, personally, agree with our thoughts that Juanjo has expressed and have just tailored the below text to a specification style, excluding eventual verbosity (and somewhere correcting English, however I don?t pretend here). If you agree we may already use it as a part of official specification. I still need to improve the reference high-level pub/sub spec, not difficult job, however not sure if will have time. Let speak tomorrow morning. 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: Thursday, June 16, 2011 8:29 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. [cid:part1.05060209.04060805 at tid.es] Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. [cid:part2.08080000.00010403 at tid.es] Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. ________________________________ 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:part3.04060802.05060906 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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:part4.05020200.06080007 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/gif Size: 7104 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 8023 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Thu Jun 23 00:19:23 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 23 Jun 2011 00:19:23 +0200 Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events In-Reply-To: <4E025466.2060808@tid.es> References: <4DFA4B76.8010602@tid.es> <4E025466.2060808@tid.es> Message-ID: Dear Juanjo, Yes, the right one is that in the second link of your email v1.3 by 21-06-2011. Sorry for the mistake. Best Regards, Boris 22/giu/2011, ? 22:45, "Juanjo Hierro" > ???????(?): Boris, The URL you have copied in your message is not an URL to an entry in the folder/files tree displayed at: https://forge.fi-ware.eu/docman/index.php?group_id=9# Are you referring to the following one ? https://forge.fi-ware.eu/docman/view.php/9/184/FI-WARE_High-Level_Description_Data-Context+Management+v1.3+21-06-01.doc If not, please go to the above page, explode the folders and while putting the cursor mouse in the proper entry, click on the right button of your mouse and then copy the link location. That should allow you to get the real URI that will allow us to download the file. Please clarify. Thanks, -- Juanjo On 21/06/11 18:09, Moltchanov Boris wrote: Dear All, Considering Juanjo?s comments and making the document more readable, simpler and better structured I?ve edited the P/S document with the following changes: 1. Reserved the section dedicated to the data structures just before starting the GE descriptions (we have to introduce what we?re going to address by those GEs and then describe the GEs; 2. As first GE introduced P/S GE simplifying and clarifying the text and rendering it adopted for any type of data, context or events; 3. Change the name leaving just high-level description data/context management. The document URI is https://forge.fi-ware.eu/docman/admin/index.php?editdoc=1&docid=184&group_id=9 . Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: Friday, June 17, 2011 3:31 AM To: Juanjo Hierro; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Dear All, please find here https://forge.fi-ware.eu/docman/view.php/9/158/FI-WARE_High-Level_Description_11-06-1+Data-Context+Management+v1.1+17-06-01-2.doc the file with reviewed pub/sub high-level description. It is private. I?m safe for your mail boxes not attaching to this email, the size is more than 2MB. Best Regards, Boris From: Moltchanov Boris Sent: Friday, June 17, 2011 2:18 AM To: 'Juanjo Hierro'; fiware-data at lists.fi-ware.eu Subject: RE: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Dear Juanjo and rest of the Folk, Please find attached the document, which might be already included as a part of our FI-WARE spec. I, personally, agree with our thoughts that Juanjo has expressed and have just tailored the below text to a specification style, excluding eventual verbosity (and somewhere correcting English, however I don?t pretend here). If you agree we may already use it as a part of official specification. I still need to improve the reference high-level pub/sub spec, not difficult job, however not sure if will have time. Let speak tomorrow morning. 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: Thursday, June 16, 2011 8:29 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Revised description of basic concepts: data elements, context elements and events Folks, Please find enclosed a revised version of the document with the description of basic concepts: data elements, context elements and events. Hopefully it captures what I believe every of us have in mind. I will send later tonight some additional comments elaborating a little bit further some points. For your convenience and if it helps to continue discussion over the email, I attach below the text of the document as body of this message. Best regards, -- Juanjo 1. Motivation This document intends to provide a precise description of some basic concepts like data, context and events in FI-WARE. These concepts are fundamental in the description of the Data/Context Management platform in FI-WARE and the way applications are developed based on that platform. Contents of this document will be considered as baseline for a post to publish in our Data/Context Management blog in www.fi-ware.eu (http://data.fi-ware.eu) 2. Definition of Data Data refers to information that is produced, generated, collected or observed that may be of relevance for processing, further analysis or information and knowledge generation. Essentially refers to information relevant to applications. Data in FI-WARE has associated a data type and a value. FI-WARE will support a set of built-in basic data types like in most programming languages. Values linked to these basic data types supported in FI-WARE are referred as basic data values. So we have the notion of the integer basic data type and basic values like ?2?, ?7? or ?365? that belong to the integer basic data type. A data element refers to data whose value is defined as a sequence of one or more triplets referred as data element attributes, where the type and value of each attribute is either linked to a basic data type and a basic value or is linked to the data type and value of another data element. Note that each data element has an associated data type as any data in the system. This data type determines what concrete sequence of attributes characterizes that data element. There may be meta-data (also referred as semantic data) linked to attributes in a data element. However, existence of meta-data linked to a data element attribute is optional. Applications may assign an identifier to Data elements in order to store them in some Data Base. However, such identifier would be generated aside and would not be considered as part of the structure of the data element. Note that a given application may decide to use the value of some attribute linked to a data element as its identifier in a given data base but, again, there is no identifier associated to the representation of a data element. The basic concepts introduced so far are represented in Figure 1. Figure 1. Basic Model for Data A cornerstone concept in FI-WARE is that data elements are not tied to a specific format representation. They can be transferred as an XML document at some given point in time and then be translated into another XML document representation later on or be transformed into some sort of efficient binary representation as part of a message. They can be stored in a Relational Database, in a RDF Repository or as entries in a noSQL data base like MongoDB, adopting a particular storage format that may be the same or different to the format used when it is transferred. It should be possible to infer the data type associated to a given Data Element based on the XML document or the format of the message in which it is transferred (e.g., a specific element of the XML document if the same XML document type is used to represent data elements of different types or just the XML document type if a different XML document type is used per data type) or based on the structure used to store it (e.g., may be inferred from the name of the table in which the data element is stored). The way data elements are represented in memory by FI-WARE GEs is not specified. Therefore, the implementer of a FI-WARE GE may decide the way it represents data element in memory. 3. Definition of Context Context in FI-WARE is represented through context elements. A context element extends the concept of data element by associating an EntityId and EntityType to it, uniquely identifying the entity in the FI-WARE system to which the context element information refers. In other words, a context element is a data element to which we add the association to an EntityId and an EntityType. As an example, a measured temperature is a data element but in order to become a context element, has to refer to some entity which exhibits that temperature (a particular room, a particular building, etc). In addition, there may be some attributes as well as meta-data associated to attributes that we may define as mandatory for any type of context element in FI-WARE. The basic concepts behind context elements representation are represented in Figure 2. Figure 2. Basic Model for Context Note that similar statements regarding format representation of data elements also apply to context elements. 4. Definition of Event An event is an occurrence within a particular system or domain; it is something that has happened, or is contemplated as having happened in that domain. The word event object is used to mean a programming entity that represents such an occurrence (event) in a computing system [EPIA]. Events are represented as event objects within computing systems to distinguish them from other types of objects and to perform operations on them, also known as event processing. It is common to refer to event objects simply as events. In FI-WARE, event objects are created internally to some GEs like the Complex Event Processing GE or the Publish/Subscribe Broker GE. These event objects are defined as a data element (or a context element) to which a number of standard event object properties (similar to a header) are associated internally to the GE. The concrete set of standard event object properties in FI-WARE is still to be defined but we may anticipate that one of these properties would be the time at which the event object is detected by the GE (arrives to the GE). There might be other properties which may be defined and tools will be provided enabling applications or admin users to assign values to those properties based on values of data element attributes (e.g., source of the event or actual creation time) or other characteristics of the data element (i.e., DataType) or the context element (i.e., EntityId and EntityType) wrapped by the event object. Data events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a data element, while context events refer to event objects handled by the CEP GE or the Publish/Subscribe Broker GE wrapping a context element. ________________________________ 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. 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. ________________________________ 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. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Thu Jun 23 08:07:26 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 23 Jun 2011 08:07:26 +0200 Subject: [Fiware-data] Fwd: Minutes of the second meeting of the FI-PPP Architecture Board Message-ID: <4E02D81E.8040308@tid.es> FYI, -- Juanjo -------- Original Message -------- Subject: Minutes of the second meeting of the FI-PPP Architecture Board Date: Mon, 20 Jun 2011 13:17:42 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, Please find enclosed the minutes of the second meeting of the FI-PPP Architecture Board that took place on June 16th. Next meeting of the FI-PPP AB will be f2f in Madrid on July 11-12. As you would see in the minutes, I already announced that the official release of the FI-WARE High-level Description deliverable will be delayed to mid July (indeed to be presented to members of the AB in our f2f meeting in July). However, we committed to share with them a draft by end of June. This draft is intended to be stable and with all target contents ready (the two first weeks of July would be devoted to final review after official release). This would help UC projects to start reading the FI-WARE High-level Description in order to understand what we plan to deliver. Please push work in your respective WPs to make it happen. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP-AB-Meeting-Minutes 11-06-16 v1.0.doc Type: application/msword Size: 591360 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From eric.clavier at orange-ftgroup.com Thu Jun 23 09:49:43 2011 From: eric.clavier at orange-ftgroup.com (eric.clavier at orange-ftgroup.com) Date: Thu, 23 Jun 2011 09:49:43 +0200 Subject: [Fiware-data] : FT contributors on Personal Data Synchronization topic References: <4DE5DD25.7090008@tid.es> Message-ID: <2CAE5634D52E194BA393187E0568E1AC0607366D@ftrdmel1> Hi Juanjo, It seems that Dany Cauchie hasn't received any mail from the WP. Could you had him to the mailing list ? Thanks Best Regards Eric Clavier De : CLAVIER Eric RD-MAPS-LAN Envoy? : mercredi 1 juin 2011 16:52 ? : Juanjo Hierro; fiware-data at lists.fi-ware.eu Cc : CAUCHIE Dany RD-MAPS-LAN Objet : [Fiware-data] : FT contributors on Personal Data Synchronization topic Hi Juanjo, Dany will replace me on the data synchronization topic aspects in the WP. Could you add him to the mailing-list ? We will get back to you to present our contribution Best regards Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Thu Jun 23 16:30:29 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 23 Jun 2011 16:30:29 +0200 Subject: [Fiware-data] =?iso-8859-1?q?R=E9f=2E_=3A_Re=3A__Details_about_br?= =?iso-8859-1?q?idge_for_our_confcall_on_Localization=09Services?= In-Reply-To: <15906_1307448684_4DEE156C_15906_7107_1_OFF6D65DB5.7E86AEC0-ONC12578A8.0042968A-C12578A8.0042F2FB@thalesaleniaspace.com> References: <15906_1307448684_4DEE156C_15906_7107_1_OFF6D65DB5.7E86AEC0-ONC12578A8.0042968A-C12578A8.0042F2FB@thalesaleniaspace.com> Message-ID: Dear Tanguy, I'm sorry for so long response for the Location GE, I've thought a little bit about that component, discussed it with colleagues and propose the following text that you may find in the section 3.1.3.2 of the https://forge.fi-ware.eu/docman/view.php/9/194/FI-WARE_High-Level_Description_Data-Context+Management+v1.4+23-06-01.doc document. If you agree with this you may integrate Thales' contribution there, maintaining that high level architecture and description. In this case we would have (in FI-WARE) and provide as a description to UAs: - Consolidated view over this component (LGE) accordingly to the rest of enablers specifically to the P/S broker; - "Free" version of the GE without a "vertical" or proprietary implementations peculiarities at this FI-WARE specification stage; - With all the functionalities that we might have from this LGE; - Both location assets, from TI and Thales are compliant with this high-level description, requirements, features and reference architecture. We may, as you suggested have a learning mechanism, indeed I've already added this into the description and we may have as well OpenCellID start, because I don't see serious problems there. Please let me know what do you think? Best Regards, Boris PS. I've added some new lines into the P/S GE description regarding the data/context cache and history optional features. From: Tanguy.Bourgault at thalesaleniaspace.com [mailto:Tanguy.Bourgault at thalesaleniaspace.com] Sent: Tuesday, June 07, 2011 2:11 PM To: Moltchanov Boris Cc: remi.challamel at thalesaleniaspace.com Subject: R?f. : Re: [Fiware-data] Details about bridge for our confcall on Localization Services Importance: Low Hi Boris, I took part of the conversation this morning about TAS Location Server. I looked at the opencellid data and although this was looking like a good starting point at the time I believe there will be limitations in using this database: 1- Number of cells is very limited and not located in Europe, 2- Cells are not identified using the complete set of cell identifiers, e.g. only location area code is utilised (MCC/MNC/LAC instead of MCC/MNC/LAC/CI), 3- No cell uncertainty is available. I guess the best way to have an autonomous database would be to implement a cell "sniffer", where the Location Server would request an autonomous GPS fix when the cellid is unknown and store the GPS fix against the retrieved cell information. This would require small development for us but could be easily demonstrated. Tanguy Bourgault Thales Alenia Space LBS Project Manager [cid:image001.gif at 01CC31B6.1694EF50]Moltchanov Boris Moltchanov Boris Envoy? par : fiware-data-bounces at lists.fi-ware.eu 07/06/2011 12:16 Pour : "fiware-data at lists.fi-ware.eu" cc : Objet : Re: [Fiware-data] Details about bridge for our confcall on Localization Services Location platform may use www.opencellid.org Just to have it send over all interested and traced in email exchange :). 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, June 07, 2011 9:40 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Details about bridge for our confcall on Localization Services Hi, We can use powonow for our confcall on Localization Services scheduled at 10:00am. powwownow PIN 050662: If needed, we can use also webex (please find the details below) Best regards, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE confcall Localization Services Date: Tue, 7 Jun 2011 09:00:03 +0200 From: Gestor i-Reunion webex9100 Reply-To: Webex9100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex9100 invites you to attend this online meeting. Topic: FI-WARE confcall Localization Services Date: Tuesday, June 7, 2011 Time: 9:30 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 965 296 726 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&PW=NZWQwZDliMDZk&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=153875242&UID=1214893992&PW=NZWQwZDliMDZk&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex9100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=153875242&UID=1214893992&ICS=MI&LD=1&RD=2&ST=1&SHA2=ugQgU0hJRBkb5PSE-99OZm0hOMfEhKyR05gOCwQldGY=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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:image006.gif at 01CC31B6.1694EF50]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 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: image001.gif Type: image/gif Size: 105 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 168 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 168 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 166 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.gif Type: image/gif Size: 677 bytes Desc: image006.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From boris.moltchanov at telecomitalia.it Thu Jun 23 16:43:57 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 23 Jun 2011 16:43:57 +0200 Subject: [Fiware-data] Confcall at 18:30 on Semantics (second part) In-Reply-To: References: Message-ID: Dear Amon, Juanjo and Partners, Please find https://forge.fi-ware.eu/docman/view.php/9/195/FI-WARE_Data_ContextHigh-Level_Description_Multimendia_Analysis_Recognition%28Siemens%26TI%29-23-06-2011.docx document with TI contribution regarding multimedia analysis and recognition. I'm not sure if we?ve right version for the editing, I believe yes. However it would be not difficult to integrate tacked changes into the final document and some of Juanjo's comments regarding this matter could be also already solved here. Sorry for confusion with the documents and contribution. I think this is a time to start with integration selecting most updated and agreed contributions for relevant topics into the same document and archiving the number of documents we've created at this point. Thank you. Best Regards, Boris -----Original Message----- From: Amon, Peter [mailto:p.amon at siemens.com] Sent: Tuesday, June 21, 2011 3:00 PM To: Moltchanov Boris Cc: jhierro at tid.es Subject: RE: [Fiware-data] Confcall at 18:30 on Semantics (second part) Dear Boris, you are right. The agreement was that TI will do the integration. (This is what I wrote at the end of my email. :-) I just wanted to help and reviewed our part under the light of yesterday's discussion. (There are only a few additions.) Of course, you are free to start from the previous version or the updated version. Sorry if this caused any confusion! Kind regards Peter > -----Original Message----- > From: Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] > Sent: Dienstag, 21. Juni 2011 14:08 > To: Amon, Peter > Cc: jhierro at tid.es > Subject: RE: [Fiware-data] Confcall at 18:30 on Semantics > (second part) > > Dear Peter, > > Thanks for the effort. > > I should mention that was not the agreement yesterday, if I'm > not wrong. The agreement was that we start from the current > release of the document and produce a new version. > > We don't have call's minutes therefore I may not insist. > > However we have already started yesterday contextually to the > call and I have to check now how difficult to merge both > works and will write you back. In the "worst" case we will > provide an edited version by TI as agreed yesterday. > > Best Regards, > Boris > > -----Original Message----- > From: Amon, Peter [mailto:p.amon at siemens.com] > Sent: Tuesday, June 21, 2011 1:42 PM > To: Moltchanov Boris; jhierro at tid.es > Cc: tomas.parientelobo at atosresearch.eu; Hutter, Andreas; > Laumer, Marcus > Subject: RE: [Fiware-data] Confcall at 18:30 on Semantics > (second part) > > Dear Boris, dear Junanjo, all, > > I updated the description of the "Multimedia Analysis" GE > following our discussion yesterday. I made some references to > TI's description of the "Multimedia Recognition Brokering", > but I did not use the text directly. It is probably better > that TI does the integration (as also agreed yesterday). > > The new version can be found at: > https://forge.fi-ware.eu/docman/view.php/9/114/FI-WARE_High-Le > vel_Description_11-06-1+Data-Context+Management+v1.0+11-06-01_ > MediaAnalysis_v05.doc > > Boris, please forward this email to your colleagues (e.g., > Walter) as I do not have their email addresses. > > Thanks and kind regards > Peter > > > > > -----Original Message----- > > From: Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] > > Sent: Donnerstag, 16. Juni 2011 17:15 > > To: Amon, Peter; jhierro at tid.es > > Cc: tomas.parientelobo at atosresearch.eu; Hutter, Andreas > > Subject: RE: [Fiware-data] Confcall at 18:30 on Semantics > > (second part) > > > > Dear All, > > > > Telecom Italia have assets on both Semantic and Data > > analysis. I'm not sure who and what exactly covering from > > Siemens and ATOS. It seemed that Siemens was available to > > discuss multimedia analysis and recognition. Sorry maybe I'm wrong. > > > > I'm saying: > > - for both technologies I have to include into work the right > > persons from; > > - it will be impossible to discuss anything with ATOS due to > > incompatibility (for rhe moment, I'm still checking) but as > > from my previous email with Siemens. We need to have this > > call even if from your point it seems that there is nothing > > to discuss because you see it alligned; > > - we could not discuss this from TI within tomorrow call > > because the people will be not there; > > - I will partecipate in tomorrow call. > > > > Best regards, > > Boris"Amon, Peter" ???????: > > > > Dear Juanjo, > > > > from my point of view, the main question is, whether we > > should merge the two GEs. I guess Boris (and Telecomitalia > > people) have some more (but related) points to discuss. > > > > For the semantic-related GEs, I do not know the open > > questions. Maybe you can clarify in the weekly confcall > > tomorrow morning. I cannot attend tomorrow morning, but > > Andreas will participate. (Please put the conclusions in the > > minutes. :-) > > > > Kind regards > > Peter > > > > > > > -----Original Message----- > > > From: Juanjo Hierro [mailto:jhierro at tid.es] > > > Sent: Donnerstag, 16. Juni 2011 15:51 > > > To: Moltchanov Boris > > > Cc: Amon, Peter; Tomas PAriente Lobo > > > Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics > > > (second part) > > > > > > > > > I'm a bit confused ... > > > > > > Weren't we trying to agree on a confcall dealing with > > > semantic-related GEs ? What do we need to discuss on multimedia > > > analysis and recognition ? > > > > > > Best regards, > > > > > > -- Juanjo > > > > > > On 16/06/11 14:35, Moltchanov Boris wrote: > > > > Dear Juanjo and Peter, > > > > > > > > I'm confirming the monday statuivi from 16:30 for the > > > discussion with Siemens about multimedia analysis and recognition. > > > > Juanjo, may you please set up usual powwownow and weber > > > session for that timeslot. > > > > > > > > I'm continuing to check about the semantic discussion and > > > that communication will follow. > > > > > > > > Br, > > > > Boris > > > > > > > > 16/giu/2011, ? 11:36, "Juanjo Hierro" > ???????(?): > > > > > > > >> Boris, > > > >> > > > >> May you try to setup a doodle on this ? > > > >> > > > >> Monday will be hard for me if earlier that 16:30. > > > Tuesday (whole > > > >> day), wednesday morning (until 13:00) or wednesday evening > > > (after 17:00) > > > >> would also work for me. > > > >> > > > >> Best regards, > > > >> > > > >> -- Juanjo > > > >> > > > >> On 16/06/11 10:52, Amon, Peter wrote: > > > >>> Hi Boris, hi Tom?s, > > > >>> > > > >>> Friday is also not perfect for me. I would be available > > > Mon/Tue/Wed next week (except some appointments at lunch time). > > > >>> > > > >>> (This concerns the confcall on "Multimedia Recognition" / > > > "Multimedia Analysis".) > > > >>> > > > >>> Kind regards > > > >>> Peter > > > >>> > > > >>> > > > >>> > > > >>>> -----Original Message----- > > > >>>> From: fiware-data-bounces at lists.fi-ware.eu > > > >>>> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of > > > >>>> Tomas PAriente Lobo > > > >>>> Sent: Donnerstag, 16. Juni 2011 10:44 > > > >>>> To: Moltchanov Boris; Juanjo Hierro; > > fiware-data at lists.fi-ware.eu > > > >>>> Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics > > > >>>> (second part) > > > >>>> > > > >>>> Hi Boris, > > > >>>> > > > >>>> Sorry, but we cannot make it this Friday. > > > >>>> > > > >>>> Cheers > > > >>>> > > > >>>> Tom?s > > > >>>> > > > >>>> Tom?s Pariente Lobo > > > >>>> Knowledge Lab > > > >>>> Atos Research and Innovation > > > >>>> C/Albarrac?n 25, 28037 Madrid (SPAIN) > > > >>>> Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 > > > >>>> http://www.atosresearch.eu > > > >>>> > > > >>>> > > > >>>> > > > >>>> -----Original Message----- > > > >>>> From: fiware-data-bounces at lists.fi-ware.eu > > > >>>> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of > > > >>>> Moltchanov Boris > > > >>>> Sent: mi?rcoles, 15 de junio de 2011 23:58 > > > >>>> To: Juanjo Hierro; fiware-data at lists.fi-ware.eu > > > >>>> Subject: Re: [Fiware-data] Confcall at 18:30 on Semantics > > > >>>> (second part) > > > >>>> > > > >>>> Dear Juanjo and Siemens and ATOS (and eventually > > other) partners, > > > >>>> > > > >>>> TI is able to participate in order to discuss this topic > > > >>>> (subject) on this Friday, starting from 15:00CET and later. > > > >>>> > > > >>>> Please let me know in time if this is feasible for you. > > > >>>> > > > >>>> Sorry for lost last communications, indeed the last email > > > >>>> (below) received very late to organize an operative action. > > > >>>> > > > >>>> 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: Tuesday, June 14, 2011 6:07 PM > > > >>>> To: fiware-data at lists.fi-ware.eu > > > >>>> Subject: [Fiware-data] Confcall at 18:30 on Semantics > > > (second part) > > > >>>> > > > >>>> Hi all, > > > >>>> > > > >>>> We would use the powwownow bridge: > > > >>>> > > > >>>> PIN: 050662 > > > >>>> > > > >>>> Dial-in phone numbers in the attachment. > > > >>>> > > > >>>> The main goal of this confcall is that Telecom Italia > > > >>>> explains their > > > >>>> contribution in the field. We will also brief those who > > > >>>> didn't attend > > > >>>> the confcall on monday about results of that meeting. > > > >>>> > > > >>>> I will check whether I can setup a webex, but I'm not > > > >>>> pretty sure I will be able to make it. > > > >>>> > > > >>>> 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 > > > >>>> > > > >>>> 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. > > > >>>> > > > >>>> _______________________________________________ > > > >>>> Fiware-data mailing list > > > >>>> Fiware-data at lists.fi-ware.eu > > > >>>> http://lists.fi-ware.eu/listinfo/fiware-data > > > >>>> > > > ------------------------------------------------------------------ > > > >>>> This e-mail and the documents attached are confidential > > > and intended > > > >>>> solely for the addressee; it may also be privileged. If > > > you receive > > > >>>> this e-mail in error, please notify the sender immediately > > > >>>> and destroy it. > > > >>>> As its integrity cannot be secured on the Internet, the > > > Atos Origin > > > >>>> group liability cannot be triggered for the message > > > content. Although > > > >>>> the sender endeavours to maintain a computer > > virus-free network, > > > >>>> the sender does not warrant that this transmission is > > > virus-free and > > > >>>> will not be liable for any damages resulting from any virus > > > >>>> transmitted. > > > >>>> > > > >>>> Este mensaje y los ficheros adjuntos pueden contener > > > >>>> informacion confidencial > > > >>>> destinada solamente a la(s) persona(s) mencionadas > > anteriormente > > > >>>> pueden estar protegidos por secreto profesional. > > > >>>> Si usted recibe este correo electronico por error, gracias > > > >>>> por informar > > > >>>> inmediatamente al remitente y destruir el mensaje. > > > >>>> Al no estar asegurada la integridad de este mensaje sobre la > > > >>>> red, Atos Origin > > > >>>> no se hace responsable por su contenido. Su contenido no > > > >>>> constituye ningun > > > >>>> compromiso para el grupo Atos Origin, salvo ratificacion > > > >>>> escrita por ambas partes. > > > >>>> Aunque se esfuerza al maximo por mantener su red libre de > > > >>>> virus, el emisor > > > >>>> no puede garantizar nada al respecto y no sera responsable de > > > >>>> cualesquiera > > > >>>> danos que puedan resultar de una transmision de virus. > > > >>>> > > > ------------------------------------------------------------------ > > > >>>> > > > >>>> _______________________________________________ > > > >>>> 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 > > > >> > > > > 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. > > > > > > > > > > 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. > > > > > > 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. > > 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 tomas.parientelobo at atosresearch.eu Fri Jun 24 07:57:37 2011 From: tomas.parientelobo at atosresearch.eu (Tomas PAriente Lobo) Date: Fri, 24 Jun 2011 07:57:37 +0200 Subject: [Fiware-data] TI will not be in the Friday call In-Reply-To: References: Message-ID: <9DA3EC560FF1564DB032154AC290954B056086E1@INTMAIL01.es.int.atosorigin.com> Dear partners, ATOS is in the same situation as TI. Chema and I are on holidays. I will try to connect from home, but I cannot guarantee it. Best regards Tom?s Tom?s Pariente Lobo Knowledge Lab Atos Research and Innovation C/Albarrac?n 25, 28037 Madrid (SPAIN) Tel. (+34) 91 214 8336 Fax. (+34) 91 754 3252 http://www.atosresearch.eu From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: mi?rcoles, 22 de junio de 2011 17:50 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] TI will not be in the Friday call Dear Partners, TI will not be able to participate in this Friday's audio-conference due to local holiday. I will check the minutes and proceed with our contributions as agreed during the last calls. Best Regards, Boris 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. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 566 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: From jhierro at tid.es Fri Jun 24 08:02:34 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 24 Jun 2011 08:02:34 +0200 Subject: [Fiware-data] Dial-in details for our weekly confcall Message-ID: <4E04287A.8090609@tid.es> Hi, Let's have a short one even if not all of us can attend. It may help us to identify some action to be done. Cortesy of IBM, as always. I'll send details about Webex, once I receive them. Cheers, -- Juanjo Participant Code: 8188850 France Caller Paid 0-170911580 France Toll-Free 0800-94-0558 Israel Toll-Free 1-809-417-783 USA Caller Paid 215-861-6239 USA Toll-Free 888-426-6840 For Other Countries: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=8188850&accessNumber=1809417783 ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 24 09:31:35 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 24 Jun 2011 09:31:35 +0200 Subject: [Fiware-data] Fwd: Meeting invitation: FI-WARE WP6 Data/Context weekly confcall Message-ID: <4E043D57.3060405@tid.es> Webex details -------- Original Message -------- Subject: Meeting invitation: FI-WARE WP6 Data/Context weekly confcall Date: Fri, 24 Jun 2011 08:57:03 +0200 From: Gestor i-Reunion webex6000 Reply-To: Webex6000 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex6000 invites you to attend this online meeting. Topic: FI-WARE WP6 Data/Context weekly confcall Date: Friday, June 24, 2011 Time: 9:30 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 967 857 275 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=154232022&UID=1216166432&PW=NM2RiNTFmNzAx&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=154232022&UID=1216166432&PW=NM2RiNTFmNzAx&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: Webex6000 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=154232022&UID=1216166432&ICS=MI&LD=1&RD=2&ST=1&SHA2=GB/xPTbliBPJ-Wmbzmpn5a-4AAw6mDOAtZtaGSmhRWE=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 24 10:48:04 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 24 Jun 2011 10:48:04 +0200 Subject: [Fiware-data] Fwd: IMPORTANT - Start of integration of FI-WARE High-level Description deliverable: next steps Message-ID: <4E044F44.5080205@tid.es> FYI, -- Juanjo -------- Original Message -------- Subject: IMPORTANT - Start of integration of FI-WARE High-level Description deliverable: next steps Date: Thu, 23 Jun 2011 09:04:32 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, I believe that all the Architecture Chapter teams have uploaded their contribution to the docman system. Thanks for your commitment and effort !! Now, I will start to integrate the different chapters into a single document and perform and overall review all the chapters while making the integration. My plan is to finish this process by monday June 27, EOB. What can teams do in the meantime ? My suggestion is that you work in the "Question Marks" section and give also a final review to the "terms and definitions" section if you had generated it in the last minute (I know it is the case for some teams :-) These two sections can be easily replaced in the integrated document. Regarding the "Question Marks" section, I would suggest to structure it into a subsection titled "Security aspects" and a subsection titled "Other topics still under discussion". * On "Security aspects": I suggest that you nominate one-two people in your team that work with the WP8 team to analyze contents of your chapter and identify Security questions. Please contact Pascal Bisson (pascal.bisson at thalesgroup.com), leader of WP8, to coordinate with him how to carry out this task. It is about identifying at least 3-5 issues, and describing each with one-two paragraphs. You can download the contribution linked to the Data/Context Management chapter and check the "Security aspects" subsection where you may find some reference examples (particularly the one on Privacy Management) * On "Other topics still under discussion": The idea is just formulate 3-5 topics for which discussion has not yet been finalized within the team. Try to elaborate on the different alternatives you are considering/discussing with respect to the topic as well as any consideration that is relevant. Each topic should be described similarly to how topics in the "Security aspects" subsection were described in the Data/Context Management chapter (again, the description of the Privacy Management issue is a good reference example). It is up to the WPL how to organize this task. Regarding the "terms and definitions" section, there isn't anything special to remark. But try to provide precise definitions. Also try to make this section something that can "work" relatively standalone. I expect your contributions to both sections by Tuesday June 29, 19:00 CET. IN ADDITION: I know that some of you still wish to work on the content of sections linked to the overview and description of GEs. How can you work in parallel to integration ? I would suggest the following: * In the placeholder under the contrib folder linked to your document you will always be able to find the last version of your chapter already integrated in the final document. * Whenever I start to work with a given chapter, I will change its status to "pending" (this is one of the valid status -like "private"- you can assign to a document in the form linked to an entry in the Admin section of the docman system). This will mean I have blocked it. You will detect that your contribution is pending because you wouldn't be able to see it in the folders/document tree that is displayed when you click on "View Documentation". You should then wait until I upload a new version (already integrated in the master document). Of course, you may still be working on some changes but then you should implement them individually over the file that I will finally upload to the docman system (that file may have comments or even changes and, for sure, some fixes in formatting I don't want to loose, so it won't be as simple as replace the file with the one you were working on in parallel to me). Whenever I upload a new version of the file, I will change its status to "private" and you will be able to see it in the folders/document tree. * If a document is not "pending", this mean that you can download it and work on it. But, PLEASE, whenever you plan to do so, please mark it also as "pending" before downloading, so that I can realize you will download it and start working on it. You only have the right to keep a document "pending" from 09:00am to 19:00pm. After 19:00 and until 09:00am the next day, I can change its status and replace the attached file without notice. In the event I need that you release the document -changing its state to "private" again- before 19:00, I'll let you know. * PLEASE, DON'T CREATE NEW ENTRIES: It should work with the already existing ones, changing the status and replacing the attached file when needed. I know that we would probably do it better using SVN but SVN got installed recently and many people don't have the time to get used to it. Despite it took some time, all WPLs already know how to manage the docman, so we should keep using docman for this release of the deliverable. For a number of reasons, I won't be able to start integration until 19:00 today (it's holiday in Spain) so you will find that all the contributions to each chapter are marked as "private", therefore, not blocked. Let's work hard to finish the document !! Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 24 10:48:24 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 24 Jun 2011 10:48:24 +0200 Subject: [Fiware-data] Fwd: Clarification on Question Marks section Message-ID: <4E044F58.3090101@tid.es> Also FYI, -- Juanjo -------- Original Message -------- Subject: Clarification on Question Marks section Date: Fri, 24 Jun 2011 10:40:26 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, In response to comments from some of the WPLs, I just want to comment that the "Question Marks" sections is not about describing the dependencies with other WPs. It's about declaring points that are still under discussion and therefore subject to change or refine. Of course, it may happen that some of those topics still under discussion may happen to be in relationship with areas of interdependencies with other WPs. You indeed may use "check for interdependencies with other WPs" as an "heuristic" to find out some topics you want to claim that are still under discussion or, simply, yet not addressed. But the section should not be targeted to describe interdependencies with other WPs. Besides, please check the style/extension of Security-related topics that I provided as an example in the Data-Context Management chapter. We shouldn't go for a long description or elaboration of topics, just a formulation of them. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Sat Jun 25 10:20:16 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sat, 25 Jun 2011 10:20:16 +0200 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Message-ID: <4E059A40.3020703@tid.es> Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: * Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) * Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server * All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 * Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. Cheers, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From p.amon at siemens.com Sat Jun 25 15:07:36 2011 From: p.amon at siemens.com (Amon, Peter) Date: Sat, 25 Jun 2011 15:07:36 +0200 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff In-Reply-To: <4E059A40.3020703@tid.es> References: <4E059A40.3020703@tid.es> Message-ID: Dear Juanjo, Boris, all, as requested in the phone call, I prepared an new version of the "Multimedia Analysis" GE and uploaded it under: https://forge.fi-ware.eu/docman/view.php/9/198/FI-WARE+High-Level+Desc+Data-Context+v2.0+11-06-22+valid+until+11-06-24_MultimediaAnalysis_v06.doc I started from the integrated version of the document provided by Juanjo on Wednesday. (Unfortunately, TI integrated in the very first version of the description, which is outdated some time already.) Still I believe I captured all changes proposed by TI. Also, all changes are traceable (separately for TI's and Siemens' contributions). I reordered the paragraphs for the "GE description" section from generic to specific: 1) Main characteristics (provided by TI) 2) Generic description (provided by Siemens): Please note that this description covers not only the Video Processor but the whole GE. I added an API component in the figure and the description to clarify this. 3) Detailed description (provided by TI) 4) Example realizations for GE (provided by Siemens) 5) Example component: Image Recognition Broker (provided by TI) I hope you like the new version. Comments are welcome of course. Boris/Walter, please check! 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: Samstag, 25. Juni 2011 10:20 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: * Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) * Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server * All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 * Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. Cheers, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From GUYSH at il.ibm.com Sun Jun 26 15:08:06 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Sun, 26 Jun 2011 16:08:06 +0300 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff In-Reply-To: <4E059A40.3020703@tid.es> References: <4E059A40.3020703@tid.es> Message-ID: 1. I reviewed the draft in the new version under the FI-WARE project Had to copy all my comments on BigData to this one which are focused mainly on the target usage. The description later I had less to comment as it describes TIDs asset which I take given. 2. As for Security - all my previous suggestions were related to trust and this is covered very generally in one of Juanjo's Security issues 3. I added two items under discussion a. The internal GE communication (I think this may be a general FI-WARE architecture point of discussion b. The stream vs. Event discussion 4. I added a comment on the terminology section on one of the last paragraphs explaining Data Event and Complex Event (wrapping data element and context element accordingly). I think this doesnt add anything and may just confuse. From CEP point of view there will need to be something \ someone that interprets the element as an event - there is no difference if this is context or data element and we dont need to treat the event differently if it wraps something else. - I say remove that paragraph. 5. I noticed that my comments on Intelligent Services are missing - here is just that section commented I uploaded my comments on the V2.0 here https://forge.fi-ware.eu/docman/view.php/9/205/FI-WARE+High-Level+Desc+Data-Context+v2.0+11-06-22+valid+until+11-06-24+comments+Guy.doc Regards, 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 From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 25/06/2011 11:20 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Sent by: fiware-data-bounces at lists.fi-ware.eu Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. 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[attachment "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE High-Level Description 11-06-1 v0.2 Intelligent Services comments Guy.doc Type: application/octet-stream Size: 1898496 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Mon Jun 27 13:20:09 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Mon, 27 Jun 2011 13:20:09 +0200 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff In-Reply-To: <4E059A40.3020703@tid.es> References: <4E059A40.3020703@tid.es> Message-ID: Dear Juanjo, All, May you or everyone who knows the answer provide me the link to the last release of the high level description document where we have freshest version of Security aspects/topics? I would like contribute there. Thank you. Best Regads, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Saturday, June 25, 2011 10:20 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: * Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) * Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server * All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 * Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Mon Jun 27 13:38:25 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Jun 2011 13:38:25 +0200 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff In-Reply-To: References: <4E059A40.3020703@tid.es> Message-ID: <4E086BB1.802@tid.es> Regarding Security aspects, I suggest that you consider the last integrated draft of our chapter (Data/Context Management Chapter) where I included some topics regarding security aspects as reference examples. They are in the docman system of the FI-WARE project (not FI-WARE data project) in FusionForge under FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs. If you want to add topics to that section or revise what is already there, please do so and and upload your contribution in our FI-WARE data internal docman system. Please just provide the text for the specific section. Best regards, -- Juanjo On 27/06/11 13:20, Moltchanov Boris wrote: Dear Juanjo, All, May you or everyone who knows the answer provide me the link to the last release of the high level description document where we have freshest version of Security aspects/topics? I would like contribute there. Thank you. Best Regads, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Saturday, June 25, 2011 10:20 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: * Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) * Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server * All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 * Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. 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 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:part1.09030701.07010700 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From p.amon at siemens.com Mon Jun 27 16:00:42 2011 From: p.amon at siemens.com (Amon, Peter) Date: Mon, 27 Jun 2011 16:00:42 +0200 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff In-Reply-To: References: <4E059A40.3020703@tid.es> Message-ID: Dear all, I uploaded a new version of the document ("Multimedia Analysis" GE) under the same link: https://forge.fi-ware.eu/docman/view.php/9/198/FI-WARE+High-Level+Desc+Data-Context+v2.0+11-06-22+valid+until+11-06-24_MultimediaAnalysis_v06.doc My colleague Marcus reviewed the document and did some minor changes (typos and some clarification). Kind regards Peter ________________________________ From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Amon, Peter Sent: Samstag, 25. Juni 2011 15:08 To: Juanjo Hierro; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Dear Juanjo, Boris, all, as requested in the phone call, I prepared an new version of the "Multimedia Analysis" GE and uploaded it under: https://forge.fi-ware.eu/docman/view.php/9/198/FI-WARE+High-Level+Desc+Data-Context+v2.0+11-06-22+valid+until+11-06-24_MultimediaAnalysis_v06.doc I started from the integrated version of the document provided by Juanjo on Wednesday. (Unfortunately, TI integrated in the very first version of the description, which is outdated some time already.) Still I believe I captured all changes proposed by TI. Also, all changes are traceable (separately for TI's and Siemens' contributions). I reordered the paragraphs for the "GE description" section from generic to specific: 1) Main characteristics (provided by TI) 2) Generic description (provided by Siemens): Please note that this description covers not only the Video Processor but the whole GE. I added an API component in the figure and the description to clarify this. 3) Detailed description (provided by TI) 4) Example realizations for GE (provided by Siemens) 5) Example component: Image Recognition Broker (provided by TI) I hope you like the new version. Comments are welcome of course. Boris/Walter, please check! 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: Samstag, 25. Juni 2011 10:20 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: * Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) * Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server * All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 * Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. Cheers, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Mon Jun 27 19:33:49 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Mon, 27 Jun 2011 19:33:49 +0200 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff In-Reply-To: <4E086BB1.802@tid.es> References: <4E059A40.3020703@tid.es> <4E086BB1.802@tid.es> Message-ID: I see that a lot of sections are not yet ultimately updated or not integrated in that document version. However, I've just uploaded a new version of this document at the https://forge.fi-ware.eu/docman/view.php/9/210/FI-WARE+High-Level+Desc+Data-Context+Security_Extended_TI.doc link, where I've inserted few sections within the 3.1.3 chapter and extended an existent one, all traced and marked by track changes. Best Regards, Boris From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Monday, June 27, 2011 1:38 PM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Regarding Security aspects, I suggest that you consider the last integrated draft of our chapter (Data/Context Management Chapter) where I included some topics regarding security aspects as reference examples. They are in the docman system of the FI-WARE project (not FI-WARE data project) in FusionForge under FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs. If you want to add topics to that section or revise what is already there, please do so and and upload your contribution in our FI-WARE data internal docman system. Please just provide the text for the specific section. Best regards, -- Juanjo On 27/06/11 13:20, Moltchanov Boris wrote: Dear Juanjo, All, May you or everyone who knows the answer provide me the link to the last release of the high level description document where we have freshest version of Security aspects/topics? I would like contribute there. Thank you. Best Regads, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Saturday, June 25, 2011 10:20 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: * Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) * Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server * All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 * Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. 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 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:image001.gif at 01CC3500.FCA2C6A0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Mon Jun 27 20:24:23 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Jun 2011 20:24:23 +0200 Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff In-Reply-To: References: <4E059A40.3020703@tid.es> <13649_1309178618_4E087AFA_13649_1904_1_f2cdb8f1-f886-46ac-9f3c-91c92ee206e0@THSONEA01HUB06P.one.grp> Message-ID: <4E08CAD7.6000402@tid.es> Dear Pascal and Boris, The Security team produced an initial document that is the one Pascal referred in his mail. That document was indeed a good starting point, as I already commented to Pascal, but as I told him there were many of the identified issues that are transversal over many GEs so that the format for the "Security aspects" section should not be that one but the one I produced (which was indeed distilled from the input from their document) Note that because of that reason, we provided the existing draft of the "Security aspects" in the Data/Context Management chapter as a reference example for that section to the other WPs. Of course, I didn't capture in that draft all the aspects mentioned in the original document from the Security team. Partly because I didn't agree with some of them, partly because I didn't understand some of them, partly because I didn't have enough time. That's why we are entering a now a task force together with the Security team trying to finalize the section. For the avoidance of any doubt, the kind of additional input I'm seeking for in the "Security aspects" section is like the one you have produced. So I indeed plan to incorporate your contributions in the next draft of the Data/Context Mananagement Chapter. I would kindly ask the security team and the rest of partners if they still believe there are some Security aspects missing. If so, let's discuss on them over the mail and try to write the corresponding contribution. Of course, if you don't agree with anything that would be there once TI's input is incorporated, let's discuss it. Hope this email answers most of the questions. BR, -- Juanjo On 27/06/11 19:39, Moltchanov Boris wrote: Dear Pascal, Thank you for your very prompt reaction on my communication regarding security topics within WP6. In order to be more productive and safe time, may you please have a look at the just uploaded document https://forge.fi-ware.eu/docman/view.php/9/210/FI-WARE+High-Level+Desc+Data-Context+Security_Extended_TI.doc , where I have extended the section 3.1.3 (traced) and extract the high-level security requirements from there? I believe that many security requirements are transversal over more GEs therefore those reqs within the document indicated by you shall be still reorganized merging into global FI-WARE and specific GE?s security requirements, while in the section 3.1.3 of the WP6 document we have already a list of the ?generic? security requirements that shall be supported by whole FI-WARE platform on application or data request. Anyway, let me know if I?m wrong and I will try to improve my vision. Best Regards, Boris From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: Monday, June 27, 2011 2:43 PM To: Moltchanov Boris Cc: GIDOIN Daniel; BISSON Pascal; Antonio Garcia Vazquez; Marton, Gabor (NSN - HU/Budapest); Juanjo Hierro Subject: RE: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Dear Boris, In complement of Juanjo?s email here is the document with Security issues we WP8 (through appointed representatives in cc ATOS, THA and NSN) identified based on WP6 input document. >From this document should be inferred what we would insert in WP6 input document for what concerns Questions marks on Security issues. Would be nice if you could review and help us to converge where the security issues on which we can agree from both sides WP6 & WP8. Hearing from you and counting on you to support us in this. Best Regards, Pascal. PS: Of course things should be re-drafted according to the example provided by Juanjo (see text inserted in latest version of WP6 input document for Privacy management). De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Moltchanov Boris Envoy? : lundi 27 juin 2011 13:20 ? : Juanjo Hierro; fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Dear Juanjo, All, May you or everyone who knows the answer provide me the link to the last release of the high level description document where we have freshest version of Security aspects/topics? I would like contribute there. Thank you. Best Regads, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Saturday, June 25, 2011 10:20 AM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Data/Context Management WP weekly follow-up confcall 11-06-24 and other stuff Hi all, Sorry for the delay in sending the minutes, but yesterday was a very busy day for me. Yesterday, only Peter (Siemens), Guy (IBM) and myself joined the confcall since it was holidays in most countries or people had taken the day off. The following actions were agreed during the confcall: * Peter will review the contribution of Telecom Italia on multimedia analysis and will integrate in the description of the multimedia analysis GE those points that he believes will not be controversial. He will develop a paragraph (or several if it is appropriate to do so) in the "Topics still under discussion" of the "Question Marks" section for those points that he finds cannot be yet incorporated and require further discussion. The current draft of the chapter you can download from the FI-WARE project (folder FI-WARE deliverables-> D2.2. FI-WARE High-level Description->D2.2 contribs) contains the description of topics related to Security that could serve as a reference example and guide how to write contributions to the "Topics still under discussion" section. I would kindly ask Peter to provide a revised version of the section by Tuesday June 29, EOB (it would be preferable that it be available on Monday, but can wait until Tuesday) * Guy will review the new draft of section on BigData Analysis in the new version of the chapter uploaded to the server * All should review the description of the different GEs and identify potential topics to be described in the "Topics still under discussion" or "Security aspects" subsections of the "Question Marks" section. Again, entries already there in the "Security aspects" section can serve as reference examples of the kind of content we intend to have there. As explained in one of the emails I sent to all WPLs and forwarded to you, you may think about interdedependencies with another WPs as one valid "heuristic" to identify topics. Others can be related to points you believe cannot be considered yet closed. Deadline for sending contributions to the "Question Marks" section is Tuesday June 29, 19:00 * Guy produced a description of some security topics to be included in the "Question Marks" section some time ago. He will review the current content of the "Security aspects" subsection in "Question Marks" and will determine if some additional entries can/should be added. If Peter or Guy miss something, please let me know. Now, in addition to what was treated during the confcall: You will find that the chapter draft uploaded to the server doesn't still include all contributions developed so far. I have to still analyze those not yet included. I can anticipate that there will be some of them that will not be included in the first release of the FI-WARE High-level Description because they will require further discussion or they are not still at the level of development to be included. That shouldn't be so much an issue. The FI-WARE High-level description that really should count is the one to be delivered by end of September. This first one has to contain the major pieces but I believe it already contains them. I still has to finalize the Overview section of the chapter and will provide a version of the "Terms and Definitions" section. He will try to do this over the weekend. 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 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:part1.01090805.09080600 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. 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:part2.03040203.01010903 at tid.es]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image/gif Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Thu Jun 30 16:59:58 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 Jun 2011 16:59:58 +0200 Subject: [Fiware-data] Updated version of sections in the Data/Context Management Chapter Message-ID: <4E0C8F6E.9000405@tid.es> Hi all, Currently, it's a little bit complex to follow what are the last pieces that I should take for integration in the next consolidated draft of our FI-WARE chapter. I would kindly ask you to upload your last contributions (just the section, not the whole chapter) in the contribs subfolder (group) I have just created under the D2.2 folder (group) ... Thanks and best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Thu Jun 30 18:48:44 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 30 Jun 2011 18:48:44 +0200 Subject: [Fiware-data] Updated version of sections in the Data/Context Management Chapter In-Reply-To: <4E0C8F6E.9000405@tid.es> References: <4E0C8F6E.9000405@tid.es> Message-ID: I've changed contribs to private and added 7 documents of TI competence (with other partners however). Please check if the sections are the last versions agreed with their respective cooperative partners and two documents have to be checked/extended: one about the data/context/event structure that is under Juanjo resp. and the location GE that has to be still discussed, agreed, extended and integrated with Thales. For the moment file names consist of Boris__.docx, that makes it clear who added document about what and agreed/compiled with whom, as far as we still don't have subversioning. 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, June 30, 2011 5:00 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Updated version of sections in the Data/Context Management Chapter Hi all, Currently, it's a little bit complex to follow what are the last pieces that I should take for integration in the next consolidated draft of our FI-WARE chapter. I would kindly ask you to upload your last contributions (just the section, not the whole chapter) in the contribs subfolder (group) I have just created under the D2.2 folder (group) ... Thanks and 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. From jhierro at tid.es Thu Jun 30 21:33:31 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 Jun 2011 21:33:31 +0200 Subject: [Fiware-data] Weekly confcall tomorrow Message-ID: <4E0CCF8B.10701@tid.es> Hi all, Due to personal reasons, I won't be able to attend a confcall on the scheduled time. The only slots available would be from 14:30pm until 17:00 ... I will schedule the confcall from 15:00 to 16:00 unless I hear from you something different. Please confirm who would be able to attend. Best regards, -- Juanjo Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From GUYSH at il.ibm.com Thu Jun 30 21:39:08 2011 From: GUYSH at il.ibm.com (Guy Sharon) Date: Thu, 30 Jun 2011 22:39:08 +0300 Subject: [Fiware-data] Weekly confcall tomorrow In-Reply-To: <4E0CCF8B.10701@tid.es> References: <4E0CCF8B.10701@tid.es> Message-ID: I can only do mornings on Friday I will not be able to join as scheduled 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 From: Juanjo Hierro To: "fiware-data at lists.fi-ware.eu" Date: 30/06/2011 22:33 Subject: [Fiware-data] Weekly confcall tomorrow Sent by: fiware-data-bounces at lists.fi-ware.eu Hi all, Due to personal reasons, I won't be able to attend a confcall on the scheduled time. The only slots available would be from 14:30pm until 17:00 ... I will schedule the confcall from 15:00 to 16:00 unless I hear from you something different. Please confirm who would be able to attend. 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 [attachment "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] _______________________________________________ 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/gif Size: 2558 bytes Desc: not available URL: From p.amon at siemens.com Thu Jun 30 23:30:06 2011 From: p.amon at siemens.com (Amon, Peter) Date: Thu, 30 Jun 2011 23:30:06 +0200 Subject: [Fiware-data] Weekly confcall tomorrow In-Reply-To: <4E0CCF8B.10701@tid.es> References: <4E0CCF8B.10701@tid.es> Message-ID: Hi Juanjo, I would also be available in the afternoon. Andreas might not be (or only partially). Kind regards 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, 30. Juni 2011 21:34 > To: fiware-data at lists.fi-ware.eu > Subject: [Fiware-data] Weekly confcall tomorrow > > Hi all, > > Due to personal reasons, I won't be able to attend a > confcall on the > scheduled time. > > The only slots available would be from 14:30pm until 17:00 ... > > I will schedule the confcall from 15:00 to 16:00 unless I hear from > you something different. Please confirm who would be able to attend. > > 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 Thu Jun 30 23:54:53 2011 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 30 Jun 2011 23:54:53 +0200 Subject: [Fiware-data] Weekly confcall tomorrow In-Reply-To: <4E0CCF8B.10701@tid.es> References: <4E0CCF8B.10701@tid.es> Message-ID: <15B01CBB-C80F-41BD-BAF5-D7348AF83F28@telecomitalia.it> I have already a meeting in that slot, however will try to reschedule that meeting thus participate in the afternoon call. BR, Boris Waiting for the call details 30/giu/2011, ? 21:33, "Juanjo Hierro" ???????(?): > Hi all, > > Due to personal reasons, I won't be able to attend a confcall on the > scheduled time. > > The only slots available would be from 14:30pm until 17:00 ... > > I will schedule the confcall from 15:00 to 16:00 unless I hear from > you something different. Please confirm who would be able to attend. > > 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.