Dear All, I'm forwarding you this email I got from Juanjo as per review he performed of material we produced so far for what concerns GE architecture specifications starting first for M9 (D2.3 deliverable) but also in view of M12 deliverable. To all and more specifically Task and GE owners who have contributed to those specification to carefully review and take account of those comments in next release of those specifications. Would also be discussed at WP8 session and for sure be re-addressed at Plenary session for sure. For those of you who are not attending the meeting in Madrid (i.e. Robert, Michael, Anja, ...) please contribute your view and answer to comments received from Juanjo. Best Regards, Pascal De : Juanjo Hierro [mailto:jhierro at tid.es] Envoyé : mardi 24 janvier 2012 08:24 À : BISSON Pascal Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : About Architecture deliverable Hi Pascal, I have carried out a quick review of what you have already there in the Security chapter and I have found that it is still a rather early draft (not that much content developed, in several cases, just figures like in Security Monitoring). On the other hand, there are some GEs for which the work that has been done is much more aligned to what has to be added for mont 12h without having developed what is needed in month 9 (i.e., detailed specification of operations in interfaces for the CSS GE, without no overview or narrative introduction first). BTW, I notice that several of the detailed interface specifications (detailed specification of operations) are provided as kind of Web Service (though I don't see a WSDL definition, I see references to SOAP in some GEs like the antivirus morphus, I guess is some sort of interface based on document-based SOAP exchange). I'm particularly worried that I didn't find anything regarding Identity Management, Access Control and Data Handling ... These are the core ones and rest of the chapter need to learn how this works !! I guess I'm taking a look at the right place: https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Security_Contrib The IoT chapter has made some more progress, but it is still to far from the target IMHO. At this point, I guess that the best I can do is to provide an example which will try to be as complete as possible. It has come to my mind that it should not be that difficult for the description of the Architecture of the Publish/Subscribe Broker GE, which description I wrote for the FI-WARE Product Vision. I will try to get it finished so it is ready for tomorrow or Thursday. It might not be fully complete, but should provide the necessary hints to get a more accurate idea of what is needed that you can share with your respective teams. Cheers, -- ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120124/35e2c988/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy