From uwe.riss at sap.com Wed Oct 3 17:58:56 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 3 Oct 2012 17:58:56 +0200 Subject: [Fiware-apps] FW: [Fiware-wpl] IMPORTANT: Next steps regarding review of FI-WARE Architecture and Open Specifications Message-ID: <1491C91A94302A448D73CD9C6B7A782046C551A2FA@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, Please pay attention to the following activity for your GEs that must start immediately to address the reviewers' demands regarding the revision of the Open Specifications. If you have any question please feel free to ask. Best regards, Uwe From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 3. Oktober 2012 17:28 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] IMPORTANT: Next steps regarding review of FI-WARE Architecture and Open Specifications Hi all, As per decision yesterday, during our weekly joint WPLs/WPAs follow-up confcall, we will implement the re-structuring of the wiki pages proposed in: https://forge.fi-ware.eu/docman/view.php/7/1335/2012-10-01_FI-WARE_Resubmission_DX11.ppt Please communicate this to your teams. Every WPL will take care of creating the FIWARE.OpenSpecifications.. wiki page per each of the GEs linked to his chapter. This is an activity that you should start on Monday October 8th and get finished by October 9th, so better you plan this in advance and, if you decide to distribute the task and assign it to GE owners/leaders, you should share with them this plan also in advance. To create the FIWARE.OpenSpecifications.. wiki page of a given GE, you should rely on the template defined in: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php?title=Open_specification_resubmission_template That template contains precise instructions about the steps to follow. You will find there a link to an example of how the resulting page may look like. One particular question you should carefully handle is the Copyright section of the specifications of a given GE. That section should contain the list of copyright statements from the companies/organizations authoring the specifications. Of course, that means that you should come with an agreement of who are the companies/organizations that should be listed as authors. Hopefully, this shouldn't be a big issue. On our side (TID), we will generate the part of the wiki that will allow us to navigate directly to the GE specs and generate the FI-WARE GE Open Specifications deliverables to be resubmitted. Once all changes are verified, we should start a final peer-review on October 10th. I will send an email with assignments for this last peer-review previous to our joint WPLs/WPAs confcall on Monday October 8th. We would like to send a note to the PO and reviewers on October 10th updating them on the results of our two first peer-reviews and the fact that they can access a revised version of the FI-WARE GE Open Specifications on the public wiki (however, the final official deliverable, in .pdf format, will be available by end of the month, incorporating results of the last, third peer-review). Because of that, you are asked to incorporate all changes derived as results of the two first peer-reviews (August and September) by end of this week, October 7th. If you have any particular question or concern, please let me know. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Sun Oct 7 11:47:23 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Sun, 7 Oct 2012 11:47:23 +0200 Subject: [Fiware-apps] FW: [Fiware-wpl] [Suspected Spam] IMPORTANT Fwd: FI-WARE: D2.6.1 State of the Art Analysis - Emerging Technologies (CANCELED) Message-ID: <1491C91A94302A448D73CD9C6B7A782046C56C1E72@DEWDFECCR02.wdf.sap.corp> FYI BR, Uwe From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Samstag, 6. Oktober 2012 12:51 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] [Suspected Spam] IMPORTANT Fwd: FI-WARE: D2.6.1 State of the Art Analysis - Emerging Technologies (CANCELED) Hi all, I have a long confcall yesterday with Arian regarding many topics. I will summarize the results later in another mail. One of the topics discussed was about deliverable D2.6.1 "State of the Art Analysis". I asked him to cancel this deliverable because that would help us to focus on the very urgent and important matters that we have currently on the table. Arian accepted. Despite some of you may have started development of this deliverable, I believe it would inevitably distract some resources from all of us, starting with WPLs and WPAs, if we wanted to deliver something of enough quality. Therefore, I believe that the decision definitively goes for the sake of the project. This doesn't mean that the two other deliveries of this deliverable are cancelled. They still hold. 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 -------- Original Message -------- Subject: FI-WARE: D2.6.1 State of the Art Analysis - Emerging Technologies Date: Sat, 6 Oct 2012 10:33:42 +0000 From: To: , CC: Dear all, FI-WARE D2.6.1 "State of the Art Analysis - Emerging Technologies", due for M18, is hereby cancelled. Best regards, Arian. ________________________________ 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 Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From thorsten.sandfuchs at sap.com Thu Oct 11 09:38:34 2012 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 11 Oct 2012 09:38:34 +0200 Subject: [Fiware-apps] Internal review D.3.1.1 FI-WARE GE Open Specifications Message-ID: Dear WP3-partners, we would like to conduct an internal review of our own deliverable (as it probably will be submitted to the EC). For this we compiled the deliverable in the DOCX format for you. You can download it here: https://sapmats-de.sap-ag.de/download/download.cgi?id=FDO0XAO5EZT9C2IINHD7Y66IZ3EACQM1EZ82JRGCV106X39ITK Please have a close look on the layout and the content of your particular chapter or have general remarks. Please check 1. Is your OpenSpecification even part of the deliverable? 2. Is all needed and desired text part of the deliverable? 3. Do you see potential on improving your contribution content wise, if you take the content and structure of other open specifications in this deliverable into account 4. Are there any layouting problems or issues with pictures or something else? You can: - Use the standard word-review functionality in order to provide feedback or attach comments - You should not change the text of your own specifications within the document, rather use the wiki-link provided on the top of every-page and change the content _directly_ in the wiki (once the final deliverable will get generated, the content will be there) - We would (if you have major changes) recommend: You should change the text of partner contributions (where you see improvement possibilities) within the document and send the document to the responsible partner for inclusion in the wiki page Thank you for your support and dedication to this topic. Best regards, /Thorsten -- Thorsten Sandfuchs SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri Oct 12 12:49:08 2012 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 12 Oct 2012 12:49:08 +0200 Subject: [Fiware-apps] Recall: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Message-ID: Sandfuchs, Thorsten would like to recall the message, "[Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications". From thorsten.sandfuchs at sap.com Fri Oct 12 07:01:34 2012 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 12 Oct 2012 07:01:34 +0200 Subject: [Fiware-apps] FW: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications In-Reply-To: <507795E8.60806@tid.es> References: <50770372.4030804@tid.es> <507795E8.60806@tid.es> Message-ID: Dear colleagues, For our chapter we take the option of central generation of documents, like Juanjo gave the option in step 1. I already compiled the needed document and you can download a rar file here: https://sapmats-de.sap-ag.de/download/download.cgi?id=UND71WW7I5TT66J8YTDXK2OSX9ZCIOK6SCIFPYZZNKQPF93K74 Therefore the request from Juanjo to have step 1-4 completed rather soon, should be a no-brainer. Once you reviewed, that I did compile it correctly, please upload the document (and only the one related to your open specification) somewhere like requested by Juanjo. If there are still errors in the document, you can contact me and we can easily generate again. Best, /Thorsten From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 12. Oktober 2012 06:01 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Hi, You may have received an email from your WPL or WPA regarding instructions about how we are going to tackle the third and final peer review of the FI-WARE GE Open Specifications that we have to resubmit by November 2nd at the latest (see attachment) IMPORTANT NOTE: We rather NEED that you to carry out a peer-review that focuses on how suitable the contents are. We are afraid that some of the peer-reviews carry out so far were mostly "editorial", i.e., polishing the English, highlighting issues regarding the structure, etc. We need that people review the document from the perspective of a developer or a potential implementer of the spec and point out what you don't understand, what you miss, etc. The intend of this message is twofold. First, make sure it arrives without further delays in your inbox. Second, add a number of enhancements to the process described in the original email that hopefully will allow to make it faster and more efficient. The enhancements have to do with trying to carry out the peer-review using docx files rather than reading the wiki and providing a list of change requests in a separate form. This would allow to drop out the part of the revision form that I sent earlier which had to do with providing detailed editorial comments. Please find attached the revised form. The following is a description of the whole process with the suggested enhancements. If you hadn't read the original email, you just need to read this. For every FI-WARE GE Open Specification (as listed in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications), we will have to carry out the following steps. 1. Generate docx-version of each of the FI-WARE GE Open Specifications to ease the review. There are multiple ways for doing so and it is up to each Chapter to select its preferred one, but here you are a simple set of steps you can follow to generate a docx version (I have used this personally and have found it rather straightforward): * Create a document in Google docs (I hope you have an account, otherwise agree with your WPL on how to get access to one or come back to us :-) * Go to the wiki page of the deliverable. Don't forget to access it in "read" mode (i.e., not logged in FusionForge) because that would avoid copying the "edits" * Copy and Paste directly from the Wiki page into the Google Docs. Notes: * You have to split this in several steps, because Google docs gets blocked if you try to copy&paste too many pages with too many figures. * Don't forget to add the API specs. Typically, you have to first copy&paste what is in the first-level FI-WARE GE Open Specification wiki page, then navigate to each API specification wiki page and copy and paste the contents. * Once the document is generated, you can save it as a Word docx in your local PC. * Run a quick check through the docx file fixing some easy-to-solve questions such as adjusting size of figures, doing some pagination which could easy reading, etc. Please, don't try to make it perfect, we just need a version on which you may apply changes and track those changes with the standard MS Word change control tools. 1. Upload the generated file in either SVN or the docman of the "FI-WARE Private" project in FusionForge (whatever tool you prefer) 2. Add the link to the docx file in SVN or docman to the column "Doc to review" corresponding to the FI-WARE GE in the following shared spreadsheet in Google that we will use as cockpit for the following-up the whole process: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc 3. Sent an email to the WPL of the reviewing chapter so that they know that the docx associated to the FI-WARE GE Open Specification is available for review. Please, don't wait until the rest of docs associated to other FI-WARE Open Specifications in your same chapter are uploaded. Leaders of reviewing chapters are also asked to check when there are new documents to review from time to time. 4. Carry out the review you have been assigned. Reviewers would be required to generate two files, that they should upload again to SVN or docman (whatever you prefer) and link from the Google cockpit. If you are a reviewer, please don't wait until you have both. Please upload each as soon as it is available and inform the leader of the chapter being reviewed that you have done so: * A commented docx for the deliverable which would include all comments under change control. A link to this file should be provided in the "Commented doc" column of the cockpit. * the simple FI-WARE Peer-review form attached. A link to this file should be provided in the "Simple peer-review form" column of the cockpit. 1. Process comments. This would be carried out typically by the owner of the FI-WARE GE Open Specifications. This would imply: * generate a temporary draft by means of accepting/rejecting changes from the commented docx of your specifications * consider general comments in the FI-WARE Peer-review form linked to your FI-WARE GE Open Specifications and introduce changes that you would consider may address them 1. You will generate a new docx by means of implementing step 6 you should upload to the SVN or docman of "FI-WARE Private" and will provide a link to it in column "Revised doc" of the cockpit 2. You will have to update the contents of the public wiki with the contents of the document associated to the revised version It's up to each Chapter Leader to decide how to organize: * Steps 1-4. Some of the Chapter Leaders may prefer to perform these steps by themselves but others may decide to distribute the task associated to each FI-WARE GE Open Specification in his chapter * Step 5. Chapter Leaders will organize the assigned peer-review involving members of his chapter. How he does this is up to him and members of the chapter. They are asked to fill the column title "Assigned reviewer" to communicate who has been assigned the task to review a given doc. Note that you can start the review of an Open Specification as soon as the file is available (i.e., there is a link available in column "Doc to review" of the Peer-Review cockpit. * Steps 6-8. I can imagine that the owner of a FI-WARE GE Open Specification will carry out these steps. However, the Chapter Leader may decide to carry out the update of the wiki, or distribute the task and assign it also to owners of each FI-WARE GE Open Specification VERY IMPORTANT: * PLEASE try to make steps 1-4 as soon as possible. Our experience is that this could be performed in maximum one hour per GE specification, probably much less. The sooner you make docx for review available on the cockpit, the sooner someone will review it. * Step 8 is quite important because we plan to submit the final deliverables based on docx documents that will be generated once again from the wiki. Therefore, if you don't update the wiki, the resubmitted deliverable will go without your changes. SAP is working in a number of tools and processes that will help to produce the docx documents that will be finally submitted and I would like to thank them for the work they are doing in this respect. Milestones for the peer-review are the following: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Assignment of peer-reviewers is as follows: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data Hope it works. Please try to make this final push. We face a critical milestone in the project that has to do with delivering a complete and rich set of FI-WARE Open Specifications. How they will be judged by reviewers will play a relevant role in our next, critical, review. Don't hesitate to ask any question or doubt. Last but not least, I would like to thank SAP for the support in defining this process and the work they are doing developing the tools that will try to automate the final generation of deliverables as much as possible. 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 -------- Original Message -------- Subject: [Fiware-wpa] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Date: Thu, 11 Oct 2012 08:59:09 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, Re-structuring of the wiki is almost done and complete FI-WARE GE Open Specifications can now be easily accessed from: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Thanks to all of you for the great job ! Only the IoT chapter has not done the job. Unfortunately, I'm afraid this was because Thierry was sick and probably the request didn't arrive at the IoT Chapter team. I will take care of this personally and, hopefully, the whole chapter will be fixed by EOB today. The pages of some few FI-WARE GE Open Specifications need to revised because they seem to have found some issue adapting to the proposed template. We will contact you directly for those cases. We should start now the last and third peer review of the Open Specifications. Following is the proposal on assignment of the third peer-reviews: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data I have tried to avoid repeating any previous peer review (you can find the tables summarizing assignment in previous peer-reviews at the end of this message, just fyi). The calendar I propose to follow is this: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Don't forget to use the attached template for comments. Since we have now re-structure the wiki, we have adapted it so that you have to carry out first a peer-review of the Chapter Architecture and then of each of the FI-WARE GE Open Specifications, once again listed at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Our target goal is to have all FI-WARE GE Open Specifications submitted by the end of the week starting October 29th, i.e., deadline would be November 2nd. Deliverables for the chapters do not have to be submitted on exactly the same date, so we will submit deliverables corresponding to the chapters along that week. Please foward to your teams. Cheers, -- Juanjo ====== Appendix: tables with assignments in previous reviews First peer review: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Second peer review: Chapter to be reviewed Reviewing chapter Data Cloud Cloud I2ND Apps IoT IoT Data I2ND Security Security Apps ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.klein at sap.com Fri Oct 12 11:10:32 2012 From: andreas.klein at sap.com (Klein, Andreas) Date: Fri, 12 Oct 2012 11:10:32 +0200 Subject: [Fiware-apps] FW: Peer review of FI-WARE Apps Open Specifications In-Reply-To: <8AF50F49B590C242AEBA50D6730499A4056D37F17B@DEWDFECCR05.wdf.sap.corp> References: <8AF50F49B590C242AEBA50D6730499A4056D37F17B@DEWDFECCR05.wdf.sap.corp> Message-ID: <8AF50F49B590C242AEBA50D6730499A4056D37F17D@DEWDFECCR05.wdf.sap.corp> Dear WP3-partners, Thorsten generated all the required WP3 docx files for the 3rd review round and we send them to the Security Chapter, so there is no further Action required from your side. Best Regards Andreas From: Klein, Andreas Sent: Freitag, 12. Oktober 2012 10:58 To: 'pascal.bisson at thalesgroup.com'; 'daniel.gidoin at thalesgroup.com' Cc: DL Research FI-WARE APPS Subject: Peer review of FI-WARE Apps Open Specifications Hi Pascal, Hi Daniel, As requested by Juanjo, the docx Versions of all FI-WARE APPS GE Open Specification are ready to be reviewed. Please find the respective documents linked in the peer-review cockpit: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc Please inform us as soon as you have finished and uploaded the review for each document that we can work on the implementation of your comments without needless delay. Thanks & Regards Andreas Andreas Klein SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe T +49-6227-7-52554 -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Wed Oct 17 16:52:33 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 17 Oct 2012 16:52:33 +0200 Subject: [Fiware-apps] To all GE Owners: Contributions to the Whitepaper Message-ID: <1491C91A94302A448D73CD9C6B7A782046C789B265@DEWDFECCR02.wdf.sap.corp> Dear all, One of the due issues is the contribution of the FI-WARE Whitepaper. The announced timeline looks as follows: * generation of almost stable draft: October 26th * peer-review during week starting October 29th * target submission date: November 5th This whitepaper will be handled as a review/evolution of the contents in the "FI-WARE Product Vision" that is described in the wiki. These are the major actions that you have to carried out: ? Drop general description of each of the GEs in the FI-WARE Product Vision. It is suggested that these contents are moved/merged with overview section of the Architecture Description of the GE (also part of its Open Specifications). This will save us from inconsistencies between contents of the Product Vision and the most recent Architecture Description and Open Specifications. ? The FI-WARE Product Vision would just keep the overview section per chapter but this will be just the initial content. The idea is to add sections dealing with usage scenarios which describe, high-level, how GEs can be used in an encompassed manner to cover those scenarios. * TID made an initial proposal on the new sections to be added. A first draft/template of the target whitepaper is available at: https://forge.fi-ware.eu/docman/view.php/27/1333/FI-WARE+Product+Vision+New+Draft+12-10-01.docx It is particularly the second action Usage Scenarios on which you can already start to works. If there are further question please feel free to ask. I will answer or forward them and distribute the information. Best regards, Uwe PS Further background information From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 24. September 2012 18:11 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Approach regarding the whitepaper document about FI-WARE including description of common usage scenarios of FI-WARE GEs Hi all, I'll try to describe the approach that we have agreed to follow, after some discussion during our regular confcall this morning, regarding development of the whitepaper document about FI-WARE including description of common usage scenarios of FI-WARE GEs. Thanks to all those who contributed with rather good ideas that have helped to improve the approach proposed initially. In this description I will also give more details about the general approach that I had in mind. I hope they will help to get a better clue of how the whitepaper / product-vision document may look like. The whitepaper would come as a result of reviewing the FI-WARE Product Vision, so that the following changes would be introduced: 1. Introduction would stay at it is now (see http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision). Note that it would provide a link to the "Overall FI-WARE Vision" where the basic concepts of FI-WARE would get introduced. 2. Regarding each chapter, we will keep for sure the "Overview" and "Terms and Definitions" section. We would essentially drop the contents linked to description of each individual GE that should go wherever it is appropriate in the Architecture Description of FI-WARE GEs (probably "Overview" and "Basic Concepts" sections) but we may also capture part of the description of each GE in the Overview section if suitable. 3. We will add per each of the chapters a number of sections each dealing with a description on how GEs in the chapter can be used or integrated, together or with other GEs from other chapters, in order to address a given common usage scenario. This sections will become "recipes" that a given application developer can read to understand how to address/solve a given scenario. Some of these scenarios will imply integration of GEs coming from several chapters, so we will have to make a choice regarding what is the chapter where description of the scenario will be more appropriate. Some examples of sections dealing with description of usage scenarios are the following (the title may change): * "Developing context-aware applications": here, we would elaborate on how several of the different GEs of the Data/Context Management chapter (particularly the Pub/Sub Broker GE, the CEP GE, the BigData GE, the Semantic Application Support GE and the Semantic Annotation Support GE) can be integrated together to support the notion of a "Context Managament Platform" that make it easier to develop context-aware applications. We would explain how data gathered by the Pub/Sub Broker GE may feed the CEP GE so that this last one can trigger actions based on detected scenarios, for example. We would also elaborate on how data generated by the CEP or the BigData GE may ultimately enrich context information, etc. The natural place where this section could fit is would be the chapter on Data/Context Management. * "Capturing data from the physical world and making it part of the context": here, we would elaborate on how data from sensors, captured through the IoT chapter GEs will feed the Context Broker, therefore the whole Context Management Platform we envision. We may place this section in any of the two chapters, the IoT or the Data chapter, but we would go for a compromise so that, for example, this section would go into the IoT chapter and would be referred from somewhere in the Data Chapter (for example, the section on "Developing context-aware applications" where we can mention that "part of the contextual information may come from physical objects. Check section on Capturing data from the physical world and making it part of the context" (text in blue would be link to the referred section) * "Supporting an Open Data approach": here, we would elaborate on how the envisioned Context Management Platform could be used to support an Open Data approach. We would elaborate on how organization willing to publish their data as open data would make that data available on a single Context Management platform linked to a FI-WARE Instance serving that purpose. We would also elaborate on how such FI-WARE Instance may bring GEs for the Apps chapter enabling services from the Context Management Platform to be published so that it becomes available to third parties and even end users ... Despite we would refer to GEs from the App Chapter, probably this section would fit more naturally as part of the Data/Context Management chapter, despite we may add a cross reference from the Apps Chapter * "Authenticaded access to APIs exported by FI-WARE GEs": here, we would elaborate on what architecture is supported that will enable authenticaded access control to APIs provided by the GEs, relying on usage of the Identity Management GE. The described architecture would be generic and should work for any GE, no matter what chapter it belongs to, but the description of the scenario would naturally fit as part of the Security chapter. * etc. 1. Telef?nica will come with a first draft of the FI-WARE Product Vision where we will drop out all those contents from the current FI-WARE Product Vision which will not longer be kept as part of the FI-WARE Product Vision. We will try that this draft be available by Wednesday EOB. Together with this first draft, we will come with a list of "usage scenario" / "recipe" sections that we would like to propose for each chapter. Once agreed with the corresponding chapter leader, it will be up to the chapter leader to organize the work as to deliver the final contents of each section. Note that development of some of this "recipe" sections may require contribution by more than one chapter so they have to organize how contents will be developed (for example, section on "Supporting an Open Data approach"). Our suggestion is that the chapter leaders take the responsibility of providing a first draft of the section and then the other complementary chapters perform a peer review (following the same example, the Data/Context Management leader would provide a first draft of the section titled "Supporting an Open Data approach" and then the Apps Chapter Leader should review it). 2. We will share the table of contents derived from previous points with UC projects and will check whether they feel like there is some "usage scenario" / "recipe" section that is missing. This would allow us to arrive at the review meeting with a document that has been validated by UC projects. Of course, we would work on a copy of the FI-WARE Product Vision we will setup on the FI-WARE Private Wiki. We will replace the current FI-WARE Product Vision once a solid version is already available (may not contain all the final sections but at least consistent with the FI-WARE Architecture Description and Open Specifications) Let me repeat again the rationale behind this approach: I may be wrong, but I believe that the reviewers look for something that is relatively stand-alone. Something someone may read to get a clear vision about what we are envisioning in FI-WARE without too many references to other parts of the FI-WARE documentation. In this respect, I believe it would be difficult to develop such a target whitepaper without repeating a lot of the good stuff that was already there in the FI-WARE Product Vision document (which, I remind you, got overall good acceptance by the reviewers). On the other hand, introducing references to contents of the FI-WARE Product Vision doesn't solve the problem because we have found that peopled ends not reading the referred contents and, besides, even those sections on the current FI-WARE Product Vision that are in the best shape would still require some update. Bottom line: it would be difficult to generate the target whitepaper without reviewing at least partially the FI-WARE Product Vision, at least to keep some consistency between the whitepaper and the FI-WARE Product Vision, so let's make it a single exercise. Your comments/feedback is welcome. I will come with specific input regarding point 3 by Wednesday this week. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Dr. Uwe Riss Senior Researcher, New Assets & Bussiness Model Innovation | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Wed Oct 17 17:28:53 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 17 Oct 2012 17:28:53 +0200 Subject: [Fiware-apps] FIWARE WP3 Call - Minutes In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> Message-ID: <1491C91A94302A448D73CD9C6B7A782046C789B2E0@DEWDFECCR02.wdf.sap.corp> Dear WP3 Colleagues, Please find the access to the minutes of our last conf call here: https://forge.fi-ware.eu/docman/view.php/12/1395/FI-WARE_WP3_Minutes_16-10-12.doc The FI-WARE Apps wiki page for our planning can be found here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/apps/index.php/Main_Page Best regards, Uwe Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Fri Oct 19 08:58:20 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Fri, 19 Oct 2012 08:58:20 +0200 Subject: [Fiware-apps] Activity Report: M16 (Aug 2012) until M17 (Sep 2012) Message-ID: <1491C91A94302A448D73CD9C6B7A782046C799046E@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, I'd like to ask you to send me a report on your activities in WP3 from M16 (Aug 2012) to M17 (Sep 2012) that I can use for an overall report on WP3. Thanks in advance and have a nice day, Uwe Dr. Uwe Riss Senior Researcher, New Assets & Bussiness Model Innovation | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Wed Oct 24 09:49:33 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 24 Oct 2012 09:49:33 +0200 Subject: [Fiware-apps] Current Status of Demo Script Development Message-ID: <1491C91A94302A448D73CD9C6B7A782046C7BA3856@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, Just to inform you about the current status of the demo script for the review, please refer to https://docs.google.com/document/d/1DhFz9JLJ211ZXNIXUYNEdKyp0HdX46rEFWxn_B2XRWU/edit# If you have further questions, please feel free to ask me. Best regards, Uwe Dr. Uwe Riss Senior Researcher, New Assets & Bussiness Model Innovation | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Wed Oct 24 10:16:40 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 24 Oct 2012 10:16:40 +0200 Subject: [Fiware-apps] FW: [Fiware-wpl] AP on FI-WARE GE implementation owners regarding fixing dates for webinars about their FI-WARE GE implementation products Message-ID: <1491C91A94302A448D73CD9C6B7A782046C7BA38C9@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, Please keep this in mind and takes appropriate actions. Thanks an best regards, Uwe Dr. Uwe Riss Senior Researcher, New Assets & Bussiness Model Innovation | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 24. Oktober 2012 01:28 To: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] AP on FI-WARE GE implementation owners regarding fixing dates for webinars about their FI-WARE GE implementation products Dear all, One of the APs that owners of FI-WARE GE implementations should take care of has to do with defining a calendar for webinars regarding their products. A webinar should be structured as a slot of 45 min - 1 hour maximum. Following the suggestion of some people that have setup webinars in another projects, the recommendation is that the webinars will be organized by two persons (a moderator and a presenter). Some tool should be used by the organizer that will enable to share the screen with attendees. Besides, we will use a special FI-WARE related twitter channel so that the moderator can twit while the presentation evolves and attendees can formulate questions. Questions will be collected by the moderator so every ten minutes these questions will be asked by the moderator to the presenter. In this way the presentation will proceed in a more easy way without the risk of interruptions and network overload. More detailed instructions will be provided in a couple of days. You have to plan at least one webinar for your GE implementation (a "developers' primer") and define at least two dates where the webinar will be made. You have to setup the date&time for those webinars at the following shared spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDRKeUpILUxzTjNNUFZBQUhfM0U4aFE#gid=0 You will find a row per GE implementation covering the mandatory webinar you should organize (developers' primer). You may add rows with dates regarding complementary webinars. You should program the first date of your first webinar sometime before the November 1th-20th period and the second before December 7th (may also fit within the November 1th-20th period) It's ok that you use your favorite tools for setting up the bridge, sharing the screen and chatting but you should indicate this using notes in column F "tools, bridge and dial-in details". WE NEED that you complete your input to the spreadsheet above no later than END OF THIS WEEK. This is because we will forward the spreadsheet to the UC projects so that they can record their intend to attend what webinar. Don't hesitate to ask any question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco.ughetti at telecomitalia.it Thu Oct 25 11:26:14 2012 From: marco.ughetti at telecomitalia.it (Ughetti Marco) Date: Thu, 25 Oct 2012 11:26:14 +0200 Subject: [Fiware-apps] I: [Fiware] AP on FI-WARE GE implementation owners regarding fixing dates for webinars about their FI-WARE GE implementation products In-Reply-To: <50872819.4020805@tid.es> References: <50872819.4020805@tid.es> Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A538469270F436@GRFMBX707BA020.griffon.local> Hi all, Regarding this, I'm wondering if the same webinar shall be related to all Mediator Implementations (TI, THALES, ATOS), in this case we have to find a way to share the timeslot among theb three partners Otherwise we have to add other two rows in the google doc table and each partner will perform a implementation specific webinar How do you think about that? Marco ____________________ Telecom Italia Marco Ughetti Tilab & Global Consulting Services Platforms & Technology Evolution Services Platforms Innovation via G. Reiss Romoli, 274 - 10148 Torino +39 011228 5654 +39 331 6001596 Da: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 24 ottobre 2012 01:28 A: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware] AP on FI-WARE GE implementation owners regarding fixing dates for webinars about their FI-WARE GE implementation products Dear all, One of the APs that owners of FI-WARE GE implementations should take care of has to do with defining a calendar for webinars regarding their products. A webinar should be structured as a slot of 45 min - 1 hour maximum. Following the suggestion of some people that have setup webinars in another projects, the recommendation is that the webinars will be organized by two persons (a moderator and a presenter). Some tool should be used by the organizer that will enable to share the screen with attendees. Besides, we will use a special FI-WARE related twitter channel so that the moderator can twit while the presentation evolves and attendees can formulate questions. Questions will be collected by the moderator so every ten minutes these questions will be asked by the moderator to the presenter. In this way the presentation will proceed in a more easy way without the risk of interruptions and network overload. More detailed instructions will be provided in a couple of days. You have to plan at least one webinar for your GE implementation (a "developers' primer") and define at least two dates where the webinar will be made. You have to setup the date&time for those webinars at the following shared spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDRKeUpILUxzTjNNUFZBQUhfM0U4aFE#gid=0 You will find a row per GE implementation covering the mandatory webinar you should organize (developers' primer). You may add rows with dates regarding complementary webinars. You should program the first date of your first webinar sometime before the November 1th-20th period and the second before December 7th (may also fit within the November 1th-20th period) It's ok that you use your favorite tools for setting up the bridge, sharing the screen and chatting but you should indicate this using notes in column F "tools, bridge and dial-in details". WE NEED that you complete your input to the spreadsheet above no later than END OF THIS WEEK. This is because we will forward the spreadsheet to the UC projects so that they can record their intend to attend what webinar. Don't hesitate to ask any question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From uwe.riss at sap.com Fri Oct 26 13:45:27 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Fri, 26 Oct 2012 13:45:27 +0200 Subject: [Fiware-apps] Resubmission Deliverables D.3.x.a Message-ID: <1491C91A94302A448D73CD9C6B7A782046C87D7E35@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, I'd like to remind you that the resubmission of the Deliverables D3.x.a (x=2,...,5) is also due by M18 beside the Open Specification. This concerns the following issues: * Update of the backlog on the wiki (new versions mean more functionality) * Unit Testing Plan & Report * Installation & Administration Guides * User and Programmers Guide * Status on integration Tracker * https://forge.fi-ware.eu/tracker/?atid=224&group_id=18&func=browse * Status on integration cockpit * https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit * Status of online catalogue * http://catalogue.fi-ware.eu * Status of software delivery The given guidelines can be found at: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables Best regards, Uwe Dr. Uwe Riss Senior Researcher, New Assets & Bussiness Model Innovation | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesus.gorronogoitia at atosresearch.eu Mon Oct 29 16:22:26 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Mon, 29 Oct 2012 16:22:26 +0100 Subject: [Fiware-apps] New Atos' member in FIWARE Apps chapter Message-ID: <1351524146.2802.34.camel@localhost> Dear Partners, let me introduce you my colleague Joaquin Iranzo (in cc) who will be working in FIWARE Apps Chapter, replacing Miguel Huerta, starting today. During the next weeks, i will be as well working with him in this WP, helping him to catch up the project and our work and helping him to complete the Atos' pending work. @Miguel, could you please add Joaquin's email to this WP mailing list (and other FIWARE list he should be included), as well as to grant him access to the FF projects. King regards Yosu -- Jes?s Gorro?ogoitia Software Architect Service Engineering & IT Platforms Lab ATOS Research & Innovation Albarracin 25 28037 MADRID T +34 91 214 8175 F +34 91 754 3252 www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos 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 uwe.riss at sap.com Mon Oct 29 16:33:55 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Mon, 29 Oct 2012 16:33:55 +0100 Subject: [Fiware-apps] New Atos' member in FIWARE Apps chapter In-Reply-To: <1351524146.2802.34.camel@localhost> References: <1351524146.2802.34.camel@localhost> Message-ID: <1491C91A94302A448D73CD9C6B7A782046C8D30CBD@DEWDFECCR02.wdf.sap.corp> Dear Yosu, That is good news. I am looking forward to our collaboration. Best regards, Uwe -----Original Message----- From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Yosu Gorro?ogoitia Sent: Montag, 29. Oktober 2012 16:22 To: fiware-apps at lists.fi-ware.eu Cc: Joaquin Iranzo Yuste; Clara M Pezuela Robles; Nuria De-Lama Sanchez Subject: [Fiware-apps] New Atos' member in FIWARE Apps chapter Dear Partners, let me introduce you my colleague Joaquin Iranzo (in cc) who will be working in FIWARE Apps Chapter, replacing Miguel Huerta, starting today. During the next weeks, i will be as well working with him in this WP, helping him to catch up the project and our work and helping him to complete the Atos' pending work. @Miguel, could you please add Joaquin's email to this WP mailing list (and other FIWARE list he should be included), as well as to grant him access to the FF projects. King regards Yosu -- Jes?s Gorro?ogoitia Software Architect Service Engineering & IT Platforms Lab ATOS Research & Innovation Albarracin 25 28037 MADRID T +34 91 214 8175 F +34 91 754 3252 www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos 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-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps From mcp at tid.es Mon Oct 29 16:41:38 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 29 Oct 2012 16:41:38 +0100 Subject: [Fiware-apps] New Atos' member in FIWARE Apps chapter In-Reply-To: <1351524146.2802.34.camel@localhost> References: <1351524146.2802.34.camel@localhost> Message-ID: <508EA3B2.4080604@tid.es> Hi Welcome to the team!! First of all please go to the manual sections on: http://wiki.fi-ware.eu/ ("FI-WARE Project Handbook" ) and take a look at them. all new members must be aware of them and check them before asking anything. As regards the mailing lists, follow the procedures (http://wiki.fi-ware.eu/How_to_join_the_mailing_lists): WP3 list: The WPL is the one in charge of this. General list: I have already added him And as for the projects on the forge, follow the concerned tutorials and ask for access to the relevant projects http://wiki.fi-ware.eu/How_to_create_a_FusionForge_account http://wiki.fi-ware.eu/How_to_join_a_FI-WARE_project_in_FusionForge Project FI-WARE: request access and I will approve it Project FI-WARE Apps: The WPL is the one in charge of approving this FI-WARE Private project (and PPP restricted project if applicable): The WPL is the one in charge of this. Best regards, Miguel El 29/10/2012 16:22, Yosu Gorro?ogoitia escribi?: Dear Partners, let me introduce you my colleague Joaquin Iranzo (in cc) who will be working in FIWARE Apps Chapter, replacing Miguel Huerta, starting today. During the next weeks, i will be as well working with him in this WP, helping him to catch up the project and our work and helping him to complete the Atos' pending work. @Miguel, could you please add Joaquin's email to this WP mailing list (and other FIWARE list he should be included), as well as to grant him access to the FF projects. King regards Yosu -- ---------------------------------------------------------------------- _/ _/_/ 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: From jsoriano at fi.upm.es Tue Oct 30 10:17:02 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Tue, 30 Oct 2012 10:17:02 +0100 Subject: [Fiware-apps] Fwd: [Fiware] AP on FI-WARE GE implementation owners regarding fixing dates for webinars about their FI-WARE GE implementation products In-Reply-To: <50872819.4020805@tid.es> References: <50872819.4020805@tid.es> Message-ID: ---------- Forwarded message ---------- From: Juanjo Hierro Date: 2012/10/24 Subject: [Fiware] AP on FI-WARE GE implementation owners regarding fixing dates for webinars about their FI-WARE GE implementation products To: "fiware at lists.fi-ware.eu" Cc: "fiware-wpl at lists.fi-ware.eu" , " fiware-wpa at lists.fi-ware.eu" Dear all, One of the APs that owners of FI-WARE GE implementations should take care of has to do with defining a calendar for webinars regarding their products. A webinar should be structured as a slot of 45 min - 1 hour maximum. Following the suggestion of some people that have setup webinars in another projects, the recommendation is that the webinars will be organized by two persons (a moderator and a presenter). Some tool should be used by the organizer that will enable to share the screen with attendees. Besides, we will use a special FI-WARE related twitter channel so that the moderator can twit while the presentation evolves and attendees can formulate questions. Questions will be collected by the moderator so every ten minutes these questions will be asked by the moderator to the presenter. In this way the presentation will proceed in a more easy way without the risk of interruptions and network overload. More detailed instructions will be provided in a couple of days. You have to plan at least one webinar for your GE implementation (a "developers' primer") and define at least two dates where the webinar will be made. You have to setup the date&time for those webinars at the following shared spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDRKeUpILUxzTjNNUFZBQUhfM0U4aFE#gid=0 You will find a row per GE implementation covering the mandatory webinar you should organize (developers' primer). You may add rows with dates regarding complementary webinars. You should program the first date of your first webinar sometime before the November 1th-20th period and the second before December 7th (may also fit within the November 1th-20th period) It's ok that you use your favorite tools for setting up the bridge, sharing the screen and chatting but you should indicate this using notes in column F "tools, bridge and dial-in details". WE NEED that you complete your input to the spreadsheet above no later than END OF THIS WEEK. This is because we will forward the spreadsheet to the UC projects so that they can record their intend to attend what webinar. Don't hesitate to ask any question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ 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 torsten.leidig at sap.com Tue Oct 30 10:24:53 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 30 Oct 2012 09:24:53 +0000 Subject: [Fiware-apps] FW: FI-Ware Whitepaper contributions In-Reply-To: <703F4EB81B2AD0428360BFE55A82DFBC07063A67@DEWDFEMB11B.global.corp.sap> References: <703F4EB81B2AD0428360BFE55A82DFBC07063A67@DEWDFEMB11B.global.corp.sap> Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC07065EF9@DEWDFEMB11B.global.corp.sap> Dear all, we have to work on an additional deliverable, which was promised to the commission and the reviewers by Juanjo (TID) in our last review meeting. Please find attached a document, where Juanjo marked the sections where he expects contributions from our side. I already started to conduct some content from our (SAP) perspective. However, I need your help according the Monetization/RSS and composition aspects. Please have a look at the remarks by Juanjo and add some paragraphs with respect to your GEs. Please notice that the work has to be done in the Wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=FI-WARE_Applications/Services_Ecosystem_and_Delivery_Framework&action=edit§ion=66 and https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=FI-WARE_Applications/Services_Ecosystem_and_Delivery_Framework&action=edit§ion=67 respectively. The rationale is to describe a scenario which illustrates how FI-Ware GE would be used for real use cases (e.g. Transport&Logistics or any other domain) I would appreciate if you can add your contributions until end of week, since the whole document shall be submitted to the commission next week. Best regards, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Product Vision New Draft 12-10-01-1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1119135 bytes Desc: FI-WARE Product Vision New Draft 12-10-01-1.docx URL: From jhierro at tid.es Tue Oct 30 15:49:26 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 30 Oct 2012 15:49:26 +0100 Subject: [Fiware-apps] URGENT TO FIX: Light Semantic Composition Editor from ATOS Message-ID: <508FE8F6.1020401@tid.es> Hi, I'm about to announce the availability of the final set of FI-WARE GEis to the UC projects and I don't see the "Light Semantic Composition Editor" supposedly being contributed by ATOS nowhere in the FI-WARE Catalogue. If it is not made available along the coming hours, it will be withdrawn from the first Release with all the consequences regarding rejection of reported costs. We have repeated multiple times that FI-WARE GE implementations had to be documented in the FI-WARE Catalogue in order to accept they have been actually released. Hope you fix this urgently. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Tue Oct 30 15:51:51 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 30 Oct 2012 15:51:51 +0100 Subject: [Fiware-apps] URGENT TO FIX: Mediator GE implementations In-Reply-To: <508FE8F6.1020401@tid.es> References: <508FE8F6.1020401@tid.es> Message-ID: <508FE987.1070904@tid.es> Hi all, I don't see any entries regarding the Mediator GEs either. Only the one provided by Telecom Italia. Please clarify the issue. Otherwise, the mediators from Thales and ATOS will be also dropped from the first release with all the consequences. 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 On 30/10/12 15:49, Juanjo Hierro wrote: > Hi, > > I'm about to announce the availability of the final set of FI-WARE > GEis to the UC projects and I don't see the "Light Semantic > Composition Editor" supposedly being contributed by ATOS nowhere in > the FI-WARE Catalogue. > > If it is not made available along the coming hours, it will be > withdrawn from the first Release with all the consequences regarding > rejection of reported costs. > > We have repeated multiple times that FI-WARE GE implementations had > to be documented in the FI-WARE Catalogue in order to accept they have > been actually released. > > Hope you fix this urgently. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jesus.gorronogoitia at atosresearch.eu Tue Oct 30 15:56:29 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 30 Oct 2012 15:56:29 +0100 Subject: [Fiware-apps] URGENT TO FIX: Light Semantic Composition Editor from ATOS In-Reply-To: <508FE8F6.1020401@tid.es> References: <508FE8F6.1020401@tid.es> Message-ID: <1351608989.2802.70.camel@localhost> Dear Juanjo, Light Semantic Composition Editor was included in the Catalogue, as you can see at: http://catalogue.fi-ware.eu/node/268 Regards Yosu On Tue, 2012-10-30 at 15:49 +0100, Juanjo Hierro wrote: > Hi, > > I'm about to announce the availability of the final set of FI-WARE > GEis to the UC projects and I don't see the "Light Semantic Composition > Editor" supposedly being contributed by ATOS nowhere in the FI-WARE > Catalogue. > > If it is not made available along the coming hours, it will be > withdrawn from the first Release with all the consequences regarding > rejection of reported costs. > > We have repeated multiple times that FI-WARE GE implementations had > to be documented in the FI-WARE Catalogue in order to accept they have > been actually released. > > Hope you fix this urgently. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps -- Jes?s Gorro?ogoitia Software Architect Service Engineering & IT Platforms Lab ATOS Research & Innovation Albarracin 25 28037 MADRID T +34 91 214 8175 F +34 91 754 3252 www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos 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 Tue Oct 30 15:58:31 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 30 Oct 2012 15:58:31 +0100 Subject: [Fiware-apps] URGENT TO FIX: Mediator GE implementations In-Reply-To: <508FE987.1070904@tid.es> References: <508FE8F6.1020401@tid.es> <508FE987.1070904@tid.es> Message-ID: <1351609111.2802.72.camel@localhost> Dear Juanjo, Atos mediation features (as part of Apps Mediation GE) has been moved to the Light-weighted Semantic Composition Editor GE, whereby there is only one GE Atos take care of in the Apps Chapter. Regards Yosu On Tue, 2012-10-30 at 15:51 +0100, Juanjo Hierro wrote: > Hi all, > > I don't see any entries regarding the Mediator GEs either. Only the > one provided by Telecom Italia. > > Please clarify the issue. Otherwise, the mediators from Thales and > ATOS will be also dropped from the first release with all the consequences. > > 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 > > On 30/10/12 15:49, Juanjo Hierro wrote: > > Hi, > > > > I'm about to announce the availability of the final set of FI-WARE > > GEis to the UC projects and I don't see the "Light Semantic > > Composition Editor" supposedly being contributed by ATOS nowhere in > > the FI-WARE Catalogue. > > > > If it is not made available along the coming hours, it will be > > withdrawn from the first Release with all the consequences regarding > > rejection of reported costs. > > > > We have repeated multiple times that FI-WARE GE implementations had > > to be documented in the FI-WARE Catalogue in order to accept they have > > been actually released. > > > > Hope you fix this urgently. > > > > Cheers, > > > > -- Juanjo > > > > ------------- > > Product Development and Innovation (PDI) - Telefonica Digital > > website: www.tid.es > > email: jhierro at tid.es > > twitter: twitter.com/JuanjoHierro > > > > FI-WARE (European Future Internet Core Platform) Chief Architect > > > > You can follow FI-WARE at: > > website: http://www.fi-ware.eu > > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > > twitter: http://twitter.com/FIware > > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps -- Jes?s Gorro?ogoitia Software Architect Service Engineering & IT Platforms Lab ATOS Research & Innovation Albarracin 25 28037 MADRID T +34 91 214 8175 F +34 91 754 3252 www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos 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 jhierro at tid.es Tue Oct 30 16:54:55 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 30 Oct 2012 16:54:55 +0100 Subject: [Fiware-apps] URGENT TO FIX: Light Semantic Composition Editor from ATOS In-Reply-To: <1351608989.2802.70.camel@localhost> References: <508FE8F6.1020401@tid.es> <1351608989.2802.70.camel@localhost> Message-ID: <508FF84F.7080607@tid.es> Are you sure that the entry is VISIBLE ? You may have an entry already prepared, but you have to publish it so that third parties can read it. Actually, I can't access the link you sent to us and I guess this is due to the fact that you haven't publish the entry yet. Please do so. 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 On 30/10/12 15:56, Yosu Gorro?ogoitia wrote: > Dear Juanjo, > Light Semantic Composition Editor was included in the Catalogue, as you > can see at: > http://catalogue.fi-ware.eu/node/268 > > Regards > Yosu > > On Tue, 2012-10-30 at 15:49 +0100, Juanjo Hierro wrote: >> Hi, >> >> I'm about to announce the availability of the final set of FI-WARE >> GEis to the UC projects and I don't see the "Light Semantic Composition >> Editor" supposedly being contributed by ATOS nowhere in the FI-WARE >> Catalogue. >> >> If it is not made available along the coming hours, it will be >> withdrawn from the first Release with all the consequences regarding >> rejection of reported costs. >> >> We have repeated multiple times that FI-WARE GE implementations had >> to be documented in the FI-WARE Catalogue in order to accept they have >> been actually released. >> >> Hope you fix this urgently. >> >> Cheers, >> >> -- Juanjo >> >> ------------- >> Product Development and Innovation (PDI) - Telefonica Digital >> website: www.tid.es >> email: jhierro at tid.es >> twitter: twitter.com/JuanjoHierro >> >> FI-WARE (European Future Internet Core Platform) Chief Architect >> >> You can follow FI-WARE at: >> website: http://www.fi-ware.eu >> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >> twitter: http://twitter.com/FIware >> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >> >> >> ________________________________ >> >> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. >> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >> _______________________________________________ >> Fiware-apps mailing list >> Fiware-apps at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-apps ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Tue Oct 30 16:56:31 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 30 Oct 2012 16:56:31 +0100 Subject: [Fiware-apps] URGENT TO FIX: Mediator GE implementations In-Reply-To: <1351609111.2802.72.camel@localhost> References: <508FE8F6.1020401@tid.es> <508FE987.1070904@tid.es> <1351609111.2802.72.camel@localhost> Message-ID: <508FF8AF.4080005@tid.es> Does this mean that we should drop any reference to mediators brought by ATOS within the Apps Chapter ? It is fine with me but I wanted to double check before dropping the corresponding row in the google docs spreadsheet we are sharing with UC projects: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 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 On 30/10/12 15:58, Yosu Gorro?ogoitia wrote: > Dear Juanjo, > Atos mediation features (as part of Apps Mediation GE) has been moved to > the Light-weighted Semantic Composition Editor GE, whereby there is only > one GE Atos take care of in the Apps Chapter. > Regards > Yosu > > On Tue, 2012-10-30 at 15:51 +0100, Juanjo Hierro wrote: >> Hi all, >> >> I don't see any entries regarding the Mediator GEs either. Only the >> one provided by Telecom Italia. >> >> Please clarify the issue. Otherwise, the mediators from Thales and >> ATOS will be also dropped from the first release with all the consequences. >> >> 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 >> >> On 30/10/12 15:49, Juanjo Hierro wrote: >>> Hi, >>> >>> I'm about to announce the availability of the final set of FI-WARE >>> GEis to the UC projects and I don't see the "Light Semantic >>> Composition Editor" supposedly being contributed by ATOS nowhere in >>> the FI-WARE Catalogue. >>> >>> If it is not made available along the coming hours, it will be >>> withdrawn from the first Release with all the consequences regarding >>> rejection of reported costs. >>> >>> We have repeated multiple times that FI-WARE GE implementations had >>> to be documented in the FI-WARE Catalogue in order to accept they have >>> been actually released. >>> >>> Hope you fix this urgently. >>> >>> Cheers, >>> >>> -- Juanjo >>> >>> ------------- >>> Product Development and Innovation (PDI) - Telefonica Digital >>> website: www.tid.es >>> email: jhierro at tid.es >>> twitter: twitter.com/JuanjoHierro >>> >>> FI-WARE (European Future Internet Core Platform) Chief Architect >>> >>> You can follow FI-WARE at: >>> website: http://www.fi-ware.eu >>> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >>> twitter: http://twitter.com/FIware >>> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >>> >> >> ________________________________ >> >> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. >> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >> _______________________________________________ >> Fiware-apps mailing list >> Fiware-apps at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-apps ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jesus.gorronogoitia at atosresearch.eu Tue Oct 30 16:58:32 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 30 Oct 2012 16:58:32 +0100 Subject: [Fiware-apps] URGENT TO FIX: Light Semantic Composition Editor from ATOS In-Reply-To: <508FF84F.7080607@tid.es> References: <508FE8F6.1020401@tid.es> <1351608989.2802.70.camel@localhost> <508FF84F.7080607@tid.es> Message-ID: <1351612712.2802.79.camel@localhost> Dear Juanjo, i have contacted Catalogue administrators to publish this GE. You are in cc. Regards Yosu On Tue, 2012-10-30 at 16:54 +0100, Juanjo Hierro wrote: > Are you sure that the entry is VISIBLE ? You may have an entry > already prepared, but you have to publish it so that third parties can > read it. > > Actually, I can't access the link you sent to us and I guess this is > due to the fact that you haven't publish the entry yet. > > Please do so. > > 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 > > On 30/10/12 15:56, Yosu Gorro?ogoitia wrote: > > Dear Juanjo, > > Light Semantic Composition Editor was included in the Catalogue, as you > > can see at: > > http://catalogue.fi-ware.eu/node/268 > > > > Regards > > Yosu > > > > On Tue, 2012-10-30 at 15:49 +0100, Juanjo Hierro wrote: > >> Hi, > >> > >> I'm about to announce the availability of the final set of FI-WARE > >> GEis to the UC projects and I don't see the "Light Semantic Composition > >> Editor" supposedly being contributed by ATOS nowhere in the FI-WARE > >> Catalogue. > >> > >> If it is not made available along the coming hours, it will be > >> withdrawn from the first Release with all the consequences regarding > >> rejection of reported costs. > >> > >> We have repeated multiple times that FI-WARE GE implementations had > >> to be documented in the FI-WARE Catalogue in order to accept they have > >> been actually released. > >> > >> Hope you fix this urgently. > >> > >> Cheers, > >> > >> -- Juanjo > >> > >> ------------- > >> Product Development and Innovation (PDI) - Telefonica Digital > >> website: www.tid.es > >> email: jhierro at tid.es > >> twitter: twitter.com/JuanjoHierro > >> > >> FI-WARE (European Future Internet Core Platform) Chief Architect > >> > >> You can follow FI-WARE at: > >> website: http://www.fi-ware.eu > >> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > >> twitter: http://twitter.com/FIware > >> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > >> > >> > >> ________________________________ > >> > >> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > >> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx > >> _______________________________________________ > >> Fiware-apps mailing list > >> Fiware-apps at lists.fi-ware.eu > >> http://lists.fi-ware.eu/listinfo/fiware-apps > > > ________________________________ > > 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 -- Jes?s Gorro?ogoitia Software Architect Service Engineering & IT Platforms Lab ATOS Research & Innovation Albarracin 25 28037 MADRID T +34 91 214 8175 F +34 91 754 3252 www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos 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 Tue Oct 30 17:02:07 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 30 Oct 2012 17:02:07 +0100 Subject: [Fiware-apps] URGENT TO FIX: Mediator GE implementations In-Reply-To: <508FF8AF.4080005@tid.es> References: <508FE8F6.1020401@tid.es> <508FE987.1070904@tid.es> <1351609111.2802.72.camel@localhost> <508FF8AF.4080005@tid.es> Message-ID: <1351612927.2802.83.camel@localhost> Dear Juanjo, that means that Atos mediator GE has been merged within the Light-weighted Semantic Composition Editor, where it makes sense, since these mediation features only apply at design time, so, yes, you can remove those references. Regards Yosu On Tue, 2012-10-30 at 16:56 +0100, Juanjo Hierro wrote: > Does this mean that we should drop any reference to mediators brought > by ATOS within the Apps Chapter ? It is fine with me but I wanted to > double check before dropping the corresponding row in the google docs > spreadsheet we are sharing with UC projects: > > https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 > > 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 > > On 30/10/12 15:58, Yosu Gorro?ogoitia wrote: > > Dear Juanjo, > > Atos mediation features (as part of Apps Mediation GE) has been moved to > > the Light-weighted Semantic Composition Editor GE, whereby there is only > > one GE Atos take care of in the Apps Chapter. > > Regards > > Yosu > > > > On Tue, 2012-10-30 at 15:51 +0100, Juanjo Hierro wrote: > >> Hi all, > >> > >> I don't see any entries regarding the Mediator GEs either. Only the > >> one provided by Telecom Italia. > >> > >> Please clarify the issue. Otherwise, the mediators from Thales and > >> ATOS will be also dropped from the first release with all the consequences. > >> > >> 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 > >> > >> On 30/10/12 15:49, Juanjo Hierro wrote: > >>> Hi, > >>> > >>> I'm about to announce the availability of the final set of FI-WARE > >>> GEis to the UC projects and I don't see the "Light Semantic > >>> Composition Editor" supposedly being contributed by ATOS nowhere in > >>> the FI-WARE Catalogue. > >>> > >>> If it is not made available along the coming hours, it will be > >>> withdrawn from the first Release with all the consequences regarding > >>> rejection of reported costs. > >>> > >>> We have repeated multiple times that FI-WARE GE implementations had > >>> to be documented in the FI-WARE Catalogue in order to accept they have > >>> been actually released. > >>> > >>> Hope you fix this urgently. > >>> > >>> Cheers, > >>> > >>> -- Juanjo > >>> > >>> ------------- > >>> Product Development and Innovation (PDI) - Telefonica Digital > >>> website: www.tid.es > >>> email: jhierro at tid.es > >>> twitter: twitter.com/JuanjoHierro > >>> > >>> FI-WARE (European Future Internet Core Platform) Chief Architect > >>> > >>> You can follow FI-WARE at: > >>> website: http://www.fi-ware.eu > >>> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > >>> twitter: http://twitter.com/FIware > >>> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > >>> > >> > >> ________________________________ > >> > >> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > >> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx > >> _______________________________________________ > >> Fiware-apps mailing list > >> Fiware-apps at lists.fi-ware.eu > >> http://lists.fi-ware.eu/listinfo/fiware-apps > > > ________________________________ > > 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 -- Jes?s Gorro?ogoitia Software Architect Service Engineering & IT Platforms Lab ATOS Research & Innovation Albarracin 25 28037 MADRID T +34 91 214 8175 F +34 91 754 3252 www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos 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 uwe.riss at sap.com Tue Oct 30 17:13:03 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 30 Oct 2012 17:13:03 +0100 Subject: [Fiware-apps] Finalization of 3rd Peer Review Message-ID: <1491C91A94302A448D73CD9C6B7A782046C8EED027@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, When you have completed the revision of your Open Spec according to the peer review, please provide your document in Forge Docman and update the information "Revised doc" and "Changed on Wiki (Y/N)" (and please actually do it) on https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0 Thanks and best regards, Uwe Dr. Uwe Riss Senior Researcher, New Assets & Bussiness Model Innovation | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Oct 30 17:47:52 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 30 Oct 2012 17:47:52 +0100 Subject: [Fiware-apps] URGENT TO FIX: Mediator GE implementations In-Reply-To: <1351612927.2802.83.camel@localhost> References: <508FE8F6.1020401@tid.es> <508FE987.1070904@tid.es> <1351609111.2802.72.camel@localhost> <508FF8AF.4080005@tid.es> <1351612927.2802.83.camel@localhost> Message-ID: <509004B8.6060306@tid.es> Done. ------------- 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 On 30/10/12 17:02, Yosu Gorro?ogoitia wrote: > Dear Juanjo, > > that means that Atos mediator GE has been merged within the > Light-weighted Semantic Composition Editor, where it makes sense, since > these mediation features only apply at design time, so, > yes, you can remove those references. > > Regards > Yosu > > On Tue, 2012-10-30 at 16:56 +0100, Juanjo Hierro wrote: >> Does this mean that we should drop any reference to mediators brought >> by ATOS within the Apps Chapter ? It is fine with me but I wanted to >> double check before dropping the corresponding row in the google docs >> spreadsheet we are sharing with UC projects: >> >> https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 >> >> 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 >> >> On 30/10/12 15:58, Yosu Gorro?ogoitia wrote: >>> Dear Juanjo, >>> Atos mediation features (as part of Apps Mediation GE) has been moved to >>> the Light-weighted Semantic Composition Editor GE, whereby there is only >>> one GE Atos take care of in the Apps Chapter. >>> Regards >>> Yosu >>> >>> On Tue, 2012-10-30 at 15:51 +0100, Juanjo Hierro wrote: >>>> Hi all, >>>> >>>> I don't see any entries regarding the Mediator GEs either. Only the >>>> one provided by Telecom Italia. >>>> >>>> Please clarify the issue. Otherwise, the mediators from Thales and >>>> ATOS will be also dropped from the first release with all the consequences. >>>> >>>> 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 >>>> >>>> On 30/10/12 15:49, Juanjo Hierro wrote: >>>>> Hi, >>>>> >>>>> I'm about to announce the availability of the final set of FI-WARE >>>>> GEis to the UC projects and I don't see the "Light Semantic >>>>> Composition Editor" supposedly being contributed by ATOS nowhere in >>>>> the FI-WARE Catalogue. >>>>> >>>>> If it is not made available along the coming hours, it will be >>>>> withdrawn from the first Release with all the consequences regarding >>>>> rejection of reported costs. >>>>> >>>>> We have repeated multiple times that FI-WARE GE implementations had >>>>> to be documented in the FI-WARE Catalogue in order to accept they have >>>>> been actually released. >>>>> >>>>> Hope you fix this urgently. >>>>> >>>>> Cheers, >>>>> >>>>> -- Juanjo >>>>> >>>>> ------------- >>>>> Product Development and Innovation (PDI) - Telefonica Digital >>>>> website: www.tid.es >>>>> email: jhierro at tid.es >>>>> twitter: twitter.com/JuanjoHierro >>>>> >>>>> FI-WARE (European Future Internet Core Platform) Chief Architect >>>>> >>>>> You can follow FI-WARE at: >>>>> website: http://www.fi-ware.eu >>>>> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >>>>> twitter: http://twitter.com/FIware >>>>> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >>>>> >>>> ________________________________ >>>> >>>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. >>>> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: >>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>>> _______________________________________________ >>>> Fiware-apps mailing list >>>> Fiware-apps at lists.fi-ware.eu >>>> http://lists.fi-ware.eu/listinfo/fiware-apps >> >> ________________________________ >> >> 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 From jhierro at tid.es Tue Oct 30 17:53:37 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 30 Oct 2012 17:53:37 +0100 Subject: [Fiware-apps] URGENT TO FIX: Light Semantic Composition Editor from ATOS In-Reply-To: <1351612712.2802.79.camel@localhost> References: <508FE8F6.1020401@tid.es> <1351608989.2802.70.camel@localhost> <508FF84F.7080607@tid.es> <1351612712.2802.79.camel@localhost> Message-ID: <50900611.3060507@tid.es> Please Matteo, Could you explain Yosu who to publish entries of the Catalogue ? 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 On 30/10/12 16:58, Yosu Gorro?ogoitia wrote: > Dear Juanjo, > i have contacted Catalogue administrators to publish this GE. > You are in cc. > Regards > Yosu > > On Tue, 2012-10-30 at 16:54 +0100, Juanjo Hierro wrote: >> Are you sure that the entry is VISIBLE ? You may have an entry >> already prepared, but you have to publish it so that third parties can >> read it. >> >> Actually, I can't access the link you sent to us and I guess this is >> due to the fact that you haven't publish the entry yet. >> >> Please do so. >> >> 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 >> >> On 30/10/12 15:56, Yosu Gorro?ogoitia wrote: >>> Dear Juanjo, >>> Light Semantic Composition Editor was included in the Catalogue, as you >>> can see at: >>> http://catalogue.fi-ware.eu/node/268 >>> >>> Regards >>> Yosu >>> >>> On Tue, 2012-10-30 at 15:49 +0100, Juanjo Hierro wrote: >>>> Hi, >>>> >>>> I'm about to announce the availability of the final set of FI-WARE >>>> GEis to the UC projects and I don't see the "Light Semantic Composition >>>> Editor" supposedly being contributed by ATOS nowhere in the FI-WARE >>>> Catalogue. >>>> >>>> If it is not made available along the coming hours, it will be >>>> withdrawn from the first Release with all the consequences regarding >>>> rejection of reported costs. >>>> >>>> We have repeated multiple times that FI-WARE GE implementations had >>>> to be documented in the FI-WARE Catalogue in order to accept they have >>>> been actually released. >>>> >>>> Hope you fix this urgently. >>>> >>>> Cheers, >>>> >>>> -- Juanjo >>>> >>>> ------------- >>>> Product Development and Innovation (PDI) - Telefonica Digital >>>> website: www.tid.es >>>> email: jhierro at tid.es >>>> twitter: twitter.com/JuanjoHierro >>>> >>>> FI-WARE (European Future Internet Core Platform) Chief Architect >>>> >>>> You can follow FI-WARE at: >>>> website: http://www.fi-ware.eu >>>> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >>>> twitter: http://twitter.com/FIware >>>> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >>>> >>>> >>>> ________________________________ >>>> >>>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. >>>> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: >>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>>> _______________________________________________ >>>> Fiware-apps mailing list >>>> Fiware-apps at lists.fi-ware.eu >>>> http://lists.fi-ware.eu/listinfo/fiware-apps >> >> ________________________________ >> >> 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 From nuria.delama at atosresearch.eu Tue Oct 30 18:04:17 2012 From: nuria.delama at atosresearch.eu (Nuria De-Lama Sanchez) Date: Tue, 30 Oct 2012 18:04:17 +0100 Subject: [Fiware-apps] URGENT TO FIX: Mediator GE implementations In-Reply-To: <1351609111.2802.72.camel@localhost> References: <508FE8F6.1020401@tid.es> <508FE987.1070904@tid.es> <1351609111.2802.72.camel@localhost> Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A014423B8@INTMAIL03.es.int.atosorigin.com> Hi Juanjo, colleagues from the Apps chapter, I have followed the exchange of e-mails with Yosu about the GE and it seems that everything is solved now. If there is any doubt about ant description, please, let us know. Yosu is following that very closely and will answer about any missing detail, but as said, it seems everything has been clarified. Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net -----Original Message----- From: Jesus Gorro?ogoitia Cruz Sent: martes, 30 de octubre de 2012 15:59 To: Juanjo Hierro Cc: fiware-apps at lists.fi-ware.eu; Clara M Pezuela Robles; Nuria De-Lama Sanchez Subject: Re: [Fiware-apps] URGENT TO FIX: Mediator GE implementations Dear Juanjo, Atos mediation features (as part of Apps Mediation GE) has been moved to the Light-weighted Semantic Composition Editor GE, whereby there is only one GE Atos take care of in the Apps Chapter. Regards Yosu On Tue, 2012-10-30 at 15:51 +0100, Juanjo Hierro wrote: > Hi all, > > I don't see any entries regarding the Mediator GEs either. Only the > one provided by Telecom Italia. > > Please clarify the issue. Otherwise, the mediators from Thales and > ATOS will be also dropped from the first release with all the consequences. > > 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 > > On 30/10/12 15:49, Juanjo Hierro wrote: > > Hi, > > > > I'm about to announce the availability of the final set of FI-WARE > > GEis to the UC projects and I don't see the "Light Semantic > > Composition Editor" supposedly being contributed by ATOS nowhere in > > the FI-WARE Catalogue. > > > > If it is not made available along the coming hours, it will be > > withdrawn from the first Release with all the consequences regarding > > rejection of reported costs. > > > > We have repeated multiple times that FI-WARE GE implementations had > > to be documented in the FI-WARE Catalogue in order to accept they have > > been actually released. > > > > Hope you fix this urgently. > > > > Cheers, > > > > -- Juanjo > > > > ------------- > > Product Development and Innovation (PDI) - Telefonica Digital > > website: www.tid.es > > email: jhierro at tid.es > > twitter: twitter.com/JuanjoHierro > > > > FI-WARE (European Future Internet Core Platform) Chief Architect > > > > You can follow FI-WARE at: > > website: http://www.fi-ware.eu > > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > > twitter: http://twitter.com/FIware > > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps -- Jes?s Gorro?ogoitia Software Architect Service Engineering & IT Platforms Lab ATOS Research & Innovation Albarracin 25 28037 MADRID T +34 91 214 8175 F +34 91 754 3252 www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos 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. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: From calin.curescu at ericsson.com Wed Oct 31 09:06:17 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Wed, 31 Oct 2012 08:06:17 +0000 Subject: [Fiware-apps] Open specification In-Reply-To: <703F4EB81B2AD0428360BFE55A82DFBC07065EF9@DEWDFEMB11B.global.corp.sap> References: <703F4EB81B2AD0428360BFE55A82DFBC07063A67@DEWDFEMB11B.global.corp.sap>, <703F4EB81B2AD0428360BFE55A82DFBC07065EF9@DEWDFEMB11B.global.corp.sap> Message-ID: <20c7ldgswvkm4t3tiskkbetj.1351670775350@email.android.com> Hi, I mostly finished the editing, but i need to put a last data structure graph. Will finish by 11.00. Sent from Moxier Mail (http://www.moxier.com) ----- Original Message ----- From: "Leidig, Torsten" To: "fiware-apps at lists.fi-ware.eu" Sent: 30/10/2012 10:25 Subject: [Fiware-apps] FW: FI-Ware Whitepaper contributions Dear all, we have to work on an additional deliverable, which was promised to the commission and the reviewers by Juanjo (TID) in our last review meeting. Please find attached a document, where Juanjo marked the sections where he expects contributions from our side. I already started to conduct some content from our (SAP) perspective. However, I need your help according the Monetization/RSS and composition aspects. Please have a look at the remarks by Juanjo and add some paragraphs with respect to your GEs. Please notice that the work has to be done in the Wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=FI-WARE_Applications/Services_Ecosystem_and_Delivery_Framework&action=edit§ion=66 and https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=FI-WARE_Applications/Services_Ecosystem_and_Delivery_Framework&action=edit§ion=67 respectively. The rationale is to describe a scenario which illustrates how FI-Ware GE would be used for real use cases (e.g. Transport&Logistics or any other domain) I would appreciate if you can add your contributions until end of week, since the whole document shall be submitted to the commission next week. Best regards, Torsten