[Fiware-data] Final Data/Context Agenda

[CARLOS RALLI UCENDO]

Dear WP Colleagues,

As you know you can see in the overall Agenda of Madrid meeting (including assigned meeting rooms until Wednesday) at:
https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdFVQMzYzOFJvNzFncTR3YjdOVVNTVnc#gid=0

Regarding Data/Context Management, find hereby the final version:

**** Data/Context meetings:

----> Slot 0: BigDATA - CEP - P/S Integration 2h.
We scheduled this one for Monday 10:00-12:30 but We have moved it to: Tuesday morning (10:00 - 12:30) so that TI may participate now.

---> Slot 1a/1b: Data/Context Assets Status (5h). Max Number Attendants: 14.
(2h on Monday 10:00-12:30 +  3h on Tuesday 14:00-17:30)
Each Baseline asset should provide a maximum of 8 slides to make a 20' presentation covering:
- Key development milestones achieved within Sprints 1, 2 & 3.
- Issues/deviations occurred during this period and countermeasure actions.
- Status/Roadmap/Considerations regarding alignment with the chapter context: REST API/interfaces, NGSI paradigm.
Confirmed Slots: CEP-Tali-IBM, PubSub-Fano-Orange, Query-Broker;Metadata-preprocessing;MMAnalysis-Peter-Siemens, BigData-Telefonica

---> Slot 2: Architectural Roundtable. Max Number Attendants: 14 (3h). Max Number Attendants: 14
(Now on Monday 14:00 - 17:30)
Middleware, REST APIs and "How we could develop dummy use-cases" (1h30 +10 min wrap up).
50 minutes at the end should be enough to review deliverables progress (mainly focused on D2.3).

---> Slot 3: UC projects Backlog review (2h). Max Number Attendants: 14
(Now on Wed 14-15h + Thu 11:30-12:30)
10 min discussions per baseline asset regarding assigned UC project tickets.
Instead of going one by one, we expect here to collect the overall status, kind of requirements and issues.
The feedback provided should be relevant to the cooperation tasks with UC projects (Architecture Board, dissemination, exploitation, etc.)

---> Slot 4: Action Points / Next Steps (Roundtable. 3h'). Max Number Attendants: 14
(Now 2h on Thu 14:00-17:30)

We should be able to cover here:
- Needs for the FI-WARE testbed (45')
- Sprint 3 retrospective and Planning of Sprint 4 (45')
- Standardization Plan (30')
- How the chapter does/will contribute to dissemination & exploitation (30')
  How the chapter does/will increase FIWARE impact with technical presentations, workshops, actions, etc.

**** Meetings with other WPs (Check dates in the googledoc above linked).
-> Apps: Interface with apps, marketplace, make sure on a uniform way to invoke/treat data by apps
-> IoT: Gathering massive data from sensors/devices, issue of their solutions overlapping CEP, PubSub, Data ...
-> Tools: We will be told what is needed from each baseline asset to build a framework of tools for "FI-WARE developers" (plugin of Eclipse to build a set of tools up).
Providing there is enough time, we might kick-off with a specific example.
-> Cloud: Monitoring, Scaling. (TBC)


Best regards,

--
------------------------------------------------------------------------------------------------------------------------
Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>)
Cell: +34696923588
Twitter: @carlosralli
Telefónica I+D SAU
Madrid, Spain
------------------------------------------------------------------------------------------------------------------------
Follow FI-WARE project (Future Internet Services Core Platform):
Website:  http://www.fi-ware.eu
Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
Twitter: @fiware
LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
------------------------------------------------------------------------------------------------------------------------


________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120122/5a1cedac/attachment.html>