[Fiware-ngsi] Releasing a first batch of NGSIv2 stable functionality as "production ready" by the end of May

marc.capdevielle at orange.com marc.capdevielle at orange.com
Mon May 2 17:57:41 CEST 2016


Hi Fermin,

The freeze and backward compatibility promise of the NGSIv2 is welcome and clearly a sign that the specification has matured.

I have two remarks I would like to discuss before the freeze.

1) Roles definitions

The current work on NGSIv2 seems to be missing some roles definition (or profiles ?) to clearly identify how different components in the FIWARE architecture (or others) can handle NGSIv2 (i.e. making some parts of NGSIv2 optional to some roles).

A broker like Orion can implement the full specification but it seems logical to have some components only implementing a subset of the specification. By having multiple roles clearly identifying what subset of the specification it support, we could then define specialized components as a simple composition of these roles.

A component like the IoT Agent node library<https://github.com/telefonicaid/iotagent-node-lib>, handling protocol adaptations to/from NGSI, only supports a subset of NGSI :
 - as a client it sends data received from devices to a broker (Context Producer)
 - as a server it registers entities to receive commands and accept some limited querying for "lazy" attributes (Context Provider)

Much like it, Fiware-Cepheus<https://github.com/Orange-OpenSource/fiware-cepheus>, handling gateway-level data aggregation, also only supports a subset of NGSI v1.

I have added some comments to the ongoing discussion here : https://github.com/telefonicaid/fiware-orion/issues/1459

2) Optional features

Moreover, some orthogonal features of the NGSIv2 could also be made optional in some contexts to lighten up the API "surface".
The proposition was made here : https://github.com/telefonicaid/fiware-orion/issues/2110

Let's discuss all this on the corresponding Github Issues.

Regards,

Marc Capdevielle



Le 26 avr. 2016 à 18:13, Fermín Galán Márquez <fermin.galanmarquez at telefonica.com<mailto:fermin.galanmarquez at telefonica.com>> a écrit :


Hi,

We started to work on NGSIv2 (both at specification level and reference implementation in Orion Context Broker) last summer. Since that time, the NGSIv2 API has been in "beta" status, thus available for early bird testing (which is good) but not suitable for production usage (which is not so good). But now, more than half a year later, we think that big part of the specification has achieved a very mature status so it should progress from "beta" to "production ready" status.

In particular, this "batch" will be focused on the context management functionality (AKA "NGSI10" in the old OMA-NGSI terms) as described right now in the specification at <http://telefonicaid.github.io/fiware-orion/api/v2> http://telefonicaid.github.io/fiware-orion/api/v2 (e.g. create/update entities, get entities attributes, filters, notifications in NGSIv2 format, etc.). The releasing date for this first batch is expected by the end of May.

Of course, this doesn't mean that the NGSIv2 work (both specification and implementation) will stop after May. There are still exciting areas (context management availability, JSON-LD, etc.) under discussion. In addition, some advanced features in context management (e.g. filters on structured attribute values) will not be ready by the end of May. Thus, at some point we will "branch" the spec document, to "freeze" a snapshot corresponding to the stable batch and, at the same time, continue to work on the new topics (and, in the future, produce new batches). However, what is important to remark is that any future evolution or addition to NGSIv2 has to be done in a way in which it is compatible with the existing stable batch, i.e. preserving backward compatibility.

In summary, the plan is as follows:

  *   To polish and branch the spec at http://telefonicaid.github.io/fiware-orion/api/v2, in two documents: stable and wip.
  *   To align reference implementation (Orion Context Broker) with that "stable" spec (most of that work is done already).
  *   To "freeze" spec and reference implementation by the end of May.
  *   In parallel with the above points, discussion on ongoing topics (e.g. JSON-LD) will continue and its "output" will be available in coming stable batches (post-May) of NGSIv2.

Any feedback is welcome. The deadline to receive such feedback is May 15th.

Thanks!

Best regards,

------
Fermín
________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org<http://lists.fiware.org> will be lost.
Please, send your messages using the new domain (Fiware-ngsi at lists.fiware.org<mailto:Fiware-ngsi at lists.fiware.org>) instead of the old one.
_______________________________________________
Fiware-ngsi mailing list
Fiware-ngsi at lists.fiware.org<mailto:Fiware-ngsi at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware-ngsi


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20160502/d54f7304/attachment.html>


More information about the Fiware-ngsi mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy