From Tim.Jonischkat at paluno.uni-due.de Wed Feb 1 13:43:42 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Wed, 1 Feb 2012 12:43:42 +0000 Subject: [Fiware-tools] IMPORTANT - Minutes draft In-Reply-To: <4F281730.9000106@eng.it> References: <4F281730.9000106@eng.it> Message-ID: <613708793959FC4A890C040BF1CF7ABA11185C46@WIWINF-EXDAG01.wiwinf.uni-due.de> Hi Davide, I am UDE's representative concerning SVN commits! The Minutes are fine from our side, except for the fact that AP-2 is closed for us. Cheers Tim Von: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] Im Auftrag von Davide Dalle Carbonare Gesendet: Dienstag, 31. Januar 2012 17:31 An: fiware-tools at lists.fi-ware.eu Betreff: [Fiware-tools] IMPORTANT - Minutes draft Dear Partners, please find attached the today meeting minutes. Pay attention to the Action Points identified and provide your comments as soon as possible Some additional information: For the AP-3, provide the contributions on the private copy, of the DevComE document, that you can find on the Tools private wiki at https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#DevComE_Infrastructure - Avoid any changes to the public version because it will be overridden by the private copy as soon as this one will be ready. - If you change the images remember to change also the file name otherwise the public document will show the updated ones (the images are shared among all the wikis) - In order to address the architecture requirements for the FI-WARE Architecture deliverable I propose to start from the Architecture chapter we already have and move to another chapter (4. Tools) the functional features of every specific tool and leave into the Architecture chapter only the architectural aspects. This way at the end we can just use this chapter as contribution to the overall architecture. SVN commit issue: please provide one representative person per parter that will receive the admin role in order to be able to commit into the SVN repository. thank you for having read until the end ... ciao, Davide -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Wed Feb 1 14:03:44 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 01 Feb 2012 14:03:44 +0100 Subject: [Fiware-tools] IMPORTANT - Minutes draft In-Reply-To: <613708793959FC4A890C040BF1CF7ABA11185C46@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <4F281730.9000106@eng.it> <613708793959FC4A890C040BF1CF7ABA11185C46@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <4F293830.4060904@eng.it> Tim, On 01/02/2012 13:43, Jonischkat, Tim wrote: > > I am UDE's representative concerning SVN commits! > ok, now as admin you can commit and organize your work under the trunk folder, let me know if the folder structure is already fine with your needs or you need something different ciao D > > The Minutes are fine from our side, except for the fact that AP-2 is > closed for us. > good! > > Cheers > > Tim > > *Von:*fiware-tools-bounces at lists.fi-ware.eu > [mailto:fiware-tools-bounces at lists.fi-ware.eu] *Im Auftrag von *Davide > Dalle Carbonare > *Gesendet:* Dienstag, 31. Januar 2012 17:31 > *An:* fiware-tools at lists.fi-ware.eu > *Betreff:* [Fiware-tools] IMPORTANT - Minutes draft > > Dear Partners, > please find attached the today meeting minutes. > > Pay attention to the Action Points identified and provide your comments > as soon as possible > > Some additional information: > > For the AP-3, provide the contributions on the private copy, of the > DevComE document, > that you can find on the Tools private wiki at > https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#DevComE_Infrastructure > - Avoid any changes to the public version because it will be overridden by > the private copy as soon as this one will be ready. > - If you change the images remember to change also the file name > otherwise > the public document will show the updated ones (the images are > shared among all the wikis) > - In order to address the architecture requirements for the FI-WARE > Architecture deliverable > I propose to start from the Architecture chapter we already have > and move to another chapter > (4. Tools) the functional features of every specific tool and > leave into the Architecture chapter only > the architectural aspects. This way at the end we can just use > this chapter as contribution to > the overall architecture. > > SVN commit issue: please provide one representative person per parter > that will receive the admin > role in order to be able to commit into the SVN repository. > > thank you for having read until the end ... > ciao, > Davide > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Wed Feb 1 14:23:09 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Feb 2012 14:23:09 +0100 Subject: [Fiware-tools] Wp8 - Wp9 bilateral meeting Message-ID: <4F293CBD.80807@eng.it> Dear Pascal, please have a look at the attached minutes and let me know if they are exhaustive or something is missing or misinterpreted. Thanks and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Minutes (bilateral Wp8-Wp9) 01-12.doc Type: application/msword Size: 208384 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Wed Feb 1 14:38:44 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Feb 2012 14:38:44 +0100 Subject: [Fiware-tools] Minutes of the f2f Wp5-6 and Wp9 Message-ID: <4F294064.1050705@eng.it> Dear Den?, Thierry and Carlos, it would be very appreciated if you can complete the list of participants in the attached minutes and if you can check that all the points discussed have been properly reported. Thanks a lot in advance and best regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Minutes (bilateral Wp5-6 - Wp9) 01-12.doc Type: application/msword Size: 208896 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From denes.bisztray at nsn.com Wed Feb 1 14:41:24 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 1 Feb 2012 14:41:24 +0100 Subject: [Fiware-tools] Minutes of the f2f Wp5-6 and Wp9 In-Reply-To: <4F294064.1050705@eng.it> References: <4F294064.1050705@eng.it> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD057BA1B5@DEMUEXC013.nsn-intra.net> Hi Matteo, As far as I remember the participants on our side were: Thierry Nagellen, Orange D?nes Bisztray, NSN Tobias Jacobs, NEC Ricardo des las Heras, Telef?nica Maarten Los, Atos I believe the Ericsson guys were not present on this meeting. From: ext Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: Wednesday, February 01, 2012 2:39 PM To: Bisztray, Denes (NSN - HU/Budapest); thierry.nagellen at orange-ftgroup.com; ralli at tid.es Cc: WP9_fi-ware Subject: Minutes of the f2f Wp5-6 and Wp9 Dear Den?, Thierry and Carlos, it would be very appreciated if you can complete the list of participants in the attached minutes and if you can check that all the points discussed have been properly reported. Thanks a lot in advance and best regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Wed Feb 1 14:47:05 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Feb 2012 14:47:05 +0100 Subject: [Fiware-tools] Minutes of the f2f Wp5-6 and Wp9 In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD057BA1B5@DEMUEXC013.nsn-intra.net> References: <4F294064.1050705@eng.it> <3F4C11BC54A36642BFB5875D599F47BD057BA1B5@DEMUEXC013.nsn-intra.net> Message-ID: <4F294259.1000504@eng.it> Thanks and what about the contents? BR, M. On mercoled? 1 febbraio 2012 14:41:24, Bisztray, Denes (NSN - HU/Budapest) wrote: > Hi Matteo, > > As far as I remember the participants on our side were: > > Thierry Nagellen, Orange > > D?nes Bisztray, NSN > > Tobias Jacobs, NEC > > Ricardo des las Heras, Telef?nica > > Maarten Los, Atos > > I believe the Ericsson guys were not present on this meeting. > > *From:*ext Matteo Melideo [mailto:matteo.melideo at eng.it] > *Sent:* Wednesday, February 01, 2012 2:39 PM > *To:* Bisztray, Denes (NSN - HU/Budapest); > thierry.nagellen at orange-ftgroup.com; ralli at tid.es > *Cc:* WP9_fi-ware > *Subject:* Minutes of the f2f Wp5-6 and Wp9 > > Dear Den?, Thierry and Carlos, > it would be very appreciated if you can complete the list of > participants in the attached minutes and if you can check that all the > points discussed have been properly reported. > > Thanks a lot in advance and best regards, > > Matteo > -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From matteo.melideo at eng.it Wed Feb 1 14:56:40 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Feb 2012 14:56:40 +0100 Subject: [Fiware-tools] Wp7 and Wp9 bilateral meeting Message-ID: <4F294498.7020509@eng.it> Dear Pierangelo and Hans could you please complete the attached minuted with the list of participants from your side and control if we forgot something. Thanks and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Minutes (bilateral Wp7 - Wp9) 01-12.doc Type: application/msword Size: 206336 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Wed Feb 1 16:11:11 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Feb 2012 16:11:11 +0100 Subject: [Fiware-tools] Reviewers comments to seriously take into account ... Message-ID: <4F29560F.703@eng.it> Dear All, I forgot to mention that last week in Madrid I took part to the Exploitation and Dissemination Wp and I started to strongly push the calatogue as a means to advertise the project results. What I did goes in the direction of what the reviewers asked us: "FI-WARE has a long-term legacy; exploitation plans should include means to encourage third-party developers to build components and instances using the development environment." In this respect, I ask those parters who already has such experience (e.g. EAB, SAP or IBM) to help in defining a winning exploitation strategy for us. We are anyway working for this by involving open source communities. Regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Wed Feb 1 16:39:36 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Feb 2012 16:39:36 +0100 Subject: [Fiware-tools] **** URGENT **** Fwd: [Fiware-wpl] Standardization In-Reply-To: References: Message-ID: <4F295CB8.8040708@eng.it> If you have any information to provide please do not hesitate. Thanks and regards, M. -------- Messaggio originale -------- Oggetto: [Fiware-wpl] Standardization Data: Wed, 01 Feb 2012 08:18:18 +0100 Mittente: thierry.nagellen at orange.com A: fiware-wpl at lists.fi-ware.eu, fiware-wpa at lists.fi-ware.eu CC: Ernoe.Kovacs at neclab.eu Dear all, On behalf of NEC, do not forget standardization deliverable: one action per partner and one action per WPL (a whole introduction to describe how your WPs expect to deal with standardization) We missed the deadline which was yesterday so we have to improve it ASAP. BR *Thierry Nagellen* */Program Manager Future Internet/* *Orange Labs Networks & Carriers* 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84+33 679 85 08 44 *New email address: *thierry.nagellen at orange.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2012-01-25 FI-WARE Standardization_Request.pptx Type: application/octet-stream Size: 761098 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware_Input_for_Standardisation_Plan_5AnswersFrom26_20120125.docx Type: application/octet-stream Size: 284478 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Parte allegato al messaggio URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Wed Feb 1 17:33:28 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Wed, 1 Feb 2012 17:33:28 +0100 Subject: [Fiware-tools] IMPORTANT - Minutes draft In-Reply-To: <4F281730.9000106@eng.it> Message-ID: Thanks Davide. I concerned about putting the effort to "demo" the tools every month. I believe it's too frequent. Couldn't we do it every third month? Cheers, Roozbeh From: Davide Dalle Carbonare > Date: Tue, 31 Jan 2012 17:30:40 +0100 To: "fiware-tools at lists.fi-ware.eu" > Subject: [Fiware-tools] IMPORTANT - Minutes draft Dear Partners, please find attached the today meeting minutes. Pay attention to the Action Points identified and provide your comments as soon as possible Some additional information: For the AP-3, provide the contributions on the private copy, of the DevComE document, that you can find on the Tools private wiki at https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#DevComE_Infrastructure - Avoid any changes to the public version because it will be overridden by the private copy as soon as this one will be ready. - If you change the images remember to change also the file name otherwise the public document will show the updated ones (the images are shared among all the wikis) - In order to address the architecture requirements for the FI-WARE Architecture deliverable I propose to start from the Architecture chapter we already have and move to another chapter (4. Tools) the functional features of every specific tool and leave into the Architecture chapter only the architectural aspects. This way at the end we can just use this chapter as contribution to the overall architecture. SVN commit issue: please provide one representative person per parter that will receive the admin role in order to be able to commit into the SVN repository. thank you for having read until the end ... ciao, Davide From matteo.melideo at eng.it Wed Feb 1 17:38:41 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Feb 2012 17:38:41 +0100 Subject: [Fiware-tools] IMPORTANT - Minutes draft In-Reply-To: References: Message-ID: <4F296A91.6010209@eng.it> Dear Roozbeh, M12 is quite close, the review is arriving and we do not have too much time to react in case of problems. Please, makes me happy, I want to see the progress every end of month. After the review we can relax a bit. Thanks and regards, Matteo Il 01/02/2012 17:33, Farahbod, Roozbeh ha scritto: > Thanks Davide. > > I concerned about putting the effort to "demo" the tools every month. I believe it's too frequent. Couldn't we do it every third month? > > Cheers, > Roozbeh > > From: Davide Dalle Carbonare> > Date: Tue, 31 Jan 2012 17:30:40 +0100 > To: "fiware-tools at lists.fi-ware.eu"> > Subject: [Fiware-tools] IMPORTANT - Minutes draft > > Dear Partners, > please find attached the today meeting minutes. > > Pay attention to the Action Points identified and provide your comments > as soon as possible > > Some additional information: > > For the AP-3, provide the contributions on the private copy, of the DevComE document, > that you can find on the Tools private wiki at > https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#DevComE_Infrastructure > - Avoid any changes to the public version because it will be overridden by > the private copy as soon as this one will be ready. > - If you change the images remember to change also the file name otherwise > the public document will show the updated ones (the images are shared among all the wikis) > - In order to address the architecture requirements for the FI-WARE Architecture deliverable > I propose to start from the Architecture chapter we already have and move to another chapter > (4. Tools) the functional features of every specific tool and leave into the Architecture chapter only > the architectural aspects. This way at the end we can just use this chapter as contribution to > the overall architecture. > > SVN commit issue: please provide one representative person per parter that will receive the admin > role in order to be able to commit into the SVN repository. > > thank you for having read until the end ... > ciao, > Davide > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From Tim.Jonischkat at paluno.uni-due.de Wed Feb 1 18:04:57 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Wed, 1 Feb 2012 17:04:57 +0000 Subject: [Fiware-tools] T9.3 Architecture (updated) Message-ID: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> Dear partners, please review the attached architecture draft for T9.3 - Please let me know - especially for the deployment tool - if there is any misconception. @Matteo/Davide: would you propose to make one diagram for all tasks? And: could you please check if that format is editable for you? Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: T9.3-Architecture-v03.ppt Type: application/vnd.ms-powerpoint Size: 281600 bytes Desc: T9.3-Architecture-v03.ppt URL: From pascal.bisson at thalesgroup.com Thu Feb 2 11:08:51 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 2 Feb 2012 11:08:51 +0100 Subject: [Fiware-tools] Wp8 - Wp9 bilateral meeting In-Reply-To: <4F293CBD.80807@eng.it> References: <4F293CBD.80807@eng.it> Message-ID: <32673_1328177335_4F2A60B7_32673_13107_1_CBBCD6C304123F4AB23FAAE3055C8C0E020645461A64@THSONEA01CMS04P.one.grp> Dear Matteo, Thanks for the minutes. Attached is the document with the revisions I propose. Best Regards, Pascal De : Matteo Melideo [mailto:matteo.melideo at eng.it] Envoy? : mercredi 1 f?vrier 2012 14:23 ? : BISSON Pascal Cc : WP9_fi-ware Objet : Wp8 - Wp9 bilateral meeting Dear Pascal, please have a look at the attached minutes and let me know if they are exhaustive or something is missing or misinterpreted. Thanks and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Minutes (bilateral Wp8-Wp9) 01-12-reV-THA.doc Type: application/msword Size: 207360 bytes Desc: FI-WARE Minutes (bilateral Wp8-Wp9) 01-12-reV-THA.doc URL: From davide.dallecarbonare at eng.it Thu Feb 2 11:14:15 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Thu, 02 Feb 2012 11:14:15 +0100 Subject: [Fiware-tools] IMPORTANT - Minutes draft In-Reply-To: <4F2A4AE6.4090907@eng.it> References: <4F281730.9000106@eng.it> <4F2A4AE6.4090907@eng.it> Message-ID: <4F2A61F7.10402@eng.it> I resend my last message ... the mailing list had some problems this morning ciao Davide On 02/02/2012 09:35, Davide Dalle Carbonare wrote: > Dear partners, > yesterday, reviewing the Architecture chapter of the DevComE technical > description > we have considered not necessary to proceed with the proposal to spit the > architecture and the functional aspects of the tools we are providing. > Let's keep the single chapter and update it directly mainly on: > - Catalogue (@EAB) > - Deploy (@ENG) > > let me know if you have comments or questions. > > cheers, > Davide > > On 31/01/2012 17:30, Davide Dalle Carbonare wrote: >> Dear Partners, >> please find attached the today meeting minutes. >> >> Pay attention to the Action Points identified and provide your comments >> as soon as possible >> >> Some additional information: >> >> For the AP-3, provide the contributions on the private copy, of the >> DevComE document, >> that you can find on the Tools private wiki at >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#DevComE_Infrastructure >> - Avoid any changes to the public version because it will be >> overridden by >> the private copy as soon as this one will be ready. >> - If you change the images remember to change also the file name >> otherwise >> the public document will show the updated ones (the images are >> shared among all the wikis) >> - In order to address the architecture requirements for the FI-WARE >> Architecture deliverable >> I propose to start from the Architecture chapter we already have >> and move to another chapter >> (4. Tools) the functional features of every specific tool and >> leave into the Architecture chapter only >> the architectural aspects. This way at the end we can just use >> this chapter as contribution to >> the overall architecture. >> >> SVN commit issue: please provide one representative person per parter >> that will receive the admin >> role in order to be able to commit into the SVN repository. >> >> thank you for having read until the end ... >> ciao, >> Davide >> >> >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Thu Feb 2 11:59:59 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 02 Feb 2012 11:59:59 +0100 Subject: [Fiware-tools] T9.3 Architecture (updated) In-Reply-To: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <4F2A6CAF.40302@eng.it> Thanks Tim. The idea is to provide a general architecture embracing the all DevCommE then we can enter into the details of each specific part where and if necessary. Concerning the second question, I will leave Davide to provide you and answer. Best, M. Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: > > Dear partners, > > please review the attached architecture draft for T9.3 -- > > Please let me know -- especially for the deployment tool -- if there > is any misconception. > > @Matteo/Davide: would you propose to make one diagram for all tasks? > And: could you please check if that format is editable for you? > > Cheers > > Tim > > --- > > Tim Jonischkat > > paluno - The Ruhr Institute for Software Technology > > University of Duisburg-Essen > > Gerlingstra?e 16 > > 45127 Essen, Germany > > T: +49 201 183 4659 > > F: +49 201 183 4699 > > E: tim.jonischkat at paluno.uni-due.de > > > http://www.paluno.uni-due.de / > > http://www.sse.uni-due.de > > VAT ID: DE811272995 > > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Thu Feb 2 09:35:50 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Thu, 02 Feb 2012 09:35:50 +0100 Subject: [Fiware-tools] IMPORTANT - Minutes draft In-Reply-To: <4F281730.9000106@eng.it> References: <4F281730.9000106@eng.it> Message-ID: <4F2A4AE6.4090907@eng.it> Dear partners, yesterday, reviewing the Architecture chapter of the DevComE technical description we have considered not necessary to proceed with the proposal to spit the architecture and the functional aspects of the tools we are providing. Let's keep the single chapter and update it directly mainly on: - Catalogue (@EAB) - Deploy (@ENG) let me know if you have comments or questions. cheers, Davide On 31/01/2012 17:30, Davide Dalle Carbonare wrote: > Dear Partners, > please find attached the today meeting minutes. > > Pay attention to the Action Points identified and provide your comments > as soon as possible > > Some additional information: > > For the AP-3, provide the contributions on the private copy, of the > DevComE document, > that you can find on the Tools private wiki at > https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#DevComE_Infrastructure > - Avoid any changes to the public version because it will be overridden by > the private copy as soon as this one will be ready. > - If you change the images remember to change also the file name > otherwise > the public document will show the updated ones (the images are > shared among all the wikis) > - In order to address the architecture requirements for the FI-WARE > Architecture deliverable > I propose to start from the Architecture chapter we already have > and move to another chapter > (4. Tools) the functional features of every specific tool and > leave into the Architecture chapter only > the architectural aspects. This way at the end we can just use > this chapter as contribution to > the overall architecture. > > SVN commit issue: please provide one representative person per parter > that will receive the admin > role in order to be able to commit into the SVN repository. > > thank you for having read until the end ... > ciao, > Davide > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Thu Feb 2 14:53:58 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Thu, 02 Feb 2012 14:53:58 +0100 Subject: [Fiware-tools] T9.3 Architecture (updated) In-Reply-To: <4F2A6CAF.40302@eng.it> References: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> <4F2A6CAF.40302@eng.it> Message-ID: <4F2A9576.50009@eng.it> Tim, the architecture is fine. Maybe I would rename the "FI-WARE Instance" in "FI-WARE Testbed". Once it's ready you can upload it into the SVN repository, I'm storing all the diagrams into trunk/design/diagrams I'm going to produce the general diagram and the one for T9.1 @EAB please provide the T9.2 (Catalogue) update architecture diagram by February 6th you can easily find the FMC notation on the already created diagrams into the SVN ... they are in grapgml, I'm using yEd http://www.yworks.com/en/products_yed_about.html Me and Matteo are inserting the tickets and the tasks into the forge but there are still some platform problems ... we close this activity as soon as possible. ciao Davide On 02/02/2012 11:59, Matteo Melideo wrote: > Thanks Tim. > The idea is to provide a general architecture embracing the all > DevCommE then we can enter into the details of each specific part > where and if necessary. > > Concerning the second question, I will leave Davide to provide you and > answer. > > Best, > > M. > > > Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: >> >> Dear partners, >> >> please review the attached architecture draft for T9.3 -- >> >> Please let me know -- especially for the deployment tool -- if there >> is any misconception. >> >> @Matteo/Davide: would you propose to make one diagram for all tasks? >> And: could you please check if that format is editable for you? >> >> Cheers >> >> Tim >> >> --- >> >> Tim Jonischkat >> >> paluno - The Ruhr Institute for Software Technology >> >> University of Duisburg-Essen >> >> Gerlingstra?e 16 >> >> 45127 Essen, Germany >> >> T: +49 201 183 4659 >> >> F: +49 201 183 4699 >> >> E: tim.jonischkat at paluno.uni-due.de >> >> >> http://www.paluno.uni-due.de / >> >> http://www.sse.uni-due.de >> >> VAT ID: DE811272995 >> >> >> >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tim.Jonischkat at paluno.uni-due.de Thu Feb 2 15:01:01 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Thu, 2 Feb 2012 14:01:01 +0000 Subject: [Fiware-tools] T9.3 Architecture (updated) In-Reply-To: <4F2A9576.50009@eng.it> References: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> <4F2A6CAF.40302@eng.it> <4F2A9576.50009@eng.it> Message-ID: <613708793959FC4A890C040BF1CF7ABA1118610F@WIWINF-EXDAG01.wiwinf.uni-due.de> Hey Davide, how about the following solution: You take the updated diagram attached and merge it with the architectural components from T9.1 and T9.2. Then we have that integrated diagram Matteo spoke of. One for the whole chapter. What do you think? Tim Von: Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] Gesendet: Donnerstag, 2. Februar 2012 14:54 An: Jonischkat, Tim Cc: fiware-tools at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture (updated) Tim, the architecture is fine. Maybe I would rename the "FI-WARE Instance" in "FI-WARE Testbed". Once it's ready you can upload it into the SVN repository, I'm storing all the diagrams into trunk/design/diagrams I'm going to produce the general diagram and the one for T9.1 @EAB please provide the T9.2 (Catalogue) update architecture diagram by February 6th you can easily find the FMC notation on the already created diagrams into the SVN ... they are in grapgml, I'm using yEd http://www.yworks.com/en/products_yed_about.html Me and Matteo are inserting the tickets and the tasks into the forge but there are still some platform problems ... we close this activity as soon as possible. ciao Davide On 02/02/2012 11:59, Matteo Melideo wrote: Thanks Tim. The idea is to provide a general architecture embracing the all DevCommE then we can enter into the details of each specific part where and if necessary. Concerning the second question, I will leave Davide to provide you and answer. Best, M. Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: Dear partners, please review the attached architecture draft for T9.3 - Please let me know - especially for the deployment tool - if there is any misconception. @Matteo/Davide: would you propose to make one diagram for all tasks? And: could you please check if that format is editable for you? Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: T9.3-Architecture-v04.ppt Type: application/vnd.ms-powerpoint Size: 282624 bytes Desc: T9.3-Architecture-v04.ppt URL: From matteo.melideo at eng.it Thu Feb 2 15:02:55 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 02 Feb 2012 15:02:55 +0100 Subject: [Fiware-tools] Easy storyboard Message-ID: <4F2A978F.30404@eng.it> Dear All, as agreed here you are with a very easy storyboard I have in mind to show DevCommE functionalities at M12. Please let me know if it is exhaustive and if I have covered all the functionalities we are going to provide by M12. Comments and suggestions are more than welcome as usual. Regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Scenarios.ppt Type: application/vnd.ms-powerpoint Size: 19456 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Thu Feb 2 15:22:49 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Thu, 02 Feb 2012 15:22:49 +0100 Subject: [Fiware-tools] T9.3 Architecture (updated) In-Reply-To: <613708793959FC4A890C040BF1CF7ABA1118610F@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> <4F2A6CAF.40302@eng.it> <4F2A9576.50009@eng.it> <613708793959FC4A890C040BF1CF7ABA1118610F@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <4F2A9C39.30805@eng.it> I see the risk to end up with something too big and complex for been easily maintained We need, anyway, separate and detailed diagrams per WP task to include into the DevComE tech. desc. (like the one you produced) the general architecture (Matteo) will be a higher level diagram to give the overall idea Davide On 02/02/2012 15:01, Jonischkat, Tim wrote: > > Hey Davide, > > how about the following solution: > > You take the updated diagram attached and merge it with the > architectural components from T9.1 and T9.2. Then we have that > integrated diagram Matteo spoke of. One for the whole chapter. > > What do you think? > > Tim > > *Von:*Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] > *Gesendet:* Donnerstag, 2. Februar 2012 14:54 > *An:* Jonischkat, Tim > *Cc:* fiware-tools at lists.fi-ware.eu > *Betreff:* Re: [Fiware-tools] T9.3 Architecture (updated) > > Tim, > the architecture is fine. > Maybe I would rename the "FI-WARE Instance" in "FI-WARE Testbed". > Once it's ready you can upload it into the SVN repository, I'm storing > all the diagrams into > trunk/design/diagrams > > I'm going to produce the general diagram and the one for T9.1 > > @EAB > please provide the T9.2 (Catalogue) update architecture diagram by > February 6th > you can easily find the FMC notation on the already created diagrams > into the SVN ... > they are in grapgml, I'm using yEd > http://www.yworks.com/en/products_yed_about.html > > Me and Matteo are inserting the tickets and the tasks into the forge > but there are still some > platform problems ... we close this activity as soon as possible. > > ciao > Davide > > > On 02/02/2012 11:59, Matteo Melideo wrote: > > Thanks Tim. > The idea is to provide a general architecture embracing the all > DevCommE then we can enter into the details of each specific part > where and if necessary. > > Concerning the second question, I will leave Davide to provide you and > answer. > > Best, > > M. > > > Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: > > Dear partners, > > please review the attached architecture draft for T9.3 -- > > Please let me know -- especially for the deployment tool -- if there > is any misconception. > > @Matteo/Davide: would you propose to make one diagram for all tasks? > And: could you please check if that format is editable for you? > > Cheers > > Tim > > --- > > Tim Jonischkat > > paluno - The Ruhr Institute for Software Technology > > University of Duisburg-Essen > > Gerlingstra?e 16 > > 45127 Essen, Germany > > T: +49 201 183 4659 > > F: +49 201 183 4699 > > E: tim.jonischkat at paluno.uni-due.de > > > http://www.paluno.uni-due.de / > > http://www.sse.uni-due.de > > VAT ID: DE811272995 > > > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools > > > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From SHARON at il.ibm.com Thu Feb 2 16:34:29 2012 From: SHARON at il.ibm.com (Sharon Keidar-Barner) Date: Thu, 2 Feb 2012 17:34:29 +0200 Subject: [Fiware-tools] T9.3 Architecture (updated) In-Reply-To: <613708793959FC4A890C040BF1CF7ABA1118610F@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> <4F2A6CAF.40302@eng.it> <4F2A9576.50009@eng.it> <613708793959FC4A890C040BF1CF7ABA1118610F@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: Hi Tim, For now all the monitoring activities defined in Fiware are in the VM level. We are still in discussion with WP4 on contributions of TA. Only after we know which information will be brought into the IDE we will know which components besides the VM we monitor. Another question - the color ?, name ? in red box -- is it a left over ? Regards Sharon From: "Jonischkat, Tim" To: Davide Dalle Carbonare Cc: "fiware-tools at lists.fi-ware.eu" Date: 02/02/2012 04:01 PM Subject: Re: [Fiware-tools] T9.3 Architecture (updated) Sent by: fiware-tools-bounces at lists.fi-ware.eu Hey Davide, how about the following solution: You take the updated diagram attached and merge it with the architectural components from T9.1 and T9.2. Then we have that integrated diagram Matteo spoke of. One for the whole chapter. What do you think? Tim Von: Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] Gesendet: Donnerstag, 2. Februar 2012 14:54 An: Jonischkat, Tim Cc: fiware-tools at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture (updated) Tim, the architecture is fine. Maybe I would rename the "FI-WARE Instance" in "FI-WARE Testbed". Once it's ready you can upload it into the SVN repository, I'm storing all the diagrams into trunk/design/diagrams I'm going to produce the general diagram and the one for T9.1 @EAB please provide the T9.2 (Catalogue) update architecture diagram by February 6th you can easily find the FMC notation on the already created diagrams into the SVN ... they are in grapgml, I'm using yEd http://www.yworks.com/en/products_yed_about.html Me and Matteo are inserting the tickets and the tasks into the forge but there are still some platform problems ... we close this activity as soon as possible. ciao Davide On 02/02/2012 11:59, Matteo Melideo wrote: Thanks Tim. The idea is to provide a general architecture embracing the all DevCommE then we can enter into the details of each specific part where and if necessary. Concerning the second question, I will leave Davide to provide you and answer. Best, M. Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: Dear partners, please review the attached architecture draft for T9.3 ? Please let me know ? especially for the deployment tool ? if there is any misconception. @Matteo/Davide: would you propose to make one diagram for all tasks? And: could you please check if that format is editable for you? Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools[attachment "T9.3-Architecture-v04.ppt" deleted by Sharon Keidar-Barner/Haifa/IBM] _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools From Tim.Jonischkat at paluno.uni-due.de Thu Feb 2 16:37:54 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Thu, 2 Feb 2012 15:37:54 +0000 Subject: [Fiware-tools] T9.3 Architecture (updated) In-Reply-To: References: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> <4F2A6CAF.40302@eng.it> <4F2A9576.50009@eng.it> <613708793959FC4A890C040BF1CF7ABA1118610F@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <613708793959FC4A890C040BF1CF7ABA111861B3@WIWINF-EXDAG01.wiwinf.uni-due.de> Hi Sharon, thanks for clarifying. 1) The box is a left-over so to say... I am still missing input from you (IBM) concerning the description and type (indicated by the color) of the box. 2) What changes are necessary from your point of view? Please just provide an alternative version. Cheers Tim -----Urspr?ngliche Nachricht----- Von: Sharon Keidar-Barner [mailto:SHARON at il.ibm.com] Gesendet: Donnerstag, 2. Februar 2012 16:34 An: Jonischkat, Tim Cc: Davide Dalle Carbonare; fiware-tools at lists.fi-ware.eu; fiware-tools-bounces at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture (updated) Hi Tim, For now all the monitoring activities defined in Fiware are in the VM level. We are still in discussion with WP4 on contributions of TA. Only after we know which information will be brought into the IDE we will know which components besides the VM we monitor. Another question - the color ?, name ? in red box -- is it a left over ? Regards Sharon From: "Jonischkat, Tim" To: Davide Dalle Carbonare Cc: "fiware-tools at lists.fi-ware.eu" Date: 02/02/2012 04:01 PM Subject: Re: [Fiware-tools] T9.3 Architecture (updated) Sent by: fiware-tools-bounces at lists.fi-ware.eu Hey Davide, how about the following solution: You take the updated diagram attached and merge it with the architectural components from T9.1 and T9.2. Then we have that integrated diagram Matteo spoke of. One for the whole chapter. What do you think? Tim Von: Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] Gesendet: Donnerstag, 2. Februar 2012 14:54 An: Jonischkat, Tim Cc: fiware-tools at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture (updated) Tim, the architecture is fine. Maybe I would rename the "FI-WARE Instance" in "FI-WARE Testbed". Once it's ready you can upload it into the SVN repository, I'm storing all the diagrams into trunk/design/diagrams I'm going to produce the general diagram and the one for T9.1 @EAB please provide the T9.2 (Catalogue) update architecture diagram by February 6th you can easily find the FMC notation on the already created diagrams into the SVN ... they are in grapgml, I'm using yEd http://www.yworks.com/en/products_yed_about.html Me and Matteo are inserting the tickets and the tasks into the forge but there are still some platform problems ... we close this activity as soon as possible. ciao Davide On 02/02/2012 11:59, Matteo Melideo wrote: Thanks Tim. The idea is to provide a general architecture embracing the all DevCommE then we can enter into the details of each specific part where and if necessary. Concerning the second question, I will leave Davide to provide you and answer. Best, M. Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: Dear partners, please review the attached architecture draft for T9.3 ? Please let me know ? especially for the deployment tool ? if there is any misconception. @Matteo/Davide: would you propose to make one diagram for all tasks? And: could you please check if that format is editable for you? Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools[attachment "T9.3-Architecture-v04.ppt" deleted by Sharon Keidar-Barner/Haifa/IBM] _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools From biberstein at il.ibm.com Mon Feb 6 17:55:12 2012 From: biberstein at il.ibm.com (Marina Biberstein) Date: Mon, 6 Feb 2012 18:55:12 +0200 Subject: [Fiware-tools] T9.3 Architecture (updated) In-Reply-To: <613708793959FC4A890C040BF1CF7ABA111861B3@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <613708793959FC4A890C040BF1CF7ABA11185E62@WIWINF-EXDAG01.wiwinf.uni-due.de> <4F2A6CAF.40302@eng.it> <4F2A9576.50009@eng.it> <613708793959FC4A890C040BF1CF7ABA1118610F@WIWINF-EXDAG01.wiwinf.uni-due.de> <613708793959FC4A890C040BF1CF7ABA111861B3@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: Hi Tim, Here's the slide with the data filled in. Cheers, -- Marina ---------------------------------------------------------------------------- Tel. +972-4-829-6133 E-mail biberstein at il.ibm.com From: "Jonischkat, Tim" To: Sharon Keidar-Barner/Haifa/IBM at IBMIL Cc: "fiware-tools at lists.fi-ware.eu" Date: 02/02/2012 05:38 PM Subject: Re: [Fiware-tools] T9.3 Architecture (updated) Sent by: fiware-tools-bounces at lists.fi-ware.eu Hi Sharon, thanks for clarifying. 1) The box is a left-over so to say... I am still missing input from you (IBM) concerning the description and type (indicated by the color) of the box. 2) What changes are necessary from your point of view? Please just provide an alternative version. Cheers Tim -----Urspr?ngliche Nachricht----- Von: Sharon Keidar-Barner [mailto:SHARON at il.ibm.com] Gesendet: Donnerstag, 2. Februar 2012 16:34 An: Jonischkat, Tim Cc: Davide Dalle Carbonare; fiware-tools at lists.fi-ware.eu; fiware-tools-bounces at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture (updated) Hi Tim, For now all the monitoring activities defined in Fiware are in the VM level. We are still in discussion with WP4 on contributions of TA. Only after we know which information will be brought into the IDE we will know which components besides the VM we monitor. Another question - the color ?, name ? in red box -- is it a left over ? Regards Sharon From: "Jonischkat, Tim" To: Davide Dalle Carbonare Cc: "fiware-tools at lists.fi-ware.eu" Date: 02/02/2012 04:01 PM Subject: Re: [Fiware-tools] T9.3 Architecture (updated) Sent by: fiware-tools-bounces at lists.fi-ware.eu Hey Davide, how about the following solution: You take the updated diagram attached and merge it with the architectural components from T9.1 and T9.2. Then we have that integrated diagram Matteo spoke of. One for the whole chapter. What do you think? Tim Von: Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] Gesendet: Donnerstag, 2. Februar 2012 14:54 An: Jonischkat, Tim Cc: fiware-tools at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture (updated) Tim, the architecture is fine. Maybe I would rename the "FI-WARE Instance" in "FI-WARE Testbed". Once it's ready you can upload it into the SVN repository, I'm storing all the diagrams into trunk/design/diagrams I'm going to produce the general diagram and the one for T9.1 @EAB please provide the T9.2 (Catalogue) update architecture diagram by February 6th you can easily find the FMC notation on the already created diagrams into the SVN ... they are in grapgml, I'm using yEd http://www.yworks.com/en/products_yed_about.html Me and Matteo are inserting the tickets and the tasks into the forge but there are still some platform problems ... we close this activity as soon as possible. ciao Davide On 02/02/2012 11:59, Matteo Melideo wrote: Thanks Tim. The idea is to provide a general architecture embracing the all DevCommE then we can enter into the details of each specific part where and if necessary. Concerning the second question, I will leave Davide to provide you and answer. Best, M. Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: Dear partners, please review the attached architecture draft for T9.3 ? Please let me know ? especially for the deployment tool ? if there is any misconception. @Matteo/Davide: would you propose to make one diagram for all tasks? And: could you please check if that format is editable for you? Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools[attachment "T9.3-Architecture-v04.ppt" deleted by Sharon Keidar-Barner/Haifa/IBM] _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: T9.3-Architecture-v05.ppt Type: application/octet-stream Size: 267776 bytes Desc: not available URL: From matteo.melideo at eng.it Mon Feb 6 21:50:45 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 06 Feb 2012 21:50:45 +0100 Subject: [Fiware-tools] Fwd: [Fiware-wpa] Reviewers have requested access to FusionForge In-Reply-To: <4F302304.9050400@tid.es> References: <4F302304.9050400@tid.es> Message-ID: <4F303D25.7090700@eng.it> All, this further confirms what we said in Madrid. Tracker, sprint and backlog MUST be kept updated frequently and in a very good shape!!!! Tomorrow we will further talk about this. Regards, M. -------- Messaggio originale -------- Oggetto: [Fiware-wpa] Reviewers have requested access to FusionForge Data: Mon, 06 Feb 2012 19:59:16 +0100 Mittente: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, Prior giving access to FusionForge to our reviewer, Man-Sze Li, I want you to be aware. I will give her access from tomorrow morning 11:00am on, unless I hear about any objection. A good reason for you to take care about the status of your stuff :-) particularly the tracker. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website:www.tid.es email:jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website:http://www.fi-ware.eu facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 twitter:http://twitter.com/FIware linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: RE: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog Date: Mon, 6 Feb 2012 11:52:16 +0100 From: Man-Sze Li To: JUAN JOSE HIERRO SUREDA Dear Dr Hierro I would wish to take up the offer to be able to access the FI-WARE backlogs live. Thank you in advance for arranging for a user account on FusionForge for me. Best regards Man-Sze Li -----Original Message----- From:Arian.ZWEGERS at ec.europa.eu [mailto:Arian.ZWEGERS at ec.europa.eu] Sent: 26 January 2012 10:35 To:msli at icfocus.co.uk;dgr at whitestein.com;rdifrancesco at ymail.com; bel.piet1 at gmail.com Subject: FW: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog fyi -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Thursday, January 26, 2012 11:11 AM To: ZWEGERS Arian (INFSO); INFSO-ICT-285248 Cc: Jose Jimenez; Miguel Carrillo; jhierro>> "Juan J. Hierro" Subject: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog Dear Arian, This is the official submission of deliverable D.2.1.a "FI-WARE Requirements Backlog" of the FI-WARE project. As you know, the FI-WARE Backlog is managed through several trackers (each FI-WARE chapter managing its own tracker), in combination with the public Wiki. Contents of the FI-WARE Backlog are constantly updated through the subsequent FI-WARE sprints, following an Agile approach. Therefore, versions of deliverable D.2.1 correspond to snapshots of these trackers. It took some time to find the way we could generate such a snapshot and adjust the format. On the other hand, the exercise allowed us to identify some missalignments regarding formatting conventions across FI-WARE chapters (e.g., notation for release or sprint ids, ids for entries, etc.) we have fixed. There should not be that much delay in subsequent submissions of the deliverable. Given the nature of the deliverable, we found that an spreadsheet format was the most useful and convenient format. Note that the deliverable corresponded to a snapshot we took early in December. Therefore, the backlog has evolved since then. If you or the reviewers wish to access the FI-WARE Backlogs "live" it would be as easy to create a user account for you on the different FI-WARE chapter projects in FusionForge. I remind you that this was something we already offered in September 2011. Best regards, Juanjo Hierro Chief Architect& Technical Manager FI-WARE project www.fi-ware.eu Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx . ------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Parte allegato al messaggio URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Tue Feb 7 11:58:30 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Tue, 7 Feb 2012 11:58:30 +0100 Subject: [Fiware-tools] WP9 Terms Message-ID: Hi all, This is my take on the three terms that is important for WP9. Of course this is my own understanding of these terms and open to discussion. The .md file is a text file readable by any text editor. Cheers, Roozbeh -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE WP9 Terms.pdf Type: application/pdf Size: 19990 bytes Desc: FI-WARE WP9 Terms.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE WP9 Terms.md Type: application/octet-stream Size: 2027 bytes Desc: FI-WARE WP9 Terms.md URL: From davide.dallecarbonare at eng.it Tue Feb 7 14:56:05 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 07 Feb 2012 14:56:05 +0100 Subject: [Fiware-tools] Mintes draft Message-ID: <4F312D75.9080704@eng.it> Dear All, attached the today meeting minutes. Please let me know if I forgot or misinterpreted something. Thanks again for joining and for your contributions. Regards, Davide -------------- next part -------------- A non-text attachment was scrubbed... Name: wp9-2012.02.07-minutes.doc Type: application/x-msword Size: 223232 bytes Desc: not available URL: From Tim.Jonischkat at paluno.uni-due.de Tue Feb 7 16:31:15 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Tue, 7 Feb 2012 15:31:15 +0000 Subject: [Fiware-tools] T9.3: Architectural descriptions for DevComE Technical Description Message-ID: <613708793959FC4A890C040BF1CF7ABA11188891@WIWINF-EXDAG01.wiwinf.uni-due.de> Dear T9.3 partners, please provide me some natural language descriptions of your architectural design in https://forge.fi-ware.eu/scmrepos/svn/tools/trunk/documents/T9.3/Architecture/T9.3-Architecture-v05.ppt. Especially pay attention to describing the integration with existing components or components from other chapters (blue). I will consolidate all inputs and copy them into the DevComE Technical Description, together with some updates on the conceptual side. Please provide your inputs via mail, I will put the result here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#Testing_and_Validation_Approach. As I am on an internal workshop on Thu and Fr, please send your inputs until tomorrow lunchtime (1:00pm latest). If there are any problems, don't hesitate to contact me. Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Tue Feb 7 17:57:49 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 07 Feb 2012 17:57:49 +0100 Subject: [Fiware-tools] Fwd: Mintes draft In-Reply-To: <4F312D75.9080704@eng.it> References: <4F312D75.9080704@eng.it> Message-ID: <4F31580D.10105@eng.it> problems with the mailing list ... I resend -------- Original Message -------- Subject: Mintes draft Date: Tue, 07 Feb 2012 14:56:05 +0100 From: Davide Dalle Carbonare To: fiware-tools at lists.fi-ware.eu Dear All, attached the today meeting minutes. Please let me know if I forgot or misinterpreted something. Thanks again for joining and for your contributions. Regards, Davide -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wp9-2012.02.07-minutes.doc Type: application/x-msword Size: 223232 bytes Desc: not available URL: From Tim.Jonischkat at paluno.uni-due.de Wed Feb 8 22:57:44 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Wed, 8 Feb 2012 21:57:44 +0000 Subject: [Fiware-tools] T9.3: Architectural descriptions for DevComE Technical Description Message-ID: <613708793959FC4A890C040BF1CF7ABA11188D13@WIWINF-EXDAG01.wiwinf.uni-due.de> Dear T9.3 partners, thanks for your input. I put together all information here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#Testing_and_Validation_Approach @Roozbeh: please add some component descriptions for your two boxes. @All: please review the text and change it they way you want it. Thanks again - Tim Von: Jonischkat, Tim Gesendet: Dienstag, 7. Februar 2012 16:31 An: fiware-tools at lists.fi-ware.eu Betreff: T9.3: Architectural descriptions for DevComE Technical Description Dear T9.3 partners, please provide me some natural language descriptions of your architectural design in https://forge.fi-ware.eu/scmrepos/svn/tools/trunk/documents/T9.3/Architecture/T9.3-Architecture-v05.ppt. Especially pay attention to describing the integration with existing components or components from other chapters (blue). I will consolidate all inputs and copy them into the DevComE Technical Description, together with some updates on the conceptual side. Please provide your inputs via mail, I will put the result here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#Testing_and_Validation_Approach. As I am on an internal workshop on Thu and Fr, please send your inputs until tomorrow lunchtime (1:00pm latest). If there are any problems, don't hesitate to contact me. Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Fri Feb 10 10:49:37 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Fri, 10 Feb 2012 10:49:37 +0100 Subject: [Fiware-tools] Fwd: [Fiware] URGENT AND IMPORTANT: Work in trackers In-Reply-To: <4F34BF4F.8020200@tid.es> References: <4F34BF4F.8020200@tid.es> Message-ID: <4F34E831.6060800@eng.it> just in case you haven't received yet. ciao Davide -------- Original Message -------- Subject: [Fiware] URGENT AND IMPORTANT: Work in trackers Date: Fri, 10 Feb 2012 07:55:11 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu , fiware at lists.fi-ware.eu Hi all, Please DON'T make any changes on your trackers until further notice (later today). This measure doesn't affect you work on the Wikis or other artifacts. You can still work there. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Fri Feb 10 17:28:52 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 10 Feb 2012 17:28:52 +0100 Subject: [Fiware-tools] Methodology ToC Message-ID: <4F3545C4.1050003@eng.it> Dear All, attached you can find a preliminary ToC of the methodology. Any comment is more than welcome. In addition to this, please let's think of what the three different versions will contain a part for improvements of the already existing texts, react to the reviewers comments, etc. In other words, do we want characterize since now the three versions of the document we are going to provide? Regard and have a nice w/e M. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Methodology TOC.doc Type: application/msword Size: 12288 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Mon Feb 13 18:32:27 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 13 Feb 2012 18:32:27 +0100 Subject: [Fiware-tools] FIAp definition Message-ID: <4F39492B.6050506@eng.it> Dear All, as agreed we have to propose a definition of FIAp necessary first of all for us to better sell what we are doing but also useful for the others. My proposal is, once we agreed, to send this to the FI-WARE coordinator. Given the inputs received (thanks to those who contributed), we arrived to the conclusion that the definition provided in the DoW is enough clear but lacks of some additional characteristics. We have extracted these characteristics from the definitions you provided and here you can find my suggestion: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Future_Internet_Application. Please feel free to comment and to provide any additional suggestion. We can further discuss this tomorrow during our conference call. Best, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Tue Feb 14 09:52:09 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Tue, 14 Feb 2012 09:52:09 +0100 Subject: [Fiware-tools] Methodology ToC In-Reply-To: <4F3545C4.1050003@eng.it> Message-ID: Hi Matteo, The overall structure looks fine to me. When we get into the more details, I think we need to talk about / define the following as well: * Roles: what roles do we involved in our methodology * Artifacts: what are the (even interim) products that are produced * Standards: which ones are recommended/considered by us If you see fit, we can already have subsections for these in the structure. Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Fri, 10 Feb 2012 17:28:52 +0100 To: WP9_fi-ware > Subject: [Fiware-tools] Methodology ToC Dear All, attached you can find a preliminary ToC of the methodology. Any comment is more than welcome. In addition to this, please let's think of what the three different versions will contain a part for improvements of the already existing texts, react to the reviewers comments, etc. In other words, do we want characterize since now the three versions of the document we are going to provide? Regard and have a nice w/e M. From matteo.melideo at eng.it Tue Feb 14 10:10:17 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 14 Feb 2012 10:10:17 +0100 Subject: [Fiware-tools] Methodology ToC In-Reply-To: References: Message-ID: <4F3A24F9.4090007@eng.it> Hi Roozbeh, very good idea. Please let's tart to think of it. Mine wanted to be just a preliminary ToC that needs to be further detailed. Best, M. Il 14/02/2012 09:52, Farahbod, Roozbeh ha scritto: > Hi Matteo, > > The overall structure looks fine to me. When we get into the more details, I think we need to talk about / define the following as well: > > > * Roles: what roles do we involved in our methodology > * Artifacts: what are the (even interim) products that are produced > * Standards: which ones are recommended/considered by us > > If you see fit, we can already have subsections for these in the structure. > > Cheers, > Roozbeh > > > From: Matteo Melideo> > Reply-To: Matteo Melideo> > Date: Fri, 10 Feb 2012 17:28:52 +0100 > To: WP9_fi-ware> > Subject: [Fiware-tools] Methodology ToC > > Dear All, > attached you can find a preliminary ToC of the methodology. > > Any comment is more than welcome. > > In addition to this, please let's think of what the three different versions will contain a part for improvements of the already existing texts, react to the reviewers comments, etc. In other words, do we want characterize since now the three versions of the document we are going to provide? > > Regard and have a nice w/e > > M. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Tue Feb 14 10:12:57 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Tue, 14 Feb 2012 10:12:57 +0100 Subject: [Fiware-tools] FIAp definition In-Reply-To: <4F39492B.6050506@eng.it> Message-ID: Hi Matteo, I like your proposal, especially how we extend (or add more details to) the DoW definition. I have one comment on the last additional feature: I am not so sure if the restriction implied in the sentence is necessary. To have FIAps accessible through ANY device would mean that they cannot be OS-, HW-, or in general Client Platform-dependent. I can imagine an Android or iOS app to be a FIAp but then that may not be available from a Linux box or vice-versa. Do we really need this? Or perhaps we can make it weaker a bit? The current sentence also has some typos: * "is ubiquitous accessible" --> "is ubiquitous; i.e., it is accessible" * "interweave" --> "interweaves" Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Mon, 13 Feb 2012 18:32:27 +0100 To: WP9_fi-ware >, stefano de panfilis > Subject: [Fiware-tools] FIAp definition Dear All, as agreed we have to propose a definition of FIAp necessary first of all for us to better sell what we are doing but also useful for the others. My proposal is, once we agreed, to send this to the FI-WARE coordinator. Given the inputs received (thanks to those who contributed), we arrived to the conclusion that the definition provided in the DoW is enough clear but lacks of some additional characteristics. We have extracted these characteristics from the definitions you provided and here you can find my suggestion: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Future_Internet_Application. Please feel free to comment and to provide any additional suggestion. We can further discuss this tomorrow during our conference call. Best, Matteo From matteo.melideo at eng.it Tue Feb 14 10:22:49 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 14 Feb 2012 10:22:49 +0100 Subject: [Fiware-tools] FIAp definition In-Reply-To: References: Message-ID: <4F3A27E9.8030101@eng.it> Hi, I agree with your analysis but while OS- HW- or Client Platform-dependent platform represent somehow the "default", the device (in the general sense) are somehow the news. Anyway, I am open to any suggestion to improve ... Thanks for the typos. M. Il 14/02/2012 10:12, Farahbod, Roozbeh ha scritto: > Hi Matteo, > > I like your proposal, especially how we extend (or add more details to) the DoW definition. > > I have one comment on the last additional feature: > I am not so sure if the restriction implied in the sentence is necessary. To have FIAps accessible through ANY device would mean that they cannot be OS-, HW-, or in general Client Platform-dependent. I can imagine an Android or iOS app to be a FIAp but then that may not be available from a Linux box or vice-versa. Do we really need this? Or perhaps we can make it weaker a bit? > > The current sentence also has some typos: > > * "is ubiquitous accessible" --> "is ubiquitous; i.e., it is accessible" > * "interweave" --> "interweaves" > > Cheers, > Roozbeh > > From: Matteo Melideo> > Reply-To: Matteo Melideo> > Date: Mon, 13 Feb 2012 18:32:27 +0100 > To: WP9_fi-ware>, stefano de panfilis> > Subject: [Fiware-tools] FIAp definition > > Dear All, > as agreed we have to propose a definition of FIAp necessary first of all for us to better sell what we are doing but also useful for the others. My proposal is, once we agreed, to send this to the FI-WARE coordinator. > Given the inputs received (thanks to those who contributed), we arrived to the conclusion that the definition provided in the DoW is enough clear but lacks of some additional characteristics. We have extracted these characteristics from the definitions you provided and here you can find my suggestion: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Future_Internet_Application. > > Please feel free to comment and to provide any additional suggestion. We can further discuss this tomorrow during our conference call. > > Best, > > Matteo > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jesus.gorronogoitia at atosresearch.eu Tue Feb 14 10:33:53 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 14 Feb 2012 10:33:53 +0100 Subject: [Fiware-tools] FIAp definition In-Reply-To: <4F3A27E9.8030101@eng.it> References: <4F3A27E9.8030101@eng.it> Message-ID: <1329212033.2723.2.camel@avalon.atos.net> Hi, typos are mine, thanks for the corrections. How do you express that we can access a FIA from everywhere, anytime? That's what i was to try to express saying ubiquitously accessible. Regards Yosu On Tue, 2012-02-14 at 10:22 +0100, Matteo Melideo wrote: > Hi, > I agree with your analysis but while OS- HW- or Client > Platform-dependent platform represent somehow the "default", the > device (in the general sense) are somehow the news. > Anyway, I am open to any suggestion to improve ... > > Thanks for the typos. > > M. > > Il 14/02/2012 10:12, Farahbod, Roozbeh ha scritto: > > Hi Matteo, > > > > I like your proposal, especially how we extend (or add more details to) the DoW definition. > > > > I have one comment on the last additional feature: > > I am not so sure if the restriction implied in the sentence is necessary. To have FIAps accessible through ANY device would mean that they cannot be OS-, HW-, or in general Client Platform-dependent. I can imagine an Android or iOS app to be a FIAp but then that may not be available from a Linux box or vice-versa. Do we really need this? Or perhaps we can make it weaker a bit? > > > > The current sentence also has some typos: > > > > * "is ubiquitous accessible" --> "is ubiquitous; i.e., it is accessible" > > * "interweave" --> "interweaves" > > > > Cheers, > > Roozbeh > > > > From: Matteo Melideo > > > Reply-To: Matteo Melideo > > > Date: Mon, 13 Feb 2012 18:32:27 +0100 > > To: WP9_fi-ware >, stefano de panfilis > > > Subject: [Fiware-tools] FIAp definition > > > > Dear All, > > as agreed we have to propose a definition of FIAp necessary first of all for us to better sell what we are doing but also useful for the others. My proposal is, once we agreed, to send this to the FI-WARE coordinator. > > Given the inputs received (thanks to those who contributed), we arrived to the conclusion that the definition provided in the DoW is enough clear but lacks of some additional characteristics. We have extracted these characteristics from the definitions you provided and here you can find my suggestion: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Future_Internet_Application. > > > > Please feel free to comment and to provide any additional suggestion. We can further discuss this tomorrow during our conference call. > > > > Best, > > > > Matteo > > > > > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 matteo.melideo at eng.it Tue Feb 14 10:32:11 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 14 Feb 2012 10:32:11 +0100 Subject: [Fiware-tools] Fwd: [Fiware] Forge back to normal In-Reply-To: <4F3A22C9.4030804@tid.es> References: <4F3A22C9.4030804@tid.es> Message-ID: <4F3A2A1B.3080909@eng.it> F.Y.I. -------- Messaggio originale -------- Oggetto: [Fiware] Forge back to normal Data: Tue, 14 Feb 2012 10:00:57 +0100 Mittente: Miguel Carrillo A: fiware at lists.fi-ware.eu Dear all, After the maintenance works tonight, eveything should be as expected. You can use the forge normally. Note that: * Any changes in docman or tracker after Thursday at 12:16am are lost (we warned you in advance so this shouldn't be a problem) * Mediawiki and SVN should not be affected by the maintenance operations Please let me know if you detect unexpected behaviour or any kind of data loss or corruption. It should not be the case, this was thoroughly tested beforehand. Needless to say, you can use all the tools normally from now on. Thanks your patience. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail:mcp at tid.es Follow FI-WARE on the net Website:http://www.fi-ware.eu Facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter:http://twitter.com/Fiware LinkedIn:http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Parte allegato al messaggio URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Tue Feb 14 11:15:19 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 14 Feb 2012 11:15:19 +0100 Subject: [Fiware-tools] Conf call reminder In-Reply-To: <4F153694.6000800@eng.it> References: <4F153694.6000800@eng.it> Message-ID: <4F3A3437.3070703@eng.it> Dear All, please remind the conference call, today at 11.30. Phone contact details as usual ... but this time we go collaborative with shared minutes: https://docs.google.com/document/d/1i60kvYOg2c24gVkH_ZfaFtFylceGwkJR-rTNVgAbW_8/edit Regards, Davide -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tim.Jonischkat at paluno.uni-due.de Tue Feb 14 14:57:27 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Tue, 14 Feb 2012 13:57:27 +0000 Subject: [Fiware-tools] Methodology ToC In-Reply-To: <4F3A24F9.4090007@eng.it> References: <4F3A24F9.4090007@eng.it> Message-ID: <613708793959FC4A890C040BF1CF7ABA111894D6@WIWINF-EXDAG01.wiwinf.uni-due.de> I really like that idea, too! Cheers Tim Von: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] Im Auftrag von Matteo Melideo Gesendet: Dienstag, 14. Februar 2012 10:10 An: Farahbod, Roozbeh Cc: WP9_fi-ware Betreff: Re: [Fiware-tools] Methodology ToC Hi Roozbeh, very good idea. Please let's tart to think of it. Mine wanted to be just a preliminary ToC that needs to be further detailed. Best, M. Il 14/02/2012 09:52, Farahbod, Roozbeh ha scritto: Hi Matteo, The overall structure looks fine to me. When we get into the more details, I think we need to talk about / define the following as well: * Roles: what roles do we involved in our methodology * Artifacts: what are the (even interim) products that are produced * Standards: which ones are recommended/considered by us If you see fit, we can already have subsections for these in the structure. Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Fri, 10 Feb 2012 17:28:52 +0100 To: WP9_fi-ware > Subject: [Fiware-tools] Methodology ToC Dear All, attached you can find a preliminary ToC of the methodology. Any comment is more than welcome. In addition to this, please let's think of what the three different versions will contain a part for improvements of the already existing texts, react to the reviewers comments, etc. In other words, do we want characterize since now the three versions of the document we are going to provide? Regard and have a nice w/e M. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Wed Feb 15 12:57:54 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 15 Feb 2012 12:57:54 +0100 Subject: [Fiware-tools] Fwd: [Fiware-wpl] IMPORTANT: Reference example on Main Interactions section to be followed In-Reply-To: <4F3B8055.1050703@tid.es> References: <4F3B8055.1050703@tid.es> Message-ID: <4F3B9DC2.6010103@eng.it> Guys, I think this is important for you and the architecture. Regards, Matteo -------- Messaggio originale -------- Oggetto: [Fiware-wpl] IMPORTANT: Reference example on Main Interactions section to be followed Data: Wed, 15 Feb 2012 10:52:21 +0100 Mittente: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi, While reviewing the different drafts of the "Architecture Description" chapters, I have found that many of the descriptions of "Main Interactions" is quite poor. We have developed a good reference example for this kind of sections. You can find it at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 If you have followed the reference example provided initially based on the CORBA specifications as well as the guidelines already provided, you should not have anything too far from this, but unfortunately, I'm discovering that this is not the case in many of the GE Architecture Descriptions. The guidelines for editing the "Architecture Description" deliverable have been updated accordingly. I encourage you to review them carefully and add any question on teh FAQ section you may have. You may find them at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Thu Feb 16 12:26:56 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 16 Feb 2012 12:26:56 +0100 Subject: [Fiware-tools] **** URGENT TO DO *** On Architecture... Message-ID: <4F3CE800.6080304@eng.it> Dear All, I read the contributions on the architecture and I have had the impression that a lot of details are missing and we provided almost the same info of M6. I think that it is important to provide some improvements. Specifically, we should try to be (where and when possible) more detailed in the definition of the APIs exposed, in the interactions among the various components internal to Wp9 and in the definition of the interfaces we intend to expose toward third party components (e.g. Testbed or other Chapters). Please try to improve this document at the very latest by next 21st of Feb EoB following Juanjo's examples\guidelines (as much as possible): 1) https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 2) attached mail The deadline is too close as I assume you perfectly know which are the interfaces and the other info requested at least for those components to be exposed at M12. Then, it is just a matter of reporting these into the document in the proper format. Anyway, what already written is now going to be integrated into the D2.3 Architecture and reviewed also by the other people to received additional comments and suggestions. Thanks a lot and regards, Matteo P.S. Please put your priority on this now. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: [Fiware-wpa] IMPORTANT: Approach for Architecture Specification Deliverable Date: Wed, 30 Nov 2011 15:38:42 +0100 Size: 712431 URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Thu Feb 16 13:08:15 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Thu, 16 Feb 2012 13:08:15 +0100 Subject: [Fiware-tools] **** URGENT TO DO *** On Architecture... In-Reply-To: <4F3CE800.6080304@eng.it> Message-ID: Hi Matteo, I will try to provide more info but the deadline is too tight and I am not sure, considering the little time I have left in my calendar till Tuesday, how much I will achieve. I believe the Juanjo's example is an overkill for WP9, with little value for us considering that we are the user of most of our components in WP9 and there is only part of it that is exposed to other chapters at the code level (i.e., not through the GUIs). It would have helped of course if we had more time. Can't this be done by M12? No one is going to use these information before we (WP9) release the first version of the tools. Last question, shall we provide more detail at the component level or user story level? I suggest component level, but a decision needs to be made group-wise so that we know where we put these; i.e., in separate pages each linked from the main architecture page? Perhaps subgroup leads (Tim for mine) should decide on the structure? Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Thu, 16 Feb 2012 12:26:56 +0100 To: WP9_fi-ware > Subject: [Fiware-tools] **** URGENT TO DO *** On Architecture... Dear All, I read the contributions on the architecture and I have had the impression that a lot of details are missing and we provided almost the same info of M6. I think that it is important to provide some improvements. Specifically, we should try to be (where and when possible) more detailed in the definition of the APIs exposed, in the interactions among the various components internal to Wp9 and in the definition of the interfaces we intend to expose toward third party components (e.g. Testbed or other Chapters). Please try to improve this document at the very latest by next 21st of Feb EoB following Juanjo's examples\guidelines (as much as possible): 1) https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 2) attached mail The deadline is too close as I assume you perfectly know which are the interfaces and the other info requested at least for those components to be exposed at M12. Then, it is just a matter of reporting these into the document in the proper format. Anyway, what already written is now going to be integrated into the D2.3 Architecture and reviewed also by the other people to received additional comments and suggestions. Thanks a lot and regards, Matteo P.S. Please put your priority on this now. From matteo.melideo at eng.it Thu Feb 16 14:26:12 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 16 Feb 2012 14:26:12 +0100 Subject: [Fiware-tools] **** URGENT TO DO *** On Architecture... In-Reply-To: References: Message-ID: <4F3D03F4.5060402@eng.it> Dear Roozbeh, my replies in lined ... Il 16/02/2012 13:08, Farahbod, Roozbeh ha scritto: > Hi Matteo, > > I will try to provide more info but the deadline is too tight and I am not sure, considering the little time I have left in my calendar till Tuesday, how much I will achieve. I believe the Juanjo's example is an overkill for WP9, with little value for us considering that we are the user of most of our components in WP9 and there is only part of it that is exposed to other chapters at the code level (i.e., not through the GUIs). It would have helped of course if we had more time. The definition and identification of the methods we are going to expose can be useful also for us to understand how our components interact each other. > Can't this be done by M12? No, because the deliverables is due now (M9). Let me know when you can provide me this info at the latest. > No one is going to use these information before we (WP9) release the first version of the tools. I know but this is a contractual deadline. > > Last question, shall we provide more detail at the component level or user story level? I suggest component level, but a decision needs to be made group-wise so that we know where we put these; i.e., in separate pages each linked from the main architecture page? Perhaps subgroup leads (Tim for mine) should decide on the structure? At Component level specifying where possible the APIs I hope this answers your questions BR, M. > > Cheers, > Roozbeh > > From: Matteo Melideo> > Reply-To: Matteo Melideo> > Date: Thu, 16 Feb 2012 12:26:56 +0100 > To: WP9_fi-ware> > Subject: [Fiware-tools] **** URGENT TO DO *** On Architecture... > > Dear All, > I read the contributions on the architecture and I have had the impression that a lot of details are missing and we provided almost the same info of M6. > > I think that it is important to provide some improvements. Specifically, we should try to be (where and when possible) more detailed in the definition of the APIs exposed, in the interactions among the various components internal to Wp9 and in the definition of the interfaces we intend to expose toward third party components (e.g. Testbed or other Chapters). > > Please try to improve this document at the very latest by next 21st of Feb EoB following Juanjo's examples\guidelines (as much as possible): > 1) https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 > 2) attached mail > > The deadline is too close as I assume you perfectly know which are the interfaces and the other info requested at least for those components to be exposed at M12. Then, it is just a matter of reporting these into the document in the proper format. > > Anyway, what already written is now going to be integrated into the D2.3 Architecture and reviewed also by the other people to received additional comments and suggestions. > > > Thanks a lot and regards, > > Matteo > > P.S. > Please put your priority on this now. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Thu Feb 16 17:23:05 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Thu, 16 Feb 2012 17:23:05 +0100 Subject: [Fiware-tools] **** URGENT TO DO *** On Architecture... In-Reply-To: <4F3CE800.6080304@eng.it> References: <4F3CE800.6080304@eng.it> Message-ID: <4F3D2D69.8070900@eng.it> Dear All, I added a section at the end of the document as proposed by the guidelines: "Main Interaction" here I'm adding for example the SOAP APIs we are using for the components that interact with FusionForge ... please try to do the same with your assets, wherever it makes sense. thanks, Davide On 16/02/2012 12:26, Matteo Melideo wrote: > Dear All, > I read the contributions on the architecture and I have had the > impression that a lot of details are missing and we provided almost > the same info of M6. > > I think that it is important to provide some improvements. > Specifically, we should try to be (where and when possible) more > detailed in the definition of the APIs exposed, in the interactions > among the various components internal to Wp9 and in the definition of > the interfaces we intend to expose toward third party components (e.g. > Testbed or other Chapters). > > Please try to improve this document at the very latest by next 21st of > Feb EoB following Juanjo's examples\guidelines (as much as possible): > 1) > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 > > 2) attached mail > > The deadline is too close as I assume you perfectly know which are the > interfaces and the other info requested at least for those components > to be exposed at M12. Then, it is just a matter of reporting these > into the document in the proper format. > > Anyway, what already written is now going to be integrated into the > D2.3 Architecture and reviewed also by the other people to received > additional comments and suggestions. > > > Thanks a lot and regards, > > Matteo > > P.S. > Please put your priority on this now. > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Fri Feb 17 09:25:24 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 17 Feb 2012 09:25:24 +0100 Subject: [Fiware-tools] Wp7 and Wp9 bilateral meeting In-Reply-To: References: <4F294498.7020509@eng.it> Message-ID: <4F3E0EF4.70206@eng.it> Thanks 1000. BR, M. Il 16/02/2012 22:33, Hans.Einsiedler at telekom.de ha scritto: > > Dear Matteo, > > Please find attached the remarks. I have only the problem, that I do > not know who else has participated L > > Cheers, > > Hans > > Message Classification: > > [ ] Public > > [ ] Private > > [ ] Internal Use Only > > [ ] For your eyes only > > [ ] General Business Use > > [ ] DTAG Internal Use Only > > [ ] DTAG Confidential Proprietary > > *From:*Matteo Melideo [mailto:matteo.melideo at eng.it] > *Sent:* Mittwoch, 1. Februar 2012 14:57 > *To:* Garino Pierangelo; Einsiedler, Hans > *Cc:* WP9_fi-ware > *Subject:* Wp7 and Wp9 bilateral meeting > > Dear Pierangelo and Hans > could you please complete the attached minuted with the list of > participants from your side and control if we forgot something. > > Thanks and regards, > > Matteo > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From Hans.Einsiedler at telekom.de Thu Feb 16 22:33:39 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 16 Feb 2012 22:33:39 +0100 Subject: [Fiware-tools] Wp7 and Wp9 bilateral meeting In-Reply-To: <4F294498.7020509@eng.it> References: <4F294498.7020509@eng.it> Message-ID: Dear Matteo, Please find attached the remarks. I have only the problem, that I do not know who else has participated :( Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: Mittwoch, 1. Februar 2012 14:57 To: Garino Pierangelo; Einsiedler, Hans Cc: WP9_fi-ware Subject: Wp7 and Wp9 bilateral meeting Dear Pierangelo and Hans could you please complete the attached minuted with the list of participants from your side and control if we forgot something. Thanks and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Minutes (bilateral Wp7 - Wp9) 01-12-HJE.doc Type: application/msword Size: 206848 bytes Desc: FI-WARE Minutes (bilateral Wp7 - Wp9) 01-12-HJE.doc URL: From matteo.melideo at eng.it Fri Feb 17 17:20:39 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 17 Feb 2012 17:20:39 +0100 Subject: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology Message-ID: <4F3E7E57.7080609@eng.it> Dear All, I would like to share with you the google doc links where I am sharing the new ToC for the DevCommE methodology and a preliminary assignment of responsibility. https://docs.google.com/document/d/1qZSrx6c6IYjPyqoXk1K3b0Cfa9B4H8AgmJBc1LEHxWg/edit As usual comments are more than welcome. Thanks and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Mon Feb 20 10:18:05 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Mon, 20 Feb 2012 10:18:05 +0100 Subject: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology In-Reply-To: <4F3E7E57.7080609@eng.it> Message-ID: Hi Matteo, Putting aside the tutorials for tools, the core of this document is the Methods (aka Methodology). I am wondering why is this assigned to SAP only? Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Fri, 17 Feb 2012 17:20:39 +0100 To: WP9_fi-ware > Subject: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology Dear All, I would like to share with you the google doc links where I am sharing the new ToC for the DevCommE methodology and a preliminary assignment of responsibility. https://docs.google.com/document/d/1qZSrx6c6IYjPyqoXk1K3b0Cfa9B4H8AgmJBc1LEHxWg/edit As usual comments are more than welcome. Thanks and regards, Matteo From matteo.melideo at eng.it Mon Feb 20 10:31:57 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 20 Feb 2012 10:31:57 +0100 Subject: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology In-Reply-To: References: Message-ID: <4F42130D.3050309@eng.it> Hi Roozbeh, It is just a matter of coordinating the section and the contribution not to write you everything. :-) Anyway you are right probably it is better if ENG will take over this responsibilty asking for the contributions. Regards, M. Il 20/02/2012 10:18, Farahbod, Roozbeh ha scritto: > Hi Matteo, > > Putting aside the tutorials for tools, the core of this document is the Methods (aka Methodology). I am wondering why is this assigned to SAP only? > > Cheers, > Roozbeh > > From: Matteo Melideo> > Reply-To: Matteo Melideo> > Date: Fri, 17 Feb 2012 17:20:39 +0100 > To: WP9_fi-ware> > Subject: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology > > Dear All, > I would like to share with you the google doc links where I am sharing the new ToC for the DevCommE methodology and a preliminary assignment of responsibility. > > https://docs.google.com/document/d/1qZSrx6c6IYjPyqoXk1K3b0Cfa9B4H8AgmJBc1LEHxWg/edit > > As usual comments are more than welcome. > > Thanks and regards, > > Matteo > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Mon Feb 20 16:08:10 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 20 Feb 2012 16:08:10 +0100 Subject: [Fiware-tools] Methodology document Message-ID: <4F4261DA.5010706@eng.it> Dear All, in order to avoid problems with my nervous system, I decided to work locally on the methodology document not using anymore Google documents. I will upload the document in the SVN under the deliverable section. In addition to this if for you it is not a problem I would use LibreOffice as it is more stable than my World editor. Please, for any modification please remind to use the track changes to on. Thanks and best, M. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Mon Feb 20 16:28:05 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Mon, 20 Feb 2012 16:28:05 +0100 Subject: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology In-Reply-To: <4F42130D.3050309@eng.it> Message-ID: :) Thanks. My misunderstanding then. Talk to you tomorrow. Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Mon, 20 Feb 2012 10:31:57 +0100 To: Roozbeh Farahbod > Cc: WP9_fi-ware > Subject: Re: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology Hi Roozbeh, It is just a matter of coordinating the section and the contribution not to write you everything. :-) Anyway you are right probably it is better if ENG will take over this responsibilty asking for the contributions. Regards, M. Il 20/02/2012 10:18, Farahbod, Roozbeh ha scritto: Hi Matteo, Putting aside the tutorials for tools, the core of this document is the Methods (aka Methodology). I am wondering why is this assigned to SAP only? Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Fri, 17 Feb 2012 17:20:39 +0100 To: WP9_fi-ware > Subject: [Fiware-tools] Deliverable D.9.2.a - DevCommE Methodology Dear All, I would like to share with you the google doc links where I am sharing the new ToC for the DevCommE methodology and a preliminary assignment of responsibility. https://docs.google.com/document/d/1qZSrx6c6IYjPyqoXk1K3b0Cfa9B4H8AgmJBc1LEHxWg/edit As usual comments are more than welcome. Thanks and regards, Matteo From matteo.melideo at eng.it Tue Feb 21 10:17:35 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 21 Feb 2012 10:17:35 +0100 Subject: [Fiware-tools] Conference call reminder Message-ID: <4F43612F.8030506@eng.it> Dear All, just to remind you that at 11,30 the scheduled conference call is on. As we did last time, the minutes will be taken on-line. The goal of the PhC is to discuss about the current status of the activities, the contribution to the Deliverable 2.3 and the Methodology. Any other business? Best M. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Tue Feb 21 10:39:15 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 21 Feb 2012 10:39:15 +0100 Subject: [Fiware-tools] Fwd: Re: Conference call reminder + the link In-Reply-To: <4F43638A.8080901@eng.it> References: <4F43638A.8080901@eng.it> Message-ID: <4F436643.9070600@eng.it> https://docs.google.com/document/d/13xwRfvVi1awJHVzEG208ITeRZlwnr89ldr2_YWQ-6aQ/edit The link for the minutes BR, M. -------- Messaggio originale -------- Oggetto: Re: [Fiware-tools] Conference call reminder Data: Tue, 21 Feb 2012 10:27:38 +0100 Mittente: Matteo Melideo Rispondi-a: matteo.melideo at eng.it Organizzazione: Engineering Ingegneria Informatica S.p.A. A: Miguel Carrillo already done ;-) M. Il 21/02/2012 10:24, Miguel Carrillo ha scritto: > "/the minutes will be taken on-line/" ... please do not forget to > export them to any suitable format (word, open office or whatever) and > upload them to your project > > El 21/02/2012 10:17, Matteo Melideo escribi?: >> Dear All, >> just to remind you that at 11,30 the scheduled conference call is on. >> >> As we did last time, the minutes will be taken on-line. >> >> The goal of the PhC is to discuss about the current status of the >> activities, the contribution to the Deliverable 2.3 and the Methodology. >> >> Any other business? >> >> Best >> >> M. > > -- > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telef?nica Distrito Telef?nica > _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 483 26 77 > > e-mail:mcp at tid.es > > Follow FI-WARE on the net > > Website:http://www.fi-ware.eu > Facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter:http://twitter.com/Fiware > LinkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > > ------------------------------------------------------------------------ > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at > http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From roozbeh.farahbod at sap.com Tue Feb 21 10:37:50 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Tue, 21 Feb 2012 10:37:50 +0100 Subject: [Fiware-tools] T9.3 Architecture In-Reply-To: <613708793959FC4A890C040BF1CF7ABA11177DA7@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: Hi Tim, Did you send us a revised version of this with all the red comments resolved? I cannot find it in my emails. Cheers, Roozbeh From: "Jonischkat, Tim" > Date: Wed, 18 Jan 2012 17:47:47 +0100 To: "fiware-tools at lists.fi-ware.eu" > Subject: [Fiware-tools] T9.3 Architecture Dear T9.3 partners, thank you very much for your contribution to the T9.3 architecture specification. Find attached a pptx file containing all your individual contributions and a pptx file with my first attempt for a consolidated view (in which I tried to merge duplicate components). Please do the following: 1) Check if I didn?t miss anything. Please pay also attention to the interfaces, for which I tried to use only one single notation (the semantics are described on a separate slide). 2) Tell me if everything is OK or send me your corrections. 3) Please work on the comments I made in red. This is especially essential for missing interface names. In my opinion a simple arrow-dependency does not say which data or functionality is actually used by the client component. Wish you all a nice evening Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 From Tim.Jonischkat at paluno.uni-due.de Tue Feb 21 10:43:23 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Tue, 21 Feb 2012 09:43:23 +0000 Subject: [Fiware-tools] T9.3 Architecture In-Reply-To: References: <613708793959FC4A890C040BF1CF7ABA11177DA7@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <613708793959FC4A890C040BF1CF7ABA1118A223@WIWINF-EXDAG01.wiwinf.uni-due.de> Hi Roozbeh, no, excuse me! The current version can be found here: https://forge.fi-ware.eu/scmrepos/svn/tools/trunk/documents/T9.3/Architecture/T9.3-Architecture-v05.ppt It is more abstract than the previous versions - just as requested by Davide and Matteo. Cheers Tim -----Urspr?ngliche Nachricht----- Von: Farahbod, Roozbeh [mailto:roozbeh.farahbod at sap.com] Gesendet: Dienstag, 21. Februar 2012 10:38 An: Jonischkat, Tim; fiware-tools at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture Hi Tim, Did you send us a revised version of this with all the red comments resolved? I cannot find it in my emails. Cheers, Roozbeh From: "Jonischkat, Tim" > Date: Wed, 18 Jan 2012 17:47:47 +0100 To: "fiware-tools at lists.fi-ware.eu" > Subject: [Fiware-tools] T9.3 Architecture Dear T9.3 partners, thank you very much for your contribution to the T9.3 architecture specification. Find attached a pptx file containing all your individual contributions and a pptx file with my first attempt for a consolidated view (in which I tried to merge duplicate components). Please do the following: 1) Check if I didn't miss anything. Please pay also attention to the interfaces, for which I tried to use only one single notation (the semantics are described on a separate slide). 2) Tell me if everything is OK or send me your corrections. 3) Please work on the comments I made in red. This is especially essential for missing interface names. In my opinion a simple arrow-dependency does not say which data or functionality is actually used by the client component. Wish you all a nice evening Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 From Tim.Jonischkat at paluno.uni-due.de Tue Feb 21 11:33:55 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Tue, 21 Feb 2012 10:33:55 +0000 Subject: [Fiware-tools] T9.3 Architecture References: <613708793959FC4A890C040BF1CF7ABA11177DA7@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <613708793959FC4A890C040BF1CF7ABA1118A27C@WIWINF-EXDAG01.wiwinf.uni-due.de> Dear all, I just updated the diagram from the PROSA viewpoint: https://forge.fi-ware.eu/scmrepos/svn/tools/trunk/documents/T9.3/Architecture/T9.3-Architecture-v06.ppt Cheers Tim -----Urspr?ngliche Nachricht----- Von: Jonischkat, Tim Gesendet: Dienstag, 21. Februar 2012 10:43 An: 'Farahbod, Roozbeh'; fiware-tools at lists.fi-ware.eu Betreff: AW: [Fiware-tools] T9.3 Architecture Hi Roozbeh, no, excuse me! The current version can be found here: https://forge.fi-ware.eu/scmrepos/svn/tools/trunk/documents/T9.3/Architecture/T9.3-Architecture-v05.ppt It is more abstract than the previous versions - just as requested by Davide and Matteo. Cheers Tim -----Urspr?ngliche Nachricht----- Von: Farahbod, Roozbeh [mailto:roozbeh.farahbod at sap.com] Gesendet: Dienstag, 21. Februar 2012 10:38 An: Jonischkat, Tim; fiware-tools at lists.fi-ware.eu Betreff: Re: [Fiware-tools] T9.3 Architecture Hi Tim, Did you send us a revised version of this with all the red comments resolved? I cannot find it in my emails. Cheers, Roozbeh From: "Jonischkat, Tim" > Date: Wed, 18 Jan 2012 17:47:47 +0100 To: "fiware-tools at lists.fi-ware.eu" > Subject: [Fiware-tools] T9.3 Architecture Dear T9.3 partners, thank you very much for your contribution to the T9.3 architecture specification. Find attached a pptx file containing all your individual contributions and a pptx file with my first attempt for a consolidated view (in which I tried to merge duplicate components). Please do the following: 1) Check if I didn't miss anything. Please pay also attention to the interfaces, for which I tried to use only one single notation (the semantics are described on a separate slide). 2) Tell me if everything is OK or send me your corrections. 3) Please work on the comments I made in red. This is especially essential for missing interface names. In my opinion a simple arrow-dependency does not say which data or functionality is actually used by the client component. Wish you all a nice evening Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 From Tim.Jonischkat at paluno.uni-due.de Tue Feb 21 14:17:20 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Tue, 21 Feb 2012 13:17:20 +0000 Subject: [Fiware-tools] Sequence Diagram Editor / Template ?? Message-ID: <613708793959FC4A890C040BF1CF7ABA1118A473@WIWINF-EXDAG01.wiwinf.uni-due.de> Dear Davide and Matteo, I did not find any suggestion concerning tools for sequence diagrams on the project wiki. What kind of tool are you using? Could you send around a preliminary version of your diagram? Cheers Tim --- Tim Jonischkat paluno - The Ruhr Institute for Software Technology University of Duisburg-Essen Gerlingstra?e 16 45127 Essen, Germany T: +49 201 183 4659 F: +49 201 183 4699 E: tim.jonischkat at paluno.uni-due.de http://www.paluno.uni-due.de / http://www.sse.uni-due.de VAT ID: DE811272995 -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Tue Feb 21 14:37:55 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 21 Feb 2012 14:37:55 +0100 Subject: [Fiware-tools] Sequence Diagram Editor / Template ?? In-Reply-To: <613708793959FC4A890C040BF1CF7ABA1118A473@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <613708793959FC4A890C040BF1CF7ABA1118A473@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <4F439E33.30307@eng.it> Dear Tim, concerning the tool Davide is using for the diagrams, due to some problems with Papyrus, it is AmaterasUML. It is an Eclipse Plugin. I think that in the next couple of hours Davide will send around some examples. Anyway, the sequence diagram should demonstrate (high level) the main interactions among the tools within the Wp9 and the one of the tools with third party components. Regards, Matteo On marted? 21 febbraio 2012 14:17:20, Jonischkat, Tim wrote: > Dear Davide and Matteo, > > I did not find any suggestion concerning tools for sequence diagrams > on the project wiki. What kind of tool are you using? Could you send > around a preliminary version of your diagram? > > Cheers > > Tim > > --- > > Tim Jonischkat > > paluno - The Ruhr Institute for Software Technology > > University of Duisburg-Essen > > Gerlingstra?e 16 > > 45127 Essen, Germany > > T: +49 201 183 4659 > > F: +49 201 183 4699 > > E: tim.jonischkat at paluno.uni-due.de > > > http://www.paluno.uni-due.de / > > http://www.sse.uni-due.de > > VAT ID: DE811272995 > -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Tue Feb 21 14:50:03 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 21 Feb 2012 14:50:03 +0100 Subject: [Fiware-tools] Sequence Diagram Editor / Template ?? In-Reply-To: <613708793959FC4A890C040BF1CF7ABA1118A473@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <613708793959FC4A890C040BF1CF7ABA1118A473@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <4F43A10B.2030905@eng.it> Tim, all the diagrams I'm preparing are versioned into the design>model folder on the forge. about the tool, I had to switch from Papyrus to another one because of some export bugs :-( at the moment I'm using AmaterasUML that's a lightweight Eclipse plug-in http://sourceforge.jp/projects/amateras/releases/?package_id=4435 and I have to say it's complete and easy to use. hope this helps, Davide On 21/02/2012 14:17, Jonischkat, Tim wrote: > > Dear Davide and Matteo, > > I did not find any suggestion concerning tools for sequence diagrams > on the project wiki. What kind of tool are you using? Could you send > around a preliminary version of your diagram? > > Cheers > > Tim > > --- > > Tim Jonischkat > > paluno - The Ruhr Institute for Software Technology > > University of Duisburg-Essen > > Gerlingstra?e 16 > > 45127 Essen, Germany > > T: +49 201 183 4659 > > F: +49 201 183 4699 > > E: tim.jonischkat at paluno.uni-due.de > > > http://www.paluno.uni-due.de / > > http://www.sse.uni-due.de > > VAT ID: DE811272995 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Tue Feb 21 16:42:10 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 21 Feb 2012 16:42:10 +0100 Subject: [Fiware-tools] Tools demo Message-ID: <4F43BB52.4070905@eng.it> Dear All, this message to summarize few points from this morning phone call. 1) for the tools demonstration, it's completely up to you to decide what to present and how to show it to the other partners. 2) tools installation for the demo server side: communicate if they can/cannot be installed on the server hosted by Engineering. client side: communicate the requirements and info necessary to follow the demo. 3) provide the information on installation and license here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tools regards, Davide From davide.dallecarbonare at eng.it Tue Feb 21 17:19:37 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 21 Feb 2012 17:19:37 +0100 Subject: [Fiware-tools] Sequence diagram example Message-ID: <4F43C419.7050806@eng.it> Dear All, I've published into the wiki the sequence diagram for the Task management https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/FI-WARE_DevComE_Technical_Description#FusionForge_Connector source and image files are in SVN, design>model folder regards, Davide From matteo.melideo at eng.it Tue Feb 21 17:45:16 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 21 Feb 2012 17:45:16 +0100 Subject: [Fiware-tools] Temptative f2f meeting dates Message-ID: <4F43CA1C.6010002@eng.it> Dear All, I received an e-mail from Tim who volunteered to host the next f2f meeting of Wp9 in Essen. The dates are the 29th and 30th of March. Please let me know your availability and other options (if any). Regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From john.sandberg at ericsson.com Wed Feb 22 04:18:09 2012 From: john.sandberg at ericsson.com (John Sandberg) Date: Wed, 22 Feb 2012 04:18:09 +0100 Subject: [Fiware-tools] Temptative f2f meeting dates In-Reply-To: <4F43CA1C.6010002@eng.it> References: <4F43CA1C.6010002@eng.it> Message-ID: <6FFCEF6A0AE1D6468ADD42818409956220A58DF1FF@ESESSCMS0352.eemea.ericsson.se> Hi, I cannot make it on those dates. I can participate earlier week 13 (26-28/3) or w15 and w16. In general, I would prefer to not meet on a Friday as I have such a long travel. BR John ________________________________ From: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] On Behalf Of Matteo Melideo Sent: den 21 februari 2012 17:45 To: WP9_fi-ware Subject: [Fiware-tools] Temptative f2f meeting dates Dear All, I received an e-mail from Tim who volunteered to host the next f2f meeting of Wp9 in Essen. The dates are the 29th and 30th of March. Please let me know your availability and other options (if any). Regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From roozbeh.farahbod at sap.com Wed Feb 22 09:33:55 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Wed, 22 Feb 2012 09:33:55 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: <4F43BB52.4070905@eng.it> Message-ID: Hi Davide, RE 2) For the demo, I will prefer to walk over the How To instructions. Actually creating the software adaptors and configurations will be lengthy process. I can also show the plugin in Eclipse if we can do screen sharing. RE 3) The wiki page is updated for SoPeCo. Cheers, Roozbeh On 21.02.12 16:42, "Davide Dalle Carbonare" wrote: >Dear All, >this message to summarize few points from this morning phone call. > >1) for the tools demonstration, it's completely up to you to decide what >to present and how to show it to the other partners. > >2) tools installation for the demo >server side: communicate if they can/cannot be installed on the server >hosted by Engineering. >client side: communicate the requirements and info necessary to follow >the demo. > >3) provide the information on installation and license here: >https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tools > >regards, >Davide >_______________________________________________ >Fiware-tools mailing list >Fiware-tools at lists.fi-ware.eu >http://lists.fi-ware.eu/listinfo/fiware-tools From roozbeh.farahbod at sap.com Wed Feb 22 09:38:48 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Wed, 22 Feb 2012 09:38:48 +0100 Subject: [Fiware-tools] Temptative f2f meeting dates In-Reply-To: <4F43CA1C.6010002@eng.it> Message-ID: Hi Matteo, Unfortunately, I won't be able to be there on those days. We have an SAP event then. In general, I will have trouble justifying another f2f meeting considering that we recently met in Madrid. Perhaps I can attend the relevant parts via teleconf? Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Tue, 21 Feb 2012 17:45:16 +0100 To: WP9_fi-ware > Subject: [Fiware-tools] Temptative f2f meeting dates Dear All, I received an e-mail from Tim who volunteered to host the next f2f meeting of Wp9 in Essen. The dates are the 29th and 30th of March. Please let me know your availability and other options (if any). Regards, Matteo From jesus.gorronogoitia at atosresearch.eu Wed Feb 22 10:32:10 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Wed, 22 Feb 2012 10:32:10 +0100 Subject: [Fiware-tools] Temptative f2f meeting dates In-Reply-To: References: Message-ID: <1329903130.2915.5.camel@avalon.atos.net> Ciao Matteo, similar situation for us. Is it really necessary to have a f2f meeting at this moment? In particular for T9.1? Cannot we move on with dedicated telco conferences? Kind regards Yosu On Wed, 2012-02-22 at 09:38 +0100, Farahbod, Roozbeh wrote: > Hi Matteo, > > Unfortunately, I won't be able to be there on those days. We have an SAP event then. > > In general, I will have trouble justifying another f2f meeting considering that we recently met in Madrid. Perhaps I can attend the relevant parts via teleconf? > > Cheers, > Roozbeh > > From: Matteo Melideo > > Reply-To: Matteo Melideo > > Date: Tue, 21 Feb 2012 17:45:16 +0100 > To: WP9_fi-ware > > Subject: [Fiware-tools] Temptative f2f meeting dates > > Dear All, > I received an e-mail from Tim who volunteered to host the next f2f meeting of Wp9 in Essen. > > The dates are the 29th and 30th of March. > > Please let me know your availability and other options (if any). > > Regards, > > Matteo > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 davide.dallecarbonare at eng.it Wed Feb 22 10:32:13 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 22 Feb 2012 10:32:13 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: References: Message-ID: <4F44B61D.2060900@eng.it> Roozbeh, I've seen the HowTo (from Github) and I think it's fine ... @ALL: For the tools presentation, I'm trying to set up a webinar using Engineering infrastructure, where we can share a traditional presentation (pdf) or the screen (for live demo). I confirm you this as soon as possible. regards, Davide On 22/02/2012 09:33, Farahbod, Roozbeh wrote: > Hi Davide, > > RE 2) > > For the demo, I will prefer to walk over the How To instructions. Actually > creating the software adaptors and configurations will be lengthy process. > I can also show the plugin in Eclipse if we can do screen sharing. > > RE 3) > The wiki page is updated for SoPeCo. > > Cheers, > Roozbeh > > > > On 21.02.12 16:42, "Davide Dalle Carbonare" > wrote: > >> Dear All, >> this message to summarize few points from this morning phone call. >> >> 1) for the tools demonstration, it's completely up to you to decide what >> to present and how to show it to the other partners. >> >> 2) tools installation for the demo >> server side: communicate if they can/cannot be installed on the server >> hosted by Engineering. >> client side: communicate the requirements and info necessary to follow >> the demo. >> >> 3) provide the information on installation and license here: >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tools >> >> regards, >> Davide >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools > > From matteo.melideo at eng.it Wed Feb 22 12:21:17 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 22 Feb 2012 12:21:17 +0100 Subject: [Fiware-tools] f2f meeting Message-ID: <4F44CFAD.4020503@eng.it> Dear All, it seems extremely difficult to organize this meeting. Fine with me, we can cancel it hoping everything will be fine. However, if I will have the impression deliveries and tasks are not properly on track a meeting will be organized short notice somewhere. Bear in mind that have the review probably in June and it seems that there will not be any plenary meetings. The f2f will be left to the Wp leaders needs. Regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jesus.gorronogoitia at atosresearch.eu Wed Feb 22 12:53:54 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Wed, 22 Feb 2012 12:53:54 +0100 Subject: [Fiware-tools] f2f meeting In-Reply-To: <4F44CFAD.4020503@eng.it> References: <4F44CFAD.4020503@eng.it> Message-ID: <1329911634.2915.22.camel@avalon.atos.net> Ciao Matteo, your comments sound reasonable. Regards Yosu On Wed, 2012-02-22 at 12:21 +0100, Matteo Melideo wrote: > Dear All, > it seems extremely difficult to organize this meeting. Fine with me, > we can cancel it hoping everything will be fine. However, if I will > have the impression deliveries and tasks are not properly on track a > meeting will be organized short notice somewhere. > Bear in mind that have the review probably in June and it seems that > there will not be any plenary meetings. The f2f will be left to the Wp > leaders needs. > > > Regards, > > Matteo > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 roozbeh.farahbod at sap.com Wed Feb 22 12:52:24 2012 From: roozbeh.farahbod at sap.com (Farahbod, Roozbeh) Date: Wed, 22 Feb 2012 12:52:24 +0100 Subject: [Fiware-tools] f2f meeting In-Reply-To: <4F44CFAD.4020503@eng.it> Message-ID: Sounds good to me. Cheers, Roozbeh From: Matteo Melideo > Reply-To: Matteo Melideo > Date: Wed, 22 Feb 2012 12:21:17 +0100 To: WP9_fi-ware > Subject: [Fiware-tools] f2f meeting Dear All, it seems extremely difficult to organize this meeting. Fine with me, we can cancel it hoping everything will be fine. However, if I will have the impression deliveries and tasks are not properly on track a meeting will be organized short notice somewhere. Bear in mind that have the review probably in June and it seems that there will not be any plenary meetings. The f2f will be left to the Wp leaders needs. Regards, Matteo From matteo.melideo at eng.it Wed Feb 22 13:10:18 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 22 Feb 2012 13:10:18 +0100 Subject: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC Message-ID: <4F44DB2A.4080302@eng.it> Dear All, I have an internal board meeting on the 28th and it is very difficult to postpone it. I was wondering if you are available to postpone the PhC Wednesday same time. Thanks and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From Tim.Jonischkat at paluno.uni-due.de Wed Feb 22 13:44:26 2012 From: Tim.Jonischkat at paluno.uni-due.de (Jonischkat, Tim) Date: Wed, 22 Feb 2012 12:44:26 +0000 Subject: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC In-Reply-To: <4F44DB2A.4080302@eng.it> References: <4F44DB2A.4080302@eng.it> Message-ID: <613708793959FC4A890C040BF1CF7ABA1118A8E9@WIWINF-EXDAG01.wiwinf.uni-due.de> Fine for me. Cheers Tim Von: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] Im Auftrag von Matteo Melideo Gesendet: Mittwoch, 22. Februar 2012 13:10 An: WP9_fi-ware Betreff: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC Dear All, I have an internal board meeting on the 28th and it is very difficult to postpone it. I was wondering if you are available to postpone the PhC Wednesday same time. Thanks and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From SHARON at il.ibm.com Wed Feb 22 14:00:34 2012 From: SHARON at il.ibm.com (Sharon Keidar-Barner) Date: Wed, 22 Feb 2012 15:00:34 +0200 Subject: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC In-Reply-To: <613708793959FC4A890C040BF1CF7ABA1118A8E9@WIWINF-EXDAG01.wiwinf.uni-due.de> References: <4F44DB2A.4080302@eng.it> <613708793959FC4A890C040BF1CF7ABA1118A8E9@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: Fine for me, Matteo, note that I didn't get your original email (the same happened for the f2f email you sent yesterday). Please check if you have a local version of the mailing list which is not updated with my email Thanks Sharon From: "Jonischkat, Tim" To: "matteo.melideo at eng.it" , WP9_fi-ware Date: 22/02/2012 02:44 PM Subject: Re: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC Sent by: fiware-tools-bounces at lists.fi-ware.eu Fine for me. Cheers Tim Von: fiware-tools-bounces at lists.fi-ware.eu [ mailto:fiware-tools-bounces at lists.fi-ware.eu] Im Auftrag von Matteo Melideo Gesendet: Mittwoch, 22. Februar 2012 13:10 An: WP9_fi-ware Betreff: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC Dear All, I have an internal board meeting on the 28th and it is very difficult to postpone it. I was wondering if you are available to postpone the PhC Wednesday same time. Thanks and regards, Matteo_______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools From matteo.melideo at eng.it Wed Feb 22 14:22:43 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 22 Feb 2012 14:22:43 +0100 Subject: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC In-Reply-To: References: <4F44DB2A.4080302@eng.it> <613708793959FC4A890C040BF1CF7ABA1118A8E9@WIWINF-EXDAG01.wiwinf.uni-due.de> Message-ID: <4F44EC23.9010000@eng.it> Sharon, that's look quite strange. In fact, I just checked and you are in the mailing list. BR, M. Il 22/02/2012 14:00, Sharon Keidar-Barner ha scritto: > Fine for me, > > Matteo, note that I didn't get your original email (the same happened for > the f2f email you sent yesterday). Please check if you have a local version > of the mailing list which is not updated with my email > > Thanks > > Sharon > > > > From: "Jonischkat, Tim" > To: "matteo.melideo at eng.it", WP9_fi-ware > > Date: 22/02/2012 02:44 PM > Subject: Re: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone > the PhC > Sent by: fiware-tools-bounces at lists.fi-ware.eu > > > > Fine for me. > > Cheers > Tim > > Von: fiware-tools-bounces at lists.fi-ware.eu [ > mailto:fiware-tools-bounces at lists.fi-ware.eu] Im Auftrag von Matteo Melideo > Gesendet: Mittwoch, 22. Februar 2012 13:10 > An: WP9_fi-ware > Betreff: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC > > Dear All, > I have an internal board meeting on the 28th and it is very difficult to > postpone it. > > I was wondering if you are available to postpone the PhC Wednesday same > time. > > Thanks and regards, > > Matteo_______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From jesus.gorronogoitia at atosresearch.eu Wed Feb 22 14:32:32 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Wed, 22 Feb 2012 14:32:32 +0100 Subject: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC In-Reply-To: <4F44DB2A.4080302@eng.it> References: <4F44DB2A.4080302@eng.it> Message-ID: <1329917552.2915.23.camel@avalon.atos.net> Ciao Matteo, i won't be off the office from 28th Feb to 1st March, due to another project meeting. Regards Yosu On Wed, 2012-02-22 at 13:10 +0100, Matteo Melideo wrote: > Dear All, > I have an internal board meeting on the 28th and it is very difficult > to postpone it. > > I was wondering if you are available to postpone the PhC Wednesday > same time. > > Thanks and regards, > > Matteo > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 jesus.gorronogoitia at atosresearch.eu Wed Feb 22 14:33:24 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Wed, 22 Feb 2012 14:33:24 +0100 Subject: [Fiware-tools] *** URGENT FAVOUR *** Request to postpone the PhC In-Reply-To: <1329917552.2915.23.camel@avalon.atos.net> References: <4F44DB2A.4080302@eng.it> <1329917552.2915.23.camel@avalon.atos.net> Message-ID: <1329917604.2915.24.camel@avalon.atos.net> i meant i will be ... :-) On Wed, 2012-02-22 at 14:32 +0100, Yosu Gorro?ogoitia wrote: > Ciao Matteo, > i won't be off the office from 28th Feb to 1st March, due to another > project meeting. > Regards > Yosu > > On Wed, 2012-02-22 at 13:10 +0100, Matteo Melideo wrote: > > Dear All, > > I have an internal board meeting on the 28th and it is very difficult > > to postpone it. > > > > I was wondering if you are available to postpone the PhC Wednesday > > same time. > > > > Thanks and regards, > > > > Matteo > > > > _______________________________________________ > > Fiware-tools mailing list > > Fiware-tools at lists.fi-ware.eu > > http://lists.fi-ware.eu/listinfo/fiware-tools > > > ------------------------------------------------------------------ > 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 > 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 > no se hace responsable por su contenido. Su contenido no constituye ningun > compromiso para el grupo Atos, 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-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 davide.dallecarbonare at eng.it Wed Feb 22 15:49:25 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 22 Feb 2012 15:49:25 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: <4F44B61D.2060900@eng.it> References: <4F44B61D.2060900@eng.it> Message-ID: <4F450075.2040102@eng.it> Dear All, we have a webinar session available for the tools demo. In order to avoid problems during the presentation I ask you 20 minutes of your time to test it in advance. please let me know your availability for the test, better if on Friday 24 or Monday 27. regards, Davide On 22/02/2012 10:32, Davide Dalle Carbonare wrote: > Roozbeh, > I've seen the HowTo (from Github) and I think it's fine ... > > @ALL: For the tools presentation, I'm trying to set up a webinar using > Engineering infrastructure, > where we can share a traditional presentation (pdf) or the screen (for > live demo). > I confirm you this as soon as possible. > > regards, > Davide > > On 22/02/2012 09:33, Farahbod, Roozbeh wrote: >> Hi Davide, >> >> RE 2) >> >> For the demo, I will prefer to walk over the How To instructions. >> Actually >> creating the software adaptors and configurations will be lengthy >> process. >> I can also show the plugin in Eclipse if we can do screen sharing. >> >> RE 3) >> The wiki page is updated for SoPeCo. >> >> Cheers, >> Roozbeh >> >> >> >> On 21.02.12 16:42, "Davide Dalle >> Carbonare" >> wrote: >> >>> Dear All, >>> this message to summarize few points from this morning phone call. >>> >>> 1) for the tools demonstration, it's completely up to you to decide >>> what >>> to present and how to show it to the other partners. >>> >>> 2) tools installation for the demo >>> server side: communicate if they can/cannot be installed on the server >>> hosted by Engineering. >>> client side: communicate the requirements and info necessary to follow >>> the demo. >>> >>> 3) provide the information on installation and license here: >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tools >>> >>> regards, >>> Davide >>> _______________________________________________ >>> Fiware-tools mailing list >>> Fiware-tools at lists.fi-ware.eu >>> http://lists.fi-ware.eu/listinfo/fiware-tools >> >> > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools > > From matteo.melideo at eng.it Wed Feb 22 16:10:32 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 22 Feb 2012 16:10:32 +0100 Subject: [Fiware-tools] Next PhC on 28th Feb 2012 Message-ID: <4F450568.1000200@eng.it> Dear All, this is to confirm that the next conference call will be on the 28th at 11.30 PM. Up to now only Yosu cannot make it but I guess a person available to replace him is available in ATOS. Right? Regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jesus.gorronogoitia at atosresearch.eu Wed Feb 22 16:21:22 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Wed, 22 Feb 2012 16:21:22 +0100 Subject: [Fiware-tools] Next PhC on 28th Feb 2012 In-Reply-To: <4F450568.1000200@eng.it> References: <4F450568.1000200@eng.it> Message-ID: <1329924082.2915.38.camel@avalon.atos.net> Hope that Clara can attend. Yosu On Wed, 2012-02-22 at 16:10 +0100, Matteo Melideo wrote: > Dear All, > this is to confirm that the next conference call will be on the 28th > at 11.30 PM. > > Up to now only Yosu cannot make it but I guess a person available to > replace him is available in ATOS. Right? > > Regards, > > Matteo > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 jesus.gorronogoitia at atosresearch.eu Wed Feb 22 16:20:42 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Wed, 22 Feb 2012 16:20:42 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: <4F450075.2040102@eng.it> References: <4F44B61D.2060900@eng.it> <4F450075.2040102@eng.it> Message-ID: <1329924042.2915.37.camel@avalon.atos.net> Both days are fine with me (Friday up to 16:00 pm). Yosu On Wed, 2012-02-22 at 15:49 +0100, Davide Dalle Carbonare wrote: > Dear All, > we have a webinar session available for the tools demo. > > In order to avoid problems during the presentation I ask you > 20 minutes of your time to test it in advance. > > please let me know your availability for the test, better if on > Friday 24 or Monday 27. > > regards, > Davide > > > On 22/02/2012 10:32, Davide Dalle Carbonare wrote: > > Roozbeh, > > I've seen the HowTo (from Github) and I think it's fine ... > > > > @ALL: For the tools presentation, I'm trying to set up a webinar using > > Engineering infrastructure, > > where we can share a traditional presentation (pdf) or the screen (for > > live demo). > > I confirm you this as soon as possible. > > > > regards, > > Davide > > > > On 22/02/2012 09:33, Farahbod, Roozbeh wrote: > >> Hi Davide, > >> > >> RE 2) > >> > >> For the demo, I will prefer to walk over the How To instructions. > >> Actually > >> creating the software adaptors and configurations will be lengthy > >> process. > >> I can also show the plugin in Eclipse if we can do screen sharing. > >> > >> RE 3) > >> The wiki page is updated for SoPeCo. > >> > >> Cheers, > >> Roozbeh > >> > >> > >> > >> On 21.02.12 16:42, "Davide Dalle > >> Carbonare" > >> wrote: > >> > >>> Dear All, > >>> this message to summarize few points from this morning phone call. > >>> > >>> 1) for the tools demonstration, it's completely up to you to decide > >>> what > >>> to present and how to show it to the other partners. > >>> > >>> 2) tools installation for the demo > >>> server side: communicate if they can/cannot be installed on the server > >>> hosted by Engineering. > >>> client side: communicate the requirements and info necessary to follow > >>> the demo. > >>> > >>> 3) provide the information on installation and license here: > >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tools > >>> > >>> regards, > >>> Davide > >>> _______________________________________________ > >>> Fiware-tools mailing list > >>> Fiware-tools at lists.fi-ware.eu > >>> http://lists.fi-ware.eu/listinfo/fiware-tools > >> > >> > > _______________________________________________ > > Fiware-tools mailing list > > Fiware-tools at lists.fi-ware.eu > > http://lists.fi-ware.eu/listinfo/fiware-tools > > > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 clara.pezuela at atosresearch.eu Wed Feb 22 18:35:33 2012 From: clara.pezuela at atosresearch.eu (Clara M Pezuela Robles) Date: Wed, 22 Feb 2012 18:35:33 +0100 Subject: [Fiware-tools] Next PhC on 28th Feb 2012 In-Reply-To: <1329924082.2915.38.camel@avalon.atos.net> References: <4F450568.1000200@eng.it> <1329924082.2915.38.camel@avalon.atos.net> Message-ID: <2E6842FF4FDB5A47B877C8CADB9D76FD58CDC3@INTMAIL03.es.int.atosorigin.com> Yes, I could Regards -----Original Message----- From: Jesus Gorro?ogoitia Cruz Sent: mi?rcoles, 22 de febrero de 2012 16:21 To: matteo.melideo at eng.it Cc: WP9_fi-ware; sharon at il.ibm.com; Clara M Pezuela Robles Subject: Re: [Fiware-tools] Next PhC on 28th Feb 2012 Hope that Clara can attend. Yosu On Wed, 2012-02-22 at 16:10 +0100, Matteo Melideo wrote: > Dear All, > this is to confirm that the next conference call will be on the 28th > at 11.30 PM. > > Up to now only Yosu cannot make it but I guess a person available to > replace him is available in ATOS. Right? > > Regards, > > Matteo > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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. ------------------------------------------------------------------ ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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 matteo.melideo at eng.it Wed Feb 22 18:39:04 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 22 Feb 2012 18:39:04 +0100 Subject: [Fiware-tools] Please review Message-ID: <4F452838.1030303@eng.it> Dear All, whoever is interested in reviewing the first two sections of the Methodology deliverable is more than welcome. They are just 2 pages but mandatory to be shared before to write the others. The document is in the svn under the Deliverables folder. To avoid conflicts please use the track changes and rename the file with your initials Thanks for your support and regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From fredrik.h.pettersson at ericsson.com Thu Feb 23 07:24:09 2012 From: fredrik.h.pettersson at ericsson.com (Fredrik Pettersson H) Date: Thu, 23 Feb 2012 07:24:09 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: <4F450075.2040102@eng.it> References: <4F44B61D.2060900@eng.it> <4F450075.2040102@eng.it> Message-ID: For the catalogue demo I would like to avoid using screen sharing if possible as this would undoubtedly lead to technical problems which would take up a lot of our limited meeting time. So, for the catalogue demo this is my suggestion. We have the catalogue running on a publicly accessible server. I will provide you with a short document listing the features available in the current version of the catalogue and how to use them, and invite you all to register in the catalogue and try it out for yourself. You will be able to test the features we have currently implemented and play around with it at your leisure. BR, /Fredrik -----Original Message----- From: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] On Behalf Of Davide Dalle Carbonare Sent: den 22 februari 2012 15:49 To: fiware-tools at lists.fi-ware.eu Subject: Re: [Fiware-tools] Tools demo Dear All, we have a webinar session available for the tools demo. In order to avoid problems during the presentation I ask you 20 minutes of your time to test it in advance. please let me know your availability for the test, better if on Friday 24 or Monday 27. regards, Davide On 22/02/2012 10:32, Davide Dalle Carbonare wrote: > Roozbeh, > I've seen the HowTo (from Github) and I think it's fine ... > > @ALL: For the tools presentation, I'm trying to set up a webinar using > Engineering infrastructure, where we can share a traditional > presentation (pdf) or the screen (for live demo). > I confirm you this as soon as possible. > > regards, > Davide > > On 22/02/2012 09:33, Farahbod, Roozbeh wrote: >> Hi Davide, >> >> RE 2) >> >> For the demo, I will prefer to walk over the How To instructions. >> Actually >> creating the software adaptors and configurations will be lengthy >> process. >> I can also show the plugin in Eclipse if we can do screen sharing. >> >> RE 3) >> The wiki page is updated for SoPeCo. >> >> Cheers, >> Roozbeh >> >> >> >> On 21.02.12 16:42, "Davide Dalle >> Carbonare" >> wrote: >> >>> Dear All, >>> this message to summarize few points from this morning phone call. >>> >>> 1) for the tools demonstration, it's completely up to you to decide >>> what to present and how to show it to the other partners. >>> >>> 2) tools installation for the demo >>> server side: communicate if they can/cannot be installed on the >>> server hosted by Engineering. >>> client side: communicate the requirements and info necessary to >>> follow the demo. >>> >>> 3) provide the information on installation and license here: >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tool >>> s >>> >>> regards, >>> Davide >>> _______________________________________________ >>> Fiware-tools mailing list >>> Fiware-tools at lists.fi-ware.eu >>> http://lists.fi-ware.eu/listinfo/fiware-tools >> >> > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools > > _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools From davide.dallecarbonare at eng.it Thu Feb 23 12:05:15 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Thu, 23 Feb 2012 12:05:15 +0100 Subject: [Fiware-tools] Server machine ready Message-ID: <4F461D6B.1090300@eng.it> Dear All, the server environment for the WP tools is now ready. There is a FusionForge installation up and running, that we are using to develop the FF plug-in and wizards. you can find that FF at http://fiware.eng.it this is the environment where all the server side components will be installed and tested. regards, Davide From matteo.melideo at eng.it Thu Feb 23 12:26:24 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 23 Feb 2012 12:26:24 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: References: <4F44B61D.2060900@eng.it> <4F450075.2040102@eng.it> Message-ID: <4F462260.8010506@eng.it> Fredrik hi, your first sentence seems to be a little pessimistic, doesn't it? How can you say since now that "this would undoubtedly lead to technical problems "? Did you already test this solution before? What is the time slot for the meeting? We can also decide to make it a bit longer due to the demo session and the fact that most likely we will not have any f2f meeting!! Said that, your approach is also feasible but I hope you can send us everything before the conference call so that during this we can ask you questions and clarifications, if any. Regards, Matteo Il 23/02/2012 07:24, Fredrik Pettersson H ha scritto: > For the catalogue demo I would like to avoid using screen sharing if possible as this would undoubtedly lead to technical problems which would take up a lot of our limited meeting time. So, for the catalogue demo this is my suggestion. We have the catalogue running on a publicly accessible server. I will provide you with a short document listing the features available in the current version of the catalogue and how to use them, and invite you all to register in the catalogue and try it out for yourself. You will be able to test the features we have currently implemented and play around with it at your leisure. > > BR, > > /Fredrik > > -----Original Message----- > From: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] On Behalf Of Davide Dalle Carbonare > Sent: den 22 februari 2012 15:49 > To: fiware-tools at lists.fi-ware.eu > Subject: Re: [Fiware-tools] Tools demo > > Dear All, > we have a webinar session available for the tools demo. > > In order to avoid problems during the presentation I ask you 20 minutes of your time to test it in advance. > > please let me know your availability for the test, better if on Friday 24 or Monday 27. > > regards, > Davide > > > On 22/02/2012 10:32, Davide Dalle Carbonare wrote: >> Roozbeh, >> I've seen the HowTo (from Github) and I think it's fine ... >> >> @ALL: For the tools presentation, I'm trying to set up a webinar using >> Engineering infrastructure, where we can share a traditional >> presentation (pdf) or the screen (for live demo). >> I confirm you this as soon as possible. >> >> regards, >> Davide >> >> On 22/02/2012 09:33, Farahbod, Roozbeh wrote: >>> Hi Davide, >>> >>> RE 2) >>> >>> For the demo, I will prefer to walk over the How To instructions. >>> Actually >>> creating the software adaptors and configurations will be lengthy >>> process. >>> I can also show the plugin in Eclipse if we can do screen sharing. >>> >>> RE 3) >>> The wiki page is updated for SoPeCo. >>> >>> Cheers, >>> Roozbeh >>> >>> >>> >>> On 21.02.12 16:42, "Davide Dalle >>> Carbonare" >>> wrote: >>> >>>> Dear All, >>>> this message to summarize few points from this morning phone call. >>>> >>>> 1) for the tools demonstration, it's completely up to you to decide >>>> what to present and how to show it to the other partners. >>>> >>>> 2) tools installation for the demo >>>> server side: communicate if they can/cannot be installed on the >>>> server hosted by Engineering. >>>> client side: communicate the requirements and info necessary to >>>> follow the demo. >>>> >>>> 3) provide the information on installation and license here: >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tool >>>> s >>>> >>>> regards, >>>> Davide >>>> _______________________________________________ >>>> Fiware-tools mailing list >>>> Fiware-tools at lists.fi-ware.eu >>>> http://lists.fi-ware.eu/listinfo/fiware-tools >>> >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools >> >> > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From fredrik.h.pettersson at ericsson.com Thu Feb 23 12:37:54 2012 From: fredrik.h.pettersson at ericsson.com (Fredrik Pettersson H) Date: Thu, 23 Feb 2012 12:37:54 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: <4F462260.8010506@eng.it> References: <4F44B61D.2060900@eng.it> <4F450075.2040102@eng.it> <4F462260.8010506@eng.it> Message-ID: Not sure why you think it is pessimistic? Technical issues are pretty common with the setup of things like that, considering that we are attempting to get several persons from different organizations and different countries to connect, not to mention that we will have multiple persons showing their separate demos. We often seem to have problems even getting something as simple as a phone conference going and getting everyone to be able to hear everyone else... My intention was to speed things up a bit since it would probably be more rewarding to play around with the catalogue yourself anyway rather than having me click through it, and since it is a server based software it is easy for everyone to connect to it with no installation required. I will move on with my suggested solution as long as there are no further objections. By the way, there are only a couple of working days left before the demo meeting, if you intend to extend it beyond the regular time slot of tuesday 11:30 to 12:30 CET then please do so as soon as possible. BR, /Fredrik ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 23 februari 2012 12:26 To: Fredrik Pettersson H Cc: fiware-tools at lists.fi-ware.eu Subject: Re: [Fiware-tools] Tools demo Fredrik hi, your first sentence seems to be a little pessimistic, doesn't it? How can you say since now that "this would undoubtedly lead to technical problems "? Did you already test this solution before? What is the time slot for the meeting? We can also decide to make it a bit longer due to the demo session and the fact that most likely we will not have any f2f meeting!! Said that, your approach is also feasible but I hope you can send us everything before the conference call so that during this we can ask you questions and clarifications, if any. Regards, Matteo Il 23/02/2012 07:24, Fredrik Pettersson H ha scritto: For the catalogue demo I would like to avoid using screen sharing if possible as this would undoubtedly lead to technical problems which would take up a lot of our limited meeting time. So, for the catalogue demo this is my suggestion. We have the catalogue running on a publicly accessible server. I will provide you with a short document listing the features available in the current version of the catalogue and how to use them, and invite you all to register in the catalogue and try it out for yourself. You will be able to test the features we have currently implemented and play around with it at your leisure. BR, /Fredrik -----Original Message----- From: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] On Behalf Of Davide Dalle Carbonare Sent: den 22 februari 2012 15:49 To: fiware-tools at lists.fi-ware.eu Subject: Re: [Fiware-tools] Tools demo Dear All, we have a webinar session available for the tools demo. In order to avoid problems during the presentation I ask you 20 minutes of your time to test it in advance. please let me know your availability for the test, better if on Friday 24 or Monday 27. regards, Davide On 22/02/2012 10:32, Davide Dalle Carbonare wrote: Roozbeh, I've seen the HowTo (from Github) and I think it's fine ... @ALL: For the tools presentation, I'm trying to set up a webinar using Engineering infrastructure, where we can share a traditional presentation (pdf) or the screen (for live demo). I confirm you this as soon as possible. regards, Davide On 22/02/2012 09:33, Farahbod, Roozbeh wrote: Hi Davide, RE 2) For the demo, I will prefer to walk over the How To instructions. Actually creating the software adaptors and configurations will be lengthy process. I can also show the plugin in Eclipse if we can do screen sharing. RE 3) The wiki page is updated for SoPeCo. Cheers, Roozbeh On 21.02.12 16:42, "Davide Dalle Carbonare" wrote: Dear All, this message to summarize few points from this morning phone call. 1) for the tools demonstration, it's completely up to you to decide what to present and how to show it to the other partners. 2) tools installation for the demo server side: communicate if they can/cannot be installed on the server hosted by Engineering. client side: communicate the requirements and info necessary to follow the demo. 3) provide the information on installation and license here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tool s regards, Davide _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Thu Feb 23 13:05:36 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 23 Feb 2012 13:05:36 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: References: <4F44B61D.2060900@eng.it> <4F450075.2040102@eng.it> <4F462260.8010506@eng.it> Message-ID: <4F462B90.2030906@eng.it> No problems at all Fredrik, fine with your solutions that as I said if perfectly reasonable. The conference call will be on Wednesday as I wrote in my mail yesterday. It is possible it will last a bit more than just an hour due to the various demos and presentations. Regards, M. Il 23/02/2012 12:37, Fredrik Pettersson H ha scritto: > Not sure why you think it is pessimistic? Technical issues are pretty > common with the setup of things like that, considering that we are > attempting to get several persons from different organizations and > different countries to connect, not to mention that we will have > multiple persons showing their separate demos. We often seem to have > problems even getting something as simple as a phone conference going > and getting everyone to be able to hear everyone else... > My intention was to speed things up a bit since it would probably be > more rewarding to play around with the catalogue yourself anyway > rather than having me click through it, and since it is a server based > software it is easy for everyone to connect to it with no installation > required. I will move on with my suggested solution as long as there > are no further objections. > By the way, there are only a couple of working days left before the > demo meeting, if you intend to extend it beyond the regular time slot > of tuesday 11:30 to 12:30 CET then please do so as soon as possible. > BR, > /Fredrik > > ------------------------------------------------------------------------ > *From:* Matteo Melideo [mailto:matteo.melideo at eng.it] > *Sent:* den 23 februari 2012 12:26 > *To:* Fredrik Pettersson H > *Cc:* fiware-tools at lists.fi-ware.eu > *Subject:* Re: [Fiware-tools] Tools demo > > Fredrik hi, > your first sentence seems to be a little pessimistic, doesn't it? How > can you say since now that "this would undoubtedly lead to technical > problems "? Did you already test this solution before? What is the > time slot for the meeting? We can also decide to make it a bit longer > due to the demo session and the fact that most likely we will not have > any f2f meeting!! > > Said that, your approach is also feasible but I hope you can send us > everything before the conference call so that during this we can ask > you questions and clarifications, if any. > > Regards, > > Matteo > > Il 23/02/2012 07:24, Fredrik Pettersson H ha scritto: >> For the catalogue demo I would like to avoid using screen sharing if possible as this would undoubtedly lead to technical problems which would take up a lot of our limited meeting time. So, for the catalogue demo this is my suggestion. We have the catalogue running on a publicly accessible server. I will provide you with a short document listing the features available in the current version of the catalogue and how to use them, and invite you all to register in the catalogue and try it out for yourself. You will be able to test the features we have currently implemented and play around with it at your leisure. >> >> BR, >> >> /Fredrik >> >> -----Original Message----- >> From:fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] On Behalf Of Davide Dalle Carbonare >> Sent: den 22 februari 2012 15:49 >> To:fiware-tools at lists.fi-ware.eu >> Subject: Re: [Fiware-tools] Tools demo >> >> Dear All, >> we have a webinar session available for the tools demo. >> >> In order to avoid problems during the presentation I ask you 20 minutes of your time to test it in advance. >> >> please let me know your availability for the test, better if on Friday 24 or Monday 27. >> >> regards, >> Davide >> >> >> On 22/02/2012 10:32, Davide Dalle Carbonare wrote: >>> Roozbeh, >>> I've seen the HowTo (from Github) and I think it's fine ... >>> >>> @ALL: For the tools presentation, I'm trying to set up a webinar using >>> Engineering infrastructure, where we can share a traditional >>> presentation (pdf) or the screen (for live demo). >>> I confirm you this as soon as possible. >>> >>> regards, >>> Davide >>> >>> On 22/02/2012 09:33, Farahbod, Roozbeh wrote: >>>> Hi Davide, >>>> >>>> RE 2) >>>> >>>> For the demo, I will prefer to walk over the How To instructions. >>>> Actually >>>> creating the software adaptors and configurations will be lengthy >>>> process. >>>> I can also show the plugin in Eclipse if we can do screen sharing. >>>> >>>> RE 3) >>>> The wiki page is updated for SoPeCo. >>>> >>>> Cheers, >>>> Roozbeh >>>> >>>> >>>> >>>> On 21.02.12 16:42, "Davide Dalle >>>> Carbonare" >>>> wrote: >>>> >>>>> Dear All, >>>>> this message to summarize few points from this morning phone call. >>>>> >>>>> 1) for the tools demonstration, it's completely up to you to decide >>>>> what to present and how to show it to the other partners. >>>>> >>>>> 2) tools installation for the demo >>>>> server side: communicate if they can/cannot be installed on the >>>>> server hosted by Engineering. >>>>> client side: communicate the requirements and info necessary to >>>>> follow the demo. >>>>> >>>>> 3) provide the information on installation and license here: >>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tool >>>>> s >>>>> >>>>> regards, >>>>> Davide >>>>> _______________________________________________ >>>>> Fiware-tools mailing list >>>>> Fiware-tools at lists.fi-ware.eu >>>>> http://lists.fi-ware.eu/listinfo/fiware-tools >>> _______________________________________________ >>> Fiware-tools mailing list >>> Fiware-tools at lists.fi-ware.eu >>> http://lists.fi-ware.eu/listinfo/fiware-tools >>> >>> >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools >> >> >> > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From fredrik.h.pettersson at ericsson.com Thu Feb 23 13:58:43 2012 From: fredrik.h.pettersson at ericsson.com (Fredrik Pettersson H) Date: Thu, 23 Feb 2012 13:58:43 +0100 Subject: [Fiware-tools] Tools demo In-Reply-To: <4F462B90.2030906@eng.it> References: <4F44B61D.2060900@eng.it> <4F450075.2040102@eng.it> <4F462260.8010506@eng.it> <4F462B90.2030906@eng.it> Message-ID: I must be missing some mail from you, perhaps the mailing list is dropping emails? The latest date I received from you regarding the conference call (copied below) stated that the demo would be on the 28th (tuesday) at 11:30pm (I assumed you meant am). Dear All, this is to confirm that the next conference call will be on the 28th at 11.30 PM. Up to now only Yosu cannot make it but I guess a person available to replace him is available in ATOS. Right? Regards, Matteo ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 23 februari 2012 13:06 To: Fredrik Pettersson H Cc: fiware-tools at lists.fi-ware.eu Subject: Re: [Fiware-tools] Tools demo No problems at all Fredrik, fine with your solutions that as I said if perfectly reasonable. The conference call will be on Wednesday as I wrote in my mail yesterday. It is possible it will last a bit more than just an hour due to the various demos and presentations. Regards, M. Il 23/02/2012 12:37, Fredrik Pettersson H ha scritto: Not sure why you think it is pessimistic? Technical issues are pretty common with the setup of things like that, considering that we are attempting to get several persons from different organizations and different countries to connect, not to mention that we will have multiple persons showing their separate demos. We often seem to have problems even getting something as simple as a phone conference going and getting everyone to be able to hear everyone else... My intention was to speed things up a bit since it would probably be more rewarding to play around with the catalogue yourself anyway rather than having me click through it, and since it is a server based software it is easy for everyone to connect to it with no installation required. I will move on with my suggested solution as long as there are no further objections. By the way, there are only a couple of working days left before the demo meeting, if you intend to extend it beyond the regular time slot of tuesday 11:30 to 12:30 CET then please do so as soon as possible. BR, /Fredrik ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 23 februari 2012 12:26 To: Fredrik Pettersson H Cc: fiware-tools at lists.fi-ware.eu Subject: Re: [Fiware-tools] Tools demo Fredrik hi, your first sentence seems to be a little pessimistic, doesn't it? How can you say since now that "this would undoubtedly lead to technical problems "? Did you already test this solution before? What is the time slot for the meeting? We can also decide to make it a bit longer due to the demo session and the fact that most likely we will not have any f2f meeting!! Said that, your approach is also feasible but I hope you can send us everything before the conference call so that during this we can ask you questions and clarifications, if any. Regards, Matteo Il 23/02/2012 07:24, Fredrik Pettersson H ha scritto: For the catalogue demo I would like to avoid using screen sharing if possible as this would undoubtedly lead to technical problems which would take up a lot of our limited meeting time. So, for the catalogue demo this is my suggestion. We have the catalogue running on a publicly accessible server. I will provide you with a short document listing the features available in the current version of the catalogue and how to use them, and invite you all to register in the catalogue and try it out for yourself. You will be able to test the features we have currently implemented and play around with it at your leisure. BR, /Fredrik -----Original Message----- From: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] On Behalf Of Davide Dalle Carbonare Sent: den 22 februari 2012 15:49 To: fiware-tools at lists.fi-ware.eu Subject: Re: [Fiware-tools] Tools demo Dear All, we have a webinar session available for the tools demo. In order to avoid problems during the presentation I ask you 20 minutes of your time to test it in advance. please let me know your availability for the test, better if on Friday 24 or Monday 27. regards, Davide On 22/02/2012 10:32, Davide Dalle Carbonare wrote: Roozbeh, I've seen the HowTo (from Github) and I think it's fine ... @ALL: For the tools presentation, I'm trying to set up a webinar using Engineering infrastructure, where we can share a traditional presentation (pdf) or the screen (for live demo). I confirm you this as soon as possible. regards, Davide On 22/02/2012 09:33, Farahbod, Roozbeh wrote: Hi Davide, RE 2) For the demo, I will prefer to walk over the How To instructions. Actually creating the software adaptors and configurations will be lengthy process. I can also show the plugin in Eclipse if we can do screen sharing. RE 3) The wiki page is updated for SoPeCo. Cheers, Roozbeh On 21.02.12 16:42, "Davide Dalle Carbonare" wrote: Dear All, this message to summarize few points from this morning phone call. 1) for the tools demonstration, it's completely up to you to decide what to present and how to show it to the other partners. 2) tools installation for the demo server side: communicate if they can/cannot be installed on the server hosted by Engineering. client side: communicate the requirements and info necessary to follow the demo. 3) provide the information on installation and license here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Tool s regards, Davide _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Fri Feb 24 12:12:48 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 24 Feb 2012 12:12:48 +0100 Subject: [Fiware-tools] *** IMPORTANT *** PhC AGAIN ON TUESDAY 28th Message-ID: <4F4770B0.4070900@eng.it> Dear All, the internal board meeting has been anticipated to Monday 27th so that the WP9 conference call is again on Tuesday as usual. Sorry about this continuous changes and best regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Fri Feb 24 17:16:14 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 24 Feb 2012 17:16:14 +0100 Subject: [Fiware-tools] Future Internet Application Message-ID: <4F47B7CE.5020804@eng.it> Dear All, I have further elaborated on what a Future Internet Application is on the methodology deliverable (in SVN under Deliverables). Whoever interested in providing comments and suggestions is more than welcome. Regards, M. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Mon Feb 27 14:49:38 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Mon, 27 Feb 2012 14:49:38 +0100 Subject: [Fiware-tools] Architecture document Message-ID: <4F4B89F2.6050407@eng.it> Dear All, during the today WPL/WPA joint meeting we agreed to move our contribution, to the Architecture deliverable, to the FI-WARE Private Wiki in order to let Juanjo and the other partners to review and comment it. Some of the contents of the architecture deliverable will be published (opened to the public) tomorrow. Our chapter will be published the 6th of March, in order to have time for review and update. This means that: - I'm going to MOVE our chapter from the Tools Private Wiki to the FI-WARE Private Wiki; I'll do this asap, at the very latest tomorrow morning. - after this, all further changes will be done directly on the FI-WARE Private Wiki; I ask you to verify that you have access to that wiki. Regards, Davide From fredrik.h.pettersson at ericsson.com Mon Feb 27 16:36:09 2012 From: fredrik.h.pettersson at ericsson.com (Fredrik Pettersson H) Date: Mon, 27 Feb 2012 16:36:09 +0100 Subject: [Fiware-tools] Catalogue Demo Message-ID: Hi all, As mentioned earlier we will do the Catalogue demo this week by letting you all play around with the version of the Catalogue that we have running right now. I have prepared a very brief outline of what you can do in the current version, which you will find below. One thing to note is that currently there is a mailing issue with emails sent from the system, where the mails are being stopped by spam filters. We are implementing a solution to this which should be up within a couple of days, but for now we know that mails to gmail.com addresses will at least work fine but will end up in the spam folder. If you are having problems registering your user in the catalogue due to the mailing issue then please send your username to me and I will activate your account for you. Please note that this is still a work in progress and that not everything is complete yet, but still feel free to report any issues you encounter. - Go to http://fi-ware.cloud.labs.ericsson.net - Register a user and log in to the site - Go to the "Enablers" section - Submit a new enabler by clicking the "Create new enabler" link at the top of the enabler listing and submitting the form - The proposed enabler is now in the validation queue and you will have to wait for an administrator (basically myself) to approve the enabler before you can progress to the next step. - After being approved your enabler will be listed in the enabler listing, but can only be seen by you and is tagged as "unpublished". - You can now edit the documentation, add downloads etc. and when happy with the content you can go to the edit tab on the main page of the enabler and change the status at the bottom to "published". The enabler can now be seen by anyone. - You can also use the "Group" tab at the top of the enabler page to add other people who should be able to help you in creating the enabler content. Best Regards, /Fredrik -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Tue Feb 28 10:58:32 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 28 Feb 2012 10:58:32 +0100 Subject: [Fiware-tools] PhC Today Message-ID: <4F4CA548.9000306@eng.it> Dear All, this is to confirm our conference call at 11.30. Contact details to join the PhC attached again for a new colleague of Engineering joining our team, Alessio Graziani. To join the webinar session follow the instructions below: - go to: http://webinars.eng.it - select the webinar from the combo-box: fiware-tools - insert your name - password: fiware ... and press "join" button. I would suggest to have no more than 10 minutes for each presentation (excluding questions) starting from the Engineering. The following ones will be ATOS, UDE, IBM, SAP (if any) and EAB (if any). As we did in the last PhC the meeting minutes will be shared on GoogleDocs so that each participant can contribute and review real time. The link: https://docs.google.com/document/d/13xwRfvVi1awJHVzEG208ITeRZlwnr89ldr2_YWQ-6aQ/edit Regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: conf call details.odt Type: application/vnd.oasis.opendocument.text Size: 15230 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Tue Feb 28 15:43:06 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 28 Feb 2012 15:43:06 +0100 Subject: [Fiware-tools] Catalogue Demo In-Reply-To: References: Message-ID: <4F4CE7FA.4060801@eng.it> Dear Fredrik, thanks for this preliminary version and for sure we will try to provide a description of our Eclipse Plugin to give a concrete example. Anyway, I have some preliminary comments on the catalogue: 1) I would list in a different tab the approved but yet unpublished enablers 2) the enabler once approved and ready to be finalized with the additional information I think that the browsing becomes not much intuitive. Let me try to explain what I meant ... I selected my enabler and I have in front of me a panel with 4 tabs: View, Edit, Group and Workflow. The one selected is View. I meant that having the "View" Tab selected I can review my Overview, Instances, Download and Documentation. In practice this is not the case as I can add from this tab new instances or software or documentation (I guess). I personally would have expected this to be done when the "Edit" tab was selected. 3) Why is there a limit of 2MB for any file uploaded? I did not try but I immediately noticed it. 4) Where can I add documentation? 5) Is the menu item "Instances" for software while "download" for any documentation but sw? Thanks and regards, Matteo Il 27/02/2012 16:36, Fredrik Pettersson H ha scritto: > Hi all, > As mentioned earlier we will do the Catalogue demo this week by > letting you all play around with the version of the Catalogue that we > have running right now. I have prepared a very brief outline of what > you can do in the current version, which you will find below. One > thing to note is that currently there is a mailing issue with emails > sent from the system, where the mails are being stopped by spam > filters. We are implementing a solution to this which should be up > within a couple of days, but for now we know that mails to gmail.com > addresses will at least work fine but will end up in the spam folder. > If you are having problems registering your user in the catalogue due > to the mailing issue then please send your username to me and I will > activate your account for you. Please note that this is still a work > in progress and that not everything is complete yet, but still feel > free to report any issues you encounter. > - Go to _http://fi-ware.cloud.labs.ericsson.net_ > - Register a user and log in to the site > - Go to the "Enablers" section > - Submit a new enabler by clicking the "Create new enabler" link at > the top of the enabler listing and submitting the form > - The proposed enabler is now in the validation queue and you will > have to wait for an administrator (basically myself) to approve the > enabler before you can progress to the next step. > - After being approved your enabler will be listed in the enabler > listing, but can only be seen by you and is tagged as "unpublished". > - You can now edit the documentation, add downloads etc. and when > happy with the content you can go to the edit tab on the main page of > the enabler and change the status at the bottom to "published". The > enabler can now be seen by anyone. > - You can also use the "Group" tab at the top of the enabler page to > add other people who should be able to help you in creating the > enabler content. > Best Regards, > /Fredrik > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Tue Feb 28 17:49:47 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 28 Feb 2012 17:49:47 +0100 Subject: [Fiware-tools] Architecure page moved to FI-WARE Private Message-ID: <4F4D05AB.5000007@eng.it> Dear All, I've moved the Architecture page to the FI-WARE Private wiki and now the link from our private wiki points to that page. If you have some update you'll do them directly there. Please take a look, that everything is ok on your sections, I just updated some picture layout to have all of them looking the same way. I now write to Juanjo to tell him that the contribution is ready for the review. I paste you at the end of this mail a note that I ask you to take care of... (the R is not for RCP-like only but for all the communications on that channel, the arrow specifies the direction of the request) regards, Davide ------------------------------------------------------------------------------------------------------------ http://www.fmc-modeling.org/download/notation_reference/Reference_Sheet-Block_Diagram.pdf Dear Open Specification Writers, while having a quick look at different Open Specifications in the private Wiki I noticed that there is some confusion according to the meaning FMC block diagrams. Please have a look at this cheat sheet. The semantics is actually very simple. However, it would be nice if we can use it consistently across the different Specs. So for example: The dotted rounded rectangle means: structure variance (parts of the diagram can be there multiple times, sometimes controlled by an agent.) If you want to subsume parts of the diagram you should us a plain border box (maybe with a light grey background) The R with a small arrow means an RPC-like semantics of a channel between two components (agents) Two components can only be connected via a channel. (no direct lines between them) A component (agent) can read/write from/to a storage (without a channel in between) Best regards, Torsten From fredrik.h.pettersson at ericsson.com Wed Feb 29 07:33:40 2012 From: fredrik.h.pettersson at ericsson.com (Fredrik Pettersson H) Date: Wed, 29 Feb 2012 07:33:40 +0100 Subject: [Fiware-tools] Catalogue Demo In-Reply-To: <4F4CE7FA.4060801@eng.it> References: <4F4CE7FA.4060801@eng.it> Message-ID: Hi Matteo, Thank you for your comments. 1. I'm not convinced that this is something we want to do. Those enablers that are approved but not published are unpublished for a reason, normally I would expect that they are not complete in documentation. Those creating the documentation should be able to do so without others viewing their incomplete work. 2. The "View" and "Edit" tabs are per subpage. This means that if you are viewing the main page of an enabler and click "Edit" you will be able to edit the enabler information that you provided in the initial enabler submission form. If you view the documentation page and click "Edit" you will be able to edit the documentation and so on. 3. This is just a default value, we will have to change it to whatever makes sense once we have any idea of what size files will be uploaded, but there should probably be some upper limit at least. 4. See answer 2 above. 5. Instances is for implementations of the GE, basically replacing what we were earlier discussing having in the instance catalogue. Downloads is for any downloadable files that need to be part of the GE and not related to an instance. Note that anyone can add a new instance to a GE but only the GE creator (and any other users the GE creator has added to the GE group) can add downloads, documentation etc. BR, /Fredrik ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 28 februari 2012 15:43 To: Fredrik Pettersson H Cc: 'fiware-tools at lists.fi-ware.eu' Subject: Re: [Fiware-tools] Catalogue Demo Dear Fredrik, thanks for this preliminary version and for sure we will try to provide a description of our Eclipse Plugin to give a concrete example. Anyway, I have some preliminary comments on the catalogue: 1) I would list in a different tab the approved but yet unpublished enablers 2) the enabler once approved and ready to be finalized with the additional information I think that the browsing becomes not much intuitive. Let me try to explain what I meant ... I selected my enabler and I have in front of me a panel with 4 tabs: View, Edit, Group and Workflow. The one selected is View. I meant that having the "View" Tab selected I can review my Overview, Instances, Download and Documentation. In practice this is not the case as I can add from this tab new instances or software or documentation (I guess). I personally would have expected this to be done when the "Edit" tab was selected. 3) Why is there a limit of 2MB for any file uploaded? I did not try but I immediately noticed it. 4) Where can I add documentation? 5) Is the menu item "Instances" for software while "download" for any documentation but sw? Thanks and regards, Matteo Il 27/02/2012 16:36, Fredrik Pettersson H ha scritto: Hi all, As mentioned earlier we will do the Catalogue demo this week by letting you all play around with the version of the Catalogue that we have running right now. I have prepared a very brief outline of what you can do in the current version, which you will find below. One thing to note is that currently there is a mailing issue with emails sent from the system, where the mails are being stopped by spam filters. We are implementing a solution to this which should be up within a couple of days, but for now we know that mails to gmail.com addresses will at least work fine but will end up in the spam folder. If you are having problems registering your user in the catalogue due to the mailing issue then please send your username to me and I will activate your account for you. Please note that this is still a work in progress and that not everything is complete yet, but still feel free to report any issues you encounter. - Go to http://fi-ware.cloud.labs.ericsson.net - Register a user and log in to the site - Go to the "Enablers" section - Submit a new enabler by clicking the "Create new enabler" link at the top of the enabler listing and submitting the form - The proposed enabler is now in the validation queue and you will have to wait for an administrator (basically myself) to approve the enabler before you can progress to the next step. - After being approved your enabler will be listed in the enabler listing, but can only be seen by you and is tagged as "unpublished". - You can now edit the documentation, add downloads etc. and when happy with the content you can go to the edit tab on the main page of the enabler and change the status at the bottom to "published". The enabler can now be seen by anyone. - You can also use the "Group" tab at the top of the enabler page to add other people who should be able to help you in creating the enabler content. Best Regards, /Fredrik _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Wed Feb 29 12:23:40 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 29 Feb 2012 12:23:40 +0100 Subject: [Fiware-tools] Catalogue Demo In-Reply-To: References: <4F4CE7FA.4060801@eng.it> Message-ID: <4F4E0ABC.80702@eng.it> Dear Fredrik, thanks some comments below... Il 29/02/2012 07:33, Fredrik Pettersson H ha scritto: > Hi Matteo, > Thank you for your comments. > 1. I'm not convinced that this is something we want to do. Those > enablers that are approved but not published are unpublished for a > reason, normally I would expect that they are not complete in > documentation. I experienced that now it is not possible to complete the description of an enabler when you select "Create New Enabler". Before you need an approval then you can proceed with the other info. Did I missed something? > Those creating the documentation should be able to do so without > others viewing their incomplete work. This is exactly what I meant but probably I not expressed myself very well. > 2. The "View" and "Edit" tabs are per subpage. This means that if you > are viewing the main page of an enabler and click "Edit" you will be > able to edit the enabler information that you provided in the initial > enabler submission form. If you view the documentation page and click > "Edit" you will be able to edit the documentation and so on. Mmmm, not very intuitive indeed at least for me > 3. This is just a default value, we will have to change it to whatever > makes sense once we have any idea of what size files will be uploaded, > but there should probably be some upper limit at least. I had this impression :-) > 4. See answer 2 above. > 5. Instances is for implementations of the GE, basically replacing > what we were earlier discussing having in the instance catalogue. > Downloads is for any downloadable files that need to be part of the GE > and not related to an instance. Note that anyone can add a new > instance to a GE but only the GE creator (and any other users the GE > creator has added to the GE group) can add downloads, documentation etc. Ok but I would better clarify. > BR, Best, M. > /Fredrik > > ------------------------------------------------------------------------ > *From:* Matteo Melideo [mailto:matteo.melideo at eng.it] > *Sent:* den 28 februari 2012 15:43 > *To:* Fredrik Pettersson H > *Cc:* 'fiware-tools at lists.fi-ware.eu' > *Subject:* Re: [Fiware-tools] Catalogue Demo > > Dear Fredrik, > thanks for this preliminary version and for sure we will try to > provide a description of our Eclipse Plugin to give a concrete example. > Anyway, I have some preliminary comments on the catalogue: > 1) I would list in a different tab the approved but yet unpublished > enablers > 2) the enabler once approved and ready to be finalized with the > additional information I think that the browsing becomes not much > intuitive. Let me try to explain what I meant ... > I selected my enabler and I have in front of me a panel with 4 tabs: > View, Edit, Group and Workflow. The one selected is View. I meant that > having the "View" Tab selected I can review my Overview, Instances, > Download and Documentation. In practice this is not the case as I can > add from this tab new instances or software or documentation (I guess). > I personally would have expected this to be done when the "Edit" tab > was selected. > > 3) Why is there a limit of 2MB for any file uploaded? I did not try > but I immediately noticed it. > > 4) Where can I add documentation? > > 5) Is the menu item "Instances" for software while "download" for any > documentation but sw? > > > Thanks and regards, > > Matteo > > Il 27/02/2012 16:36, Fredrik Pettersson H ha scritto: >> Hi all, >> As mentioned earlier we will do the Catalogue demo this week by >> letting you all play around with the version of the Catalogue that we >> have running right now. I have prepared a very brief outline of what >> you can do in the current version, which you will find below. One >> thing to note is that currently there is a mailing issue with emails >> sent from the system, where the mails are being stopped by spam >> filters. We are implementing a solution to this which should be up >> within a couple of days, but for now we know that mails to gmail.com >> addresses will at least work fine but will end up in the spam folder. >> If you are having problems registering your user in the catalogue due >> to the mailing issue then please send your username to me and I will >> activate your account for you. Please note that this is still a work >> in progress and that not everything is complete yet, but still feel >> free to report any issues you encounter. >> - Go to _http://fi-ware.cloud.labs.ericsson.net_ >> - Register a user and log in to the site >> - Go to the "Enablers" section >> - Submit a new enabler by clicking the "Create new enabler" link at >> the top of the enabler listing and submitting the form >> - The proposed enabler is now in the validation queue and you will >> have to wait for an administrator (basically myself) to approve the >> enabler before you can progress to the next step. >> - After being approved your enabler will be listed in the enabler >> listing, but can only be seen by you and is tagged as "unpublished". >> - You can now edit the documentation, add downloads etc. and when >> happy with the content you can go to the edit tab on the main page of >> the enabler and change the status at the bottom to "published". The >> enabler can now be seen by anyone. >> - You can also use the "Group" tab at the top of the enabler page to >> add other people who should be able to help you in creating the >> enabler content. >> Best Regards, >> /Fredrik >> >> >> _______________________________________________ >> Fiware-tools mailing list >> Fiware-tools at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From fredrik.h.pettersson at ericsson.com Wed Feb 29 12:27:04 2012 From: fredrik.h.pettersson at ericsson.com (Fredrik Pettersson H) Date: Wed, 29 Feb 2012 12:27:04 +0100 Subject: [Fiware-tools] Catalogue Demo In-Reply-To: <4F4E0ABC.80702@eng.it> References: <4F4CE7FA.4060801@eng.it> <4F4E0ABC.80702@eng.it> Message-ID: Hi Matteo, The process as we have implemented it is that you first provide some initial information regarding the enabler (in the create new enabler form), and then you wait for approval. Once approval has been given you are able to add more detailed information such as documentation and downloads and edit the overview etc. BR, /Fredrik ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 29 februari 2012 12:24 To: Fredrik Pettersson H Cc: 'fiware-tools at lists.fi-ware.eu' Subject: Re: [Fiware-tools] Catalogue Demo Dear Fredrik, thanks some comments below... Il 29/02/2012 07:33, Fredrik Pettersson H ha scritto: Hi Matteo, Thank you for your comments. 1. I'm not convinced that this is something we want to do. Those enablers that are approved but not published are unpublished for a reason, normally I would expect that they are not complete in documentation. I experienced that now it is not possible to complete the description of an enabler when you select "Create New Enabler". Before you need an approval then you can proceed with the other info. Did I missed something? Those creating the documentation should be able to do so without others viewing their incomplete work. This is exactly what I meant but probably I not expressed myself very well. 2. The "View" and "Edit" tabs are per subpage. This means that if you are viewing the main page of an enabler and click "Edit" you will be able to edit the enabler information that you provided in the initial enabler submission form. If you view the documentation page and click "Edit" you will be able to edit the documentation and so on. Mmmm, not very intuitive indeed at least for me 3. This is just a default value, we will have to change it to whatever makes sense once we have any idea of what size files will be uploaded, but there should probably be some upper limit at least. I had this impression :-) 4. See answer 2 above. 5. Instances is for implementations of the GE, basically replacing what we were earlier discussing having in the instance catalogue. Downloads is for any downloadable files that need to be part of the GE and not related to an instance. Note that anyone can add a new instance to a GE but only the GE creator (and any other users the GE creator has added to the GE group) can add downloads, documentation etc. Ok but I would better clarify. BR, Best, M. /Fredrik ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 28 februari 2012 15:43 To: Fredrik Pettersson H Cc: 'fiware-tools at lists.fi-ware.eu' Subject: Re: [Fiware-tools] Catalogue Demo Dear Fredrik, thanks for this preliminary version and for sure we will try to provide a description of our Eclipse Plugin to give a concrete example. Anyway, I have some preliminary comments on the catalogue: 1) I would list in a different tab the approved but yet unpublished enablers 2) the enabler once approved and ready to be finalized with the additional information I think that the browsing becomes not much intuitive. Let me try to explain what I meant ... I selected my enabler and I have in front of me a panel with 4 tabs: View, Edit, Group and Workflow. The one selected is View. I meant that having the "View" Tab selected I can review my Overview, Instances, Download and Documentation. In practice this is not the case as I can add from this tab new instances or software or documentation (I guess). I personally would have expected this to be done when the "Edit" tab was selected. 3) Why is there a limit of 2MB for any file uploaded? I did not try but I immediately noticed it. 4) Where can I add documentation? 5) Is the menu item "Instances" for software while "download" for any documentation but sw? Thanks and regards, Matteo Il 27/02/2012 16:36, Fredrik Pettersson H ha scritto: Hi all, As mentioned earlier we will do the Catalogue demo this week by letting you all play around with the version of the Catalogue that we have running right now. I have prepared a very brief outline of what you can do in the current version, which you will find below. One thing to note is that currently there is a mailing issue with emails sent from the system, where the mails are being stopped by spam filters. We are implementing a solution to this which should be up within a couple of days, but for now we know that mails to gmail.com addresses will at least work fine but will end up in the spam folder. If you are having problems registering your user in the catalogue due to the mailing issue then please send your username to me and I will activate your account for you. Please note that this is still a work in progress and that not everything is complete yet, but still feel free to report any issues you encounter. - Go to http://fi-ware.cloud.labs.ericsson.net - Register a user and log in to the site - Go to the "Enablers" section - Submit a new enabler by clicking the "Create new enabler" link at the top of the enabler listing and submitting the form - The proposed enabler is now in the validation queue and you will have to wait for an administrator (basically myself) to approve the enabler before you can progress to the next step. - After being approved your enabler will be listed in the enabler listing, but can only be seen by you and is tagged as "unpublished". - You can now edit the documentation, add downloads etc. and when happy with the content you can go to the edit tab on the main page of the enabler and change the status at the bottom to "published". The enabler can now be seen by anyone. - You can also use the "Group" tab at the top of the enabler page to add other people who should be able to help you in creating the enabler content. Best Regards, /Fredrik _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Wed Feb 29 12:39:42 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 29 Feb 2012 12:39:42 +0100 Subject: [Fiware-tools] Catalogue Demo In-Reply-To: References: <4F4CE7FA.4060801@eng.it> <4F4E0ABC.80702@eng.it> Message-ID: <4F4E0E7E.3050001@eng.it> :-) I also shared this process and I agree with this. What I meant is something different. I will try to explain it better. When you enter the catalogue portal you have a page dedicated to the enablers. I would like to see my enablers classified as published and unpublished in two different columns, forms or whatever but not all on the same list as it is now. That's all. It is just a matter of look&feed rather than process. In addition to this consider this just like an impression I had from a very first look. Best M. Il 29/02/2012 12:27, Fredrik Pettersson H ha scritto: > Hi Matteo, > The process as we have implemented it is that you first provide some > initial information regarding the enabler (in the create new enabler > form), and then you wait for approval. Once approval has been given > you are able to add more detailed information such as documentation > and downloads and edit the overview etc. > BR, > /Fredrik > > ------------------------------------------------------------------------ > *From:* Matteo Melideo [mailto:matteo.melideo at eng.it] > *Sent:* den 29 februari 2012 12:24 > *To:* Fredrik Pettersson H > *Cc:* 'fiware-tools at lists.fi-ware.eu' > *Subject:* Re: [Fiware-tools] Catalogue Demo > > Dear Fredrik, > thanks some comments below... > > Il 29/02/2012 07:33, Fredrik Pettersson H ha scritto: >> Hi Matteo, >> Thank you for your comments. >> 1. I'm not convinced that this is something we want to do. Those >> enablers that are approved but not published are unpublished for a >> reason, normally I would expect that they are not complete in >> documentation. > I experienced that now it is not possible to complete the description > of an enabler when you select "Create New Enabler". Before you need an > approval then you can proceed with the other info. Did I missed something? >> Those creating the documentation should be able to do so without >> others viewing their incomplete work. > This is exactly what I meant but probably I not expressed myself very > well. >> 2. The "View" and "Edit" tabs are per subpage. This means that if you >> are viewing the main page of an enabler and click "Edit" you will be >> able to edit the enabler information that you provided in the initial >> enabler submission form. If you view the documentation page and click >> "Edit" you will be able to edit the documentation and so on. > Mmmm, not very intuitive indeed at least for me >> 3. This is just a default value, we will have to change it to >> whatever makes sense once we have any idea of what size files will be >> uploaded, but there should probably be some upper limit at least. > I had this impression :-) >> 4. See answer 2 above. >> 5. Instances is for implementations of the GE, basically replacing >> what we were earlier discussing having in the instance catalogue. >> Downloads is for any downloadable files that need to be part of the >> GE and not related to an instance. Note that anyone can add a new >> instance to a GE but only the GE creator (and any other users the GE >> creator has added to the GE group) can add downloads, documentation etc. > > Ok but I would better clarify. >> BR, > Best, > > M. >> /Fredrik >> >> ------------------------------------------------------------------------ >> *From:* Matteo Melideo [mailto:matteo.melideo at eng.it] >> *Sent:* den 28 februari 2012 15:43 >> *To:* Fredrik Pettersson H >> *Cc:* 'fiware-tools at lists.fi-ware.eu' >> *Subject:* Re: [Fiware-tools] Catalogue Demo >> >> Dear Fredrik, >> thanks for this preliminary version and for sure we will try to >> provide a description of our Eclipse Plugin to give a concrete example. >> Anyway, I have some preliminary comments on the catalogue: >> 1) I would list in a different tab the approved but yet unpublished >> enablers >> 2) the enabler once approved and ready to be finalized with the >> additional information I think that the browsing becomes not much >> intuitive. Let me try to explain what I meant ... >> I selected my enabler and I have in front of me a panel with 4 tabs: >> View, Edit, Group and Workflow. The one selected is View. I meant >> that having the "View" Tab selected I can review my Overview, >> Instances, Download and Documentation. In practice this is not the >> case as I can add from this tab new instances or software or >> documentation (I guess). >> I personally would have expected this to be done when the "Edit" tab >> was selected. >> >> 3) Why is there a limit of 2MB for any file uploaded? I did not try >> but I immediately noticed it. >> >> 4) Where can I add documentation? >> >> 5) Is the menu item "Instances" for software while "download" for any >> documentation but sw? >> >> >> Thanks and regards, >> >> Matteo >> >> Il 27/02/2012 16:36, Fredrik Pettersson H ha scritto: >>> Hi all, >>> As mentioned earlier we will do the Catalogue demo this week by >>> letting you all play around with the version of the Catalogue that >>> we have running right now. I have prepared a very brief outline of >>> what you can do in the current version, which you will find below. >>> One thing to note is that currently there is a mailing issue with >>> emails sent from the system, where the mails are being stopped by >>> spam filters. We are implementing a solution to this which should be >>> up within a couple of days, but for now we know that mails to >>> gmail.com addresses will at least work fine but will end up in the >>> spam folder. If you are having problems registering your user in the >>> catalogue due to the mailing issue then please send your username to >>> me and I will activate your account for you. Please note that this >>> is still a work in progress and that not everything is complete yet, >>> but still feel free to report any issues you encounter. >>> - Go to _http://fi-ware.cloud.labs.ericsson.net_ >>> - Register a user and log in to the site >>> - Go to the "Enablers" section >>> - Submit a new enabler by clicking the "Create new enabler" link at >>> the top of the enabler listing and submitting the form >>> - The proposed enabler is now in the validation queue and you will >>> have to wait for an administrator (basically myself) to approve the >>> enabler before you can progress to the next step. >>> - After being approved your enabler will be listed in the enabler >>> listing, but can only be seen by you and is tagged as "unpublished". >>> - You can now edit the documentation, add downloads etc. and when >>> happy with the content you can go to the edit tab on the main page >>> of the enabler and change the status at the bottom to "published". >>> The enabler can now be seen by anyone. >>> - You can also use the "Group" tab at the top of the enabler page to >>> add other people who should be able to help you in creating the >>> enabler content. >>> Best Regards, >>> /Fredrik >>> >>> >>> _______________________________________________ >>> Fiware-tools mailing list >>> Fiware-tools at lists.fi-ware.eu >>> http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From john.sandberg at ericsson.com Wed Feb 29 12:52:30 2012 From: john.sandberg at ericsson.com (John Sandberg) Date: Wed, 29 Feb 2012 12:52:30 +0100 Subject: [Fiware-tools] Catalogue Demo In-Reply-To: <4F4E0E7E.3050001@eng.it> References: <4F4CE7FA.4060801@eng.it> <4F4E0ABC.80702@eng.it> <4F4E0E7E.3050001@eng.it> Message-ID: <6FFCEF6A0AE1D6468ADD42818409956220A6D0108D@ESESSCMS0352.eemea.ericsson.se> Ciao, Do you mean as an admin? Users will only see the published ones plus their own that they are workng on and it will be marked "un-published". /J ________________________________ From: fiware-tools-bounces at lists.fi-ware.eu [mailto:fiware-tools-bounces at lists.fi-ware.eu] On Behalf Of Matteo Melideo Sent: den 29 februari 2012 12:40 To: Fredrik Pettersson H Cc: 'fiware-tools at lists.fi-ware.eu' Subject: Re: [Fiware-tools] Catalogue Demo :-) I also shared this process and I agree with this. What I meant is something different. I will try to explain it better. When you enter the catalogue portal you have a page dedicated to the enablers. I would like to see my enablers classified as published and unpublished in two different columns, forms or whatever but not all on the same list as it is now. That's all. It is just a matter of look&feed rather than process. In addition to this consider this just like an impression I had from a very first look. Best M. Il 29/02/2012 12:27, Fredrik Pettersson H ha scritto: Hi Matteo, The process as we have implemented it is that you first provide some initial information regarding the enabler (in the create new enabler form), and then you wait for approval. Once approval has been given you are able to add more detailed information such as documentation and downloads and edit the overview etc. BR, /Fredrik ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 29 februari 2012 12:24 To: Fredrik Pettersson H Cc: 'fiware-tools at lists.fi-ware.eu' Subject: Re: [Fiware-tools] Catalogue Demo Dear Fredrik, thanks some comments below... Il 29/02/2012 07:33, Fredrik Pettersson H ha scritto: Hi Matteo, Thank you for your comments. 1. I'm not convinced that this is something we want to do. Those enablers that are approved but not published are unpublished for a reason, normally I would expect that they are not complete in documentation. I experienced that now it is not possible to complete the description of an enabler when you select "Create New Enabler". Before you need an approval then you can proceed with the other info. Did I missed something? Those creating the documentation should be able to do so without others viewing their incomplete work. This is exactly what I meant but probably I not expressed myself very well. 2. The "View" and "Edit" tabs are per subpage. This means that if you are viewing the main page of an enabler and click "Edit" you will be able to edit the enabler information that you provided in the initial enabler submission form. If you view the documentation page and click "Edit" you will be able to edit the documentation and so on. Mmmm, not very intuitive indeed at least for me 3. This is just a default value, we will have to change it to whatever makes sense once we have any idea of what size files will be uploaded, but there should probably be some upper limit at least. I had this impression :-) 4. See answer 2 above. 5. Instances is for implementations of the GE, basically replacing what we were earlier discussing having in the instance catalogue. Downloads is for any downloadable files that need to be part of the GE and not related to an instance. Note that anyone can add a new instance to a GE but only the GE creator (and any other users the GE creator has added to the GE group) can add downloads, documentation etc. Ok but I would better clarify. BR, Best, M. /Fredrik ________________________________ From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: den 28 februari 2012 15:43 To: Fredrik Pettersson H Cc: 'fiware-tools at lists.fi-ware.eu' Subject: Re: [Fiware-tools] Catalogue Demo Dear Fredrik, thanks for this preliminary version and for sure we will try to provide a description of our Eclipse Plugin to give a concrete example. Anyway, I have some preliminary comments on the catalogue: 1) I would list in a different tab the approved but yet unpublished enablers 2) the enabler once approved and ready to be finalized with the additional information I think that the browsing becomes not much intuitive. Let me try to explain what I meant ... I selected my enabler and I have in front of me a panel with 4 tabs: View, Edit, Group and Workflow. The one selected is View. I meant that having the "View" Tab selected I can review my Overview, Instances, Download and Documentation. In practice this is not the case as I can add from this tab new instances or software or documentation (I guess). I personally would have expected this to be done when the "Edit" tab was selected. 3) Why is there a limit of 2MB for any file uploaded? I did not try but I immediately noticed it. 4) Where can I add documentation? 5) Is the menu item "Instances" for software while "download" for any documentation but sw? Thanks and regards, Matteo Il 27/02/2012 16:36, Fredrik Pettersson H ha scritto: Hi all, As mentioned earlier we will do the Catalogue demo this week by letting you all play around with the version of the Catalogue that we have running right now. I have prepared a very brief outline of what you can do in the current version, which you will find below. One thing to note is that currently there is a mailing issue with emails sent from the system, where the mails are being stopped by spam filters. We are implementing a solution to this which should be up within a couple of days, but for now we know that mails to gmail.com addresses will at least work fine but will end up in the spam folder. If you are having problems registering your user in the catalogue due to the mailing issue then please send your username to me and I will activate your account for you. Please note that this is still a work in progress and that not everything is complete yet, but still feel free to report any issues you encounter. - Go to http://fi-ware.cloud.labs.ericsson.net - Register a user and log in to the site - Go to the "Enablers" section - Submit a new enabler by clicking the "Create new enabler" link at the top of the enabler listing and submitting the form - The proposed enabler is now in the validation queue and you will have to wait for an administrator (basically myself) to approve the enabler before you can progress to the next step. - After being approved your enabler will be listed in the enabler listing, but can only be seen by you and is tagged as "unpublished". - You can now edit the documentation, add downloads etc. and when happy with the content you can go to the edit tab on the main page of the enabler and change the status at the bottom to "published". The enabler can now be seen by anyone. - You can also use the "Group" tab at the top of the enabler page to add other people who should be able to help you in creating the enabler content. Best Regards, /Fredrik _______________________________________________ Fiware-tools mailing list Fiware-tools at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Wed Feb 29 15:24:02 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 29 Feb 2012 15:24:02 +0100 Subject: [Fiware-tools] Fwd: [Fiware-wpl] Technical roadmap In-Reply-To: <4F4E319E.9040301@tid.es> References: <4F4E319E.9040301@tid.es> Message-ID: <4F4E3502.9080503@eng.it> F.Y.I. -------- Messaggio originale -------- Oggetto: [Fiware-wpl] Technical roadmap Data: Wed, 29 Feb 2012 15:09:34 +0100 Mittente: Juanjo Hierro A: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, We are still working on the reference example and guidelines for producing the Technical Roadmap deliverable. We will deliver it later this evening. We are trying to provide a rather clear set of instructions, plus an example around the Data/Context Management Chapter, that avoids having to fix things later in order to achieve the necessary alignment. At the same time, something rather easy to write (no more than two pages, probably closer to one, per chapter) which focuses on what can be useful. In the meantime, keep working on the Architecture Deliverable to meet the March 6 deadline, please. I also encourage you to plan activities in the Sprint of March (if you haven't already done so). I understand that this Sprint should already include activities dealing with actual software development around GEs for most of the chapters. I would like to review such planning in the bilateral meetings we will have next week. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: