From axel.fasse at sap.com Sun Jan 6 12:37:05 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Sun, 6 Jan 2013 12:37:05 +0100 Subject: [Fiware-apps] Composition, Sync-Call to clarify the next steps Message-ID: <2C6296E1876B5C49962495FDACDC7A636177DD55D4@DEWDFECCR01.wdf.sap.corp> Dear Composition-Partners, last year we have agreed to plan a meeting to clarify the next steps to ?solve? the issue with respect to the different composition engines. If you or your company provides a composition technology, this meeting is mandatory. Because of that, if you are not able to participate, please suggest another concrete date or timeslot for the meeting. I think we should come to an agreement within the next weeks to plan the next steps accordingly. Because of the upcoming FI-WARE Architecture-Meeting (planned for Jan 21-25/01/2013) we should prepare some concrete offers for our FI-WARE coordinator Juanjo and especially for our WP-Partners and the Use-case Projects. Beside this, I want to mention the agreed deadline to finalize the roadmap until the 15.01.2013 within the WIKI https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Applications/Services_Ecosystem_and_Delivery_Framework and the corresponding google-docs document: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 Best regards, Axel To join the meeting: https://sap.emea.pgiconnect.com/fi-ware_wp3_call/ Participant Passcode: 9525481261 Germany, Frankfurt : +49 69 2222 10764 Germany : 0800 588 9331 France, Paris : +33 1 70 70 17 77 Ireland, Dublin : +353 1 247 6192 Italy, Milan : +39 02 3600 9839 Switzerland, Zurich : +41 43 456 9248 UK, London : +44 20 3364 5639 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3074 bytes Desc: not available URL: From axel.fasse at sap.com Sun Jan 6 12:54:08 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Sun, 6 Jan 2013 12:54:08 +0100 Subject: [Fiware-apps] Roadmap WP3 References: <2C6296E1876B5C49962495FDACDC7A6361779229D6@DEWDFECCR01.wdf.sap.corp> Message-ID: <2C6296E1876B5C49962495FDACDC7A636177DD55DD@DEWDFECCR01.wdf.sap.corp> Dear Partners, the action point to provide a concrete roadmap is very simple. You should provide a clear picture of your contributions for the current and the new use-case projects. The Roadmap should be documented within the WIKI and the corresponding Google-Docs-File https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 actually there is no content for the Apps Chapter (Phase II) [cid:image001.png at 01CDEC0C.91074D70] I think we should insert some offers for the existing and the new Use-Case Projects. Especially with respect to your contribution, the new partners and Use-Cases should get a clear understanding about your offers. What is provided under which conditions. [cid:image002.png at 01CDEC0C.91074D70] So I would like to ask you to insert the missing information into the WIKI and the Google-Docs-File. Please take into account that you also have to provide the "Terms and Conditions" within the FI-WARE CATALOG http://catalogue.fi-ware.eu/ If you have any kind of questions, please let me know. Best regards, Axel From: Calin Curescu [mailto:calin.curescu at ericsson.com] Sent: Freitag, 21. Dezember 2012 10:10 To: Fasse, Axel Subject: RE: Roadmap WP3 Importance: High Dear Axel, I want to finalize the "first revision of the current content". However I do not remember what are the APs needed for that. Could you please point me to the minutes of the meetings or any other document that can tell me that? Thanks, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Fasse, Axel Sent: den 18 december 2012 16:25 To: 'fiware-apps at lists.fi-ware.eu' (fiware-apps at lists.fi-ware.eu) Subject: [Fiware-apps] Roadmap WP3 Dear Partners, I have had a discussion with Torsten about the "right place" to provide the requested information. Please use the WIKI https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Applications/Services_Ecosystem_and_Delivery_Framework As discussed within the last WP3 Call, we have agreed to finalize the "first revision of the current content" until the 21.12.2012 and we agreed to finalize the Roadmap until the 15.01.2013 (EOB). I think Juanjo will ask for this deadlines and - if you have no concerns - I will provide this information at Friday (21.12.2013). If you have any concerns or questions, please contact me directly. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 24075 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 42084 bytes Desc: image002.png URL: From axel.fasse at sap.com Tue Jan 8 09:40:44 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Tue, 8 Jan 2013 09:40:44 +0100 Subject: [Fiware-apps] Our Meeting tomorrow "Composition, Sync-Call to clarify the next steps" Message-ID: <2C6296E1876B5C49962495FDACDC7A636177EA6637@DEWDFECCR01.wdf.sap.corp> Dear Composition-Partners, I plan to start the meeting with a review of the existing EPICS and User-Stories. Because of this I would like to ask you to review the existing descriptions to identify "open gaps" if Ericsson and DT will leave the Composition-Parts of the WP. This work is necessary to adopt our descriptions in the WIKI accordingly. Please have a look at the related pages so that we can start directly and without of any delays. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Jan 8 10:11:39 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 8 Jan 2013 09:11:39 +0000 Subject: [Fiware-apps] Changed Meeting Room Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC325C8D8A@DEWDFEMB11B.global.corp.sap> Dear W3 Partners, Axel decided to use the FI-Ware Meeting Room for other purposes. So we have to change: https://sap.emea.pgiconnect.com/d029752 You may use the callbac function to get into the phone conference or look for the dial in numbers. Sorry, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Tue Jan 8 10:18:36 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Tue, 8 Jan 2013 10:18:36 +0100 Subject: [Fiware-apps] Can't find the data for today's conf call... Message-ID: Hi Torsten, I'm unable to find the correct data for today's conf call I've tried https://sap.emea.pgiconnect.com/fi-ware_wp3_call and Axel is there, but in a different conf call. He has told me that you intended to send a different dial info but I can't find it in my inbox. Of course, https://sap.emea.pgiconnect.com/fi-ware_apps hasn't yet started Best regards, Javier -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Jan 8 10:20:18 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 8 Jan 2013 09:20:18 +0000 Subject: [Fiware-apps] Can't find the data for today's conf call... In-Reply-To: References: Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC325C8DD0@DEWDFEMB11B.global.corp.sap> Please refer to my previous mail. From: Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es] Sent: Dienstag, 8. Januar 2013 10:19 To: Leidig, Torsten Cc: fiware-apps at lists.fi-ware.eu Subject: Can't find the data for today's conf call... Hi Torsten, I'm unable to find the correct data for today's conf call I've tried https://sap.emea.pgiconnect.com/fi-ware_wp3_call and Axel is there, but in a different conf call. He has told me that you intended to send a different dial info but I can't find it in my inbox. Of course, https://sap.emea.pgiconnect.com/fi-ware_apps hasn't yet started Best regards, Javier -- [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 2240 bytes Desc: image001.jpg URL: From jsoriano at fi.upm.es Wed Jan 9 09:08:15 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Wed, 9 Jan 2013 09:08:15 +0100 Subject: [Fiware-apps] Composition, Sync-Call to clarify the next steps In-Reply-To: <2C6296E1876B5C49962495FDACDC7A636177DD55D4@DEWDFECCR01.wdf.sap.corp> References: <2C6296E1876B5C49962495FDACDC7A636177DD55D4@DEWDFECCR01.wdf.sap.corp> Message-ID: Hi Axel, The link doesn't work. It says that the host has ended the meeting. The phone number for Madrid (Spain) isn't among those provided in the email. Any clue? BR, Javier 2013/1/6 Fasse, Axel > Dear Composition-Partners, > > last year we have agreed to plan a meeting to clarify the next steps to > ?solve? the issue with respect to the different composition engines. If you > or your company provides a composition technology, this meeting is > mandatory. Because of that, if you are not able to participate, please > suggest another concrete date or timeslot for the meeting. > I think we should come to an agreement within the next weeks to plan the > next steps accordingly. Because of the upcoming FI-WARE > Architecture-Meeting (planned for Jan 21-25/01/2013) we should prepare some > concrete offers for our FI-WARE coordinator Juanjo and especially for our > WP-Partners and the Use-case Projects. > > Beside this, I want to mention the agreed deadline to finalize the roadmap > until the 15.01.2013 within the WIKI > > * > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Applications/Services_Ecosystem_and_Delivery_Framework > * > and the corresponding google-docs document: > > * > https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 > * > > > > Best regards, > Axel > > > > > > To join the meeting: *https://sap.emea.pgiconnect.com/fi-ware_wp3_call/* > > Participant Passcode: *9525481261 > * > Germany, Frankfurt : +49 69 2222 10764 > Germany : 0800 588 9331 > France, Paris : +33 1 70 70 17 77 > Ireland, Dublin : +353 1 247 6192 > Italy, Milan : +39 02 3600 9839 > Switzerland, Zurich : +41 43 456 9248 > UK, London : +44 20 3364 5639 > > > > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps > > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Wed Jan 9 09:09:16 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Wed, 9 Jan 2013 09:09:16 +0100 Subject: [Fiware-apps] Composition, Sync-Call to clarify the next steps In-Reply-To: References: <2C6296E1876B5C49962495FDACDC7A636177DD55D4@DEWDFECCR01.wdf.sap.corp> Message-ID: Ok! it seems that the session is now started. BR, Javier 2013/1/9 Javier Soriano (FI-UPM) > Hi Axel, > > The link doesn't work. It says that the host has ended the meeting. > > The phone number for Madrid (Spain) isn't among those provided in the > email. > Any clue? > > BR, > Javier > > > 2013/1/6 Fasse, Axel > >> Dear Composition-Partners, >> >> last year we have agreed to plan a meeting to clarify the next steps to >> ?solve? the issue with respect to the different composition engines. If you >> or your company provides a composition technology, this meeting is >> mandatory. Because of that, if you are not able to participate, please >> suggest another concrete date or timeslot for the meeting. >> I think we should come to an agreement within the next weeks to plan the >> next steps accordingly. Because of the upcoming FI-WARE >> Architecture-Meeting (planned for Jan 21-25/01/2013) we should prepare some >> concrete offers for our FI-WARE coordinator Juanjo and especially for our >> WP-Partners and the Use-case Projects. >> >> Beside this, I want to mention the agreed deadline to finalize the >> roadmap until the 15.01.2013 within the WIKI >> >> * >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Applications/Services_Ecosystem_and_Delivery_Framework >> * >> and the corresponding google-docs document: >> >> * >> https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 >> * >> >> >> >> Best regards, >> Axel >> >> >> >> >> >> To join the meeting: *https://sap.emea.pgiconnect.com/fi-ware_wp3_call/* >> >> Participant Passcode: *9525481261 >> * >> Germany, Frankfurt : +49 69 2222 10764 >> Germany : 0800 588 9331 >> France, Paris : +33 1 70 70 17 77 >> Ireland, Dublin : +353 1 247 6192 >> Italy, Milan : +39 02 3600 9839 >> Switzerland, Zurich : +41 43 456 9248 >> UK, London : +44 20 3364 5639 >> >> >> >> >> _______________________________________________ >> Fiware-apps mailing list >> Fiware-apps at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-apps >> >> > > > -- > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From axel.fasse at sap.com Wed Jan 9 09:10:15 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Wed, 9 Jan 2013 09:10:15 +0100 Subject: [Fiware-apps] Composition, Sync-Call to clarify the next steps In-Reply-To: References: <2C6296E1876B5C49962495FDACDC7A636177DD55D4@DEWDFECCR01.wdf.sap.corp> Message-ID: <2C6296E1876B5C49962495FDACDC7A636177F44FB6@DEWDFECCR01.wdf.sap.corp> Dear Javier, I have re-opened the Session, so it should work now. Best regards, Axel From: Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es] Sent: Mittwoch, 9. Januar 2013 09:08 To: Fasse, Axel Cc: 'fiware-apps at lists.fi-ware.eu' (fiware-apps at lists.fi-ware.eu) Subject: Re: [Fiware-apps] Composition, Sync-Call to clarify the next steps Hi Axel, The link doesn't work. It says that the host has ended the meeting. The phone number for Madrid (Spain) isn't among those provided in the email. Any clue? BR, Javier 2013/1/6 Fasse, Axel > Dear Composition-Partners, last year we have agreed to plan a meeting to clarify the next steps to "solve" the issue with respect to the different composition engines. If you or your company provides a composition technology, this meeting is mandatory. Because of that, if you are not able to participate, please suggest another concrete date or timeslot for the meeting. I think we should come to an agreement within the next weeks to plan the next steps accordingly. Because of the upcoming FI-WARE Architecture-Meeting (planned for Jan 21-25/01/2013) we should prepare some concrete offers for our FI-WARE coordinator Juanjo and especially for our WP-Partners and the Use-case Projects. Beside this, I want to mention the agreed deadline to finalize the roadmap until the 15.01.2013 within the WIKI https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Applications/Services_Ecosystem_and_Delivery_Framework and the corresponding google-docs document: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 Best regards, Axel To join the meeting: https://sap.emea.pgiconnect.com/fi-ware_wp3_call/ Participant Passcode: 9525481261 Germany, Frankfurt : +49 69 2222 10764 Germany : 0800 588 9331 France, Paris : +33 1 70 70 17 77 Ireland, Dublin : +353 1 247 6192 Italy, Milan : +39 02 3600 9839 Switzerland, Zurich : +41 43 456 9248 UK, London : +44 20 3364 5639 _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps -- [http://conwet.fi.upm.es/images/pieemailupm.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From joaquin.iranzo at atos.net Thu Jan 10 08:57:30 2013 From: joaquin.iranzo at atos.net (Joaquin Iranzo Yuste) Date: Thu, 10 Jan 2013 08:57:30 +0100 Subject: [Fiware-apps] Light Semantic Composition features ("Composition, Sync-Call to clarify the next steps") Message-ID: Dear Composition-Partners, This is the features list for the Light Semantic Composition that is aligned with the Open Specification. I think that this classification together with the detail of the Open Specification will help the use-case projects to understand and to decide if they need the GE. * Model Composition This GE provides support for service composition modeling, assuming BPMN 2.0 as graphical notation and execution semantics. Through the BPMN Composition Editor, business modelers can create or open composition models, modify them (edit) and manage them (save, delete). Composition models are stored within a Repository. Composition edition also includes support for create/update/delete features for composition elements, such as service tasks, gateways (exclusive, parallel), flows and events (start, end). Composition editor allows to select the composition itself or concrete composition elements. * Prepare DSL/Semantics: In this GE approach, the business modelers describe composition models and their elements by annotating them with concepts taken from concrete domain specific languages DSL (or vocabularies) which provide concrete semantics. From operational point of view, it is common to use ontologies as DSL or vocabularies. The Light-weighted Semantic Mediator enables the business modeler to: *Register new DSL/Ontologies within it *Select a concrete DSL/Ontology for a given domain modeling context. Select a concrete DSL/Ontology concept within the domain ontology. These concepts are used to annotate and describe a composition model and their elements. * Describe Model Composition/Task using DSL/Semantics (Business modelers): The Light-weighted Semantic Mediator enables the business modeler to describe the composition model and its elements using semantic annotations. In the scope of a composition task, the annotations constitute a description of the task. In other words, they describe the goal of the task. This goal will be used in the service matchmaking process to look for services whose semantic description will match it. A semantic task description is constituted by several annotations of certain type according to the semantic schema used to represent the goal (i.e MSM ) In the scope of the composition itself, the annotations constitute a description of the global composition requirements, preferences and contextual information. * Describe Service using DSL/Semantics (Service Providers): Light-weighted Semantic-enabled Service Composition GE approach assumes that composable services are described using light semantics. Those semantic service descriptions are available within the Semantic Knowledge Base, and are provided by service providers. A service composition created by applying this GE approach is a service by its own, whereby the business modeler, acting as service provider, is required to provide this semantic description. Same applies to any other third party service intented to be composed by others. The Light-weighted Semantic Mediator enables service providers to create semantic descriptions compliant to the semantic schema used by the complete GE solution. The concrete schema is left for the implementation, but it should be consistent along with all components that use it. The schema includes links to the business oriented description stored in the Marketplace, and the technical description stored in the Repository. * Bind task to service: One of the main jobs in service composition modeling is to bind every task the composition is divided out to a matching service that performs the task. A business modeler can conduct this task binding per task or for the whole composition. The Light-weighted Semantic Mediator enables the modeler to discover matching services based on task goal criteria, rank them according to preferences or non-functional requirements (NFR) and select one service, which is bound to the task. Those activities are typically performed by querying the Semantic Knowledge Base. * Validate, generate, translate executable BPMN composition model: After binding task to service, next step in service composition modeling consists on filling the missing information that the composition model requires before being shipped for deployment and execution. Examples of missing information are: *Task binding technical description. For each BPMN 2.0 service task, a concrete task binding information has to be included, by inspecting the technical description (i.e. WSDL). *Data flow mapping, including IO mappings at task and composition level. Once the service composition model has been completed with missing required executable information, the composition model is validated (BPMN 2.0 compliance validation) and serialized (for storage and deployment). Optionally, the composition model can be translated from its original BPMN 2.0 format to another mappable format, such as BPEL 1.2/2.0 . This is required when the select target environment for execution is not BPMN 2.0 compatible. * Deploy composition model: Full executable validated composition models can be deployed into the selected target Composition Execution environment, using the Composition Deployer. Once deployed, the service composition is enabled, being ready to received incoming requests from service consumers. Similarly, deployed service compositions can be undeployed anytime. * Composition Execution: During the execution time, deployed services can be enabled or disabled any time through the Composition Execution UI. Besides, running compositions (enabled) can be continuously monitored and monitoring data can be collected for given time frames. Best regards, Joaquin Iranzo. ------------------------------------------------------------------ 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: From jsoriano at fi.upm.es Fri Jan 11 19:10:59 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Fri, 11 Jan 2013 19:10:59 +0100 Subject: [Fiware-apps] Composition, Sync-Call to clarify the next steps In-Reply-To: <2C6296E1876B5C49962495FDACDC7A636177DD55D4@DEWDFECCR01.wdf.sap.corp> References: <2C6296E1876B5C49962495FDACDC7A636177DD55D4@DEWDFECCR01.wdf.sap.corp> Message-ID: Dear all, As agreed during our last conf call on wednesday, I want to share with you a google doc in which we describe the features related to composition from the perspective of the Application Mashup GE (i.e. Wirecloud). Hope you find it useful as a preliminary input for the next conf call. https://docs.google.com/document/d/10r7op4HCQM_6F3cCMR6-4di3NoPLXkcXAHhnpn8neCk/edit Let me know if you have any problem with that link. Best regards, Javier 2013/1/6 Fasse, Axel > Dear Composition-Partners, > > last year we have agreed to plan a meeting to clarify the next steps to > ?solve? the issue with respect to the different composition engines. If you > or your company provides a composition technology, this meeting is > mandatory. Because of that, if you are not able to participate, please > suggest another concrete date or timeslot for the meeting. > I think we should come to an agreement within the next weeks to plan the > next steps accordingly. Because of the upcoming FI-WARE > Architecture-Meeting (planned for Jan 21-25/01/2013) we should prepare some > concrete offers for our FI-WARE coordinator Juanjo and especially for our > WP-Partners and the Use-case Projects. > > Beside this, I want to mention the agreed deadline to finalize the roadmap > until the 15.01.2013 within the WIKI > > * > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Applications/Services_Ecosystem_and_Delivery_Framework > * > and the corresponding google-docs document: > > * > https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 > * > > > > Best regards, > Axel > > > > > > To join the meeting: *https://sap.emea.pgiconnect.com/fi-ware_wp3_call/* > > Participant Passcode: *9525481261 > * > Germany, Frankfurt : +49 69 2222 10764 > Germany : 0800 588 9331 > France, Paris : +33 1 70 70 17 77 > Ireland, Dublin : +353 1 247 6192 > Italy, Milan : +39 02 3600 9839 > Switzerland, Zurich : +41 43 456 9248 > UK, London : +44 20 3364 5639 > > > > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps > > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From calin.curescu at ericsson.com Tue Jan 15 10:02:06 2013 From: calin.curescu at ericsson.com (Calin Curescu) Date: Tue, 15 Jan 2013 09:02:06 +0000 Subject: [Fiware-apps] FI-WARE WP3 Call Message-ID: Preliminay classification attempt: ---------------------------------------------------- Common Features ---------------- FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithStore -- - comprises of Store-related features - covers existing common features: FIWARE.FEATURE.Apps.CompositionEditor.ContractFromStore FIWARE.FEATURE.Apps.CompositionEditor.ConfigureService FIWARE.FEATURE.Apps.CompositionEditor.PublishServiceToStore FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithUSDLEditor FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithMarketplace FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithRepository FIWARE.FEATURE.Apps.ApplicationMashup.SupportForIdManagement FIWARE.FEATURE.Apps.ApplicationMashup.SupportForOAuth2 - Security and ID management here: - similar to (could be conjoined): FIWARE.FEATURE.Apps.CompositionEditor.CommonUserManagement Specific UPM Features --------------------- FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition - with some tech-dependent subfeatures FIWARE.FEATURE.Apps.ApplicationMashup.SupportForOpenSocial FIWARE.FEATURE.Apps.ApplicationMashup.SupportForW3CWidgets FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers FIWARE.EPIC.Apps.ApplicationMashup.DeploymentOfWirecloudPlatformAsAService UPM features not directly relevant to End-User ------------------------------------------- FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithFiWareIDManagementSystem FIWARE.FEATURE.Apps.ApplicationMashup.AllowHostingWidgetsInContainerApp FIWARE.FEATURE.Apps.ApplicationMashup.AllowHostingWidgetsInWebBasedSystem FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithNGSI-10QueryBrokerGE FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithDataChapterCEPGE FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithDataChapterPubSubGE, FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithDataChapterLocationGE FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithCloudChapterObjectStorage Atos specific features ------------------------ FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation FIWARE.FEATURE.Apps.CompositionEditor.ExportImportBPMN20Models FIWARE.FEATURE.Apps.CompositionEditor.CreateBPMNComposition FIWARE.FEATURE.Apps.ExecutionEngine.BPMN20andBPELStandartExecution DT specific features ----------------------- FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch Ericsson specific features --------------------------- FIWARE.FEATURE.Apps.ServiceComposition-ImportExport - import/export ECE format to XML, Repository REST FIWARE.FEATURE.Apps.ServiceComposition-CreateServiceDescription - Create a desription to remotely access the different services w.r.t. their interface technology (SIP, WSDL, REST, RMI) FIWARE.FEATURE.Apps.ServiceComposition-ConstraintsEditor FIWARE.FEATURE.Apps.ServiceComposition-CreateGraphicComposition (start, Service Template, Condition, SSM, Command, Goto, End) FIWARE.FEATURE.Apps.ServiceComposition-SharedStateManager - a shared state manager that has a global view of all the input output and state variables in the execution FIWARE.FEATURE.Apps.ServiceComposition-ConstraintsResolutionAndDynamicBinding FIWARE.FEATURE.Apps.ServiceComposition-SkeletonExecution -----Original Appointment----- From: Fasse, Axel [mailto:axel.fasse at sap.com] Sent: den 17 december 2012 15:08 To: Fasse, Axel; 'fiware-apps at lists.fi-ware.eu'; Klein, Andreas; 'Ronco Enrico'; Sandfuchs, Thorsten; 'matteo.melideo at eng.it'; Magerkurth, Carsten; 'Froese, Andreas'; 'miguel.huerta at atos.net'; Calin Curescu; 'Jonischkat, Tim'; Leidig, Torsten; 'Andreas.Grothe at telekom.de'; Sammodi, Osama; Mathieu Hutschemaekers Subject: FI-WARE WP3 Call When: den 15 januari 2013 10:00-11:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: https://sap.emea.pgiconnect.com/fi-ware_wp3_call/ Dear WP3 Partners, I?d like to invite you to the next FI-WARE Apps calls, regularly on Tuesday. I will send the agenda separately. I have corrected the link in the subject now. Best regards, Axel To join the meeting: https://sap.emea.pgiconnect.com/fi-ware_wp3_call/ Participant Passcode: 9525481261 Germany, Frankfurt : +49 69 2222 10764 Germany : 0800 588 9331 France, Paris : +33 1 70 70 17 77 Ireland, Dublin : +353 1 247 6192 Italy, Milan : +39 02 3600 9839 Switzerland, Zurich : +41 43 456 9248 UK, London : +44 20 3364 5639 -------------- next part -------------- An HTML attachment was scrubbed... URL: From axel.fasse at sap.com Tue Jan 15 10:11:46 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Tue, 15 Jan 2013 10:11:46 +0100 Subject: [Fiware-apps] FI-WARE WP3 Call Message-ID: <2C6296E1876B5C49962495FDACDC7A63617811ECEF@DEWDFECCR01.wdf.sap.corp> Dear WP3 Partners, I?d like to invite you to the next FI-WARE Apps calls, regularly on Tuesday. I will send the agenda separately. I have corrected the link in the subject now. Best regards, Axel To join the meeting: https://sap.emea.pgiconnect.com/fi-ware_wp3_call/ Participant Passcode: 9525481261 Germany, Frankfurt : +49 69 2222 10764 Germany : 0800 588 9331 France, Paris : +33 1 70 70 17 77 Ireland, Dublin : +353 1 247 6192 Italy, Milan : +39 02 3600 9839 Switzerland, Zurich : +41 43 456 9248 UK, London : +44 20 3364 5639 Spain : +34 93 800 0782 Spain : +34 91 769 9443 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4348 bytes Desc: not available URL: From joaquin.iranzo at atos.net Tue Jan 15 15:35:31 2013 From: joaquin.iranzo at atos.net (Joaquin Iranzo Yuste) Date: Tue, 15 Jan 2013 15:35:31 +0100 Subject: [Fiware-apps] FI-WARE WP3 Call Message-ID: Dear Composition-Partners, After the ?Preliminary classification? sending by Calin, and how the Atos specific features are not common, I think it would be better to change the name and the description of these features (LightSemanticComposition), to be aligned with the openSpecification (FIWARE.OpenSpecification.Apps.LightSemanticComposition) in order to be clearer for the use-case. So I propose to change these: Atos specific features ------------------------ FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation FIWARE.FEATURE.Apps.CompositionEditor.ExportImportBPMN20Models FIWARE.FEATURE.Apps.CompositionEditor.CreateBPMNComposition FIWARE.FEATURE.Apps.ExecutionEngine.BPMN20andBPELStandartExecution For this one: FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel But, I am not clear how to link the old item with the new (maybe by a redirected) in order to harmonize the wiki. Axel or Torsten, I would like to know your opinion about them, thanks in advance. Best regards, Joaquin Iranzo. From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Calin Curescu Sent: martes, 15 de enero de 2013 10:02 To: Fasse, Axel; 'fiware-apps at lists.fi-ware.eu'; Klein, Andreas; 'Ronco Enrico'; Sandfuchs, Thorsten; 'matteo.melideo at eng.it'; Magerkurth, Carsten; 'Froese, Andreas'; 'miguel.huerta at atos.net'; 'Jonischkat, Tim'; Leidig, Torsten; 'Andreas.Grothe at telekom.de'; Sammodi, Osama; Mathieu Hutschemaekers Subject: Re: [Fiware-apps] FI-WARE WP3 Call Preliminay classification attempt: ---------------------------------------------------- Common Features ---------------- FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithStore -- - comprises of Store-related features - covers existing common features: FIWARE.FEATURE.Apps.CompositionEditor.ContractFromStore FIWARE.FEATURE.Apps.CompositionEditor.ConfigureService FIWARE.FEATURE.Apps.CompositionEditor.PublishServiceToStore FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithUSDLEditor FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithMarketplace FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithRepository FIWARE.FEATURE.Apps.ApplicationMashup.SupportForIdManagement FIWARE.FEATURE.Apps.ApplicationMashup.SupportForOAuth2 - Security and ID management here: - similar to (could be conjoined): FIWARE.FEATURE.Apps.CompositionEditor.CommonUserManagement Specific UPM Features --------------------- FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition - with some tech-dependent subfeatures FIWARE.FEATURE.Apps.ApplicationMashup.SupportForOpenSocial FIWARE.FEATURE.Apps.ApplicationMashup.SupportForW3CWidgets FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers FIWARE.EPIC.Apps.ApplicationMashup.DeploymentOfWirecloudPlatformAsAService UPM features not directly relevant to End-User ------------------------------------------- FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithFiWareIDManagementSystem FIWARE.FEATURE.Apps.ApplicationMashup.AllowHostingWidgetsInContainerApp FIWARE.FEATURE.Apps.ApplicationMashup.AllowHostingWidgetsInWebBasedSystem FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithNGSI-10QueryBrokerGE FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithDataChapterCEPGE FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithDataChapterPubSubGE, FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithDataChapterLocationGE FIWARE.FEATURE.Apps.ApplicationMashup.IntegrationWithCloudChapterObjectStorage Atos specific features ------------------------ FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation FIWARE.FEATURE.Apps.CompositionEditor.ExportImportBPMN20Models FIWARE.FEATURE.Apps.CompositionEditor.CreateBPMNComposition FIWARE.FEATURE.Apps.ExecutionEngine.BPMN20andBPELStandartExecution DT specific features ----------------------- FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch Ericsson specific features --------------------------- FIWARE.FEATURE.Apps.ServiceComposition-ImportExport - import/export ECE format to XML, Repository REST FIWARE.FEATURE.Apps.ServiceComposition-CreateServiceDescription - Create a desription to remotely access the different services w.r.t. their interface technology (SIP, WSDL, REST, RMI) FIWARE.FEATURE.Apps.ServiceComposition-ConstraintsEditor FIWARE.FEATURE.Apps.ServiceComposition-CreateGraphicComposition (start, Service Template, Condition, SSM, Command, Goto, End) FIWARE.FEATURE.Apps.ServiceComposition-SharedStateManager - a shared state manager that has a global view of all the input output and state variables in the execution FIWARE.FEATURE.Apps.ServiceComposition-ConstraintsResolutionAndDynamicBinding FIWARE.FEATURE.Apps.ServiceComposition-SkeletonExecution -----Original Appointment----- From: Fasse, Axel [mailto:axel.fasse at sap.com] Sent: den 17 december 2012 15:08 To: Fasse, Axel; 'fiware-apps at lists.fi-ware.eu'; Klein, Andreas; 'Ronco Enrico'; Sandfuchs, Thorsten; 'matteo.melideo at eng.it'; Magerkurth, Carsten; 'Froese, Andreas'; 'miguel.huerta at atos.net'; Calin Curescu; 'Jonischkat, Tim'; Leidig, Torsten; 'Andreas.Grothe at telekom.de'; Sammodi, Osama; Mathieu Hutschemaekers Subject: FI-WARE WP3 Call When: den 15 januari 2013 10:00-11:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: https://sap.emea.pgiconnect.com/fi-ware_wp3_call/ Dear WP3 Partners, I?d like to invite you to the next FI-WARE Apps calls, regularly on Tuesday. I will send the agenda separately. I have corrected the link in the subject now. Best regards, Axel To join the meeting: https://sap.emea.pgiconnect.com/fi-ware_wp3_call/ Participant Passcode: 9525481261 Germany, Frankfurt : +49 69 2222 10764 Germany : 0800 588 9331 France, Paris : +33 1 70 70 17 77 Ireland, Dublin : +353 1 247 6192 Italy, Milan : +39 02 3600 9839 Switzerland, Zurich : +41 43 456 9248 UK, London : +44 20 3364 5639 ------------------------------------------------------------------ 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 -------------- An embedded message was scrubbed... From: "Joaquin Iranzo Yuste" Subject: [Fiware-apps] Light Semantic Composition features ("Composition, Sync-Call to clarify the next steps") Date: Thu, 10 Jan 2013 08:57:30 +0100 Size: 25966 URL: From axel.fasse at sap.com Tue Jan 15 19:25:50 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Tue, 15 Jan 2013 19:25:50 +0100 Subject: [Fiware-apps] Meeting Minutes 15.01.2013 Message-ID: <2C6296E1876B5C49962495FDACDC7A63617811F44F@DEWDFECCR01.wdf.sap.corp> Dear Partners, I have now finalized a first version of the Minutes for our WP3 Call. https://forge.fi-ware.eu/docman/view.php/12/1816/FI-WARE_WP3_Minutes_2013-01-15.doc Because of the "sudden" end of our meeting, I have added some additional Links and Comments. I think I have mentioned all of the relevant topics and action-point that we have discussed. If you have any comments or questions, please let me know. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From axel.fasse at sap.com Fri Jan 18 12:10:02 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Fri, 18 Jan 2013 12:10:02 +0100 Subject: [Fiware-apps] FW: Review of stakeholder field in the backlog of WP3 In-Reply-To: <50F8410E.3040500@tid.es> References: <50F8410E.3040500@tid.es> Message-ID: <2C6296E1876B5C49962495FDACDC7A63617825B8C1@DEWDFECCR01.wdf.sap.corp> Dear Partners, Miguel has reviewed our EIPC's and Featured, Within the XLS File you will find a detailed description of "open issues". Together with the explanations from Miguel and the Links and Information that we have been talking about within our WP3 Call, you have a concrete ToDo List. I will use this list as a basis for a short "review" about the current stat at the beginning of the next WP3 Call. You will get aware, that there are some "red" comments for some of the Features and Epis, especially with respect to Composition, there are a lot of "red" comments. Please do whatever you can to solve this issues. Beside this I have to mention, that I have not received any kind of feedback about the finalization of the tasks that we have been talking about within the last Call. Pablo was the only one who sent out his feedback in the agreed timeslot. Thank you Pablo!! I think we can (and have to) optimize this in the feature. If you have any kind of questions about the concrete next steps and ToDo's please ask the as soon as possible. Best regards, Axel From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Donnerstag, 17. Januar 2013 19:21 To: Fasse, Axel; Leidig, Torsten Cc: Sandfuchs, Thorsten; JUAN JOSE HIERRO SUREDA Subject: Review of stakeholder field in the backlog of WP3 Dear all, I have gone through the Epics and Features of your backlog and checked the status of the stakeholder field. As stated by Juanjo, the common reference for the stakeholder field at this stage is the interest expressed by the UC Projects here: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E I followed these rules in my review: * We will check Epics and Features (not User Stories) - those in "Materializing ... " on the wiki (not user stories) * We will just check those present in Release 1 (Release 2 is obviously not well populated) * We will inherit the GEs with "D" or "U" ( "E" is not enough to take a UC as a stakeholder) The enclosed excel file contains my comments. To ease your work, I marked in red the cells where I ask for a change or alternatively an explanation. These do not necessarily mean that you have to change something (well, most of the times they actually mean that but not always). The changes of the whole chapter should take less than an hour of a single person. But as I guess that you need to distribute and people will not react immediately, we can set a deadeline of next tuesday EOB. I will start checking again on wednesday first thing in the morning. Hope this is reasonable/clear enough. If you need any clarifications, let me know. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Review_Stakeholder_20130117_apps.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 24008 bytes Desc: Review_Stakeholder_20130117_apps.xlsx URL: From calin.curescu at ericsson.com Tue Jan 22 02:19:59 2013 From: calin.curescu at ericsson.com (Calin Curescu) Date: Tue, 22 Jan 2013 01:19:59 +0000 Subject: [Fiware-apps] Meeting Minutes 15.01.2013 In-Reply-To: <2C6296E1876B5C49962495FDACDC7A63617811F44F@DEWDFECCR01.wdf.sap.corp> References: <2C6296E1876B5C49962495FDACDC7A63617811F44F@DEWDFECCR01.wdf.sap.corp> Message-ID: Dear all, Ericsson finalized work reworking the features in the wiki and editing the Roadmap. BR, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Fasse, Axel Sent: den 15 januari 2013 19:26 To: 'fiware-apps at lists.fi-ware.eu' (fiware-apps at lists.fi-ware.eu) Subject: [Fiware-apps] Meeting Minutes 15.01.2013 Dear Partners, I have now finalized a first version of the Minutes for our WP3 Call. https://forge.fi-ware.eu/docman/view.php/12/1816/FI-WARE_WP3_Minutes_2013-01-15.doc Because of the "sudden" end of our meeting, I have added some additional Links and Comments. I think I have mentioned all of the relevant topics and action-point that we have discussed. If you have any comments or questions, please let me know. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Jan 22 17:01:08 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 22 Jan 2013 16:01:08 +0000 Subject: [Fiware-apps] FW: Vorschlag Composition Features In-Reply-To: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> References: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> Dear Apps Partners, Actually it is subject to the Task 3.1 partners to come to a conclusion and decide. However, we discussed the current state internally and came up with the following proposal. The basic idea is to create Features which are common to a number of GE. We already have global features in FI-WARE. So there is no reason why we should not have Apps common features. In the Wiki there is a section listing the common features. Each GE then as a subsection listing the common features it will support plus the specific features for the GE. The common features are only documented once. The stakeholder field is a join of all stakeholders for GE implementing the feature. The description text should be somehow generic of course. The Wiki page will look like below. Please give us feedback whether that is OK for you. We have to do the changes quickly and also synchronize with the tracker (means changing the respective tracker entries) ASAP since the next delivery will be created from this information this week. Thanks and best regards, Torsten From: Klein, Andreas Sent: Dienstag, 22. Januar 2013 15:59 To: Fasse, Axel; Leidig, Torsten Cc: DL Research FI-WARE APPS Subject: Vorschlag Composition Features Hallo zusammen, Wie eben besprochen der Vorschlag zur Umstrukturierung unserer Composition Features Viele Gr??e Andreas Composition Light Semantic Composition (Atos) Common Features: ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: ? FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition ? FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics ? FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL ? FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL ? FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService ? FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel ? FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel Service Mashup (DT) Common Features: None Specific Features: ? FIWARE.FEATURE.Apps.ServiceMashup.CommonRepositoryImportExport ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test ? FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch Service Composition (EAB) Common Features: ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore Specific Features: ? FIWARE.FEATURE.Apps.ServiceComposition.CreateComposition ? FIWARE.FEATURE.Apps.ServiceComposition.CreateServiceDescription ? FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsEditor ? FIWARE.FEATURE.Apps.ServiceComposition.ExecuteComposition ? FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding ? FIWARE.FEATURE.Apps.ServiceComposition.ServiceCompositionCloudReady ? FIWARE.FEATURE.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons ? FIWARE.FEATURE.Apps.ServiceComposition.ContractFromStore ? FIWARE.FEATURE.Apps.ServiceComposition.SupportForOAuth2 Application Mashup (UPM) Common Features: ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: ? FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment ? FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition ? FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution ? FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers ? FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping 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 axel.fasse at sap.com Tue Jan 22 18:14:43 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Tue, 22 Jan 2013 18:14:43 +0100 Subject: [Fiware-apps] Review_Stakeholder_20130117_apps_SAP_Comments.xlsx Message-ID: <2C6296E1876B5C49962495FDACDC7A63617857C7B9@DEWDFECCR01.wdf.sap.corp> Dear Colleagues and Partners, after our WP3 Call I have made a very "funny" exercise that takes some hours of my time. I have opened the XLS File (provided by Miguel) and have checked all the "red" comments. Within this exercise I learned, that some issues are still open and some issued needs at least some short explanations. I have marked all the issues explicitly, so it should be very simple for you to go through the list and check if there is a todo for you or not. I have sent you the list last week, and Miguel mentioned that he will start the review & consolidation tomorrow morning. So please do the changes as soon as possible and confirm that you have solved the issues and confirm your changes to Miguel and me. I think it is not necessary that Miguel has to do the same exercise again. Thank you for your support. Best regards, Axel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Review_Stakeholder_20130117_apps_SAP_Comments.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 25041 bytes Desc: Review_Stakeholder_20130117_apps_SAP_Comments.xlsx URL: From axel.fasse at sap.com Wed Jan 23 10:06:55 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Wed, 23 Jan 2013 10:06:55 +0100 Subject: [Fiware-apps] Important informations, please read carefully!! Message-ID: <2C6296E1876B5C49962495FDACDC7A63617857CC5A@DEWDFECCR01.wdf.sap.corp> Dear Apps-Partner, yesterday we have had some discussions to improve the success of our WP3. I think it is very important to share the most relevant information with you: ? Please check if you have really finalized all the topics and comments that were mentioned by Miguel o Please have a look at my mail with additional comments and remarks o After my analysis I received so far only TWO confirmations. o I think we can improve this without spending too much time. But this improvement needs your support!! ? Stakeholder o For new Features for existing GE's you are allowed to "copy" the stakeholder from the existing Features to the new features. o For Features for new GE's you should find a "U" or a "D" in the Matrix (google docs https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=4) or the Stakeholderfield is empty ? Documentation o Release 1 ? Because of the fact that these documents are already published, I would suggest to leave them unchanged o Release 2++ ? I think we should use the current wording and naming conventions ? We should asap agree on the proposal that was send out to you by Torsten about the modification of the WIKI "Common Features" ? I think that this approach is very good because the Features and Functionalities and their integration into the chapter and FI-WARE will be very transparent for potential users ? Please confirm (Mail to apps) that you agree on this approach or provide another (better) one ? Tracker o Please be aware that we have to put all User-Stories (and maybe Workitems) into the tracker. ? This should be done as soon as possible ? This step is necessary to ensure that you are allowed to claim your costs o Link to Apps Tracker: https://forge.fi-ware.eu/tracker/?group_id=12 ? select & run Power Query corresponding to your GE on the upper left ? or open https://forge.fi-ware.eu/tracker/index.php?group_id=12&atid=181 to see all Apps Tracker items o If we have to duplicate also the EPIC's and FEATURE's into the TRACKER is under discussion with our coordinator ? We are waiting for an official statement. ? We will share the answer from our coordinator as soon as possible. I will reflect these topics also in the minutes. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Wed Jan 23 10:09:39 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 23 Jan 2013 09:09:39 +0000 Subject: [Fiware-apps] Features, Epics, User Stories and Work Items in the tracker Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC325D0DE1@DEWDFEMB11B.global.corp.sap> Dear Apps partners, after some discussion with Juanjo, it became clear that all Features and Epics shall be replicated into the Chapter Backlog tracker. Yesterday we sent a proposal on how to deal with the Composition Features and Epics. So far I did not receive any feedback. So we will start to change the Wiki pages accordingly. Then we will also create the respective tracker entries for Features and Epics for all GE in the Backlog tracker. Thereafter (we will send you a notification today), you are responsible 1. to check the Features and Eppics and to create Work Items and/or User Stories in the tracker for the actual implementation work for your GE. Since a deliverable will be created from the content of the tracker, we need to set a deadline of Thu, EOB to have all the tracker items up to date. If you have any question or problem, please don't hesitate and ask! Best regards, Torsten Dr. Torsten Leidig SAP Next Business and Technology SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227-7525-35 F +49 6227 78-52535 www.sap.com Please consider the impact on the environment before printing this e-mail. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfernandez at fi.upm.es Wed Jan 23 13:00:07 2013 From: rfernandez at fi.upm.es (=?ISO-8859-1?Q?Rafael_Fern=E1ndez?=) Date: Wed, 23 Jan 2013 13:00:07 +0100 Subject: [Fiware-apps] FW: Vorschlag Composition Features In-Reply-To: <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> References: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> Message-ID: Hi Torsten, We had last week a discussion with Calin about how to face this topic... We agreed we need a common set of features, but if we define them in the way you propose, some problems will arise: - Common features are implemented at different times (in different releases) in different GEs - The version field is not common to all GEs. Even more, the tracker entries will lead to confusion. - What should we write in the Source field? - Who is the Owner? - In the end, even having the same name, different implementations offer different features from the perspective of the UC project because respond to different needs. E.g. both Wirecloud and the mashup factory (could) use the marketplace to publish the components they use to build a mashup, but for different objectives. And if we use the FIWARE.FEATURE.Apps.CommonFeature.xxx notation, we won't be following the appropriate name convention (see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow)) The previous are some examples of why we think the Calin's proposal of having a common "title last name" and text in the "goal" part is better. Best regards, Rafa On Tue, Jan 22, 2013 at 5:01 PM, Leidig, Torsten wrote: > Dear Apps Partners,**** > > ** ** > > Actually it is subject to the Task 3.1 partners to come to a conclusion > and decide. However, we discussed the current state internally and came up > with the following proposal. The basic idea is to create Features which are > common to a number of GE. We already have global features in FI-WARE. So > there is no reason why we should not have Apps common features. In the Wiki > there is a section listing the common features. Each GE then as a > subsection listing the common features it will support plus the specific > features for the GE.**** > > The common features are only documented once. The stakeholder field is a > join of all stakeholders for GE implementing the feature.**** > > The description text should be somehow generic of course.**** > > ** ** > > The Wiki page will look like below. Please give us feedback whether that > is OK for you. We have to do the changes quickly and also synchronize with > the tracker (means changing the respective tracker entries) ASAP since the > next delivery will be created from this information this week.**** > > ** ** > > Thanks and best regards,**** > > Torsten**** > > ** ** > > ** ** > > ** ** > > *From:* Klein, Andreas > *Sent:* Dienstag, 22. Januar 2013 15:59 > *To:* Fasse, Axel; Leidig, Torsten > *Cc:* DL Research FI-WARE APPS > *Subject:* Vorschlag Composition Features**** > > ** ** > > Hallo zusammen,**** > > Wie eben besprochen der Vorschlag zur Umstrukturierung unserer Composition > Features**** > > Viele Gr??e**** > > Andreas** > > *Composition* > > *Light Semantic Composition (Atos)* > > *Common Features:* > > **? **FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor > **** > > **? **FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository > **** > > **? **FIWARE.FEATURE.Apps. > CommonFeature.IntegrationWithMarketplace > **** > > **? **FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement > ** > > *Specific Features:* > > **? ** > FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition > **** > > **? ** > FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics > **** > > **? ** > FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL > **** > > **? ** > FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL > **** > > **? ** > FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService > **** > > **? ** > FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel > **** > > **? ** > FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel > **** > > *Service Mashup (DT)* > > *Common Features:* > > *None* > > *Specific Features:*** > > **? ** > FIWARE.FEATURE.Apps.ServiceMashup.CommonRepositoryImportExport > **** > > **? **FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose > **** > > **? **FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install > **** > > **? **FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test > **** > > **? **FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch > **** > > *Service Composition (EAB)* > > *Common Features:* > > **? **FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor > **** > > **? **FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository > **** > > **? **FIWARE.FEATURE.Apps. > CommonFeature.IntegrationWithMarketplace > **** > > **? **FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement > ** > > **? **FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore > ** > > *Specific Features:***** > > **? **FIWARE.FEATURE.Apps.ServiceComposition.CreateComposition > **** > > **? ** > FIWARE.FEATURE.Apps.ServiceComposition.CreateServiceDescription > **** > > **? **FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsEditor > **** > > **? **FIWARE.FEATURE.Apps.ServiceComposition.ExecuteComposition > **** > > **? ** > FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding > **** > > **? ** > FIWARE.FEATURE.Apps.ServiceComposition.ServiceCompositionCloudReady > **** > > **? ** > FIWARE.FEATURE.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons > **** > > **? **FIWARE.FEATURE.Apps.ServiceComposition.ContractFromStore > **** > > **? **FIWARE.FEATURE.Apps.ServiceComposition.SupportForOAuth2 > **** > > *Application Mashup (UPM)* > > *Common Features:* > > **? **FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor > **** > > **? **FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository > **** > > **? **FIWARE.FEATURE.Apps. > CommonFeature.IntegrationWithMarketplace > **** > > **? **FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore > **** > > **? **FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement > ** > > *Specific Features:***** > > **? ** > FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment > **** > > **? ** > FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition > **** > > **? ** > FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution > **** > > **? ** > FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers > **** > > **? **FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping > **** > > **** > > ** ** > > * * > > ** ** > > ** ** > > Andreas Klein**** > > SAP AG**** > > SAP Research Center Karlsruhe **** > > Vincenz-Priessnitz-Strasse 1 **** > > D - 76131 Karlsruhe **** > > ** ** > > T +49-6227-7-52554**** > > ** ** > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps > > -- *Dr. Rafael Fern?ndez* Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Wed Jan 23 13:22:24 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 23 Jan 2013 12:22:24 +0000 Subject: [Fiware-apps] FW: Vorschlag Composition Features In-Reply-To: References: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> Message-ID: <703F4EB81B2AD0428360BFE55A82DFBC325D11C8@DEWDFEMB11B.global.corp.sap> Hi Rafa, I'm open to your solution. See comments below... From: rfernandez at conwet.com [mailto:rfernandez at conwet.com] On Behalf Of Rafael Fern?ndez Sent: Mittwoch, 23. Januar 2013 13:00 To: Leidig, Torsten Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi Torsten, We had last week a discussion with Calin about how to face this topic... We agreed we need a common set of features, but if we define them in the way you propose, some problems will arise: * Common features are implemented at different times (in different releases) in different GEs sure, I would expect this. A feature should not have a release number. However, one could give a list of releases together with the partner name. * The version field is not common to all GEs. Even more, the tracker entries will lead to confusion. I see no problem. The version is the according to the feature description, not for the implementation version. * What should we write in the Source field? The comma-separated list of all sources * Who is the Owner? There should be one owner who is responsible for defining the feature. However, I see no reason to have a list of owners * In the end, even having the same name, different implementations offer different features from the perspective of the UC project because respond to different needs. E.g. both Wirecloud and the mashup factory (could) use the marketplace to publish the components they use to build a mashup, but for different objectives. The feature is usually high-level. If it is a generic feature which is provided by multiple GE, then any specific things should go into the User Stories of an individual GE. And if we use the FIWARE.FEATURE.Apps.CommonFeature.xxx notation, we won't be following the appropriate name convention (see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) ) The previous are some examples of why we think the Calin's proposal of having a common "title last name" and text in the "goal" part is better. But then we have many GE common features for the same generic functionality, which is hard to understand and causes trouble for synchronizing. Anyway, we need to have a consistent Wiki/Tracker and all entries in the tracker by the end of the week. You can decide within the task 3.1! But please implement it in the Wiki/tracker as soon as possible. Best regards, Rafa On Tue, Jan 22, 2013 at 5:01 PM, Leidig, Torsten > wrote: Dear Apps Partners, Actually it is subject to the Task 3.1 partners to come to a conclusion and decide. However, we discussed the current state internally and came up with the following proposal. The basic idea is to create Features which are common to a number of GE. We already have global features in FI-WARE. So there is no reason why we should not have Apps common features. In the Wiki there is a section listing the common features. Each GE then as a subsection listing the common features it will support plus the specific features for the GE. The common features are only documented once. The stakeholder field is a join of all stakeholders for GE implementing the feature. The description text should be somehow generic of course. The Wiki page will look like below. Please give us feedback whether that is OK for you. We have to do the changes quickly and also synchronize with the tracker (means changing the respective tracker entries) ASAP since the next delivery will be created from this information this week. Thanks and best regards, Torsten From: Klein, Andreas Sent: Dienstag, 22. Januar 2013 15:59 To: Fasse, Axel; Leidig, Torsten Cc: DL Research FI-WARE APPS Subject: Vorschlag Composition Features Hallo zusammen, Wie eben besprochen der Vorschlag zur Umstrukturierung unserer Composition Features Viele Gr??e Andreas Composition Light Semantic Composition (Atos) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: * FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition * FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics * FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL * FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL * FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService * FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel * FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel Service Mashup (DT) Common Features: None Specific Features: * FIWARE.FEATURE.Apps.ServiceMashup.CommonRepositoryImportExport * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test * FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch Service Composition (EAB) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore Specific Features: * FIWARE.FEATURE.Apps.ServiceComposition.CreateComposition * FIWARE.FEATURE.Apps.ServiceComposition.CreateServiceDescription * FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsEditor * FIWARE.FEATURE.Apps.ServiceComposition.ExecuteComposition * FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding * FIWARE.FEATURE.Apps.ServiceComposition.ServiceCompositionCloudReady * FIWARE.FEATURE.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons * FIWARE.FEATURE.Apps.ServiceComposition.ContractFromStore * FIWARE.FEATURE.Apps.ServiceComposition.SupportForOAuth2 Application Mashup (UPM) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: * FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment * FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition * FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution * FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers * FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping Andreas Klein SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe T +49-6227-7-52554 _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps -- Dr. Rafael Fern?ndez Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From calin.curescu at ericsson.com Wed Jan 23 13:31:35 2013 From: calin.curescu at ericsson.com (Calin Curescu) Date: Wed, 23 Jan 2013 12:31:35 +0000 Subject: [Fiware-apps] FW: Vorschlag Composition Features In-Reply-To: <703F4EB81B2AD0428360BFE55A82DFBC325D11C8@DEWDFEMB11B.global.corp.sap> References: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> <703F4EB81B2AD0428360BFE55A82DFBC325D11C8@DEWDFEMB11B.global.corp.sap> Message-ID: Hi, As UPM will be the main contributor I propose to go with their version. In our discussion last week we started with something like your proposal but quickly realized that unfortunately features have "release numbers", and with owner, stakeholder are important for tracking in this project and we did not want to have headaches with changing things again in the future. Who is interested could match the "common" features by name... Br, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: den 23 januari 2013 13:22 To: Rafael Fern?ndez Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi Rafa, I'm open to your solution. See comments below... From: rfernandez at conwet.com [mailto:rfernandez at conwet.com] On Behalf Of Rafael Fern?ndez Sent: Mittwoch, 23. Januar 2013 13:00 To: Leidig, Torsten Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi Torsten, We had last week a discussion with Calin about how to face this topic... We agreed we need a common set of features, but if we define them in the way you propose, some problems will arise: * Common features are implemented at different times (in different releases) in different GEs sure, I would expect this. A feature should not have a release number. However, one could give a list of releases together with the partner name. * The version field is not common to all GEs. Even more, the tracker entries will lead to confusion. I see no problem. The version is the according to the feature description, not for the implementation version. * What should we write in the Source field? The comma-separated list of all sources * Who is the Owner? There should be one owner who is responsible for defining the feature. However, I see no reason to have a list of owners * In the end, even having the same name, different implementations offer different features from the perspective of the UC project because respond to different needs. E.g. both Wirecloud and the mashup factory (could) use the marketplace to publish the components they use to build a mashup, but for different objectives. The feature is usually high-level. If it is a generic feature which is provided by multiple GE, then any specific things should go into the User Stories of an individual GE. And if we use the FIWARE.FEATURE.Apps.CommonFeature.xxx notation, we won't be following the appropriate name convention (see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) ) The previous are some examples of why we think the Calin's proposal of having a common "title last name" and text in the "goal" part is better. But then we have many GE common features for the same generic functionality, which is hard to understand and causes trouble for synchronizing. Anyway, we need to have a consistent Wiki/Tracker and all entries in the tracker by the end of the week. You can decide within the task 3.1! But please implement it in the Wiki/tracker as soon as possible. Best regards, Rafa On Tue, Jan 22, 2013 at 5:01 PM, Leidig, Torsten > wrote: Dear Apps Partners, Actually it is subject to the Task 3.1 partners to come to a conclusion and decide. However, we discussed the current state internally and came up with the following proposal. The basic idea is to create Features which are common to a number of GE. We already have global features in FI-WARE. So there is no reason why we should not have Apps common features. In the Wiki there is a section listing the common features. Each GE then as a subsection listing the common features it will support plus the specific features for the GE. The common features are only documented once. The stakeholder field is a join of all stakeholders for GE implementing the feature. The description text should be somehow generic of course. The Wiki page will look like below. Please give us feedback whether that is OK for you. We have to do the changes quickly and also synchronize with the tracker (means changing the respective tracker entries) ASAP since the next delivery will be created from this information this week. Thanks and best regards, Torsten From: Klein, Andreas Sent: Dienstag, 22. Januar 2013 15:59 To: Fasse, Axel; Leidig, Torsten Cc: DL Research FI-WARE APPS Subject: Vorschlag Composition Features Hallo zusammen, Wie eben besprochen der Vorschlag zur Umstrukturierung unserer Composition Features Viele Gr??e Andreas Composition Light Semantic Composition (Atos) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: * FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition * FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics * FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL * FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL * FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService * FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel * FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel Service Mashup (DT) Common Features: None Specific Features: * FIWARE.FEATURE.Apps.ServiceMashup.CommonRepositoryImportExport * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test * FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch Service Composition (EAB) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore Specific Features: * FIWARE.FEATURE.Apps.ServiceComposition.CreateComposition * FIWARE.FEATURE.Apps.ServiceComposition.CreateServiceDescription * FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsEditor * FIWARE.FEATURE.Apps.ServiceComposition.ExecuteComposition * FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding * FIWARE.FEATURE.Apps.ServiceComposition.ServiceCompositionCloudReady * FIWARE.FEATURE.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons * FIWARE.FEATURE.Apps.ServiceComposition.ContractFromStore * FIWARE.FEATURE.Apps.ServiceComposition.SupportForOAuth2 Application Mashup (UPM) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: * FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment * FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition * FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution * FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers * FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping Andreas Klein SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe T +49-6227-7-52554 _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps -- Dr. Rafael Fern?ndez Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From axel.fasse at sap.com Wed Jan 23 15:40:28 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Wed, 23 Jan 2013 15:40:28 +0100 Subject: [Fiware-apps] FW: Review of stakeholder field in the backlog of WP3 In-Reply-To: <50FFEB9A.4050704@tid.es> References: <50F8410E.3040500@tid.es> <50FFBC30.4090907@tid.es> <2C6296E1876B5C49962495FDACDC7A63617857CF9C@DEWDFECCR01.wdf.sap.corp> <50FFEB9A.4050704@tid.es> Message-ID: <2C6296E1876B5C49962495FDACDC7A63617857D105@DEWDFECCR01.wdf.sap.corp> Dear Partner, thank you very much for your support to finalize the issue with the stakeholder field. Miguel has confirmed that we have done our job. Thank you! Best regards, Axel From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Mittwoch, 23. Januar 2013 14:55 To: Fasse, Axel Cc: Sandfuchs, Thorsten; JUAN JOSE HIERRO SUREDA; Leidig, Torsten; Klein, Andreas Subject: Re: Review of stakeholder field in the backlog of WP3 Dear Axel, After some quick checking, I confirm that this is finished in WP3. I see that part of the backlog items have been removed and other corrected. All the lines linked from "Materializing..." look fine to me. Thansk Miguel El 23/01/2013 13:59, Fasse, Axel escribi?: Dear Miguel, thank you for the update. From our point of view we have done the required changes (even the changes that should have been done by the partners). Best regards, Axel From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Mittwoch, 23. Januar 2013 11:32 To: Fasse, Axel; Leidig, Torsten Cc: Sandfuchs, Thorsten; JUAN JOSE HIERRO SUREDA Subject: Re: Review of stakeholder field in the backlog of WP3 Dear Axel & Torsten, This is the review. I only need your reaction in those maked in red, do not worry too much about the rest of them. Thanks for your support. Miguel El 17/01/2013 19:21, Miguel Carrillo escribi?: Dear all, I have gone through the Epics and Features of your backlog and checked the status of the stakeholder field. As stated by Juanjo, the common reference for the stakeholder field at this stage is the interest expressed by the UC Projects here: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E I followed these rules in my review: * We will check Epics and Features (not User Stories) - those in "Materializing ... " on the wiki (not user stories) * We will just check those present in Release 1 (Release 2 is obviously not well populated) * We will inherit the GEs with "D" or "U" ( "E" is not enough to take a UC as a stakeholder) The enclosed excel file contains my comments. To ease your work, I marked in red the cells where I ask for a change or alternatively an explanation. These do not necessarily mean that you have to change something (well, most of the times they actually mean that but not always). The changes of the whole chapter should take less than an hour of a single person. But as I guess that you need to distribute and people will not react immediately, we can set a deadeline of next tuesday EOB. I will start checking again on wednesday first thing in the morning. Hope this is reasonable/clear enough. If you need any clarifications, let me know. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ 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 -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ 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 axel.fasse at sap.com Wed Jan 23 16:23:37 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Wed, 23 Jan 2013 16:23:37 +0100 Subject: [Fiware-apps] FW: Vorschlag Composition Features In-Reply-To: References: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> <703F4EB81B2AD0428360BFE55A82DFBC325D11C8@DEWDFEMB11B.global.corp.sap> Message-ID: <2C6296E1876B5C49962495FDACDC7A63617857D19A@DEWDFECCR01.wdf.sap.corp> Dear Calin, Dear Rafael, to avoid additional re-work, it is for sure a good idea to think about possible consequences of the suggested changes. The ideas from Torsten seems to be good and valid and I would like to ask you to provide your feedback. This feedback-step is important to ensure that we can agree on a final decision as soon as possible. It will be very helpful for all of us if we were able to provide a consistent picture of the Compositions-Technologies. Best regards, Axel From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Calin Curescu Sent: Mittwoch, 23. Januar 2013 13:32 To: Leidig, Torsten; Rafael Fern?ndez Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi, As UPM will be the main contributor I propose to go with their version. In our discussion last week we started with something like your proposal but quickly realized that unfortunately features have "release numbers", and with owner, stakeholder are important for tracking in this project and we did not want to have headaches with changing things again in the future. Who is interested could match the "common" features by name... Br, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: den 23 januari 2013 13:22 To: Rafael Fern?ndez Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi Rafa, I'm open to your solution. See comments below... From: rfernandez at conwet.com [mailto:rfernandez at conwet.com] On Behalf Of Rafael Fern?ndez Sent: Mittwoch, 23. Januar 2013 13:00 To: Leidig, Torsten Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi Torsten, We had last week a discussion with Calin about how to face this topic... We agreed we need a common set of features, but if we define them in the way you propose, some problems will arise: * Common features are implemented at different times (in different releases) in different GEs sure, I would expect this. A feature should not have a release number. However, one could give a list of releases together with the partner name. * The version field is not common to all GEs. Even more, the tracker entries will lead to confusion. I see no problem. The version is the according to the feature description, not for the implementation version. * What should we write in the Source field? The comma-separated list of all sources * Who is the Owner? There should be one owner who is responsible for defining the feature. However, I see no reason to have a list of owners * In the end, even having the same name, different implementations offer different features from the perspective of the UC project because respond to different needs. E.g. both Wirecloud and the mashup factory (could) use the marketplace to publish the components they use to build a mashup, but for different objectives. The feature is usually high-level. If it is a generic feature which is provided by multiple GE, then any specific things should go into the User Stories of an individual GE. And if we use the FIWARE.FEATURE.Apps.CommonFeature.xxx notation, we won't be following the appropriate name convention (see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) ) The previous are some examples of why we think the Calin's proposal of having a common "title last name" and text in the "goal" part is better. But then we have many GE common features for the same generic functionality, which is hard to understand and causes trouble for synchronizing. Anyway, we need to have a consistent Wiki/Tracker and all entries in the tracker by the end of the week. You can decide within the task 3.1! But please implement it in the Wiki/tracker as soon as possible. Best regards, Rafa On Tue, Jan 22, 2013 at 5:01 PM, Leidig, Torsten > wrote: Dear Apps Partners, Actually it is subject to the Task 3.1 partners to come to a conclusion and decide. However, we discussed the current state internally and came up with the following proposal. The basic idea is to create Features which are common to a number of GE. We already have global features in FI-WARE. So there is no reason why we should not have Apps common features. In the Wiki there is a section listing the common features. Each GE then as a subsection listing the common features it will support plus the specific features for the GE. The common features are only documented once. The stakeholder field is a join of all stakeholders for GE implementing the feature. The description text should be somehow generic of course. The Wiki page will look like below. Please give us feedback whether that is OK for you. We have to do the changes quickly and also synchronize with the tracker (means changing the respective tracker entries) ASAP since the next delivery will be created from this information this week. Thanks and best regards, Torsten From: Klein, Andreas Sent: Dienstag, 22. Januar 2013 15:59 To: Fasse, Axel; Leidig, Torsten Cc: DL Research FI-WARE APPS Subject: Vorschlag Composition Features Hallo zusammen, Wie eben besprochen der Vorschlag zur Umstrukturierung unserer Composition Features Viele Gr??e Andreas Composition Light Semantic Composition (Atos) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: * FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition * FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics * FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL * FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL * FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService * FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel * FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel Service Mashup (DT) Common Features: None Specific Features: * FIWARE.FEATURE.Apps.ServiceMashup.CommonRepositoryImportExport * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install * FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test * FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch Service Composition (EAB) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore Specific Features: * FIWARE.FEATURE.Apps.ServiceComposition.CreateComposition * FIWARE.FEATURE.Apps.ServiceComposition.CreateServiceDescription * FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsEditor * FIWARE.FEATURE.Apps.ServiceComposition.ExecuteComposition * FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding * FIWARE.FEATURE.Apps.ServiceComposition.ServiceCompositionCloudReady * FIWARE.FEATURE.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons * FIWARE.FEATURE.Apps.ServiceComposition.ContractFromStore * FIWARE.FEATURE.Apps.ServiceComposition.SupportForOAuth2 Application Mashup (UPM) Common Features: * FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace * FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore * FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: * FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment * FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition * FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution * FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers * FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping Andreas Klein SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe T +49-6227-7-52554 _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps -- Dr. Rafael Fern?ndez Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From axel.fasse at sap.com Fri Jan 25 14:37:02 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Fri, 25 Jan 2013 14:37:02 +0100 Subject: [Fiware-apps] [Fiware-pcc] URGENT: withdrawal of Ericsson and data on Costs/funding justification of Ericsson until Message-ID: <2C6296E1876B5C49962495FDACDC7A6361793F6237@DEWDFECCR01.wdf.sap.corp> Hallo Kollegen, diese Info betrifft uns vermutlich auch in WP3, daher wollte ich euch diese nicht vorenthalten. Bez?glich der genauen Konsequenzen und Budget Diskussionen werde ich mich mit Calin abstimmen. Sobald ich hier f?r einen Termin habe melde ich mich. Gru? Axel ---------- Forwarded message ---------- From: Juanjo Hierro > Date: 2013/1/25 Subject: [Fiware-pcc] URGENT: withdrawal of Ericsson and data on Costs/funding justification of Ericsson until To: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Cc: Javier de Pedro Sanchez >, "subsidies at tid.es" >, "fiware-pcc at lists.fi-ware.eu" > Dear all, Regretfully, we have to communicate the complete withdrawal of Ericsson in the FI-WARE project. Some of you may have already been notified by the Ericsson representative in your WP, but let this email being forwarded work as official communication. Withdrawn of Ericsson from WP3 and WP9 had already been announce time ago. It had been properly handled by the corresponding WPLs and the necessary changes in the new amendment of the DoW were already introduced. Leaders of the rest of WPs where Ericsson was participating have now to prepare and assessment of the impact and come with a proposal before Wednesday 30th noon, on how to handle the withdrawn of Ericsson in their corresponding WPs, including a proposal on how funding initially assigned to Ericsson can be transferred to other partners that can take over the role of Ericsson. Their proposal will be discussed in the Management PCC meeting that has been call on Thursday 31st, 15:00 CET. Javier de Pedro, in copy of this mail, will send the information about remaining funding associated to Ericsson after month 18th to each of the WPLs where Ericsson was involved. Available funding will help you to make a proposal about PMs to allocate to other partners that can take over the role of Ericsson. Please also consider the opportunity to keep part of the funding available for future unforeseen needs of your WP, i.e., it's not a matter of assigning the maximum PMs possible to the partner who can take over the role of Ericsson. These remaining funding would be allocated to the WPL or Telefonica, to be transferred later on, whatever option is preferred by the WPL. 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: Ericsson in FIWARE Date: Wed, 23 Jan 2013 09:54:55 +0000 From: Henrik Abramowicz To: Juanjo Hierro , "JOSE JIMENEZ DELGADO (jimenez at tid.es)" CC: Magnus Madfors , Anders Casp?r Dear Juanjo and Jose, As you have noticed we have not been so active lately in FIWARE and I am sorry to inform you that Ericsson will no longer be able to participate in FIWARE. You might also have noticed in media that Ericsson is currently downsizing and re-organising and we will have even less resources for FIWARE. This means that we will have to withdraw from FIWARE and I am personally sorry for that and that it might hurt the project inadvertently. We need to have a discussion on the withdrawal and how limit the effects for FIWARE. I have possibility for a telco already on Friday afternoon it that suits you BR Henrik HENRIK ABRAMOWICZ M Sc Ericsson AB Ericsson Research F?r?gatan 6 164 80 Stockholm, Sweden Phone +46 10 714 6608 SMS/MMS + 46 (0) 70 540 33 72 henrik.abramowicz at ericsson.com www.ericsson.com [cid:part2.03000509.04040303 at tid.es] This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer ________________________________ 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-pcc mailing list Fiware-pcc at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-pcc -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00001.gif Type: image/gif Size: 1417 bytes Desc: ATT00001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00002.gif Type: image/gif Size: 20657 bytes Desc: ATT00002.gif URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00003.txt URL: From axel.fasse at sap.com Fri Jan 25 15:12:24 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Fri, 25 Jan 2013 15:12:24 +0100 Subject: [Fiware-apps] [Fiware-pcc] URGENT: withdrawal of Ericsson and data on Costs/funding justification of Ericsson until In-Reply-To: <9AF75462DD581C48B6AFEBB0BB6E6119631309D196@DEWDFECCR01.wdf.sap.corp> References: <9AF75462DD581C48B6AFEBB0BB6E6119631309D196@DEWDFECCR01.wdf.sap.corp> Message-ID: <2C6296E1876B5C49962495FDACDC7A6361793F629C@DEWDFECCR01.wdf.sap.corp> Dear Partners, At first I have to say sorry because of the fact that I wrote the former mail in German. Sorry. But beside this, I think it is very important that you know about the official withdrawal of Ericsson. Especially in the context of WP3 we have to identify and clarify the details and implications of the changes. I would suggest to discuss this and the next steps within the next WP3 Call. Best regards, Axel From: Fasse, Axel Sent: Freitag, 25. Januar 2013 14:37 To: 'fiware-apps at lists.fi-ware.eu' (fiware-apps at lists.fi-ware.eu) Cc: Theilmann, Wolfgang (wolfgang.theilmann at sap.com) Subject: [Fiware-pcc] URGENT: withdrawal of Ericsson and data on Costs/funding justification of Ericsson until Hallo Kollegen, diese Info betrifft uns vermutlich auch in WP3, daher wollte ich euch diese nicht vorenthalten. Bez?glich der genauen Konsequenzen und Budget Diskussionen werde ich mich mit Calin abstimmen. Sobald ich hier f?r einen Termin habe melde ich mich. Gru? Axel ---------- Forwarded message ---------- From: Juanjo Hierro > Date: 2013/1/25 Subject: [Fiware-pcc] URGENT: withdrawal of Ericsson and data on Costs/funding justification of Ericsson until To: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Cc: Javier de Pedro Sanchez >, "subsidies at tid.es" >, "fiware-pcc at lists.fi-ware.eu" > Dear all, Regretfully, we have to communicate the complete withdrawal of Ericsson in the FI-WARE project. Some of you may have already been notified by the Ericsson representative in your WP, but let this email being forwarded work as official communication. Withdrawn of Ericsson from WP3 and WP9 had already been announce time ago. It had been properly handled by the corresponding WPLs and the necessary changes in the new amendment of the DoW were already introduced. Leaders of the rest of WPs where Ericsson was participating have now to prepare and assessment of the impact and come with a proposal before Wednesday 30th noon, on how to handle the withdrawn of Ericsson in their corresponding WPs, including a proposal on how funding initially assigned to Ericsson can be transferred to other partners that can take over the role of Ericsson. Their proposal will be discussed in the Management PCC meeting that has been call on Thursday 31st, 15:00 CET. Javier de Pedro, in copy of this mail, will send the information about remaining funding associated to Ericsson after month 18th to each of the WPLs where Ericsson was involved. Available funding will help you to make a proposal about PMs to allocate to other partners that can take over the role of Ericsson. Please also consider the opportunity to keep part of the funding available for future unforeseen needs of your WP, i.e., it's not a matter of assigning the maximum PMs possible to the partner who can take over the role of Ericsson. These remaining funding would be allocated to the WPL or Telefonica, to be transferred later on, whatever option is preferred by the WPL. 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: Ericsson in FIWARE Date: Wed, 23 Jan 2013 09:54:55 +0000 From: Henrik Abramowicz To: Juanjo Hierro , "JOSE JIMENEZ DELGADO (jimenez at tid.es)" CC: Magnus Madfors , Anders Casp?r Dear Juanjo and Jose, As you have noticed we have not been so active lately in FIWARE and I am sorry to inform you that Ericsson will no longer be able to participate in FIWARE. You might also have noticed in media that Ericsson is currently downsizing and re-organising and we will have even less resources for FIWARE. This means that we will have to withdraw from FIWARE and I am personally sorry for that and that it might hurt the project inadvertently. We need to have a discussion on the withdrawal and how limit the effects for FIWARE. I have possibility for a telco already on Friday afternoon it that suits you BR Henrik HENRIK ABRAMOWICZ M Sc Ericsson AB Ericsson Research F?r?gatan 6 164 80 Stockholm, Sweden Phone +46 10 714 6608 SMS/MMS + 46 (0) 70 540 33 72 henrik.abramowicz at ericsson.com www.ericsson.com [cid:image002.gif at 01CDFB0E.612EE6B0] This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer ________________________________ 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-pcc mailing list Fiware-pcc at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-pcc -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1417 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 20657 bytes Desc: image002.gif URL: From rfernandez at fi.upm.es Fri Jan 25 19:35:58 2013 From: rfernandez at fi.upm.es (=?ISO-8859-1?Q?Rafael_Fern=E1ndez?=) Date: Fri, 25 Jan 2013 19:35:58 +0100 Subject: [Fiware-apps] FW: Vorschlag Composition Features In-Reply-To: <2C6296E1876B5C49962495FDACDC7A63617857D19A@DEWDFECCR01.wdf.sap.corp> References: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> <703F4EB81B2AD0428360BFE55A82DFBC325D11C8@DEWDFEMB11B.global.corp.sap> <2C6296E1876B5C49962495FDACDC7A63617857D19A@DEWDFECCR01.wdf.sap.corp> Message-ID: Hi Apps partners, Finally we have decided that better approach was to follow Calin's proposal regarding features. Thus, we have updated ours, both in the tracker and in the wiki. Besides, we have also checked our Epics, User-stories and Workitems in the tracker. Kind regards and have a nice weekend, Rafa. On Wed, Jan 23, 2013 at 4:23 PM, Fasse, Axel wrote: > Dear Calin, Dear Rafael, **** > > ** ** > > to avoid additional re-work, it is for sure a good idea to think about > possible consequences of the suggested changes.**** > > The ideas from Torsten seems to be good and valid and I would like to ask > you to provide your feedback.**** > > This feedback-step is important to ensure that we can agree on a final > decision as soon as possible.**** > > It will be very helpful for all of us if we were able to provide a > consistent picture of the Compositions-Technologies.**** > > ** ** > > Best regards,**** > > Axel**** > > ** ** > > ** ** > > ** ** > > *From:* fiware-apps-bounces at lists.fi-ware.eu [mailto: > fiware-apps-bounces at lists.fi-ware.eu] *On Behalf Of *Calin Curescu > *Sent:* Mittwoch, 23. Januar 2013 13:32 > *To:* Leidig, Torsten; Rafael Fern?ndez > > *Cc:* fiware-apps at lists.fi-ware.eu > *Subject:* Re: [Fiware-apps] FW: Vorschlag Composition Features**** > > ** ** > > Hi,**** > > ** ** > > As UPM will be the main contributor I propose to go with their version. ** > ** > > ** ** > > In our discussion last week we started with something like your proposal > but quickly realized that unfortunately features have ?release numbers?, > and with owner, stakeholder are important for tracking in this project and > we did not want to have headaches with changing things again in the future. > **** > > ** ** > > Who is interested could match the ?common? features by name?**** > > ** ** > > Br,**** > > /Calin**** > > ** ** > > ** ** > > *From:* fiware-apps-bounces at lists.fi-ware.eu [ > mailto:fiware-apps-bounces at lists.fi-ware.eu] > *On Behalf Of *Leidig, Torsten > *Sent:* den 23 januari 2013 13:22 > *To:* Rafael Fern?ndez > *Cc:* fiware-apps at lists.fi-ware.eu > *Subject:* Re: [Fiware-apps] FW: Vorschlag Composition Features**** > > ** ** > > Hi Rafa,**** > > ** ** > > I?m open to your solution. **** > > See comments below...**** > > ** ** > > ** ** > > *From:* rfernandez at conwet.com [mailto:rfernandez at conwet.com] > *On Behalf Of *Rafael Fern?ndez > *Sent:* Mittwoch, 23. Januar 2013 13:00 > *To:* Leidig, Torsten > *Cc:* fiware-apps at lists.fi-ware.eu > *Subject:* Re: [Fiware-apps] FW: Vorschlag Composition Features**** > > ** ** > > Hi Torsten, **** > > ** ** > > We had last week a discussion with Calin about how to face this topic... > We agreed we need a common set of features, but if we define them in the > way you propose, some problems will arise:**** > > - Common features are implemented at different times (in different > releases) in different GEs**** > > sure, I would expect this. A feature should not have a release number. > However, one could give a list of releases together with the partner name. > **** > > - The version field is not common to all GEs. Even more, the tracker > entries will lead to confusion.**** > > I see no problem. The version is the according to the feature description, > not for the implementation version.**** > > - What should we write in the Source field?**** > > The comma-separated list of all sources**** > > - Who is the Owner?**** > > There should be one owner who is responsible for defining the feature. > However, I see no reason to have a list of owners**** > > - In the end, even having the same name, different implementations > offer different features from the perspective of the UC project because > respond to different needs. E.g. both Wirecloud and the mashup factory > (could) use the marketplace to publish the components they use to build a > mashup, but for different objectives.**** > > The feature is usually high-level. If it is a generic feature which is > provided by multiple GE, then any specific things should go into the User > Stories of an individual GE.**** > > And if we use the FIWARE.FEATURE.Apps.CommonFeature.xxx notation, we won't > be following the appropriate name convention (see > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow)) > **** > > ** ** > > The previous are some examples of why we think the Calin's proposal of > having a common "title last name" and text in the "goal" part is better.** > ** > > ** ** > > But then we have many GE common features for the same generic > functionality, which is hard to understand and causes trouble for > synchronizing.**** > > ** ** > > Anyway, we need to have a consistent Wiki/Tracker and all entries in the > tracker by the end of the week. You can decide within the task 3.1! But > please implement it in the Wiki/tracker as soon as possible.**** > > ** ** > > Best regards, **** > > Rafa**** > > ** ** > > ** ** > > On Tue, Jan 22, 2013 at 5:01 PM, Leidig, Torsten > wrote:**** > > Dear Apps Partners,**** > > **** > > Actually it is subject to the Task 3.1 partners to come to a conclusion > and decide. However, we discussed the current state internally and came up > with the following proposal. The basic idea is to create Features which are > common to a number of GE. We already have global features in FI-WARE. So > there is no reason why we should not have Apps common features. In the Wiki > there is a section listing the common features. Each GE then as a > subsection listing the common features it will support plus the specific > features for the GE.**** > > The common features are only documented once. The stakeholder field is a > join of all stakeholders for GE implementing the feature.**** > > The description text should be somehow generic of course.**** > > **** > > The Wiki page will look like below. Please give us feedback whether that > is OK for you. We have to do the changes quickly and also synchronize with > the tracker (means changing the respective tracker entries) ASAP since the > next delivery will be created from this information this week.**** > > **** > > Thanks and best regards,**** > > Torsten**** > > **** > > **** > > **** > > *From:* Klein, Andreas > *Sent:* Dienstag, 22. Januar 2013 15:59 > *To:* Fasse, Axel; Leidig, Torsten > *Cc:* DL Research FI-WARE APPS > *Subject:* Vorschlag Composition Features**** > > **** > > Hallo zusammen,**** > > Wie eben besprochen der Vorschlag zur Umstrukturierung unserer Composition > Features**** > > Viele Gr??e**** > > Andreas**** > > *Composition***** > > *Light Semantic Composition (Atos)***** > > *Common Features:***** > > ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement > **** > > *Specific Features:***** > > ? FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition > **** > > ? FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics > **** > > ? > FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL > **** > > ? > FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL > **** > > ? FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService > **** > > ? > FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel > **** > > ? > FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel > **** > > *Service Mashup (DT)***** > > *Common Features:***** > > *None***** > > *Specific Features:***** > > ? FIWARE.FEATURE.Apps.ServiceMashup.CommonRepositoryImportExport > **** > > ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose > **** > > ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install > **** > > ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test > **** > > ? FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch > **** > > *Service Composition (EAB)***** > > *Common Features:***** > > ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore > **** > > *Specific Features:***** > > ? FIWARE.FEATURE.Apps.ServiceComposition.CreateComposition > **** > > ? FIWARE.FEATURE.Apps.ServiceComposition.CreateServiceDescription > **** > > ? FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsEditor > **** > > ? FIWARE.FEATURE.Apps.ServiceComposition.ExecuteComposition > **** > > ? > FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding > **** > > ? > FIWARE.FEATURE.Apps.ServiceComposition.ServiceCompositionCloudReady > **** > > ? > FIWARE.FEATURE.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons > **** > > ? FIWARE.FEATURE.Apps.ServiceComposition.ContractFromStore > **** > > ? FIWARE.FEATURE.Apps.ServiceComposition.SupportForOAuth2 > **** > > *Application Mashup (UPM)***** > > *Common Features:***** > > ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore > **** > > ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement > **** > > *Specific Features:***** > > ? > FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment > **** > > ? > FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition > **** > > ? > FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution > **** > > ? > FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers > **** > > ? FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping > **** > > **** > > **** > > * ***** > > **** > > **** > > Andreas Klein**** > > SAP AG**** > > SAP Research Center Karlsruhe **** > > Vincenz-Priessnitz-Strasse 1 **** > > D - 76131 Karlsruhe **** > > **** > > T +49-6227-7-52554**** > > **** > > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps**** > > > > **** > > ** ** > > -- > *Dr. Rafael Fern?ndez* > Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software > Facultad de Inform?tica - Universidad Polit?cnica de Madrid > Campus Internacional de Excelencia Montegancedo > 28660 - Boadilla del Monte, Madrid > Spain**** > -- *Dr. Rafael Fern?ndez* Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Mon Jan 28 10:23:05 2013 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 28 Jan 2013 09:23:05 +0000 Subject: [Fiware-apps] FW: Vorschlag Composition Features In-Reply-To: References: <8AF50F49B590C242AEBA50D6730499A4057303BD6C@DEWDFECCR05.wdf.sap.corp> <703F4EB81B2AD0428360BFE55A82DFBC325D055B@DEWDFEMB11B.global.corp.sap> <703F4EB81B2AD0428360BFE55A82DFBC325D11C8@DEWDFEMB11B.global.corp.sap> <2C6296E1876B5C49962495FDACDC7A63617857D19A@DEWDFECCR01.wdf.sap.corp>, Message-ID: Trank you very much! Am 25.01.2013 um 19:36 schrieb "Rafael Fern?ndez" >: Hi Apps partners, Finally we have decided that better approach was to follow Calin's proposal regarding features. Thus, we have updated ours, both in the tracker and in the wiki. Besides, we have also checked our Epics, User-stories and Workitems in the tracker. Kind regards and have a nice weekend, Rafa. On Wed, Jan 23, 2013 at 4:23 PM, Fasse, Axel > wrote: Dear Calin, Dear Rafael, to avoid additional re-work, it is for sure a good idea to think about possible consequences of the suggested changes. The ideas from Torsten seems to be good and valid and I would like to ask you to provide your feedback. This feedback-step is important to ensure that we can agree on a final decision as soon as possible. It will be very helpful for all of us if we were able to provide a consistent picture of the Compositions-Technologies. Best regards, Axel From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Calin Curescu Sent: Mittwoch, 23. Januar 2013 13:32 To: Leidig, Torsten; Rafael Fern?ndez Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi, As UPM will be the main contributor I propose to go with their version. In our discussion last week we started with something like your proposal but quickly realized that unfortunately features have ?release numbers?, and with owner, stakeholder are important for tracking in this project and we did not want to have headaches with changing things again in the future. Who is interested could match the ?common? features by name? Br, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: den 23 januari 2013 13:22 To: Rafael Fern?ndez Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi Rafa, I?m open to your solution. See comments below... From: rfernandez at conwet.com [mailto:rfernandez at conwet.com] On Behalf Of Rafael Fern?ndez Sent: Mittwoch, 23. Januar 2013 13:00 To: Leidig, Torsten Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: Vorschlag Composition Features Hi Torsten, We had last week a discussion with Calin about how to face this topic... We agreed we need a common set of features, but if we define them in the way you propose, some problems will arise: * Common features are implemented at different times (in different releases) in different GEs sure, I would expect this. A feature should not have a release number. However, one could give a list of releases together with the partner name. * The version field is not common to all GEs. Even more, the tracker entries will lead to confusion. I see no problem. The version is the according to the feature description, not for the implementation version. * What should we write in the Source field? The comma-separated list of all sources * Who is the Owner? There should be one owner who is responsible for defining the feature. However, I see no reason to have a list of owners * In the end, even having the same name, different implementations offer different features from the perspective of the UC project because respond to different needs. E.g. both Wirecloud and the mashup factory (could) use the marketplace to publish the components they use to build a mashup, but for different objectives. The feature is usually high-level. If it is a generic feature which is provided by multiple GE, then any specific things should go into the User Stories of an individual GE. And if we use the FIWARE.FEATURE.Apps.CommonFeature.xxx notation, we won't be following the appropriate name convention (see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) ) The previous are some examples of why we think the Calin's proposal of having a common "title last name" and text in the "goal" part is better. But then we have many GE common features for the same generic functionality, which is hard to understand and causes trouble for synchronizing. Anyway, we need to have a consistent Wiki/Tracker and all entries in the tracker by the end of the week. You can decide within the task 3.1! But please implement it in the Wiki/tracker as soon as possible. Best regards, Rafa On Tue, Jan 22, 2013 at 5:01 PM, Leidig, Torsten > wrote: Dear Apps Partners, Actually it is subject to the Task 3.1 partners to come to a conclusion and decide. However, we discussed the current state internally and came up with the following proposal. The basic idea is to create Features which are common to a number of GE. We already have global features in FI-WARE. So there is no reason why we should not have Apps common features. In the Wiki there is a section listing the common features. Each GE then as a subsection listing the common features it will support plus the specific features for the GE. The common features are only documented once. The stakeholder field is a join of all stakeholders for GE implementing the feature. The description text should be somehow generic of course. The Wiki page will look like below. Please give us feedback whether that is OK for you. We have to do the changes quickly and also synchronize with the tracker (means changing the respective tracker entries) ASAP since the next delivery will be created from this information this week. Thanks and best regards, Torsten From: Klein, Andreas Sent: Dienstag, 22. Januar 2013 15:59 To: Fasse, Axel; Leidig, Torsten Cc: DL Research FI-WARE APPS Subject: Vorschlag Composition Features Hallo zusammen, Wie eben besprochen der Vorschlag zur Umstrukturierung unserer Composition Features Viele Gr??e Andreas Composition Light Semantic Composition (Atos) Common Features: ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: ? FIWARE.FEATURE.Apps.LightSemanticComposition.ModelComposition ? FIWARE.FEATURE.Apps.LightSemanticComposition.PrepareDSLSemantics ? FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL ? FIWARE.FEATURE.Apps.LightSemanticComposition.DescribeServiceUsingDSL ? FIWARE.FEATURE.Apps.LightSemanticComposition.BindTaskToService ? FIWARE.FEATURE.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel ? FIWARE.FEATURE.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel Service Mashup (DT) Common Features: None Specific Features: ? FIWARE.FEATURE.Apps.ServiceMashup.CommonRepositoryImportExport ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Compose ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Install ? FIWARE.FEATURE.Apps.ServiceMashup.MashupFactory-Test ? FIWARE.FEATURE.Apps.ServiceMashup.GeoLocationSearch Service Composition (EAB) Common Features: ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore Specific Features: ? FIWARE.FEATURE.Apps.ServiceComposition.CreateComposition ? FIWARE.FEATURE.Apps.ServiceComposition.CreateServiceDescription ? FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsEditor ? FIWARE.FEATURE.Apps.ServiceComposition.ExecuteComposition ? FIWARE.FEATURE.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding ? FIWARE.FEATURE.Apps.ServiceComposition.ServiceCompositionCloudReady ? FIWARE.FEATURE.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons ? FIWARE.FEATURE.Apps.ServiceComposition.ContractFromStore ? FIWARE.FEATURE.Apps.ServiceComposition.SupportForOAuth2 Application Mashup (UPM) Common Features: ? FIWARE.FEATURE.Apps.CommonFeature.IntegrationWithUSDLEditor ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithRepository ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithMarketplace ? FIWARE.FEATURE.Apps. CommonFeature.IntegrationWithStore ? FIWARE.FEATURE.Apps. CommonFeature.SupportForIdManagement Specific Features: ? FIWARE.FEATURE.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment ? FIWARE.FEATURE.Apps.ApplicationMashup.CreateUIOrientedServiceComposition ? FIWARE.FEATURE.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution ? FIWARE.FEATURE.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers ? FIWARE.FEATURE.Apps.ApplicationMashup.SupportForPiping Andreas Klein SAP AG SAP Research Center Karlsruhe Vincenz-Priessnitz-Strasse 1 D - 76131 Karlsruhe T +49-6227-7-52554 _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps -- Dr. Rafael Fern?ndez Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -- Dr. Rafael Fern?ndez Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Tue Jan 29 09:49:06 2013 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Tue, 29 Jan 2013 09:49:06 +0100 Subject: [Fiware-apps] [Fiware-pcc] URGENT: withdrawal of Ericsson and data on Costs/funding justification of Ericsson until In-Reply-To: <2C6296E1876B5C49962495FDACDC7A6361793F629C@DEWDFECCR01.wdf.sap.corp> References: <9AF75462DD581C48B6AFEBB0BB6E6119631309D196@DEWDFECCR01.wdf.sap.corp> <2C6296E1876B5C49962495FDACDC7A6361793F629C@DEWDFECCR01.wdf.sap.corp> Message-ID: Dear Axel, I would really appreciate if you could tackle this issue at the very beginning of the conf call because I have to leave by 10:30 to join a dissertation defense. BR, Javier 2013/1/25 Fasse, Axel > Dear Partners,**** > > ** ** > > At first I have to say sorry because of the fact that I wrote the former > mail in German. Sorry.**** > > ** ** > > But beside this, I think it is very important that you know about the > official withdrawal of Ericsson.**** > > Especially in the context of WP3 we have to identify and clarify the > details and implications of the changes.**** > > I would suggest to discuss this and the next steps within the next WP3 > Call.**** > > ** ** > > ** ** > > Best regards,**** > > Axel**** > > ** ** > > ** ** > > ** ** > > *From:* Fasse, Axel > *Sent:* Freitag, 25. Januar 2013 14:37 > *To:* 'fiware-apps at lists.fi-ware.eu' (fiware-apps at lists.fi-ware.eu) > *Cc:* Theilmann, Wolfgang (wolfgang.theilmann at sap.com) > > *Subject:* [Fiware-pcc] URGENT: withdrawal of Ericsson and data on > Costs/funding justification of Ericsson until**** > > ** ** > > Hallo Kollegen,**** > > ** ** > > diese Info betrifft uns vermutlich auch in WP3, daher wollte ich euch > diese nicht vorenthalten.**** > > Bez?glich der genauen Konsequenzen und Budget Diskussionen werde ich mich > mit Calin abstimmen. **** > > Sobald ich hier f?r einen Termin habe melde ich mich.**** > > ** ** > > Gru?**** > > Axel**** > > ---------- Forwarded message ---------- > From: *Juanjo Hierro* > Date: 2013/1/25 > Subject: [Fiware-pcc] URGENT: withdrawal of Ericsson and data on > Costs/funding justification of Ericsson until > To: "fiware-wpl at lists.fi-ware.eu" , " > fiware-wpa at lists.fi-ware.eu" > Cc: Javier de Pedro Sanchez , "subsidies at tid.es" < > subsidies at tid.es>, "fiware-pcc at lists.fi-ware.eu" < > fiware-pcc at lists.fi-ware.eu>**** > > Dear all, > > Regretfully, we have to communicate the complete withdrawal of Ericsson > in the FI-WARE project. Some of you may have already been notified by > the Ericsson representative in your WP, but let this email being forwarded > work as official communication. > > Withdrawn of Ericsson from WP3 and WP9 had already been announce time > ago. It had been properly handled by the corresponding WPLs and the > necessary changes in the new amendment of the DoW were already introduced. > > Leaders of the rest of WPs where Ericsson was participating have now to > prepare and assessment of the impact and come with a proposal before > Wednesday 30th noon, on how to handle the withdrawn of Ericsson in their > corresponding WPs, including a proposal on how funding initially assigned > to Ericsson can be transferred to other partners that can take over the > role of Ericsson. Their proposal will be discussed in the Management > PCC meeting that has been call on Thursday 31st, 15:00 CET. > > Javier de Pedro, in copy of this mail, will send the information about > remaining funding associated to Ericsson after month 18th to each of the > WPLs where Ericsson was involved. Available funding will help you to > make a proposal about PMs to allocate to other partners that can take over > the role of Ericsson. Please also consider the opportunity to keep part > of the funding available for future unforeseen needs of your WP, i.e., it's > not a matter of assigning the maximum PMs possible to the partner who can > take over the role of Ericsson. These remaining funding would be > allocated to the WPL or Telefonica, to be transferred later on, whatever > option is preferred by the WPL. > > 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: * > > Ericsson in FIWARE**** > > *Date: * > > Wed, 23 Jan 2013 09:54:55 +0000**** > > *From: * > > Henrik Abramowicz > **** > > *To: * > > Juanjo Hierro , "JOSE JIMENEZ DELGADO ( > jimenez at tid.es)" **** > > *CC: * > > Magnus Madfors , > Anders Casp?r *** > * > > ** ** > > Dear Juanjo and Jose,**** > > As you have noticed we have not been so active lately in FIWARE and I am > sorry to inform you that Ericsson will no longer be able to participate in > FIWARE. **** > > You might also have noticed in media that Ericsson is currently downsizing > and re-organising and we will have even less resources for FIWARE.**** > > This means that we will have to withdraw from FIWARE and I am personally > sorry for that and that it might hurt the project inadvertently.**** > > **** > > We need to have a discussion on the withdrawal and how limit the effects > for FIWARE.**** > > **** > > I have possibility for a telco already on Friday afternoon it that suits > you**** > > BR**** > > *Henrik***** > > [image: line]**** > > *HENRIK ABRAMOWICZ M Sc* * > ***** > > > Ericsson AB > Ericsson Research > F?r?gatan 6 > 164 80 Stockholm, Sweden > Phone +46 10 714 6608 > SMS/MMS + 46 (0) 70 540 33 72 > henrik.abramowicz at ericsson.com > www.ericsson.com **** > > > > [image: http://www.ericsson.com/current_campaign] > **** > > **** > > This Communication is Confidential. We only send and receive email on the > basis of the terms set out at www.ericsson.com/email_disclaimer **** > > **** > > ** ** > > ** ** > ------------------------------ > > > 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-pcc mailing list > Fiware-pcc at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-pcc**** > > > > > -- > Stefano De Panfilis > Chief Innovation Officer > Engineering Ingegneria Informatica S.p.A. > via Riccardo Morandi 32 > 00148 Roma > Italy > > tel (direct): +39-068307-4295 > tel (secr.): +39-068307-4513 > fax: +39-068307-4200 > cell: +39-335-7542-567**** > > > > > -- > Stefano De Panfilis > Chief Innovation Officer > Engineering Ingegneria Informatica S.p.A. > via Riccardo Morandi 32 > 00148 Roma > Italy > > tel (direct): +39-068307-4295 > tel (secr.): +39-068307-4513 > fax: +39-068307-4200 > cell: +39-335-7542-567**** > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps > > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 20657 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1417 bytes Desc: not available URL: From axel.fasse at sap.com Wed Jan 30 15:51:04 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Wed, 30 Jan 2013 15:51:04 +0100 Subject: [Fiware-apps] Roadmap, WIKI and Tracker Message-ID: <2C6296E1876B5C49962495FDACDC7A6361796CA2C9@DEWDFECCR01.wdf.sap.corp> Dear Partners, I would like to send an email to Juanjo by end of this week to announce that WP3 has finished its work on the Roadmap. This means that TID will be able to create the upcoming deliverables automatically afterwards. So please check that you have updated the WIKI and that you have finished the consolidation of the EIPC's, Features and Use-Cases in the WIKI in a consistent way. Our last analysis has shown, that Composition, RSS und BE&BM have only a few (or no!!!) entries. Please take into account that you might run into trouble to justify your budget if your work and your working-plans are not properly reflected within the Tracker. Beside this some information are not complete or consistent, please have a look into the XLS File. Please fix this issue until Friday 10:00 AM. Afterwards I will send the "confirmation mail" to Juanjo. So please finalize this task in time. If you are not able to finalize this task in the given timeslot, please contact me directly to avoid any kind of misunderstanding and delay. Beside this you can have a look into the minutes for our last call: https://forge.fi-ware.eu/docman/view.php/12/1827/FI-WARE_WP3_Minutes_2013-01-29.doc If you have any kind of questions or comments, please let me know. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TechnicalRoadmapWP3.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 20391 bytes Desc: TechnicalRoadmapWP3.xlsx URL: