Dear all, I am sorry for not attending the telco, i am afraid i misunderstood the last email and i thought no telco was scheduled today. Regards Yosu On Fri, 2011-06-24 at 12:22 +0200, Friesen, Andreas wrote: > Dear All, > > > > here the summary of today’s WP3 call: > > > > Participants > > > > Andreas Friesen (SAP) > > Calin Curescu (EAB) > > Horst Stein (DT) > > Keven Kearney (ENG) > > > > Andreas: Reported on the current status of the WP3 contribution to the > M2 deliverable (the first complete draft submitted to FusionForge at > 21st of June). The feedback from WP2 about the integration into M2 > deliverable expected on Monday, 27th of June (EOB). The next actions > are to improve the “terms and definitions” section and the “question > marks” section. > > Calin: Distributed an improved version of T3.1 contribution > > Keven: Submitted the first version of SLA Management description > > Andreas: We continue to collect partner updates for the M2 > deliverable. The next consolidated version of WP3 contribution will be > created next week after we received feedback from WP2. After the M2 > deliverable has been finalized we should start talking to other WPs, > first of all to the security WP. Please start thinking about potential > security requirements and threats. We will have to nominate 2-3 > experts to talk with security architects about security issues in the > WP3 architecture. Please find attached the email from Juanjo > explaining the next actions expected from us in more detail. > > > > Best regards, > > 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. > > > > > > > email message attachment > > -------- Forwarded Message -------- > > From: Juanjo Hierro <jhierro at tid.es> > > To: fiware-wpl at lists.fi-ware.eu <fiware-wpl at lists.fi-ware.eu>, > > fiware-wpa at lists.fi-ware.eu <fiware-wpa at lists.fi-ware.eu> > > Subject: [Fiware-wpl] IMPORTANT - Start of integration of FI-WARE > > High-level Description deliverable: next steps > > Date: Thu, 23 Jun 2011 09:04:32 +0200 > > > > Hi all, > > > > I believe that all the Architecture Chapter teams have uploaded > > their contribution to the docman system. Thanks for your > > commitment and effort !! > > > > Now, I will start to integrate the different chapters into a > > single document and perform and overall review all the chapters > > while making the integration. My plan is to finish this process by > > monday June 27, EOB. > > > > What can teams do in the meantime ? My suggestion is that you > > work in the "Question Marks" section and give also a final review to > > the "terms and definitions" section if you had generated it in the > > last minute (I know it is the case for some teams :-) These two > > sections can be easily replaced in the integrated document. > > > > Regarding the "Question Marks" section, I would suggest to > > structure it into a subsection titled "Security aspects" and a > > subsection titled "Other topics still under discussion". > > * On "Security aspects": I suggest that you nominate one-two > > people in your team that work with the WP8 team to analyze > > contents of your chapter and identify Security questions. > > Please contact Pascal Bisson > > (pascal.bisson at thalesgroup.com), leader of WP8, to > > coordinate with him how to carry out this task. It is > > about identifying at least 3-5 issues, and describing each > > with one-two paragraphs. You can download the > > contribution linked to the Data/Context Management chapter > > and check the "Security aspects" subsection where you may > > find some reference examples (particularly the one on > > Privacy Management) > > * On "Other topics still under discussion": The idea is just > > formulate 3-5 topics for which discussion has not yet been > > finalized within the team. Try to elaborate on the > > different alternatives you are considering/discussing with > > respect to the topic as well as any consideration that is > > relevant. Each topic should be described similarly to how > > topics in the "Security aspects" subsection were described > > in the Data/Context Management chapter (again, the > > description of the Privacy Management issue is a good > > reference example). It is up to the WPL how to organize > > this task. > > Regarding the "terms and definitions" section, there isn't > > anything special to remark. But try to provide precise > > definitions. Also try to make this section something that can > > "work" relatively standalone. > > > > I expect your contributions to both sections by Tuesday June 29, > > 19:00 CET. > > > > IN ADDITION: I know that some of you still wish to work on the > > content of sections linked to the overview and description of GEs. > > How can you work in parallel to integration ? I would suggest the > > following: > > * In the placeholder under the contrib folder linked to your > > document you will always be able to find the last version of > > your chapter already integrated in the final document. > > * Whenever I start to work with a given chapter, I will change > > its status to "pending" (this is one of the valid status > > -like "private"- you can assign to a document in the form > > linked to an entry in the Admin section of the docman > > system). This will mean I have blocked it. You will > > detect that your contribution is pending because you > > wouldn't be able to see it in the folders/document tree that > > is displayed when you click on "View Documentation". You > > should then wait until I upload a new version (already > > integrated in the master document). Of course, you may > > still be working on some changes but then you should > > implement them individually over the file that I will > > finally upload to the docman system (that file may have > > comments or even changes and, for sure, some fixes in > > formatting I don't want to loose, so it won't be as simple > > as replace the file with the one you were working on in > > parallel to me). Whenever I upload a new version of the > > file, I will change its status to "private" and you will be > > able to see it in the folders/document tree. > > * If a document is not "pending", this mean that you can > > download it and work on it. But, PLEASE, whenever you plan > > to do so, please mark it also as "pending" before > > downloading, so that I can realize you will download it and > > start working on it. You only have the right to keep a > > document "pending" from 09:00am to 19:00pm. After 19:00 > > and until 09:00am the next day, I can change its status and > > replace the attached file without notice. In the event I > > need that you release the document -changing its state to > > "private" again- before 19:00, I'll let you know. > > * PLEASE, DON'T CREATE NEW ENTRIES: It should work with the > > already existing ones, changing the status and replacing the > > attached file when needed. > > > > I know that we would probably do it better using SVN but SVN got > > installed recently and many people don't have the time to get used > > to it. Despite it took some time, all WPLs already know how to > > manage the docman, so we should keep using docman for this release > > of the deliverable. > > > > For a number of reasons, I won't be able to start integration > > until 19:00 today (it's holiday in Spain) so you will find that all > > the contributions to each chapter are marked as "private", > > therefore, not blocked. > > > > Let's work hard to finish the document !! > > > > Best regards, > > > > -- Juanjo > > > > > > > > > > ____________________________________________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > > consultar nuestra política de envío y recepción de correo > > electrónico en el enlace situado más abajo. > > This message is intended exclusively for its addressee. We only send > > and receive email on the basis of the terms set out at. > > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy