Dear Fermin and Ernö I tend to side more with the view expressed by NEC that it is risky to freeze now a version in which all the issues raised in our discussions on JSON-LD have not been fully addressed and solved in mutual agreement. Regarding issues raised in section 1.3 of the NEC document, I have strong misgivings when I read from Fermin that JSON-LD would just be a different “encoding” : it is much more than that, and using it means a structural shift from a restricted entity-centric meta-model (as used by NGSI and JSON) to a much more powerful and universal graph-based model (that of RDF), even though the surface syntax may appear very similar. Orion may very well keep the previous NGSI-originating model internally for compatibility reasons , but the data model exposed by for external interfaces will be different, and this is where we gain openness. We should make sure that this has been properly taken into account in any version that will get freezed, even provisionally De : fiware-ngsi-bounces at lists.fiware.org [mailto:fiware-ngsi-bounces at lists.fiware.org] De la part de Fermín Galán Márquez Envoyé : vendredi 13 mai 2016 09:46 À : fiware-ngsi at lists.fiware.org Objet : Re: [Fiware-ngsi] Proposal to resolve NGSIv2 issues Dear Enroe, JSON-LD and context availability management (registrations) are not mature enough and should be left out for the first batch of stable functionality, which should be focused in the real mature part: context management (which I understand is the piece you name "representation of entity information"). This will make the work much easier and allow to achieve the target by end of May. Of course, if you want to set a new target for the second release of stable functionality including representation of entity information (the one frozen by end of May) + representation of registrations + information section on requirements and system assumptions + JSON-LD, it is ok with me (although I think that the end of June date is too optimistic for that, as the last three topics are not so mature). Given that looking to the doodle it may pass some time until we have the audio and we cannot lose time, I have taken the liberty of answering your comment in the doc (see inline [FGM] comments in green). As you can see, leaving apart the JSON-LD part, all the issues can be concluded in either one of this three ways: * It is not a blocker for the releasing of a frozen stable batch of NGSIv2 focused on context management. * The issue is solvable adding optionality * Is a minor thing, easily fixable in the spec .apib before end of May So, I'm still thinking that we can frozen a stable version now, apart from some minor details that need to be polished. Finally, regarding specification format/tool, FIWARE rules mandates to use APIary to describe REST APIs (see https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Developer_Guidelines). And NGSIv2 is a REST API. Thus, the specification format is out of scope: it has to be APIary (which of course doesn't preclude to generate other documents based on that APIary specifications if you need so for other fora, eg. ETSI). Best regards, ------ Fermín El 12/05/2016 a las 8:53, Ernoe Kovacs escribió: Dear FIWARE colleagues, In the recent weeks intensive technical discussions about the next version of NGSI have been taking place, mostly concerning 1) details of a JSON-LD representation 2) the maturity of the current NGSI v2 proposal (on GitHub repository of Orion Context Broker) for official release In our understanding there are two competing high-level requirements: a) very soon releasing NGSI v2 and committing to a certain level of backwards compatibility of future NGSI 2 versions. b) making sure that the released version is sufficiently mature, complete, and has been agreed by the involved partners, so that backwards compatibility can indeed be guaranteed. In NEC’s view it will not be possible to achieve the needed agreement and maturity of the full specification to enable a release within a few weeks. We have prepared a document listing the various technical issues we are seeing at the moment; please find it attached. In order to move forward in an effective way, NEC proposes the following approach: - Target: reaching an agreement and formal specifications on a subset of the aspects by the end of June 2016. What we concretely propose is to restrict the current scope to the NGSI data model and its representation in JSON and JSON-LD, including o representation of entity information o representation of registrations o (optionally) an informative section on requirements and system assumptions - Process: o weekly phone conferences in a fixed time slot o systematically documenting the discussion threads and the conclusions reached. Such documents can then be continued to be used inside the ETSI ISG for any remaining unresolved issue. A document structure as we propose it is shown in the attached screenshot Issues_Resolution_ToC.png file, for discussion, and some material that might be brought into such a format is in the file 20160511_ngsi-2_open-issues.docx. o preparation of a standalone specification document, so that it will be clear what the partners exactly agree to. Which tool to use (GitHub, APIary, googledoc, word file, etc.) is subject to discussion. The resulting document can again serve as input for the ETSI ISG. We believe that restricting the scope for now is necessary in order to be able to achieve the necessary level of maturity within a short time. Of course this means that the backwards compatibility promise is limited to the representation format and does not include the details of the query language. As written on Tuesday, we would like to discuss this proposal in a conference call this week; please specify your availability here http://doodle.com/poll/43meqmm9eeq427mp Best regards Ernoe Kovacs (NEC) and NEC team (Martin Bauer, Tobias Jacobs, Lindsay Frost) 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 _________________________________________________________________________________________________________________________ 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/20160513/a9a41933/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy