Dear Thorsten, We didn't address this during our WPL/WPA confcall because we run out of time and this is an issue that can be handle off-line through active discussion in the mailing list. I'm happy to incorporate this kind of picture in the introduction of the Architecture document but I believe there are still some improvements we have to make in the picture if we don't want it to be a mere collection of boxes clustered in chapters ... inmho that would be a source of criticism. There are at least two enhancements I would like to implement in the picture and would go on this direction: * It would be nice to distinguish between backend and Local (cloud edge or however we want to call it). This distinction applies to infrastructure and the FI-WARE software running on top of that infrastructure. Besides, this will allow to position also the network and therefore the places where I2ND GEs will fit (otherwise completely missed in the proposed picture). It would even be nice to incorporate access devices (the devices -PC, laptops, tablets, mobiles- from which enduser access to applications) * It is nice to incorporate existing backend systems with which integration of FI-WARE GEs will typically be performed (to be implemented by each FI-WARE Instance Provider). However, I wouldn't position them in the picture "below" FI-WARE GEs and at the same level as the infrastructure. Besides this, I miss some of the FI-WARE GEs in the Data Chapter (e.g., Semantic Application support) and the ones listed for the IoT chapter are wrong. I can make a proposal but only later this evening. If Thorsten may come with an alternative based on the above comments, it would be nice. I don't believe "we have literally no time". I believe we have already agreed that the Architecture deliverable will be submitted April 10th so there is still some time ... Best regards, -- Juanjo ------------- 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) Coordinator and 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 On 21/03/13 07:56, Sandfuchs, Thorsten wrote: Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. März 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu> [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoyé : lundi 18 mars 2013 20:16 À : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com<mailto:glikson at il.ibm.com> | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: "Sandfuchs, Thorsten" <thorsten.sandfuchs at sap.com<mailto:thorsten.sandfuchs at sap.com>> To: "fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>" <fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>>, "fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>" <fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>>, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu> ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu<mailto:fiware-wpa-bounces at lists.fi-ware.eu> [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten [mailbox:///Users/jhierro/Mail/correo.tid.es/Inbox?number=1257296033&header=quotebody&part=1.1.2&filename=image001.jpg] -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.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. Please consider the environment before printing this mail! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu<mailto:Fiware-wpl at lists.fi-ware.eu> https://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu<mailto:Fiware-wpa at lists.fi-ware.eu> https://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ 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/fiware-wpa/attachments/20130321/fad98b24/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 71929 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20130321/fad98b24/attachment.jpe>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy