Dear Tobias, No news since Wednesday... should we understand that the proposed call will not take place next Monday? (ok for me, just to free the slot in my agenda :) Thanks! Best regards, ------ Fermín El 04/05/2016 a las 22:29, Fermín Galán Márquez escribió: Dear Tobias, As far as I understand, the JSON-LD NGSI encoding proposal was designed in a way fully aligned with "plain" NGSIv2 from the very beginning. At least based in the examples at https://docs.google.com/document/d/1lWH_a-JkwfSR9uE03KQbKe09uajpJqsPXk7nHFJPYQs/edit#heading=h.vx9h5b418g4u, basically JSON-LD payload = "plain" NGSIv2 payload in keyValues render mode + @context and other JSON-LD stuff. However, I understand you are proposing this call because you feel there is some "risk" of non-alignment. Is that correct? Could you share with us before we meeting the points in which you think the alignment is broken, please? Regarding the conference itself, I'd prefer May 9th, 15:30 CET but I think that I could make if most of the people prefers 14:30 CET. In parallel, we would be more than happy to know your feedback after you re-evaluate the current status of the (JSON-LD independent) NGSIv2 proposal. Thanks! Best regards, ------ Fermín El 04/05/2016 a las 17:06, Tobias Jacobs escribió: Dear all, In the confcall that has just taken place we have not been able to discuss this issue below, but we propose to have a dedicated conference call on the relation between JSON-LD and the plans to make the current Orion NGSI-v2 a “stable version”. The proposed time slot is Monday, May 9th at 14:30 CET Could you please confirm your availability? Sergio or someone else, could you provide the conference bridge? Thank you! Best Regards Tobias From: Tobias Jacobs Sent: Dienstag, 3. Mai 2016 15:44 To: 'Fermín Galán Márquez'; <mailto:marc.capdevielle at orange.com> marc.capdevielle at orange.com<mailto:marc.capdevielle at orange.com> Cc: fiware-ngsi at lists.fiware.org<mailto:fiware-ngsi at lists.fiware.org>; Tobias Jacobs; SERGIO GARCIA GOMEZ; wenbin.li at orange.com<mailto:wenbin.li at orange.com>; FERMIN GALAN MARQUEZ; JUAN JOSE HIERRO SUREDA; PRIVAT Gilles IMT/OLPS; RAMPARANY Fano IMT/OLPS; t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>; CAPDEVIELLE Marc IMT/OLPS; Martin Bauer; Lindsay Frost Subject: RE: [Fiware-ngsi] Releasing a first batch of NGSIv2 stable functionality as "production ready" by the end of May Dear Fermin and all, >From NEC side we have been rather concentrating on the JSON-LD discussions since the beginning of this year, so we have to re-evaluate the current status of the (JSON-LD independent) NGSI-2 proposal before we can make a statement. In the past we have been insisting on not making implicit assumptions on the system architecture when specifying the features of the query language (e.g. not assuming that the broker is a centralized system which has all data in a local database). We will analyze the current version and prepare a more detailed statement. Besides, there is yet another issue, which has to do with the current JSON-LD serialization: We would like to ask all partners how they see the interrelationship between the current JSON-LD discussion and the NGSI-2 interface as defined by Orion on GitHub. On the JSON-LD side we are having very constructive discussions, and I am optimistic that we are about to agree on the last open points soon. For me the main question here is: Are we targeting to align the ‘plain’ JSON message format with what we have decided for JSON-LD? Concretely, aligning would mean that the plain JSON body is what you get when you remove the @context from the JSON-LD body. In our view this alignment would be very useful, so that the JSON-LD bodies are fully backwards compatible with the plain JSON-bodies (which was anyway one of the primary design targets of JSON-LD), and the JSON-LD serialization does not become a decoupled “NGSI 3.0”. By the way, there will be a conference call on JSON-LD next Wednesday (tomorrow) at 15:00, where we could discuss this question. Best regards Tobias From: fiware-ngsi-bounces at lists.fiware.org<mailto:fiware-ngsi-bounces at lists.fiware.org> [mailto:fiware-ngsi-bounces at lists.fiware.org] On Behalf Of Fermín Galán Márquez Sent: Dienstag, 3. Mai 2016 07:56 To: marc.capdevielle at orange.com<mailto:marc.capdevielle at orange.com> Cc: fiware-ngsi at lists.fiware.org<mailto:fiware-ngsi at lists.fiware.org> Subject: Re: [Fiware-ngsi] Releasing a first batch of NGSIv2 stable functionality as "production ready" by the end of May Dear Marc, Thank you very much for the feedback! As you suggest, let's continue discussion on the specific issues a github. That's the way to go :) Best regards, ------ Fermín El 02/05/2016 a las 17:57, <mailto:marc.capdevielle at orange.com> marc.capdevielle at orange.com<mailto:marc.capdevielle at orange.com> escribió: 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> 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 (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> 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 (<mailto:Fiware-ngsi at lists.fiware.org>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. ________________________________ 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 ________________________________ 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 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 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20160506/84bfc192/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy