Hello, For the AndroidFlowMonitoring and MalwareDetectionService parts, the "Copyright" and "Legal Notice" are present in the wiki pages, and they have been for at least a month. Also, there has recently been some changes to these pages on the public wiki, to address comments made during the OpenSpec review (which includes the Architecture Description). And Finally could I get some clarifications about the "Legal Notice" ? A few days ago we got another mail telling us that the licenses were ready and there were two to choose from… P.S.: should'n the "Copyright" section of the Security Monitoring section include every participant as well? Best regards, Alexandre ----- Mail original ----- > De: "BISSON Pascal" <pascal.bisson at thalesgroup.com> > À: "Juanjo Hierro" <jhierro at tid.es> > Cc: fiware-security at lists.fi-ware.eu > Envoyé: Lundi 27 Mai 2013 11:00:02 > Objet: Re: [Fiware-security] [Fiware-wpl] Fwd: Submission of FI-WARE > Deliverable D.2.3.2 - FI-WARE Architecture > Dear All, > I’m forwarding you this email I got from Juanjo. See comments he did > provide on architecture specifications and especially ours (aka > Security). > Please notice they have incorporated in the architecture deliverable > he did already submit (as stated in his email). > But now we have to perform the necessary adjustments on the wiki for > them to be included in the Open Specs deliverable. > Being said we are already beyond schedule please update the wiki asap > so that we can generate and deliver the open specs. > As usual drop me and/Daniel an email once changes have been > performed. > Counting on your promptness to get this demand addressed > Thanks, > Regards > Pascal > De : fiware-wpl-bounces at lists.fi-ware.eu > [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo > Hierro > Envoyé : lundi 27 mai 2013 07:45 > À : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - > FI-WARE Architecture > Hi, > Please find attached the final official submission of the FI-WARE > Architecture deliverable. > While carrying out a very final cross-chapter revision, I have > identified the need to achieve a better consistency between names of > sections in the different chapters and even within chapters: > * There were some cases where the section titled "Basic Concepts" > within the Architecture Description of a given GE was titled as > "Main Concepts". I have changed this wherever I found it > * There were some cases where the "Main Interactions" section within > the Architecture Description of a given GE was titled as "Main > Operations". I have changed this wherever I found it. > There were GEs in the Security chapter for which the sections related > to Copyright and Legal Notices were missing. This also happens > regarding Basic Design Principles. Please add these sections asap. > Despite I asked for the names of the companies to be added manually, > I got no response. > It would be nice that you perform a general review of the structure > in your chapters and double-check alignment with the standard > structure template we defined. I fixed a lot of the issues but this > would be only reflected in the final deliverable so I have produced > and already sent to you a version with comments that highlighted the > changes you should introduce in the public wiki ASAP (note that this > document is marked as private). For your convenience, here it goes > the structure of sections that should have been adopted: > 1. General Architecture Description of a Chapter: > 1. Introduction > 2. Architecture Overview > 3. <several high-level sections such as "Use Cases" may come here> > 4. Architecture Description of GEs > 5. Interface to other chapters > 6. References > 2. > Architecture Description of a given GE: > 1. Copyright > 2. Legal Notice > 3. Overview (Target usage should be inside) > 4. Basic Concepts > 5. <Name-of-GE> Architecture (recommended but optional, sometimes you > have put this before "Basic concepts" but it would be nice to keep > consistency and place it after) > 6. Main Interactions > 7. Basic Design Principles > 8. Detailed Open Specifications (which should contain the links to > the rest of Open Specifications) > 9. References > There were also A LOT of inconsistencies regarding level of headings. > As an example, there were many chapters where there wasn't a second > level heading. This was revealed thanks to the automated generation > process and should be fixed in the wiki asap to avoid wrong > generation next times. > I carried out a final spelling checking to all chapters finding also > many typos. > I have to confess that I got astonished when I saw still those kind > of issues in a so late stage of the peer-review ... Didn't nobody > notice that? Despite we incurred in a delay, I have now found that > it was worth carrying out this final review. Without giving names, > when I have asked "how can we still find this issues?" in the draft > I had just reviewed, I got the response "honestly, I believe some > people hasn't read the contents in that detail". We honestly have to > reconsider how we are carrying out our peer-review processes. > I have also carried out several changes to improve overall > readability. > The detailed Open Specifications where not included in all cases, > even within the same chapter, so I have had to put a note to the EC > and reviewers explaining that we had decided to keep the inclusion > by those GEs that decided to include it, because we will adopt that > convention finally. Therefore, please do so. > In addition, I also found that the copyright notice in many of the > cases was only for 2012. This maybe interpreted by the reviewers as > "no single line has been touched by the owners this year" when > clearly this doesn't apply. Please fix those Copyright Notices where > you have to write 2012-2013 (in the case of new GEs, 2013) > Last but not least, there are a number of things that I have detected > about which we have to reach a final agreement and adopt a > convention across all chapters: > * Titles, numbering and format (i.e., centered or not) of figures. I > believe that we proposed a convention, and asked to avoid using of > figure numbers, but apparently hasn't been followed consistently > * Architecture section within a GE Architecture Description > * Style for references > We should address all of them once we finish with the most urgent > things we currently have on our plate, but have them ready at the > time we will start disseminating this among the wider community of > developers. > Please share with members of your respective chapters. > Best regards, -- Juanjo > ------------- Product Development and Innovation (PDI) - Telefonica > Digital website: www.tid.es email: 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 > -------- Original Message -------- > Subject: > Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture > Date: > Mon, 27 May 2013 07:32:02 +0200 > From: > Juanjo Hierro <jhierro at tid.es> > To: > Arian.ZWEGERS at ec.europa.eu <Arian.ZWEGERS at ec.europa.eu> , > Ragnar.Bergstrom at ec.europa.eu , dgr at whitestein.com , > msli at icfocus.co.uk , renaud.difrancesco at eu.sony.com , > irena.pavlova at isoft-technology.com > CC: > INFSO-ICT-285248 at ec.europa.eu , Vanessa.VANHUMBEECK at ec.europa.eu , > mcp at tid.es , "jhierro >> \"Juan J. Hierro\"" <jhierro at tid.es> > Dear all, > This is the official submission of deliverable D.2.3.2 FI-WARE > Architecture. To ease review of its contents, separate files have > been produced for the different chapters that made up the whole > document. All of these files can be extracted from the .zip file you > can download from the following URL: > https://forge.fi-ware.eu/docman/view.php/7/2468/D.2.3.2+FI-WARE+Architecture+Official+deliverable.zip > Note that the FI-WARE Architecture specification is public and its > contents become part of the several FI-WARE GE Open Specifications, > therefore you can download this file without logging in your > FusionForge account. We haven't delivered it earlier to make sure > that it was aligned with the contents of FI-WARE GE Open > Specifications that will be delivered along this week (some of them > have already been delivered to you). > The FI-WARE Architecture has beed produced conducting several > peer-reviews and a final whole revision by myself, as chief > architect, to ensure overall consistency. > You will see that the description of the architecture of some GEs > ended with a sections that provides the links to the Detailed > Specifications. This doesn't happen in all the cases and will be > fixed in subsequent releases of the deliverable. However, we thought > it was not critical to add them here because you are going to > receive them separately. > Note that specifications are still provided together with an interim > Legal Notice. This is because the Legal Notice accompanying > specifications is still going through a final review by legal > representatives of the different partners. This process is about to > finish, so we don't expect major issues regarding usage by UC > projects within the FI-PPP or impact in the launch of the FI-WARE > Open Innovation Lab. Furthermore, differences between the final and > interim Legal Notices is rather minor. > As you know, the FI-WARE GE Open Specifications are constantly > updated on the FI-WARE public wiki. You can refer to contents of the > public wiki for the most up-to-date contents of public documentation > associated to the FI-WARE project. > Don't hesitate to contact us in case you have any question. > Best regards, > -- Juanjo Hierro > ------------- Product Development and Innovation (PDI) - Telefonica > Digital website: www.tid.es email: 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 > 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-security mailing list > Fiware-security at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20130527/686623c5/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy