Dear Susana, Dear ALL, According to my understanding and despite additional instructions I requested from Juanjo here are my recommendations on how to proceed: · First you should assume the Table of Content of FI-WARE Architecture description should follow the one defined for V1 even (so please have a look at what was done for V1 and re-use it for V2) o See for V1: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security_Architecture · In case you'd like to change Introduction or Architecture Overview at Chapter level please drop an email to Daniel (cc me) since as Security Architect he will address suggested changes at Sec Chapter level for what concerns Architecture Description. · Concentrate on Architecture Description of GEs either for update of existing ones or new ones as per statements in Technical Roadmap V2. Regarding Architecture Description of GEs please follow the same template as for V1 so 1-Overview, 2-Basic concepts, 3-Main interactions, 4-Basic design principles (and obviously not 5-Open Specifications since to be added later). · And now for changes/add-ons: o For minor changes compare to V1 to save time would suggest to make them directly on the Public wiki (since at the end content would be moved there - but here please proceed cautiously !! -) of course you could also prefer to put a copy of what is one public wiki, and edit it for requested update ... o For major changes I would suggest to first upload on the private Wiki for peer review (first on security Chapter Private Wiki see link below - in case a shared space on private wiki for this deliverable would be created by Juanjo will let you know ...) https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Security_Contrib Hope I have answered and yes each of the GEs' owners for V2 please upload your draft contributions on the Security private wiki. Thanks for your cooperation and support. Best Regards, Pascal PS: Apologize for my late answer but I was in a meeting the whole day ... De : Susana Gonzalez Zarzosa [mailto:susana.gzarzosa at atosresearch.eu] Envoyé : mardi 26 février 2013 13:34 À : BISSON Pascal; fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu> Objet : RE: [Fiware-security] FI-WARE Architecture for Release 2 [REMINDER] Hi Pascal, Could you please tell us where exactly should we add our contributions in private wiki? https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3Security is almost empty... and the same for security wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Security_Contrib Thank you very much! Regards, Susana From: fiware-security-bounces at lists.fi-ware.eu<mailto:fiware-security-bounces at lists.fi-ware.eu> [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: lunes, 25 de febrero de 2013 20:36 To: fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu> Subject: [Fiware-security] FI-WARE Architecture for Release 2 [REMINDER] Dear All, Just to remind you that First draft of Security Chapter contributions to FI-WARE Architecture for Release 2 is expected to be ready for review by end of February. As such we would review this First draft of our contributions per each of the Tasks and attached GE(s) at our weekly audio conf of Friday March 1st. Please each of the task leads take necessary steps to be in a positio dy on (private wiki) to be presented on Friday. Just to remind you that: 1. Architecture description already released is the one on the public wiki available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security_Architecture<http://forge.fi-ware.euiware/index.php/Security_Architecture> 2. First draft of Security Chapter contributions to FI-WARE Architecture for Release 2 is aiming at getting it completed for what concerns second release of existing GEs or new GEs (and their targeted features) as stated in the technical roadmap which was already updated (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Security<http://forge.fi-ware.eu/plugins/mediap/Roadmap_of_Security>). a. NB1: For those of you who were involved in FI-WARE Architecture for Release 1 you should be familiar with what to and how to contribute. For those of you who were not involved please don't hesitate to refer to what was done for V1 (see 1)) and interact Task lead to which your GE is attached. b. NB2: regarding Architecture description of each of the GEs please check your conform to the template which was the one used for V1 (i.e.. 1- Overview & Architecture, 2-Basic concepts, 3- Main Interactions, 4- Basic Design Principles) As for the next steps (assuming we would have delivered fir d of this week) here they are as discussed this morning with CA and other WPL/WPA colleagues: * Comments on first draft due by March 8th * Second draft of chapters ready for peer review: March 15th * Comments on second draft due by March 22th * Final version: April 5th Hope it helps to clarify. Best Regards, Pascal PS: Will let you know in case of further instructions would be provided b 7; lead. ------------------------------------------------------------------ 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: <https://lists.fiware.org/private/old-fiware-security/attachments/20130227/e91cfe73/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy