Dear Daniel, dear all, @Daniel: thanks for that, I will check @all:status: * IoT - delivered on time, I will review it (thanks, Thierry) * Security - delivered one day late, I will review it (thanks, Daniel) * Apps - delayed - some partners did not finish their part * Cloud - delayed - no news (Alex, what's the situation?) Best regards, Miguel El 19/06/2013 13:00, GIDOIN Daniel escribió: Dear Miguel, Please find attached the SOTA deliverable with the security chapter updates. Best regards Daniel De : 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] De la part de Miguel Carrillo Envoyé : lundi 10 juin 2013 16:11 À : fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> Objet : [Fiware-wpa] Update on State of the Art deliverable (action required) Dear all, This message is to update you on the status of this deliverable and also to allow direct forwarding to your teams if you like( you are very busy these days). @WPL: be aware that you have to unify the contributions of the partners in your WP. The last contribution came extremely late (last tuesday) so delivering now could even be backfiring: * If we deliver, they will complain about delivering 3-4 days before the review (this will irritate them) and also that the document could be seen as a muddle of different contributions put together with no accord (the references section is largely different across WPs) * If we do not deliver, they will complain about not having the deliverable Assuming that they will complain anyway (and they will be right in doing so), let us get this properly done. After putting all your contributions together and reformatting all the whole lot, it became apparent that each chapter was using a different approach. Theoretically we should have followed the convention from the DoW, that is the one that I circulated in the initial "skeleton" I sent. It is essential to unify it. Things to do/change: * Some have a table at the end, some have more than a table (one at the end of each intra-WP section). We need a single unified table at the end of each chapter. * Some follow the original convention, some other write [1], [2] .... We want the original one. * Please make sure that the contributions are in alphabetical order (sorted by reference code) In summary: * Apps, Cloud and Security to reformat their references (not numbers) and to add a single table at the end (take the table in Data as the reference). Please use the table format (same as Data) * IoT to add such a table * I2ND do not follow it 100% but we can take it as it is. Just convert it into a table (now it is just plain text if I am right). Please use the attached document as the starting point to do this work. It took hours to reformat and we cannot lose all that work. Let us prevent the usual iterations. The way to do it is to get it right from the start. These are the checkpoints would cause a rejection so please avoid them and all of us will make good use of our time: * Contributions not using the attached doc as starting point * Contributions not following the naming convention (also the format - capital letters, table format, etc.) * Contributions with more than one table * Contributions not in alphabetical order * Mismatches between the references in the text and the references table Deadline: Tuesday, 18th of June It is the time to start applying the new rules that we discussed in out latest WPL/WPA call. So please note that if a given WPL sends me a contribution, it means that he has personally checked that the above list of checkpoints is met. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telefónica Distrito Telefónica _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es<mailto:mcp at tid.es> Follow FI-WARE on the net 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 -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telefónica Distrito Telefónica _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es<mailto:mcp at tid.es> Follow FI-WARE on the net 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/fiware-wpa/attachments/20130619/99ffe5c2/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy