From francesco.di.cerbo at sap.com Mon Jun 3 12:01:06 2013 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Mon, 3 Jun 2013 10:01:06 +0000 Subject: [Fiware-security] USDL-SEC Release + Editor Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E6070AF0DA@DEWDFEMB18B.global.corp.sap> Hello all, As announced last Friday, please find the updated USDL-SEC specification and the pointer towards the USDL-SEC editor (merged with the official USDL Editor): https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.USDL-SEC this page contains information about the specification, as well as a documentation on how to use the USDL-SEC part of the editor. In case you need more information, please don't hesitate to ask. Best regards, Francesco ___ Francesco Di Cerbo, PhD SAP Next Business and Technology Applied Research Security & Trust SAP Labs France 805, avenue Maurice Donat Font de l'Orme BP 1216 06250 Mougins Cedex France Tel. +33 4 92 28 64 45 e-mail: Francesco.Di.Cerbo at sap.com From Adrian.Waller at uk.thalesgroup.com Tue Jun 4 11:03:11 2013 From: Adrian.Waller at uk.thalesgroup.com (WALLER Adrian) Date: Tue, 4 Jun 2013 10:03:11 +0100 Subject: [Fiware-security] IEEE TSP 2013 CFPs with 8 SCI & EI Indexed Journal Special Issues In-Reply-To: <95D1675184F5DA469C7C701C9F5DBE3752FF0756@DAPHNIS.office.hd> References: <95D1675184F5DA469C7C701C9F5DBE3752FF0756@DAPHNIS.office.hd> Message-ID: <7C80A1EAA66A4F45BA3A574774382B9BA90C96BFA1@THSONEP02CMB01P.one-02-priv.grp> FYI. Given deadline of June 15th I suspect you may have other priorities :o), but you never know. Apologies if you received multiple copies of this IEEE TSP 2013 CFPs. Regards, Adrian ------------------------------------------------------------------------------------------ Call for Papers for the Fourth IEEE International Symposium on Trust, Security and Privacy for Emerging Applications (TSP-13),November 13-15, 2013 in Zhangjiajie, China http://trust.csu.edu.cn/conference/tsp2013 In Conjunction with the 15th IEEE International Conference on High Performance Computing and Communications (HPCC 2013), November 13-15, 2013 in Zhangjiajie, China http://trust.csu.edu.cn/conference/hpcc2013 ------------ Highlight: ------------ Distinguished papers, after further revisions, will be published in the following SCI & EI indexed journal special issues: (1) Information Sciences - Elsevier (SCI&EI Indexed, Impact Factor: 2.833) http://www.journals.elsevier.com/information-sciences/ (2) Future Generation Computer Systems - Elsevier (SCI&EI Indexed, Impact Factor: 1.978) http://www.journals.elsevier.com/future-generation-computer-systems/ (3) IEEE Systems Journal (SCI&EI Indexed, Impact Factor: 0.923) http://ieeesystemsjournal.org/ (4) Computers & Security - Elsevier (SCI&EI Indexed, Impact Factor: 0.868) http://ees.elsevier.com/cose/ (5) International Journal of Ad Hoc and Ubiquitous Computing (IJAHUC) - INDERSCIENCE (SCI&EI Indexed, Impact Factor: 0.848) http://www.inderscience.com/jhome.php?jcode=IJAHUC (6) Security and Communication Networks - Wiley (SCI&EI Indexed, Impact Factor: 0.414) http://www.interscience.wiley.com/security (7) *International Journal of Computational Science and Engineering (IJCSE) - INDERSCIENCE (EI Indexed) http://www.inderscience.com/jhome.php?jcode=IJCSE (8) *International Journal of Autonomous and Adaptive Communications Systems (IJAACS) - INDERSCIENCE (EI Indexed) http://www.inderscience.com/jhome.php?jcode=IJAACS *Selected papers from this conference will be published directly in those journal special issues (they will NOT appear in the conference proceedings). ------------------------------------------------------------------------------------------------------------- Introduction Satisfying user requirements for trust, security and privacy in an efficient way is one of the first considerations for almost all emerging applications, using emerging technologies such as pervasive computing, peer to peer computing, grid computing, cloud computing, virtualization and, mobile and wireless technologies. Challenges arise as emerging applications evolve to provide more scalable and comprehensive services. One of the biggest challenges is that traditional security technologies and measures may not meet user requirements in open, dynamic, heterogeneous, and distributed computing environments. Therefore, we need to build networks and systems in which emerging applications allow users to enjoy more scalable and comprehensive services while preserving trust, security and privacy at the same time. Following the success of TSP 2008 in Shanghai, China during December 17-20, 2008, TSP-09 in Macau SAR, China, during October 12-14, 2009, and TSP-10 in Bradford, UK, during June 29- July 1, 2010, ??The Fourth IEEE International Symposium on Trust, Security and Privacy for Emerging Applications (TSP-13)?? will be held in Zhangjiajie, China, during November 13-15, 2013, in conjunction with ??The 15th IEEE International Conference on High Performance Computing and Communications (HPCC 2013) ??, aims at bringing together researchers and practitioners in the world working on trust, security, privacy, and related issues such as technical, social, and cultural implications for all emerging devices, services, applications, networks, and systems, and providing a forum for them to present and discuss emerging ideas and trends in this highly challenging research area. Scope and Interests TSP-13 is an international forum for presenting and discussing emerging ideas and trends in trust, security and privacy for emerging applications from both the research community as well as the industry. Topics of interest include, but are not limited to: (1) TSP metrics, architectures, and models (2)TSP in big data (3) TSP in pervasive computing (4) TSP in peer to peer computing (5) TSP in grid computing (6) TSP in cloud computing (7) TSP in mobile and wireless communications (8) TSP in cyber-physical systems (9) TSP in parallel and distributed systems (10) TSP in e-commerce and e-government systems (11) TSP in hardware and software co-design (12) TSP in operating systems (13) TSP in database systems (14) TSP in virtualization technologies (15) Privacy and anonymity technologies (16) Risk analysis and management (17) Reliability, dependability, and fault tolerance (18) Network attacks and defenses (19) Cryptography and security protocols (20) Authentication, access control, and accounting Submission and Publication Information The accepted papers from this symposium will be published by IEEE Computer Society in IEEE HPCC 2013 conference proceedings (indexed by EI Compendex). Papers should be written in English conforming to the IEEE standard conference format (8.5" x 11", Two-Column). Papers should be submitted through the paper submission system at the symposium website. Each paper is limited to 6 pages (or 10 pages with over length charge). Distinguished papers, after further revisions, will be published in several SCI & EI indexed special issues. The program committee will select one winner for the Best Paper Award for this symposium. Authors (at least one) of any accepted paper are requested to register at the conference. Important Dates Submission Deadline: June 15, 2013 Authors Notification: August 15, 2013 Final Manuscript Due: September 15, 2013 Conference Dates: November 13-15, 2013 General Co-Chairs Geyong Min, The University of Bradford, UK Vijay Varadharajan, Macquarie University, Australia Ryan K. L. Ko, The University of Waikato, New Zealand Program Co-Chairs Yang Xiang, Deakin University, Australia Felix Gomez Marmol, NEC Laboratories Europe, Germany Sushmita Ruj, Indian Statistical Institute, Kolkata, India Program Committee (in alphabetical order) Habtamu Abie, Norwegian Computing Center, Norway Ruo Ando, NICT, Japan Alex Aravind, University of Northern British Columbia, Canada Salima Benbernou, Universite Paris Descartes, France Rajendra V. Boppana, UT San Antonio, USA Christian Callegari, The University of Pisa, Italy Sudip Chakraborty, Valdosta State University, USA Anupam Chattopadhyay, RWTH, Germany Aloysius Cheang, Cloud Security Alliance, Singapore Franco Chiaraluce, Polytechnical University of Marche (UVPM), Italy Jianfeng Chu, Jilin University, China John A. Clark, University of York, UK Junzhao Du, Xidian University, P. R. China Jorde Forne, Universitat Polit??cnica de Catalunya (UPC), Spain Jianming Fu, Wuhan University, P. R. China Kannan Govindan, Samsung Research, India Nils Gruschka, Fachhochschule Kiel, Germany Sheikh Mahbub Habib, TU Darmstadt, Germany Yoshiaki Hori, Saga University, Japan Robert C. H. Hsu, Chung Hua University, Taiwan Tanya Ignatenko, Eindhoven University of Technology, The Netherlands Hai Jiang, Arkansas State University, USA Georgios Kambourakis, University of the Aegean, Greece Melike Erol-Kantarci, University of Ottawa, Canada Tai-hoon Kim, Sungshin W. University, Korea Christopher Leckie, University of Melbourne, Australia Francis Bu Sung Lee, Nanyang Technological University, Singapore Juan Li, North Dakota State University, USA Xiaodong Lin, University of Ontario Institute of Technology, Canada Peng Liu, Hangzhou Dianzi University, P. R. China Giovanni Livraga, Universita' degli Studi di Milano, Italy Volkmar Lotz, SAP Labs France, France Rongxing Lu, Nanyang Technological University, Singapore Sanjay Madria, Missouri University of Science and Technology, USA Abdallah Mhamed, TELECOM SudParis, France Is-Haka Mkwawa, University of Plymouth, UK Saad Bani Mohammad, Al al-Bayt University, Jordan Amiya Nayak, University of Ottawa, Canada Joon S. Park, Syracuse University, USA Ricardo Azevedo Pereira, Portugal Telecom Inovacao, Portugal Roberto Di Pietro, Roma Tre University of Rome, Italy Vincenzo Piuri, University of Milan, Italy Gang Pan, Zhejiang University, P. R. China Imed Romdhani, Edinburgh Npier University, UK Bimal Roy, Indian Statistical Institute, India Giovanni Russello, University of Auckland, New Zealand Christoph Sorge, University of Paderborn, Germany Masakazu Soshi, Hiroshima City University, Japan Chunhua Su, JAIST, Japan Willy Susilo, University of Wollongong, Australia Chang-Ai Sun, University of Science and Technology Beijing, P. R. China Dhiah el Diehn I. Abou-Tair, University of Siegen, Germany Kenichi Takahashi, Tottori University, Japan Zhe Tang, Central South University, P. R. China Yoshifumi UESHIGE, Nagasaki University, Japan Pramode Verma, The University of Oklahoma-Tulsa, USA Luis Javier Garc??a Villalba, Complutense University of Madrid, Spain Adrian Waller, Thales Research and Technology (UK) Ltd., UK Lizhe Wang, Rochester Institute of Technology, USA Hejun Wu, Sun Yat-Sen University, P. R. China Yongdong Wu, Institute for Infocomm Research, Singapore Sugang Xu, NICT, Japan Toshihiro Yamauchi, Okayama University, Japan Yanjiang Yang, Institute for Infocomm Research, Singapore Muneer Bani Yassein, Jordan University of Science and Technology, Jordan Baoliu Ye, Nanjing University, P. R. China Shucheng Yu, University of Arkansas at Little Rock, USA Shui Yu, Deakin University, Australia Sherali Zeadally, University of the District of Columbia, USA Steering Committee Guojun Wang, Central South University, China (Chair) Laurence T. Yang, St. Francis Xavier University, Canada (Chair) Jiannong Cao, The Hong Kong Polytechnic University, Hong Kong Minyi Guo, Shanghai Jiao Tong University, China Jie Li, University of Tsukuba, Japan Jianhua Ma, Hosei University, Japan Peter Mueller, IBM Zurich Research Laboratory, Switzerland Indrakshi Ray, Colorado State University, USA Kouichi Sakurai, Kyushu University, Japan Ivan Stojmenovic, University of Ottawa, Canada Bhavani Thuraisingham, The University of Texas at Dallas, USA Jie Wu, Temple University, USA Yang Xiang, Deakin University, Australia Kun Yang, University of Essex, UK Wanlei Zhou, Deakin University, Australia Publicity Co-Chairs Al-Sakib Khan Pathan, IIUM, Malaysia Kejie Lu, University of Puerto Rico at Mayaguez, USA Raja Naeem Akram, Edinburgh Napier, UK Secretariats Qin Liu, Central South University, China Tao Peng, Central South University, China Contact Please email inquiries concerning TSP-13 to: Prof. Guojun Wang: csgjwang AT gmail DOT com and the conference organizers: tsp2013zhangjiajie AT gmail DOT com Homepage: http://trust.csu.edu.cn/faculty/~csgjwang/ Copyright @ Trusted Computing Institute, CSU http://trust.csu.edu.cn/ -------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Jun 4 14:54:02 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 4 Jun 2013 14:54:02 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Message-ID: <16734_1370350450_51ADE371_16734_1221_1_9469874a-0f98-46ad-860a-8d1a113584f7@THSONEA01HUB05P.one.grp> Dear WP8 colleagues, I'm forwarding you that email reminded you to update the backlog tracker if not done already due to Sprint transition (S2.3.2 (May) -> S2.3.2 (June). Please also be reminded that the proposal here as been agreed to improve backlog management so please follow check and follow. https://forge.fi-ware.eu/docman/view.php/27/2180/FI-WARE-Proposal+for+backlog+improvements+v6.pdf Counting on you. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : jeudi 30 mai 2013 17:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Dear Partners, Let me remind you that we are finishing sprint S2.3.2-M25 and about to start S2.3.3-M26. Please, be aware S2.3.3 is the last sprint of the second major release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog accordingly: * Close the backlog items finished during M25 (if not already done) * Update items under execution not finished to belong to S2.3.3 * Proceed to identify the backlog items for next sprint Let me inform you that the trackers have implemented the new features: * Bug is available as entry type - theme isn't available anymore * You can update sprints and releases by selecting them on a select box. The old release and sprint fields will exist until we transfer data to the new fields. * You have available all states for the backlog items, let me remind: o Open -> defined o Scheduled -> mean those selected for the current sprint and release o Under execution -> developing them o Impeded -> items cannot be progressed because something else prevents you doing it o Under verification -> validating them o Closed -> finished successfully * All chapters have available the GE Implementation field. If you had any doubt, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From Richard.Egan at uk.thalesgroup.com Tue Jun 4 15:26:43 2013 From: Richard.Egan at uk.thalesgroup.com (EGAN Richard) Date: Tue, 4 Jun 2013 14:26:43 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers In-Reply-To: <16734_1370350450_51ADE371_16734_1221_1_9469874a-0f98-46ad-860a-8d1a113584f7@THSONEA01HUB05P.one.grp> References: <16734_1370350450_51ADE371_16734_1221_1_9469874a-0f98-46ad-860a-8d1a113584f7@THSONEA01HUB05P.one.grp> Message-ID: <7C80A1EAA66A4F45BA3A574774382B9BA90C9AF826@THSONEP02CMB01P.one-02-priv.grp> Pascal (or anyone) when I tried to change the Workflow State of an item in the tracker from "under execution" to "closed", the "closed" option was greyed out and not available. Any suggestions for what I might be doing wrong? Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 04 June 2013 13:54 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Dear WP8 colleagues, I'm forwarding you that email reminded you to update the backlog tracker if not done already due to Sprint transition (S2.3.2 (May) -> S2.3.2 (June). Please also be reminded that the proposal here as been agreed to improve backlog management so please follow check and follow. https://forge.fi-ware.eu/docman/view.php/27/2180/FI-WARE-Proposal+for+backlog+improvements+v6.pdf Counting on you. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : jeudi 30 mai 2013 17:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Dear Partners, Let me remind you that we are finishing sprint S2.3.2-M25 and about to start S2.3.3-M26. Please, be aware S2.3.3 is the last sprint of the second major release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog accordingly: * Close the backlog items finished during M25 (if not already done) * Update items under execution not finished to belong to S2.3.3 * Proceed to identify the backlog items for next sprint Let me inform you that the trackers have implemented the new features: * Bug is available as entry type - theme isn't available anymore * You can update sprints and releases by selecting them on a select box. The old release and sprint fields will exist until we transfer data to the new fields. * You have available all states for the backlog items, let me remind: o Open -> defined o Scheduled -> mean those selected for the current sprint and release o Under execution -> developing them o Impeded -> items cannot be progressed because something else prevents you doing it o Under verification -> validating them o Closed -> finished successfully * All chapters have available the GE Implementation field. If you had any doubt, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ 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: From mcp at tid.es Tue Jun 4 16:02:09 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 04 Jun 2013 16:02:09 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers In-Reply-To: <7C80A1EAA66A4F45BA3A574774382B9BA90C9AF826@THSONEP02CMB01P.one-02-priv.grp> References: <16734_1370350450_51ADE371_16734_1221_1_9469874a-0f98-46ad-860a-8d1a113584f7@THSONEA01HUB05P.one.grp> <7C80A1EAA66A4F45BA3A574774382B9BA90C9AF826@THSONEP02CMB01P.one-02-priv.grp> Message-ID: <51ADF361.8010402@tid.es> F.Y.I. (please note that same transitions maybe restricted to admin or WPL profiles only) The transition you refer to is not allowed. [cid:part1.02060201.01010301 at tid.es] El 04/06/2013 15:26, EGAN Richard escribi?: Pascal (or anyone) when I tried to change the Workflow State of an item in the tracker from "under execution" to "closed", the "closed" option was greyed out and not available. Any suggestions for what I might be doing wrong? Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 04 June 2013 13:54 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Dear WP8 colleagues, I'm forwarding you that email reminded you to update the backlog tracker if not done already due to Sprint transition (S2.3.2 (May) -> S2.3.2 (June). Please also be reminded that the proposal here as been agreed to improve backlog management so please follow check and follow. https://forge.fi-ware.eu/docman/view.php/27/2180/FI-WARE-Proposal+for+backlog+improvements+v6.pdf Counting on you. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : jeudi 30 mai 2013 17:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Dear Partners, Let me remind you that we are finishing sprint S2.3.2-M25 and about to start S2.3.3-M26. Please, be aware S2.3.3 is the last sprint of the second major release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog accordingly: * Close the backlog items finished during M25 (if not already done) * Update items under execution not finished to belong to S2.3.3 * Proceed to identify the backlog items for next sprint Let me inform you that the trackers have implemented the new features: * Bug is available as entry type - theme isn't available anymore * You can update sprints and releases by selecting them on a select box. The old release and sprint fields will exist until we transfer data to the new fields. * You have available all states for the backlog items, let me remind: o Open -> defined o Scheduled -> mean those selected for the current sprint and release o Under execution -> developing them o Impeded -> items cannot be progressed because something else prevents you doing it o Under verification -> validating them o Closed -> finished successfully * All chapters have available the GE Implementation field. If you had any doubt, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: abgfijad.png Type: image/png Size: 44936 bytes Desc: not available URL: From Wolfgang.Steigerwald at telekom.de Wed Jun 5 11:10:56 2013 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Wed, 5 Jun 2013 11:10:56 +0200 Subject: [Fiware-security] Meeting in Paris Message-ID: Hallo Robert, here the filled slide for the meeting. Best regards Wolfgang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Paris Meeting June 2013_v01.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 185404 bytes Desc: Paris Meeting June 2013_v01.pptx URL: From francesco.di.cerbo at sap.com Wed Jun 5 12:04:47 2013 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Wed, 5 Jun 2013 10:04:47 +0000 Subject: [Fiware-security] T8.4 contributors: your help for Paris meeting! Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E6070AF8B4@DEWDFEMB18B.global.corp.sap> Hello T8.4 partners, Please find this presentation, you are kindly invited to contribute to it, at your earliest convenience! Sorry for the last-minute request. Best regards, Francesco ___ Francesco Di Cerbo, PhD SAP Next Business and Technology Applied Research Security & Trust SAP Labs France 805, avenue Maurice Donat Font de l'Orme BP 1216 06250 Mougins Cedex France Tel. +33 4 92 28 64 45 e-mail: Francesco.Di.Cerbo at sap.com -------------- next part -------------- A non-text attachment was scrubbed... Name: T8.4-Paris Meeting June 2013_v01.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 186141 bytes Desc: T8.4-Paris Meeting June 2013_v01.pptx URL: From daniel.gidoin at thalesgroup.com Tue Jun 11 17:16:29 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Tue, 11 Jun 2013 17:16:29 +0200 Subject: [Fiware-security] [Fiware-wpa] Current draft of periodic report In-Reply-To: <51B5E4CE.5020708@tid.es> References: <51B5E4CE.5020708@tid.es> Message-ID: <10137_1370963826_51B73F6E_10137_14194_1_eaa1b70a-03f7-485f-a378-fc3f84fa2991@THSONEA01HUB02P.one.grp> Dear Juanjo, I corrected some things pages 117, 119, 120. Best regards Daniel -----Message d'origine----- De?: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy??: lundi 10 juin 2013 16:38 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpa] Current draft of periodic report Hi, I pass it to you as it stands now in case you can provide some early feedback. Cheers, -- 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 ________________________________ 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE-2ndyearreview-preparation.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 4137495 bytes Desc: FI-WARE-2ndyearreview-preparation.docx URL: From daniel.gidoin at thalesgroup.com Tue Jun 11 17:24:12 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Tue, 11 Jun 2013 17:24:12 +0200 Subject: [Fiware-security] [Fiware-wpa] Current draft of periodic report References: <51B5E4CE.5020708@tid.es> Message-ID: <10137_1370964294_51B74146_10137_14521_1_01bd876d-317e-4316-80fb-5173928a3e0b@THSONEA01HUB04P.one.grp> Dear Juanjo, Please find attached the latest update of our slides for the review Best regards Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE M24 Official Review WP8 report v5 11062013-security.ppt Type: application/vnd.ms-powerpoint Size: 1702400 bytes Desc: FI-WARE M24 Official Review WP8 report v5 11062013-security.ppt URL: From pascal.bisson at thalesgroup.com Tue Jun 11 18:35:29 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 11 Jun 2013 18:35:29 +0200 Subject: [Fiware-security] =?utf-8?q?Annul=C3=A9=3A_FI-WARE_WP8_Weekly_aud?= =?utf-8?q?io_conf?= Message-ID: <25046_1370968530_51B751D2_25046_11338_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E867D7E7@THSONEA01CMS04P.one.grp> Quand : vendredi 14 juin 2013 08:30-09:00 (GMT+01:00) Bruxelles, Copenhague, Madrid, Paris. Emplacement : Meeting Room Number: 391581 Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Liste des num?ros LocalConnect: Australia Australia Toll Free 1800 005 574 Australia Sydney +61 (0) 282 239 767 Austria Vienna +43 (0) 2682 205 6609 Belgium Brussels +32 (0) 2 789 8678 Denmark Copenhagen +45 3271 4340 Finland Helsinki +358 (0) 923 142 830 France Lyon +33 (0) 426 840 285 France Marseille +33 (0) 488 915 385 France Paris +33 (0) 170 994 816 Germany Berlin +49 (0) 3072 616 7342 Germany D?sseldorf +49 (0) 2115 407 3902 Germany Frankfurt +49 (0) 6971 044 5635 Germany Hamburg +49 (0) 4080 902 0684 Germany Munich +49 (0) 8924 443 2893 Germany Stuttgart +49 (0) 7111 856 2130 Greece Greece Toll Free 0080 012 6344 Hong Kong Hong Kong +852 301 145 59 Hungary Budapest +36 (06) 1-889-3286 Ireland Dublin +353 (0) 14 860 780 Israel Israel Toll Free 1809 245 981 Italy Milan +39 0 230 413 017 Italy Rome +39 0 645 217 056 Italy Turin +39 0 112 179 2159 Japan Japan Toll Free 005 311 212 65 Japan Tokyo +81 (0) 357 675 025 Korea, Republic Of Seoul +82 (0) 234 831 224 Luxembourg Luxemburg City +352 2700 41 42 Malaysia Kuala Lumpur +60 (0) 377 124 640 Netherlands Amsterdam +31 (0) 207 948 529 New Zealand Auckland +64 (0) 9 919 2428 Norway Oslo +47 2153 3919 Poland Poland Toll Free 0080 0121 1304 Portugal Portugal Toll Free 800 814 183 Russia Russia Toll Free 81080 02209 4011 Singapore Singapore +65 6622 1068 Spain Barcelona +34 93 492 3235 Spain Madrid +34 91 788 9908 Sweden Stockholm +46 (0) 850 520 145 Switzerland Geneva +41 (0) 225 927 428 United Kingdom Birmingham +44 (0) 121 260 4686 United Kingdom London +44 (0) 207 153 9902 United Kingdom Manchester +44 (0) 161 250 0679 United States USA & Canada Toll Free 1888 249 0050 United States USA Toll +1 954 334 1559 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4362 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 11 20:30:23 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Jun 2013 20:30:23 +0200 Subject: [Fiware-security] [Fiware] TASK FORCE for FI-WARE GEi owners towards the 2nd year project review In-Reply-To: <51B1B86D.8080902@tid.es> References: <51B1B86D.8080902@tid.es> Message-ID: <51B76CBF.3020103@tid.es> Dear all, First of all, let me rather thank all of you who have already completed the requested exercise ... This is a clear sign of your commitment. There are few partners who haven't completed the task force, and the reviewers will notice: * Cloud chapter: * INRIA: Job Scheduler * Technicolor: Cloud Proxy * IoT chapter: * Surrey University: IoT Discovery * Fraunhofer: IoT Gateway Device Management * Security chapter: * Thales: Secure Storage * I2ND chapter: * ALU-I: VNEIC * Technicolor: Cloud Proxy 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 On 07/06/13 12:39, Juanjo Hierro wrote: Dear all, As you know, we are facing the 2nd year official project review next week. During the last preparation meeting we had this Wednesday, we agreed to prepare a revision of the FI-WARE GEi planned availability and usage cockpit that we are currently sharing with the UC projects. This revision would be enriched with information about status, planned terms and conditions in the different environments, base line assets, etc. Please we need to complete this task force by EOB Monday at the latest. It is a pretty simple exercise, so it won't take so much time. I have prepared a shared spreadsheet in Google docs that will help us to work in the new version of the cockpit without creating so much noise in front of the UC projects. You can find it available at the following link: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 You have to complete columns N (already filled, just double-check) and the new columns, namely columns O to X. Columns O-Q deal with info about availability for the FI-PPP partners (which includes availability on the FI-WARE Testbed being used by UC projects to run their experiments). All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Columns R-T deal with info about availability within the FI-WARE Open Innovation Lab (OIL). I guess you all know about the FI-WARE OIL so I don't need to elaborate. Despite the concrete legal terms and conditions are under definition, you can assume that this will be an environment where GEis will be offered (in whatever mode is decided per GEi) for free to third parties (i.e., anyone) who wish to experiment with the technology. The GEis will be provided "as-is" without no warranty and only committing a best-effort support. They will be provided for non-comercial experimental-only use by those third parties. All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Why is there a distinction between availability within the FI-PPP and within OIL ? Mainly because the mode in which you will offer a GEi may vary. Actually, within the FI-PPP you are more constrained and have to comply with the signed Collaboration Agreement. Thus, you may decide to support "Dedicated SaaS instance, binaries" for FI-PPP partners, but may decide to only support "Dedicated SaaS instance" to users of the FI-WARE OIL. Columns U-V deal with info about availability beyond the FI-PPP. Again, all relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Column W has to contain a link to the place in the "materializing the FI-WARE vision" part of the wiki where you described the baseline assets used for your GEi. Adding the proper link is pretty straight forward. Go to the wiki page associated to "materializing the FI-WARE vision" for your chapter and then, click on the "Baseline assets" section of your GEi in the Table of Contents of that wiki page. That action, besides it will place you at the right place in the wiki page, will imply that the URL in your browser will then be precisely pointing to that section. Column X has to contain the link to the corresponding entry in the FI-WARE Catalogue. I guess I don't need to explain how to fill it. WPLs are encouraged to follow-up this process and make sure it gets finalized on time for GEis in their chapters. Don't hesitate to ask if you have any doubt on how to fill the spreadsheet. Cheers, -- 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 ________________________________ 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 mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware ________________________________ 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: From pascal.bisson at thalesgroup.com Wed Jun 19 14:26:50 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 19 Jun 2013 14:26:50 +0200 Subject: [Fiware-security] TR: [Fiware] Deadline for delivery of GEs in June: 28TH of JUNE Message-ID: <24668_1371644814_51C1A38E_24668_11428_1_996d21ea-ec61-492a-a444-2f18aa396739@THSONEA01HUB06P.one.grp> Dear All, I'm forwarding you this email from Miguel to remind you the set (and incompressible) deadline for delivery of GEs V2 in June. So as stressed at our last plenary meeting please take necessary steps to meet this deadline and make sure you GEs deliveries are complete and do comply with the set guidelines once more reminded by Miguel in his email. Be sure that if your GE deliveries is not complete or do not comply with the set guidelines it would be rejected. Something I'm sure you and we would like all to avoid. So counting on you and yes this is something I will also re-address at next audio conf (This Friday at 10am). Best Regards, Pascal De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 18 juin 2013 16:46 ? : fiware at lists.fi-ware.eu Objet : [Fiware] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, A reminder and also to ensure that you are aware if it not communicated in your WP at the time. As agreed in June, 3rd (WPL/WPA weekly call) the final delivery of major release R2 (once concluded R2.3) is the 28th of June. Each WPL/WPA will organize it internally as he thinks it's best. All we need is the deliverables in good shape - complying with the guidelines on : * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 So we expect the Install & admin Manual, the User & Programmers manual, Unit Testing plan & Software itself for all the GEs to be delivered in R2.3. I guess that many ones delivered in R2.2 will be "refreshed" as well since those with backlog items in R2.3 (most) will have to deliver software. There you also have the links to the placeholders where you have to link the manuals. Obviously, the block we will use now for each manual will be the one named "Contributions for June/2013 " 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 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From xavier.aghina at orange.com Fri Jun 21 08:59:09 2013 From: xavier.aghina at orange.com (xavier.aghina at orange.com) Date: Fri, 21 Jun 2013 06:59:09 +0000 Subject: [Fiware-security] Audio conf to morning Message-ID: <28793_1371798065_51C3FA31_28793_27_1_81FF741594681345A3FBB024B01054B906F7656E@PEXCVZYM11.corporate.adroot.infra.ftgroup> Hello, Friday I will be able to participate in the audio conference this morning, following restraint, if you have any comments / questions thank you for making me a return mail. Good meeting you. Xavier. [http://www.francetelecom.com/sirius/logos_mail/orange_logo.gif] Xavier Aghina FT/OLNC/OLPS/ASE/SEC Ing?nieur de Recherche en S?curit? t?l. 01 45 29 81 59 xavier.aghina at orange.com _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1264 bytes Desc: image001.gif URL: From pascal.bisson at thalesgroup.com Mon Jun 24 12:12:49 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 24 Jun 2013 12:12:49 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Message-ID: <30353_1372070512_51C82270_30353_479_2_4df8b7fd-b31e-4b9c-a2b3-e9d67f8114ee@THSONEA01HUB06P.one.grp> Dear Colleagues and GE owners, Regarding June Release (Software+Manuals) I'm forwarding you this email. Please notice what is said by Miguel: "Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there." Despite the fact I did call TID for further clarification my understanding is that you can perform the editing (for those of you already delivered for R2.2 their GEs) on the pubic wiki if you want but provide the links to update of the manuals you performed to on June release link at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 As for fully new GEs for R2.3 (aka Privacy GE/IBM and SSS/TCS) there is no question and content (each of the manuals) has to appear on June release at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 18 juin 2013 15:34 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, As agreed on June, 3 we expect all the delivery for June ready on the 28th of June. "Ready" means all the manuals and the software. As we said, how you organize it internally in each WP is your bussines. I just want the manuals linked from the private wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 I will start reviews from the links I see here, and only the blocks named "Contributions for June/2013 ". Make sure that you link the right pages from there. Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there. I will send an email to the general list but this does not discharge the WPL/WPAs from the obligation of communicating the procedure. In fact, my email will be deliberately shallow and deadline-oriented. I spoke privately to all WPLs in Brussels but one (there is therefore a pending conversation with one of you - I started but we could not finish). The idea is that before the 28th you will perform internal reviews of the deliverables to make sure that all is ok. When you deliver it means that you ensorse it and it has your "seal of approval", meaning the the guidelines are met. In other words, we will reduce the review cycles by delivering more quality. If a given partner refuses to comply with the guidelines you must try to convince them but if they persist in their refusal, you can let us know (a soon as you know it, do not wait for the deadline!!) I also remind you something said on the 3rd of June: We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. 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 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From mcp at tid.es Wed Jun 26 08:51:23 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 26 Jun 2013 08:51:23 +0200 Subject: [Fiware-security] [Fiware] Important messages in yesterday's coordination call In-Reply-To: <51C9807E.3060507@tid.es> References: <51C9807E.3060507@tid.es> Message-ID: <51CA8F6B.9080604@tid.es> Dear all, I suspect that there are many people out of the general list (fiware at lists.fi-ware.eu). All people should be there. Those who did not receive the message at the bottom contact me privately and I will add you to this list. There is a presentation with general background on the use of our resources in FI-WARE here: https://forge.fi-ware.eu/docman/view.php/27/1982/FI-WARE-Forge+and+tools.pptx The presentation is on the private project on the forge. I remind you that all of you should have access to the project "FI-WARE Private" and that this is managed in each WP by the respective WPL/WPA. As them to add you if you do not have access to this file. Best regards, Miguel El 25/06/2013 13:35, Miguel Carrillo escribi?: Dear all, I would like to circulate the minutes of meeting of yesterday's coordination call, there are too important messages to miss them. I am sure the WPL/WPA will circulate them but I want to ensure that it gets to all of you in any case. The link is here: * https://docs.google.com/document/d/1NGqZPL0uNvsmpnrJI5x-MxdN6YJi0hBePs6euimoUrs Incidentally, we keep the list of links to the minutes of the WPL/WPA calls on the private wiki. There is a direct link on the private wiki home page that takes you there: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Minutes_of_WPL/WPA_Meetings If someone cannot access the private wiki, I remind you that the WPL/WPA are the ones in charge of granting you access to this repository. 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 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware -- ---------------------------------------------------------------------- _/ _/_/ 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 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: From daniel.gidoin at thalesgroup.com Wed Jun 26 11:58:05 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Wed, 26 Jun 2013 11:58:05 +0200 Subject: [Fiware-security] [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation In-Reply-To: References: Message-ID: <1416_1372240692_51CABB33_1416_3774_1_a132f1c4-7bf1-4eaf-9e25-11c57d264276@THSONEA01HUB04P.one.grp> Dear All, I would ask you to confirm that your manuals had been updated and that I can already generate the deliverables : * FI-WARE Deliverable "D3-8.3 FIWARE Installation and Administration Guide Release 2" * FI-WARE Deliverable "D3-8.4 FIWARE User and Programmers Guide Release 2" * FI-WARE Deliverable "D3-8.5 FIWARE Unit Testing Plan and Report Edition Release 2" Thanks a lot Best regards Daniel De : BISSON Pascal Envoy? : lundi 24 juin 2013 12:13 ? : GIDOIN Daniel; TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Wolfgang.Steigerwald at telekom.de; Seidl, Robert (NSN - DE/Munich); Franz-Stefan Preiss; Gulden Yilmaz Cc : BISSON Pascal; GIDOIN Daniel; fiware-security at lists.fi-ware.eu Objet : TR: [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Importance : Haute Dear Colleagues and GE owners, Regarding June Release (Software+Manuals) I'm forwarding you this email. Please notice what is said by Miguel: "Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there." Despite the fact I did call TID for further clarification my understanding is that you can perform the editing (for those of you already delivered for R2.2 their GEs) on the pubic wiki if you want but provide the links to update of the manuals you performed to on June release link at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 As for fully new GEs for R2.3 (aka Privacy GE/IBM and SSS/TCS) there is no question and content (each of the manuals) has to appear on June release at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 18 juin 2013 15:34 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, As agreed on June, 3 we expect all the delivery for June ready on the 28th of June. "Ready" means all the manuals and the software. As we said, how you organize it internally in each WP is your bussines. I just want the manuals linked from the private wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 I will start reviews from the links I see here, and only the blocks named "Contributions for June/2013 ". Make sure that you link the right pages from there. Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there. I will send an email to the general list but this does not discharge the WPL/WPAs from the obligation of communicating the procedure. In fact, my email will be deliberately shallow and deadline-oriented. I spoke privately to all WPLs in Brussels but one (there is therefore a pending conversation with one of you - I started but we could not finish). The idea is that before the 28th you will perform internal reviews of the deliverables to make sure that all is ok. When you deliver it means that you ensorse it and it has your "seal of approval", meaning the the guidelines are met. In other words, we will reduce the review cycles by delivering more quality. If a given partner refuses to comply with the guidelines you must try to convince them but if they persist in their refusal, you can let us know (a soon as you know it, do not wait for the deadline!!) I also remind you something said on the 3rd of June: We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. 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 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: From robert.seidl at nsn.com Wed Jun 26 12:02:29 2013 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Wed, 26 Jun 2013 10:02:29 +0000 Subject: [Fiware-security] [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation In-Reply-To: <1416_1372240692_51CABB33_1416_3774_1_a132f1c4-7bf1-4eaf-9e25-11c57d264276@THSONEA01HUB04P.one.grp> References: <1416_1372240692_51CABB33_1416_3774_1_a132f1c4-7bf1-4eaf-9e25-11c57d264276@THSONEA01HUB04P.one.grp> Message-ID: Hi Daniel, for NSN they will be ready on Friday, as it was requested. But not before Friday. Greetings Robert From: ext GIDOIN Daniel [mailto:daniel.gidoin at thalesgroup.com] Sent: Wednesday, June 26, 2013 11:58 AM To: TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Wolfgang.Steigerwald at telekom.de; Seidl, Robert (NSN - DE/Munich); Franz-Stefan Preiss; Gulden Yilmaz Cc: fiware-security at lists.fi-ware.eu; BISSON Pascal; MUSARAJ Kreshnik; CAO Phong; GASPARD Lucie Subject: RE: [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation Dear All, I would ask you to confirm that your manuals had been updated and that I can already generate the deliverables : * FI-WARE Deliverable "D3-8.3 FIWARE Installation and Administration Guide Release 2" * FI-WARE Deliverable "D3-8.4 FIWARE User and Programmers Guide Release 2" * FI-WARE Deliverable "D3-8.5 FIWARE Unit Testing Plan and Report Edition Release 2" Thanks a lot Best regards Daniel De : BISSON Pascal Envoy? : lundi 24 juin 2013 12:13 ? : GIDOIN Daniel; TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Wolfgang.Steigerwald at telekom.de; Seidl, Robert (NSN - DE/Munich); Franz-Stefan Preiss; Gulden Yilmaz Cc : BISSON Pascal; GIDOIN Daniel; fiware-security at lists.fi-ware.eu Objet : TR: [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Importance : Haute Dear Colleagues and GE owners, Regarding June Release (Software+Manuals) I'm forwarding you this email. Please notice what is said by Miguel: "Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there." Despite the fact I did call TID for further clarification my understanding is that you can perform the editing (for those of you already delivered for R2.2 their GEs) on the pubic wiki if you want but provide the links to update of the manuals you performed to on June release link at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 As for fully new GEs for R2.3 (aka Privacy GE/IBM and SSS/TCS) there is no question and content (each of the manuals) has to appear on June release at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 18 juin 2013 15:34 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, As agreed on June, 3 we expect all the delivery for June ready on the 28th of June. "Ready" means all the manuals and the software. As we said, how you organize it internally in each WP is your bussines. I just want the manuals linked from the private wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 I will start reviews from the links I see here, and only the blocks named "Contributions for June/2013 ". Make sure that you link the right pages from there. Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there. I will send an email to the general list but this does not discharge the WPL/WPAs from the obligation of communicating the procedure. In fact, my email will be deliberately shallow and deadline-oriented. I spoke privately to all WPLs in Brussels but one (there is therefore a pending conversation with one of you - I started but we could not finish). The idea is that before the 28th you will perform internal reviews of the deliverables to make sure that all is ok. When you deliver it means that you ensorse it and it has your "seal of approval", meaning the the guidelines are met. In other words, we will reduce the review cycles by delivering more quality. If a given partner refuses to comply with the guidelines you must try to convince them but if they persist in their refusal, you can let us know (a soon as you know it, do not wait for the deadline!!) I also remind you something said on the 3rd of June: We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. 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 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: From susana.gzarzosa at atosresearch.eu Wed Jun 26 12:05:05 2013 From: susana.gzarzosa at atosresearch.eu (Susana Gonzalez Zarzosa) Date: Wed, 26 Jun 2013 12:05:05 +0200 Subject: [Fiware-security] [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation In-Reply-To: References: <1416_1372240692_51CABB33_1416_3774_1_a132f1c4-7bf1-4eaf-9e25-11c57d264276@THSONEA01HUB04P.one.grp> Message-ID: Hi Daniel, We have not updated all the deliverables yet. They will be ready on Friday morning too. Best regards, Susana From: Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Sent: mi?rcoles, 26 de junio de 2013 12:02 To: ext GIDOIN Daniel; TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Wolfgang.Steigerwald at telekom.de; Franz-Stefan Preiss; Gulden Yilmaz Cc: fiware-security at lists.fi-ware.eu; BISSON Pascal; MUSARAJ Kreshnik; CAO Phong; GASPARD Lucie Subject: RE: [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation Hi Daniel, for NSN they will be ready on Friday, as it was requested. But not before Friday. Greetings Robert From: ext GIDOIN Daniel [mailto:daniel.gidoin at thalesgroup.com] Sent: Wednesday, June 26, 2013 11:58 AM To: TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Wolfgang.Steigerwald at telekom.de; Seidl, Robert (NSN - DE/Munich); Franz-Stefan Preiss; Gulden Yilmaz Cc: fiware-security at lists.fi-ware.eu; BISSON Pascal; MUSARAJ Kreshnik; CAO Phong; GASPARD Lucie Subject: RE: [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation Dear All, I would ask you to confirm that your manuals had been updated and that I can already generate the deliverables : * FI-WARE Deliverable "D3-8.3 FIWARE Installation and Administration Guide Release 2" * FI-WARE Deliverable "D3-8.4 FIWARE User and Programmers Guide Release 2" * FI-WARE Deliverable "D3-8.5 FIWARE Unit Testing Plan and Report Edition Release 2" Thanks a lot Best regards Daniel De : BISSON Pascal Envoy? : lundi 24 juin 2013 12:13 ? : GIDOIN Daniel; TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Wolfgang.Steigerwald at telekom.de; Seidl, Robert (NSN - DE/Munich); Franz-Stefan Preiss; Gulden Yilmaz Cc : BISSON Pascal; GIDOIN Daniel; fiware-security at lists.fi-ware.eu Objet : TR: [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Importance : Haute Dear Colleagues and GE owners, Regarding June Release (Software+Manuals) I'm forwarding you this email. Please notice what is said by Miguel: "Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there." Despite the fact I did call TID for further clarification my understanding is that you can perform the editing (for those of you already delivered for R2.2 their GEs) on the pubic wiki if you want but provide the links to update of the manuals you performed to on June release link at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 As for fully new GEs for R2.3 (aka Privacy GE/IBM and SSS/TCS) there is no question and content (each of the manuals) has to appear on June release at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 18 juin 2013 15:34 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, As agreed on June, 3 we expect all the delivery for June ready on the 28th of June. "Ready" means all the manuals and the software. As we said, how you organize it internally in each WP is your bussines. I just want the manuals linked from the private wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 I will start reviews from the links I see here, and only the blocks named "Contributions for June/2013 ". Make sure that you link the right pages from there. Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there. I will send an email to the general list but this does not discharge the WPL/WPAs from the obligation of communicating the procedure. In fact, my email will be deliberately shallow and deadline-oriented. I spoke privately to all WPLs in Brussels but one (there is therefore a pending conversation with one of you - I started but we could not finish). The idea is that before the 28th you will perform internal reviews of the deliverables to make sure that all is ok. When you deliver it means that you ensorse it and it has your "seal of approval", meaning the the guidelines are met. In other words, we will reduce the review cycles by delivering more quality. If a given partner refuses to comply with the guidelines you must try to convince them but if they persist in their refusal, you can let us know (a soon as you know it, do not wait for the deadline!!) I also remind you something said on the 3rd of June: We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. 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 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 ------------------------------------------------------------------ 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: From Wolfgang.Steigerwald at telekom.de Wed Jun 26 15:00:26 2013 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Wed, 26 Jun 2013 15:00:26 +0200 Subject: [Fiware-security] [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation In-Reply-To: <1416_1372240692_51CABB33_1416_3774_1_a132f1c4-7bf1-4eaf-9e25-11c57d264276@THSONEA01HUB04P.one.grp> References: <1416_1372240692_51CABB33_1416_3774_1_a132f1c4-7bf1-4eaf-9e25-11c57d264276@THSONEA01HUB04P.one.grp> Message-ID: Hello Daniel, I had a look to the examples and to what is there from our side. I'm a bit puzzled what I should provide especially to the "Installation and Administration Guide". What is on the example page is not applicable for us because we don't provide code, but we provide an administration UI which I basically described how to configure a new service. So please have a look on our pages and say what is wrong and what we should provide. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Identity_Management_-_GCP_Installation_and_Administration_Guide https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Identity_Management_-_GCP_User_and_Programmer_Guide https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Identity_Management_-_GCP_Unit_Testing_Plan Best regards Wolfgang Von: GIDOIN Daniel [mailto:daniel.gidoin at thalesgroup.com] Gesendet: Mittwoch, 26. Juni 2013 11:58 An: TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Steigerwald, Wolfgang; Seidl, Robert (NSN - DE/Munich); Franz-Stefan Preiss; Gulden Yilmaz Cc: fiware-security at lists.fi-ware.eu; BISSON Pascal; MUSARAJ Kreshnik; CAO Phong; GASPARD Lucie Betreff: RE: [Fiware-wpl]delivery of GEs in June - VERY URGENT - deliverable generation Dear All, I would ask you to confirm that your manuals had been updated and that I can already generate the deliverables : * FI-WARE Deliverable "D3-8.3 FIWARE Installation and Administration Guide Release 2" * FI-WARE Deliverable "D3-8.4 FIWARE User and Programmers Guide Release 2" * FI-WARE Deliverable "D3-8.5 FIWARE Unit Testing Plan and Report Edition Release 2" Thanks a lot Best regards Daniel De : BISSON Pascal Envoy? : lundi 24 juin 2013 12:13 ? : GIDOIN Daniel; TRABELSI, Slim; DI CERBO, Francesco; Susana Gonzalez Zarzosa; Alexandre Boeglin; Fabrice SABATIER; EGAN Richard; Wolfgang.Steigerwald at telekom.de; Seidl, Robert (NSN - DE/Munich); Franz-Stefan Preiss; Gulden Yilmaz Cc : BISSON Pascal; GIDOIN Daniel; fiware-security at lists.fi-ware.eu Objet : TR: [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Importance : Haute Dear Colleagues and GE owners, Regarding June Release (Software+Manuals) I'm forwarding you this email. Please notice what is said by Miguel: "Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there." Despite the fact I did call TID for further clarification my understanding is that you can perform the editing (for those of you already delivered for R2.2 their GEs) on the pubic wiki if you want but provide the links to update of the manuals you performed to on June release link at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 As for fully new GEs for R2.3 (aka Privacy GE/IBM and SSS/TCS) there is no question and content (each of the manuals) has to appear on June release at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 18 juin 2013 15:34 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, As agreed on June, 3 we expect all the delivery for June ready on the 28th of June. "Ready" means all the manuals and the software. As we said, how you organize it internally in each WP is your bussines. I just want the manuals linked from the private wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 I will start reviews from the links I see here, and only the blocks named "Contributions for June/2013 ". Make sure that you link the right pages from there. Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there. I will send an email to the general list but this does not discharge the WPL/WPAs from the obligation of communicating the procedure. In fact, my email will be deliberately shallow and deadline-oriented. I spoke privately to all WPLs in Brussels but one (there is therefore a pending conversation with one of you - I started but we could not finish). The idea is that before the 28th you will perform internal reviews of the deliverables to make sure that all is ok. When you deliver it means that you ensorse it and it has your "seal of approval", meaning the the guidelines are met. In other words, we will reduce the review cycles by delivering more quality. If a given partner refuses to comply with the guidelines you must try to convince them but if they persist in their refusal, you can let us know (a soon as you know it, do not wait for the deadline!!) I also remind you something said on the 3rd of June: We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. 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 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: From daniel.gidoin at thalesgroup.com Wed Jun 26 17:18:44 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Wed, 26 Jun 2013 17:18:44 +0200 Subject: [Fiware-security] FI-WARE: weekly WP8 Audio conf on Friday - exceptional schedule change (9:30-10:30) Message-ID: <4724_1372259946_51CB066A_4724_1846_4_10097d06-80ab-414b-af69-5d4a1adaf6fc@THSONEA01HUB01P.one.grp> Dear All, Thanks a lot to take into account an exceptional schedule change for our weekly WP8 audio conf this Friday: 9:30-10:30 am Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: