[Fiware-i2nd] R: Summary of comments to the I2ND chapter

[BANNIZA, Thomas-Rolf]

 Dear Pier,

please find attached an updated version of I2ND_D2-2-a_v7.5.doc. 

After a short talk with Hans, I removed the text hans inserted in section 3.6.2.3 on page 24. Instead, I added some explaining words in section 3.6.1.1 on page 8/9 which should cover the issues Hans intended to solve. If there is a need to have an explanatory example, then it should be part already of the high level GE description, not smoewhere in the details.

Regarding your comment P.G.1: this is ok for us.

Furthermore I added a comment on page 9 (bz3). In my eyes, the related text might be removed, the mentioned details are explained later and are not needed here.

Best regards,
Thomas


-----Ursprüngliche Nachricht-----
Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo
Gesendet: Donnerstag, 30. Juni 2011 12:27
An: fiware-i2nd at lists.fi-ware.eu
Betreff: [Fiware-i2nd] R: Summary of comments to the I2ND chapter

Dear All, I have uploaded twice the document as one of modifications received was not inserted in the first release... please find the correct doc attached and sorry for flooding your mailbox with so many heavy attachments (I think from next time it will be better to just ask everybody to download the document by the repository to avoid circulating large mails).

BR

Pier




Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo
Inviato: giovedì 30 giugno 2011 12:08
A: fiware-i2nd at lists.fi-ware.eu
Oggetto: [Fiware-i2nd] R: Summary of comments to the I2ND chapter

Dear All, a new update of the I2ND chapter for D2.2a is being uploaded to the Forge repository, it is identical to the version you find attached to the mail. All the inputs received so far have been inserted in it. Some of the actions defined in the mail below have not been completed yet, I therefore ask the partners who have in charge those actions to provide their input asap. 

In the new document I have inserted a pair of comments which need a feedback by some of you, please have a look and tell me if there are things to be modified.

Next steps: as agreed, we'll wait for a revision by Juanjo, and then we'll have in the next few days (i.e. Monday) the possibility to make further refinements if necessary. As soon as a new doc is available I'll let you know.

Best Regards

Pier

Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo
Inviato: mercoledì 29 giugno 2011 12:05
A: fiware-i2nd at lists.fi-ware.eu
Oggetto: [Fiware-i2nd] R: Summary of comments to the I2ND chapter

Dear All,

we had yesterday the (periodic) I2ND audioconference with Juanjo, this time to revise the I2ND contribution to deliverable D2.2a. The document is already well in line with expectations, there are however a few points which need some update.

Below you'll find the feedback by Juanjo, where I have added the set of actions (and the corresponding owner)  we defined in the call to be applied on current release of the document. I 'encourage' the owners of APs to involve other relevant people in the WP who could contribute to complete the action. 

Please use the attached document to do your changes: have first a look at the few updates already there (in case you have objections to them let me know), then accept the changes and finally insert your modifications.

The deadline is providing by tomorrow at noon an updated version of the document, so please distribute you revision no later than tomorrow morning at 11:30 CEST, thanks. 

Best Regards

Pier

Da: Juanjo Hierro [mailto:jhierro at tid.es] 
Inviato: martedì 28 giugno 2011 10:36
A: Garino Pierangelo; Hans.Einsiedler at telekom.de
Cc: jhierro >> "Juan J. Hierro"
Oggetto: Summary of comments to the I2ND chapter

Hi,

  For your convenience, please find below my comments to the chapter.  We already discussed them during our confcall:

*	I've found the Introduction (text until section 3.6.1.1) a little bit confusing.   It was not clear what is the value of introducing the "three stratum" model described there and how it helps to explain the taxonomy of GEs we have finally derived.   Things got indeed clear when I started to read the text on page 7 "Figure 4. provides a high level view of the Interface to Network and Devices architecture, composed of  the following four Generic Enablers: ...".   Before that, I have to confess I was a little bit lost.   Please try to improve it.  à AP1 Hans 
*	I haven't found any reference to the GSMA standards in the section about CDI (Connected Device Interfacing).   Besides, it was not clear what our intention will be regarding the CDI GE ... are we planning to implement the proposed interfaces ?   are we going to extend the standard specs providing new specs that can be more complete and valuable to programmers ?   We need to provide a clear statement on what we aim to deliver à AP2 Pier 
*	Text below Figure 4 is repeated at the beginning of section 3.6.2....   I suggest to move the beginning of section 3.6.2 to the overview part and merge it with the text that was there below figure 4.   The section of Generic Enablers should start sharp with the description of the first one (CDI GE).   This is more an editorial comment, trying to avoid repetition and a better alignment in the structure of the different FI-WARE chapters à AP3 Pier 
*	The functionality described below Figure 7 and before section on "High-level Architecture of the CDI GE" is unclear to me.   What is the point we intend to make in each of the parapraphs?   More or less, a each paragraph corresponds to a problem statement but nothing is said regarding positioning towards that problem statement ... à AP4: Vincenzo/Marco? 
*	Does the CDI GE Architecture description come from any standard effort ?   I believe it should be worth mentioning (even if it is compliance to some proposed architecture) à AP5: Pier (Vincenzo/Marco?) 
*	Regarding the Cloud Edge GE, I have detected a relevant degree of overlapping with the description provided in the Cloud Hosting chapter ... we need to fix this.   I will come with a proposal on the matter. à Waiting input from Juanjo 
*	Regarding the Net Information and Control (NetIC) I have found that there is no reference to APIs enabling to manage network QoS parameters dynamically ... or is it in the S3C ...   It was not clear what would be the GE that would export the API that would deal with dynamic allocation of communication resources and definition QoS parameters à AP3 T7.3/T7.4 Partners? 
*	Regarding the S3C GE, I have found that device localization services are mentioned, as well as generation of context ... we need to coordinate this with twhat is been defined in the Data/Context Management chapter.   I will come with a proposal on specific paragraphs to insert in the text that would fix the issue. . à Waiting input from Juanjo

There's an additional point I took note of, that is relationship with cloud (and with cloud proxy) for paragraph in the middle of page 10 (I have put a comment on it, see doc attached) . à Joe/Serge?

Besides the revision call, I also ask the owners of the APs we defined last week, concerning the analysis of interaction between I2ND and other WP GEs, to provide their comments by tomorrow as well. The interoperability issues between the I2ND GEs and the rest of the Fi-ware GEs should be briefly described, as points to be addressed later by the project, in the 'Question Marks' section (3.6.3).

  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

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. 

rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non è necessario. 

	

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. 

rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non è necessario. 

	

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. 

rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non è necessario. 

	
-------------- next part --------------
FILE QUARANTINED
----------------

The original contents of this file have been replaced with
this message because of its characteristics.
File name: "I2ND_D2-2-a_v7.5_ALU.doc"
Virus name: "ScanTimeExceeded"