[Fiware-security] FI-WARE - Security

[Antonio Garcia Vazquez]

Pascal, 

 

My report on Sprint 1 & 2 Tasks:

 

1)      Sprint 1: FIWARE.Work-Items.Security.Context-based security and compliance.USDL-SEC Definition

The main objectives of this work-Item were:

-          Define the roadmap to develop the USDL-SEC language

-          Define the starting point and evolution of USDL-SEC taking as reference the work already done by both The USDL W3C Incubator group and FI-WARE WP3.

A power point with this results has been uploaded as an attachment in the tracker.

 

2)      Sprint 2: FIWARE.Work-Items.Security.Context-based security and compliance.USDL-SEC Features

Under this tracker we are going to work on the analysis and description of the different features offered by the different GE in order to work towards the identification of the language vocabulary

 

Regarding to this also tell you that I can't change the state of any tracker from "open" to "under execution" or "closed"; so Sprint 1 and sprint 2 trackers are both listed as open instead of close (Sprint 1) and under execution (Sprint 2).

 

Do you know if could be a rights problem?

Could you change their states for me?

 

Thanks and Best Regards.

 

************************************

*      Antonio García-Vázquez      *
*        (+34) 91 214 9384         *
*  antonio.garcia at atosresearch.eu  *
************************************ 

 

From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal
Sent: lunes, 05 de diciembre de 2011 10:57
To: fiware-security at lists.fi-ware.eu
Subject: [Fiware-security] FI-WARE - Security

 

Dear All,

 

This just to confirm our next audio conf of Friday 9/12  (10am-12am).

 

At this audio conf we will address the following items:

 

Report on Sprint 1 outcomes per task and per GE (please task leaders prepare and distribute prior to our audio conf a short textual report on Sprint1. To be reviewed at our audio and them uploaded on the WP8 internal repository),

a.       Also update the status of work items you had for sprint 1 accordingly (closed vs still under execution)

2.       2.       Report per task and per GE work items and user stories planned to be addressing during the Second sprint (December). Once more I need here from each of the task leads a short textual description of what 

a.       Bear in mind Sprint 2 items should somehow also reflect things we are now engaged in (i.e. Architecture spec., Open Calls, ...)

3.       Report on progress regarding tickets issued and by the UC and which have been assigned. 

4.       M9 Deliverable - Architecture Specifications (will discuss our approach to it)

5.       Open Calls

a.       n lang=EN-US>Need here a short but sound textual description for each of the items which have been proposed (in order to have them reviewed and further discussed)

b.      Count here on each of the Task leads/GE Owners topics proposers to come  once more with such a textual description at our meeting (...)

6.       WP8 Meeting (set the date of next Physical meeting)

7.       Other topics (M12 deliverables, ...)

 

 

Counting on you all to be present at our audio conf on Friday being said we have important topics to be discussed there.

 

Don't forget to also perform preparatory actions requested to make our audio conf effective/efficient.

 

Thanks in advance and talk with you there.

 

Best Regards,

 

Pascal

------------------------------------------------------------------
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/20111209/65a8afd9/attachment.html>