[Fiware-data] Presentation summarizing GEs relevant to IoT

[Juanjo Hierro]

   Please find the updated version of the presentation at the following
URL in FusionForge:

https://forge.fi-ware.eu/docman/view.php/9/351/Data-Context-Event+GEs+in+the+FI-WARE+project+11-09-13.pptx

   Below and between lines, how I have dealed with the comments from
Boris (thanks for them !)

On 12/09/11 14:05, Moltchanov Boris wrote:
> Hi Juanjo,
>
> Thank you very much for the slides drafting.
>
> I have couple of small comments:
>
> - [slide 3] insert OMA logo in the slide and give uri locator www.openmobilealliance.org there;
> - [slide 6] change "formar" to "formal" or "format" (I remember it was already a mistake in the document, please check this in the wiki-repo, and you answered the comment that it shall be "format", while I, instead, suppose it should be "formal", which is correct terming used in this field);
> - [slide 6] "contextML" ->  "ContextML" (this is a correct representation name adopted by TI);
> - [slide 6] "sensorML" ->  "SensorML" (I believe this is the correct name and this is how it is used in the slide 8);
> - [slide 8] instead of using "format representation" it would be better to adopt the term "representation formalism" that is the "correct" term using worldwide in this field;
> - [slide 10] don't forget please explain (verbally or inserting a very small and short explanation in the beginning of this slide)  what is "event" in the roles listed in that slide. I mean that the event there is different from event of e.i. "complex event processor" (do you remember our long discussion? ;-));
   Done
> - [slide 10] "by invoking the query operation" ->  "by invoking query of subscription operations". Indeed the slide 13 is correctly stating "through subscriptions or making explicit queries";
   This query operation is just a query, as far as I understand from
your presentations and from the OMA specs.   Don't confuse it with the
operation we use to establish a subscription (where a query is also
passed).   This query operation directly returns a set of events
(data/context elements) that fulfill the query expression while the
operation for subscription passes also a query expression but is just as
parameter of the subscription (results are sent to the Consumer via
notify operation)
> - [slide 12] instead of usage "application" I would use everywhere "Event Consumer" and then say that usually an "application" is "Event Consumer" and that an "Event Consumer" means an "application". It will eliminate confusion, what is difference between "application" and "Event Consumer" preserving at the same time all the features demonstrated there in the slide. Indeed in the slide 13 you use only "consumers" and no "application";
   I do not agree.   I believe that we should emphasize that the
application that registers an Event Consumer may perfectly not be an
Event Consumer itself.
> - [slide 13] I would recommend to you same terminology - "Event Producer" and "Event Consumer" as in the slide 12;
   Done
> - [slide 15] Pay attention that someone (Data/Context or IoT) shall then implement the OMA interface for that, if it will accepted by IoT ;-) or maybe they propose some other existing in IoT technique, such as one available in ZegBee (www.sigbee.org), which is a very dedicated to IoT standard and TI is active there in definition as probably as the usage). Advantage of ZigBee that it is ready for the real world usage, has very detailed specification, has defined many application profiles that could be used by UA, and it has tons of devices in the market by big manufacturers like OKI, Texas Ins., etc.;
   This is just a suggestion.   The IoT chapter has to define
interfaces/services enabling to discover resources dynamically (that is
what is mentioned in the FI-WARE Product Vision).   So my intend is to
say "don't re-invent the wheel" and put on the table a proposal of what
can be done.

   Regarding your suggestion about ZegBee, my understanding is that
ZegBee is one of the several IoT communication technologies that are
being used.    My understanding is that the suggested OMA interfaces may
indeed be implemented wrapping access to ZegBee and other protocols.

   The message I would like to bring overall is that we should be able
to provide to Application Developers a set of APIs that ease programming
of IoT applications in a way that is independent to the particular IoT
communication protocol, providing an easy-to-program environment similar
to what Pachube is providing today (but yet more powerful and trying to
be open).   Indeed, the kind of interfaces we are proposing from the
Data/Context Management chapter (Publish/Subscribe, Resource Discovery,
Complex Event Processing) should allow to provide a framework like
pachube in a FI-WARE Instance.

   But regarding this particular chapter (resource discovery) it's just
a suggestion.
> - [entire presentation] I believe it would be correct if Telefonica I+D in slides footer and Telefonica in the last slide are changed to FI-WARE or some other form that reflect that the content of the slides is not Telefonica ownership but of the FI-WARE consortium.
   Yes, of course, sorry for sending this version.   The point is that I
was reusing a presentation I elaborated in the first place to explain
internally what we were doing in our chapter :-)   I forgot to make the
translation when I passed it to you.   But this is fixed in the updated
version.  Thanks for bringing this because i sincerely didn't notice.

   Cheers,

-- Juanjo
>
> Thank you.
>
> Best Regards,
> Boris
>
> -----Original Message-----
> From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro
> Sent: Thursday, September 08, 2011 8:11 AM
> To: fiware-data at lists.fi-ware.eu
> Subject: [Fiware-data] Presentation summarizing GEs relevant to IoT
>
> Hi all (and specially IBM and TI guys)
>
>     Please find the URL from which you can download the draft of the
> presentation I had developed so far regarding IoT-relevant GEs.   We may
> use it for a presentation we would make during our joint session with
> the IoT team on Wednesday morning:
>
> https://forge.fi-ware.eu/docman/view.php/9/351/Data-Context-Event+Generic+Enablers+in+the+FI-WARE+project+11-09-06.pptx
>
>     You will see there is a chapter dealing with entity/resource
> discovery.   This comes like a proposal for the IoT to consider as
> baseline for their work in the Resource Discovery component that is part
> of their architecture.   I believe that it would nice that they take
> what OMA specs propose into consideration to gain maximum alignment with
> OMA instead of re-inventing the wheel.
>
>     Don't hesitate to propose adding anything that is needed.
> Particularly, any further detail on the baseline assets that may be
> relevant.  If you send me additional slides, I will integrate them on
> Monday.
>
>     Best regards,
>
> --
> Juanjo Hierro
> Chief Technologist on Software Technologies
> Telefonica R&D Labs
>
> email: jhierro at tid.es
> phone: +34 91 48 32932
> www.tid.es
> twitter.com/JuanjoHierro
>
> Oeste 1, Planta 5. Distrito C
> Ronda de la Comunicacion s/n
> Madrid 28050
> Spain
>
>
> 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
> _______________________________________________
> Fiware-data mailing list
> Fiware-data at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware-data
>
> 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.
>
> .
>

--
Juanjo Hierro
Chief Technologist on Software Technologies
Telefonica R&D Labs

email: jhierro at tid.es
phone: +34 91 48 32932
www.tid.es
twitter.com/JuanjoHierro

Oeste 1, Planta 5. Distrito C
Ronda de la Comunicacion s/n
Madrid 28050
Spain


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