[Fiware-apps] FI-WARE-DoW-WP3-Amendment 4 - v1.docx

[Javier Soriano (FI-UPM)]

Dear Axel,

I've decided to share ASAP a new version of the document with my own
inputs, comments and explanations, because we are on a very tight schedule
(but necessary, because there are many "old" points whose approval is still
pending, and "new" ones that also imply important risks if they are not
solved ASAP).

Some remarks:


>  I have done the changes that were discussed last year together with Uwe
> and I have integrated the content of iMinds and UPM.****
>
> **
>

I'm fine with the changes that have to do with UPM. I think that they
perfectly define our new role in the project.


>  **
>
> For some partners we have to find a good explanation for their work in WP3
> (ENG, Thales), otherwise we might run into trouble within the next review.
> ****
>
> So I would like to ask ENG and Thales to take care about this topic and
> provide an updated version until tomorrow (05.03.2012 at 16:00).****
>
> **
>

Still pending. ENG and Thales, please provide ASAP a paragraph explaining
your role and you workplan in WP3 and T3.1 in particular.

Currently, there is NO role definition for ENG, and Thales contribution is
described as follows:

    "THALES: Data, protocol, and process mediation for highly dynamic cases
like service discovery at execution time."

Are there (in the tracker and in the wiki) any EPICS, features, etc.
related to this description. if it is not the case, there is an urgent need
for changing this.


> **
>
> All the colleagues that are not in the role of a Task-Leader, please check
> and update the information for your task and contribution and send an
> update to your task lead.****
>
> **
>

Still pending. Please check carefully the new text we need to agree on.


> **
>
> I have marked the leader of each of the tasks in red and I what to ask the
> Task-Leads to ensure that the text valid, please have a look at:****
>
> **·         **The explanations****
>
> **·         **The PM’s ****
>
> **·         **…****
>
> Please help your task lead to deliver the update in time.****
>
> **
>

Please, provide your input asap, if needed. Otherwise, we will consider
that you are fine with the text, it needs no rewording and you agree on
this new version of the DoW.


> **
>
> Beside this I plan to delete the task 3.4 if I did not hear any complains.
> ****
>
> **
>

I fully support you Axel. Currently, there are no efforts assigned to this
task, which has already been the subject of an open call (at least in
part). It is very risky to maintain it in the DoW with no activity in the
tracker since the very beginning of the project.


>  I will consolidate the Task-Lead contributions and create a new version
> by end of tomorrow.****
>
> Afterwards I will send out this new version to all of you for the final
> review. Please take into account that we have to deliver the document on
> Thursday.****
>
> **
>
Axel, please check my comments and changes and, tell us whether we can
consider it (or a new version sent by you) as the working version or the
DoW.

BR,
Javier


> **
>
> Best regards,****
>
> Axel ****
>
> ** **
>
> ** **
>
> _______________________________________________
> Fiware-apps mailing list
> Fiware-apps at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware-apps
>
>


--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130304/d05f1322/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FI-WARE-DoW-WP3-Amendment 4 - v1_UPM input.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 258114 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20130304/d05f1322/attachment.docx>