[Fiware-data] Minutes of confcall 11-05-13

[Juanjo Hierro]

Attendees:

TID: Juanjo
IBM: Guy
Telecom Italia:
ATOS: Tomas and Chema
Orange: <don't took note of names, please apologize>
Siemens: Andreas
Thales: Remi
UPM: David

Goals of the meeting:

  Agree on the ToC and the assignment of editing tasks.   Also the setup of Task Forces to deal with a) areas where there are overlapping assets, b) "question marks" (this include those related to security aspects)

Summary of the meeting

  We reviewed the ToC proposal distributed by TID:

  1. Overview
          * Should include some short of overall Functional Architecture picture
          * Expected length: 3-4 pages
   2. Generic Enabler descriptions
          * Focus on technical description without binding to any specific asset (although it can certailnly be inspired on assets that are clearly considered as baseline)
          * Should cover  all the ingredients of the "product vision" in Agile Sprint 0:
                o Who is going to "buy" the product? Who is the target user?
                o Which user needs will the product address?
                o Which product attributes are critical to satisfy the needs selected, and therefore for the success of the product?
                o How does the product compare against existing products, both from competitors and the same company? What are the product's unique selling points?
          * Expected length (per Generic Enablers): 3-5 pages
   3. Section on "Question Marks"
          * Formulates what topics are still under discussion
          * Expected length for the whole section: 3-5 pages
   4. Detailed list of terms and definitions


  TID is willing to act as main editor of sections 1, 3 and 4.    We would produce first drafts of these sections for review of the rest of the partners.

   We should concentrate on agreeing the subsections within section 2.   Target subsections and editors in a very first approach (not necessarely in this order):

    * Off-line analysis-processing/mining platform (TID)
    * Intelligent Services Plug-ins (TID)
    * Real-time stream processing based on CPE (IBM)
    * Real-time stream processing based on map-reduce (TID)
    * Preprocessing of meta-data during/after gathering (Siemens)
    * Preprocessing of unstructured data during/after gathering (ATOS)
    * Data/Context Pub/Sub Broker (TI) - note: Orange have brought also some asset here and TID wish to incorporate some requirements
    * Semantic Web annotation tools (ATOS)
    * Searching/Query-access (???)
    * Multimedia analysis to gather multimedia meta-data (Siemens)


Thales asked where the Location Enabler should be placed.  Juanjo explained that we have to firs solve the issue that
was raised during the kick-off.   If the issue gets no solved on time for first release of deliverable at least would
be covered in section about "Question Marks"

Action: setup confcall to start discusion on Location Enabler

ATOS misses:

* Real-time stream processing of unstructured data (ATOS) - added
* Management tools - probably have to go to the "question marks"
* Description of RFD repository - this should be covered in subsection Semantic Web annotation tools (ATOS)

Action: ALL to provide better names for subsections in section 2

Action: Rename box about Query/Search Engine in slide 4 of the target arch and name it as "Searching/Query access"

Action: Setup confcall to address the Searching/Query access involving Telecom Italia, Siemens and TID prior assigning edition role to description of this GE.   Juanjo will setup a doodle on the matter.   Siemens and Telecom Italia to provide their input on vision about the Searching/Query access enabler prior to this confcall.

Action: TID to provide requirements in the Pub/Sub Broker

Action: TID, Telecom Italia and Orange to have a confcall on Pub/Sub Broker.  We'll review Orange's asset, Telecom Italia's asset and TID requirements

To be pragmatic and be able to deliver a description on time, Telecom Italia leads the edition of the Pub/Sub Broker Section.  The description should incorporate features by TID and Orange and the two of them will participate as reviewers of this section.   Remember that description should be high-leve for deliverable in month 2, not tied to any specific asset.

Action: The editor of each subsection in section 2, have to consider and hightlight whatever aspect related to Security is relevant for the GE description

Action: Juanjo to involve someone representing the Security WP in the team (first adding him/her to our mailing list)

Action: Juanjo will distribute a template for writing the sections

It was agreed that writing style should be that of a white-paper or product vision document.   No requirements-list like.




On 13/05/11 08:19, Juanjo Hierro wrote:
Hi all,

  Regarding the Table of Contents, there is nothing much to add to what I already presented during the final plenary session on friday last week.   Anyway, please find it enclosed for your convenience


 1.  Overview
    *   Should include some short of overall Functional Architecture picture
    *   Expected length: 3-4 pages
 2.  Generic Enabler descriptions
    *   Focus on technical description without binding to any specific asset (although it can certailnly be inspired on assets that are clearly considered as baseline)
    *   Should cover  all the ingredients of the "product vision" in Agile Sprint 0:
       *   Who is going to "buy" the product? Who is the target user?
       *   Which user needs will the product address?
       *   Which product attributes are critical to satisfy the needs selected, and therefore for the success of the product?
       *   How does the product compare against existing products, both from competitors and the same company? What are the product's unique selling points?
    *   Expected length (per Generic Enablers): 3-5 pages
 3.  Section on "Question Marks"
    *   Formulates what topics are still under discussion
    *   Expected length for the whole section: 3-5 pages
 4.  Detailed list of terms and definitions

  TID is willing to act as main editor of sections 1, 3 and 4.    We would produce first drafts of these sections for review of the rest of the partners.

   We should concentrate on agreeing the subsections within section 2.   Target subsections and editors in a very first approach (not necessarely in this order):

 *   Off-line analysis-processing/mining platform (TID)
 *   Intelligent Services Plug-ins (TID)
 *   Real-time stream processing based on CPE (IBM)
 *   Real-time stream processing based on map-reduce (TID)
 *   Real-time stream processing by Siemens ?
 *   Data/Context Pub/Sub Broker (TI) - note: Orange have brought also some asset here and TID wish to incorporate some requirements
 *   Semantic Web annotation tools (ATOS)
 *   Searching/Query-access (???)
 *   Multimedia analysis to gather multimedia meta-data (Siemens)

  Goal of our confcall is to definitively agree on the ToC and the assignment of editing tasks.   Also the setup of Task Forces to deal with a) areas where there are overlapping assets, b) "question marks" (this include those related to security aspects)

  Best regards,

-- Juanjo

________________________________
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/20110513/b4f9d6b9/attachment.html>
-------------- 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/20110513/b4f9d6b9/attachment.vcf>