[Fiware-data] Agenda for our weekly follow-up confcall

[Juanjo Hierro]

Hi everybody,

  I suggest that we follow the action points that were identified during our last confcall.   Unfortunately, several of them were on my plate and I couldn't make them.   We are still in the process of hiring the person who would work as leader of this WP but haven't still been able to find it :-( ... and the workload corresponding to this plus the workload of overall management of the project and chairing of the FI-PPP Architecture Board is way too much ...   Apologize for the inconvenience and I hope you will indulgent.

  Anyway, it's still the best way to organize the agenda for this follow-up confcall.   We will decide on the corrective actions to take when we address those points.

  I have added a point in the minutes of our last confcall so that we can address it during today's confcall.   I identified it while elaborating the presentation of each of the FI-WARE chapters to the FI-PPP Architecture Board.   It has to do with the description of the Query Access GE.   The definition of this GE seems to me still too much oriented to multimedia databases while I though we were going to generalize its description to be able to cope with different kind of data base/repositories and different query language families ...    Indeed, I believe we also agreed to connect this GE with the Publish/Subscribe Broker GE and that was one of the reasons why we would need to support this notion ...    I guess this comment may have to do with the comment that Boris has recently sent to the mailing list regarding problems to merge the description of the "query search" GE already in the document and the query search functions needed for Context (also Data, I guess) Management.   We should address this in the final official deliverable, at least as one of the "Points still under discussion"

  Best regards,

-- Juanjo


-------- Original Message --------
Subject:        [Fiware-data] Minutes of our weekly follow-up confcall
Date:   Fri, 8 Jul 2011 14:07:58 +0200
From:   Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es>
To:     fiware-data at lists.fi-ware.eu<mailto:fiware-data at lists.fi-ware.eu> <fiware-data at lists.fi-ware.eu><mailto:fiware-data at lists.fi-ware.eu>


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

 *   Query Access GE
    *   Current text seems to be really just oriented to multimedia and not formulated under the view of being also applicable to access data managing different query families, etc
    *   The relationship with query functions by the Publish/Subscribe Broker GE is not addressed

 *   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


________________________________
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/20110715/67d8e160/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001..txt
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110715/67d8e160/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhierro.vcf
Type: text/x-vcard
Size: 429 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110715/67d8e160/attachment.vcf>