[Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates

[Defrance Serge]

Dear Pier,

I updated my contribution according to your comments.
In particular, I have added to figures to better describe the interaction between the local devices in the home network and the cloud proxy (home system management).
Do not hesitate to tell me if additional comments.

Best Regards,
Serge.


From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it]
Sent: mercredi 8 février 2012 11:29
To: Defrance Serge
Cc: fiware-i2nd at lists.fi-ware.eu
Subject: R: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates

Hi Serge,

Thanks a lot for your effort. I reviewed the CE page you have provided, and I believe you have done already a rather extended description.

By trying to evaluate it against the guidelines however, I identified some aspects which probably need to be updated (mostly moving portions of what described already), here I report them using as reference the sections in the page:

-          Overview: Ok, but see next point

-          Basic Concepts:

o   Maybe the picture can be anticipated already in the 'Overview' along with some of the text there, i.e. everything up to 'The cloud proxy is acting as an organizing agent of the home network, in particular unifying the access to the data contained in the home network.' included.

o   Remaining text should stay in the 'basic concepts' section, however I consider a part of it as introductory (or complementary) to the 'general description and architecture' which is currently in the following section

-          Main Interactions

o   The actual contents of the 'main interactions' sections should be a description (a number of items) about how the CE is going to interact with the 'rest of the world' (or better the reverse: how the rest of world will interact with CE...): this has to be in narrative description (no need at the moment for having a list of parameters and expected data format), but this should be more or less a list of 'interfacing functions' to interact with the GE (unless the CE is self-contained, i.e. it doesn't have interactions with the outside world, e.g. other GEs or application developers or applications, but I think this is not the case, otherwise nobody would be able to use it ;-)

o   As reference, you can (re)check the guidelines page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions and the first example in line with those guidelines (but not completely yet, so pay attention!) which is the usual QueryBroker description at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker

o   I therefore believe that the 'general description and architecture' should be moved in previous section, almost entirely in my view, or at least up to the entire 'home system management' description.

o   Sub-section 'Home System Modelling, Basic Design Principles' is more in line with the expected contents of this section, but probably it should be made clearer who does it and how the interaction is expected to happen (e.g. who and how is going to create/model the files explained).

o   Not completely sure, but probably also the registration mechanism described ion the description of the entire 'home system management'  could be one of the interactions described here. I wonder if a reference e.g. to how applications can be managed could be put here.

Hope this is clear, otherwise we can have a short call e.g. today afternoon (I should be free from 15 to 17).

BR
Pier



Da: Defrance Serge [mailto:serge.defrance at technicolor.com]
Inviato: mercoledì 8 febbraio 2012 09:59
A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu
Oggetto: RE: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates

Dear all,

I found the way to upload figures to the wiki. Contribution is now up to date.
Pier, let me know if any problem. Note also that I shall be out of office from 10/02 to 20/02 (included, back to my office 21st of February).
Serge.


From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Defrance Serge
Sent: mercredi 8 février 2012 09:07
To: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu
Subject: Re: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates

Pier and all,

I updated the contribution regarding cloud edge for the D2.3 on our I2ND private wiki. However I don't know how to add figure. Maybe Pier you can help me ?
Cheers,
Serge.


From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo
Sent: vendredi 3 février 2012 11:12
To: fiware-i2nd at lists.fi-ware.eu
Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates

Dear All,

you can find the minutes of the confcall held yesterday at the following link:

https://forge.fi-ware.eu/docman/view.php/10/779/I2ND_Confcall_20120202_minutes.doc

Please correct possible mistakes, thanks.

Moreover, there are important updates concerning two of the topics discussed there:


-          Standardisation per WP: we have now a .doc template for WP contribution (which implies also an excel one...), although it seems rather more extended that what it was planned earlier. I'll send a separate mail to Task cords about this, to coordinate the actions.



-          Architecture description: there are guidelines available at the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions  PLEASE TAKE NOTE that the first part of guideline  "FI-WARE GE Architecture Descriptions" concerns the description of a single GE architecture (what we call Open Specifications, e.g. the page FIWARE.OpenSpecification.I2ND.CE<https://forge.fi-ware.eu/plugins/mediawiki/wiki/i2nd/index.php/FIWARE.OpenSpecification.I2ND.CE> , while the second part  "FI-WARE Chapter Architecture Description" describes the overall architecture contribution, i.e. the entire Deliverable "D2.3 FIWARE Architecture" - I2ND Contrib<https://forge.fi-ware.eu/plugins/mediawiki/wiki/i2nd/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_I2ND_Contrib> page.


About the latter item, there's also an interesting discussion going on in the WPL/WPA list, about the use of uniform terms; below is an excerpt of a mail by Juanjo, we're all assumed to adopt the description style and terms suggested when referring to 'GE (open) specifications' and 'GE implementations' (including the non-verbose way):

(...)
  Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences.   It doesn't mean anything tangible.   What do really exist (i.e., refers to something "tangible") are things like:

 *   "GE specifications" (or "GE Open Specifications")
 *   "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications".

  Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like:

"The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp"  (A)
we should indeed say:

"The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B)


  However, I believe that this would lead us to documents that would be rather "verbose".   On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity.

I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as:

In order to avoid a too verbose text, we typically use the term "<name-of-GE> GE" or simply "<name-of-GE>" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the <name-of-GE> GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications").  Note that the notion of GE is abstract and what actually refers to tangible things are:

 *   "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs.
 *   "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications".
You may refer to the set of terms and definitions provided at:
http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced

(...)

Hope this helps in making more uniform and formally consistent the descriptions.

BR
Pier


------------------------------------------------------------------
Telecom Italia
Pierangelo Garino
Innovation & Industry Relations - Research & Prototyping
Via G. Reiss Romoli 274, I-10148 TORINO
Tel: +39 011 228 7142

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:image001.gif at 01CCE672.23277370]Rispetta 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.
[cid:image001.gif at 01CCE672.23277370]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-i2nd/attachments/20120208/fb2998c0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120208/fb2998c0/attachment.gif>