[Fiware-data] Minutes of our weekly follow-up confcall

[Moltchanov Boris]

Dear All,

Regarding action points from Juanjo mail below:


-          I have done what was planned and confirmed (btw didn't see any changes to pub/sun GE by juanjo yet). I've even reviewed the Introduction section, even if this was not planned to be performed by TI in the last call :).


-          The location GE integration is not yet initiated by Thales to be supported by TI, however we have had some comments from Orange Labs there.


-          I'm afraid the context management platform query search can not be integrated with that query search GE included into this version of the document, it is also pointed out in the last reviewed be me version of the document. I believe two query search assets proposed by different partners are different and serving for different purposes (multimedia or generic data processing and context information), impossible to merge.

FYI, I will be not available for this Friday call, therefore if we plan to discuss open issues involving TI we have to do it before Friday excluding Thursday morning as well.

BR,
Boris

From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Amon, Peter
Sent: Tuesday, July 12, 2011 2:50 PM
To: Juanjo Hierro; fiware-data at lists.fi-ware.eu
Subject: Re: [Fiware-data] Minutes of our weekly follow-up confcall

Dear Juanjo, all,

as requested in the last confcall, please find on the repository under "peer-review" a few paragraphs on "Data Gathering" (Section 3.4.2). The link is:
https://forge.fi-ware.eu/docman/view.php/9/257/FI-WARE+High-Level+Description+-+Data-Context+chapter+-+DataGatheringGE_3.4.2_v01.doc

A few more review comments:
- I found some typos in Section 3.4.1 on Security (see document).
- In Figure 1 ("High-Level view of GEs in the Data/Context Management chapter"), some names do not match the GE names in the text, e.g., "Query/Search Engine" -> "Query Access" (similarly: "BigData Analysis" -> "Big Data Processing, etc.)
- "Generic Enabler" should always be written upper case (sometimes "generic enabler").
- "Pre-processing" (Section 3.2.4) <-> "Preprocessing" (Section 3.2.5): Should be written the same way (e.g., "Pre-processing")

Kind regards
 Peter



________________________________
From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro
Sent: Freitag, 8. Juli 2011 14:08
To: fiware-data at lists.fi-ware.eu
Subject: [Fiware-data] Minutes of our weekly follow-up confcall
Folks,

  Here you are the minutes of our meeting this morning.    Please check overall for the actions (some of them assigned to people that didn't attend so they should confirm !!)

  Cheers,

-- Juanjo


The main topics of the agenda were:

  1. Finishing the FI-WARE High-level Description deliverable

  2. Rolling-out activities with the blogs

  3. Briefing on FI-PPP AB meeting and next steps


Finishing the FI-WARE High-level Description deliverable

  Here we address two points

Peer review of the IoT Service Enablement chapter:

  First of all, we have to cope with the revision of another chapter.  Based on the assignment made after delivering the integrated draft, we have to review the IoT Service Enablement chapter.

  Juanjo already reviewed it in great detail and provided a relevant number of comments that were already integrated.    Therefore, it makes sense that other make the next peer reviews.

  Actions agreed:

 *   Guy will perform a first peer review and will generate .doc with changes under control by EOB Sunday
 *   We need a candidate for taking the token and carrying out a revision (on Monday): (Boris 1st candidate, Fano 2nd, Peter 3rd so we will ask them by this email)
 *   Juanjo to inform about plan to IoT WPL/WPA
Finishing some pieces that were not that complete in the delivered draft:

  We reviewed a number of points on which we have still to work a bit:

 *   Introduction

    *   First take delivered by Federico
    *   Federico to send a version of it with adapted styles today
    *   Revision: Chema will take the token to review this and will deliver comments before monday 11:00am
    *   Juanjo to take the final token afterwards

 *   Section on "Points still under discussion".
We have to elaborate on a number of items, generating 3-4 paragraphs per item as we already have done for the Security aspects.

Deadline for having them ready should be July 14th.

Following is the list of items identfied together with who would be assigned to deal with them:

    *   Data gathering GE: we have kind of a gap in this point ... we need to elaborate on it a bit and essentially bring the message that we are working on it (Siemens)
    *   BigData Analysis vs Complex Event Processing ... what are the scenarios where each is more suitable (IBM)
    *   Support to multiple Query Languages and Query Language Families ... try to elaborate on this part and the implications it may have (TI, Boris)

 *   GEs dealing with semantic infrastructure:

    *   ATOS reported that they feel like the last contributions had not been integrated.
    *   Guy and Juanjo reported that they thought they took the last ones.  If something was missing, it was not on purpose ...
    *   ATOS to review this ASAP and send clarifications to the mailing list so that we can take an urgent action

 *   Adding terms to the terms an definition sections

    *   Juanjo to send an email to request for additional definitions

 *   Integration of Location-related input from Telecom Italia.

    *   This will be done by Thales with support from Telecom Italia
    *   Juanjo will send an email elaborating on how he sees this integration to take place.

 *   Review additional enablers proposed by Thales not yet integrated in the deliverable

    *   Juanjo decided not to integrate them in the current draft since no enough discussion on them has taken place
    *   Juanjo will setup a doodle for a dedicated confcall next week to discuss their inclusion

 *   Revision of the description of the Publish/Subscribe Broker GE

    *   This had been already discussed in our previous confcall.  It's just a matter of describing the interfaces, operations and interactions: Juanjo will take care of this






________________________________
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
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110712/d6bae6bc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia.jpg
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110712/d6bae6bc/attachment.jpg>