[Fiware-apps] Agenda for today's WP3 call - next action

[Horst.Stein at telekom.de]

 Hey everybody,

I support Yosus contribution, (especially the "bank-end business service" remembering the financial crisis two years ago).
For the service delivery framework I propose the definition in wiki for SDP:
Service Delivery Platform (SDP) refers to a set of components that provide a services delivery architecture (such as service creation, session control & protocols) for a type of service.
http://en.wikipedia.org/wiki/Service_delivery_platform
This may fit better than the one for
http://en.wikipedia.org/wiki/Service_delivery_framework

Best regards
Horst

-----Ursprüngliche Nachricht-----
Von: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] Im Auftrag von Jesus Gorroñogoitia Cruz
Gesendet: Montag, 4. Juli 2011 12:52
An: Friesen, Andreas; fiware-apps at lists.fi-ware.eu
Betreff: Re: [Fiware-apps] Agenda for today's WP3 call - next action

Dear All,
my two cents for section Terms and Definitions.
Kind regards
Yosu


-----Original Message-----
From: fiware-apps-bounces at lists.fi-ware.eu on behalf of Friesen, Andreas
Sent: Fri 7/1/2011 16:04
To: 'fiware-apps at lists.fi-ware.eu'
Subject: Re: [Fiware-apps] Agenda for today's WP3 call - next action

Dear All,

after a call with Juanjo today afternoon, I created an updated version of our M2 contribution that will be reviewed by Juanjo over the weekend. Please find this version attached (it has been also uploaded to FusionForge).

The last section in the document is about "Terms And Definitions". The list of terms we distributed earlier this week is included. I also tried to reuse already available definitions for some of the terms. Please take a look to the list of terms and send definitions to terms from your area of expertice to the wp mailing list.

Deadline: As agreed in the call today -> Monday 04.07 eob!

Tim (UDE) will consolidate and provide an update until Wednesday 06.07.

Furthermore, we will have to react to Juanjo's review until Monday, eob. Most probably we will need your support to perform this update, so I hope many of you will be able to contribute on short term.

Thanks and regards
Andreas

From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Friesen, Andreas
Sent: Freitag, 1. Juli 2011 09:46
To: 'fiware-apps at lists.fi-ware.eu'
Subject: [Fiware-apps] Agenda for today's WP3 call

Dear All,

we still have no feedback from WP2 on WP3 M2 contribution.

Here is a list of open tasks we have to discuss:


-          Terms and definitions (we send around a list of potential terms to be defined) - we have to agree on granularity, responsibilities, and deadlines to finalize this part of M2 deliverable

-          SLA Management (we made this week some progress with ENG, a new section for SLA Management as GE is available)

-          Business Framework ( a new figure created, to be agreed with T3.3 partners)

First contacts to other WPs to be established:

Security

-          SAP established the first contact with respect to USDL sec extensions

-          What are the security requirements of T3.1? A contact person from T3.1 to talk with security architects to be nominated!!!

Interface to Network and Devices

-          A number of composition tools in T3.1 are able to consume telco services... A contact person from T3.1 to talk with this WP to be nominated!!!

-
Cloud

-          Cloud services can be potentially offered on marketplaces similar to services and apps from WP3, so there could be specific requirements on USDL (SAP to talk to cloud people)

-          T3.1 services and apps can be potentially deployed/hosted to the cloud. A contact person from T3.1 to be nominated!!!

-
IoT Service Enablement

-          Similar to cloud there could be IoT specific requirements on USDL (SAP to talk to IoT people)

-          What is the relationship of T3.1 tools and environments to IoT services? A contact person from T3.1 to talk with this WP to be nominated!!!

Context/Data Management relationship to WP3???

Best
Andreas
Dr. Andreas Friesen
Research Program Manager Service Science
SAP Research Center Karlsruhe
SAP AG
Vincenz-Priessnitz-Strasse 1
76131 Karlsruhe, Germany
T   + 49 6227 752 586
F   + 49 6227 78-43567
M   +49 171 8674630
mailto:andreas.friesen 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.




------------------------------------------------------------------
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.
------------------------------------------------------------------