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) -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20160512/0480a0d3/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Issues_Resolution_ToC.PNG Type: image/png Size: 17812 bytes Desc: Issues_Resolution_ToC.PNG URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20160512/0480a0d3/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: 20160511_ngsi-2_open-issues.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 42942 bytes Desc: 20160511_ngsi-2_open-issues.docx URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20160512/0480a0d3/attachment.docx>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy