Dear WPL Could you please provide some feedback relating the Standards management in each domain and could you complete with some inputs the xls document, created by NEC to begin a gap analysis for standardization Up to now, we have just received some inputs from I2nd domain and we need additional inputs for each domain by EOB today, as our coordinator ask us for the review meeting on the 22nd Thanks for your collaboration Juan Juan Bareño Atos Research and Innovation T +34 912148859 juan.bareno at atos.net <mailto:blanca.jordan at atosresearch.eu> Albarracín 25 28037 Madrid Spain www.atos.net <http://www.atos.net/> www.atosresearch.eu <http://www.atosresearch.eu/> From: Juan Bareño Guerenabarrena Sent: martes, 08 de noviembre de 2011 11:48 To: 'fiware-wpl at lists.fi-ware.eu' Cc: Nuria De-Lama Sanchez; 'Ernoe Kovacs'; Lindsay Frost; Carmen Perea Escribano; Andrea Rossi Subject: Standards management Importance: High Dear Colleagues We have two topics regarding standardization: (1) Assets >From the standardization aspect, we would like to add 2 columns to the excel sheet about IPRs that we created previously in https://forge.fi-ware.eu/docman/view.php/16/256/IPR+control.xlsx but finally, this IPR´s table was not used and IPR´s were included as an additional chapter in the General Document in the wi-ki and all the WP have been working on this chapter as well as in the Product Vision, part of this table also as you can see below in the contents proposed: Component Description Innovation, added value Target Market Exploited License (1)Most Relevant SDO (2) FI WARE partner/Contact Name of the component,asset that could generate benefits for the market Brief description Please explain briefly what innovation is given by the component. What problems will the component solve? extra features the component provides Identify the target market Separately, partly alone, bundle, etc Regarding Standardization we will need to obtain the following feedback: 1. Most Relevant SDO (i.e. If the component would benefit from standardization, where should it be done? If the component depends on existing standards, where are those standards maintained/updated? If more than one SDO is important, list by approximate order of relevance.) 2. FI-Ware Partner/Contact which is active in that SDO (i.e. which organization and contact person could monitor dependencies and perhaps be involved in any agreed pro-active standardization? If more than one SDO is important, try to include one contact for each) So in order to avoid duplicate efforts, as in the case of IPRs (excelsheet + wi-ki), I propose to create an additional chapter (4) in the wiki within the General Document to deal with this issue. Is it ok with you? or you prefer to deal it separately from the General Document in a excel sheet?. In case of working in the wi- ki who could create this additional chapter? [hide <javascript:toggleToc()> ] * 1 Brief Description <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Drools#Brief_Description> * 2 Technologies used <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Drools#Technologies_used> * 2.1 Known software requirements <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Drools#Known_software_requirements> * 3 IPR <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Drools#IPR> * 4 Standardization * 5 Publically Available Documentation <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Drools#Publically_Available_Documentation> We are in the M7 and we have a deliverable for the M9, so it is urgent to start to gather all of this information about the assets which could leverage on existing standards or on new ones. So your opinion about how to deal this issue in the more agile way will be very helpful (2) Standardisation Attached is an xls document, created by NEC to begin a gap analysis for standardization * 1st worksheet "Introduction" showing the planned usage of the document * 2nd worksheet "SDO" with a list of relevant Standardisation Organisations and including "promised" contribution areas from you (extracted from the final Fi-Ware Agreement). Your actions: Would you please be so kind as to edit the document worksheet "SDO" to a) show any additional SDOs you consider relevant to FI-ware b) show (or change) information about where your company plans to contribute (Note that not all partners are yet included. Please add an extra row where ever needed.) c) show email addresses of contact persons in your organization who are delegates to the organizations (NO DELEGATE WILL BE CONTACTED AT THIS TIME! The FI-Ware Plenary will later define/agree how to co-ordinate work and disseminate information to interested delegates) d) please mark all cells you change using yellow highlighting, because EXCEL has no change-tracking Any additional improvements are most welcome. Would you please reply to Lindsay.Frost at neclab.eu (administrator for this part of WP11). He will combine all answers into a draft summary document for review (and prioritization/trimming !) Kind regards Ernö & Lindsay & Juan ------------------------------------------------------------------ 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: <https://lists.fiware.org/private/fiware-wpl/attachments/20111116/5cefb979/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20111116/5cefb979/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20111116/5cefb979/attachment-0001.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware_Standardization_List_20110926_CONFIDENTIAL.xlsx Type: application/octet-stream Size: 23034 bytes Desc: FI-Ware_Standardization_List_20110926_CONFIDENTIAL.xlsx URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20111116/5cefb979/attachment.obj>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy