[Fiware-security] TR: IPR Management-missing info to be completed ASAP (WPL responsibilities)

BISSON Pascal pascal.bisson at thalesgroup.com
Tue May 22 16:56:56 CEST 2012


Dear Task leads,

Please check this email and address with support of GE owners also assets owners attached to your task to close any pending action on this.

Counting on you to have this demand be addressed according to the deadline set by Nuria and WP12 lead.

BR
Pascal


De : fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] De la part de Nuria De-Lama Sanchez
Envoyé : mardi 22 mai 2012 14:51
À : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Cc : fiware-pcc at lists.fi-ware.eu
Objet : [Fiware-pcc] IPR Management-missing info to be completed ASAP (WPL responsibilities)
Importance : Haute

Dear WP leaders,

As you well know, my colleagues in WP11 are working in the IPR management activity. They have been asking each of you about the fulfillment of the tables created for the purpose of specifying the type of license of each asset. However, and despite the time devoted to that and the subsequent reminders not everything is ready for the review, and furthermore, not everything is ready for the deliverable that should be submitted next week.

This is now an urgent issue. I suppose that you are also conscious of the questions made by use case projects in that respect (I am sure that this issue has been raised this week in Zurich). Therefore, let me point out THREE VERY IMPORTANT points that you need either to complete or to take into account.


·         Each WPL/WPA has to complete the tables of his chapter. Some of them have red text or missing information --> DEADLINE for this is next Friday (take advantage of the meetings in Zurich to clarify any doubt you have)

·         As you can see in the tables, the license type is associated to each asset. Since every GE is composed of one or several assets what we have to ensure is that all the license types are compatible for the GE implementation.

o    Therefore, make sure that each asset has a type license

o    Fill in the cell of license compatibility at the level of GE (not asset!) --> of course, in the end the statement should make visible the fact that all the assets that are part of the GE implementation can work together without major issues. If not, come back to us ASAP

o    If one or several assets are open source components that you take from Internet, please, give the source in the cell devoted to ownership --> avoid saying "unknown" or leaving the space without specifying anything

o    If you want an example of a GE that has been completed as we need it check the BigData GE.

·         Finally, we have realized that many assets have the "label" CLOSED (license type) --> this should be replaced by FRAND

As far as we understand all SW should be realized at least under FRAND conditions (this should be the most restricted term).

I hope this is clear for everyone. If not, come to my colleagues Carmen and Juan (keeping me in CC for the sake of coordination). Thanks in advance for your work!


Nuria de Lama

Research & Innovation
Representative to the European Commission

T +34 91214 9321
F +34 91754 3252
nuria.delama at atosresearch.eu<mailto:nuria.delama at atosresearch.eu>
Albarracín 25
28037 Madrid
Spain
www.atosresearch.eu<http://www.atosresearch.eu>
es.atos.net
 [cid:image002.gif at 01CD3826.FDF02960]


________________________________


------------------------------------------------------------------
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/old-fiware-security/attachments/20120522/705c2a55/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/old-fiware-security/attachments/20120522/705c2a55/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/old-fiware-security/attachments/20120522/705c2a55/attachment-0001.gif>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120522/705c2a55/attachment.txt>


More information about the Old-Fiware-security mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy