[Fiware-ngsi] Proposal to resolve NGSIv2 issues

[Tobias Jacobs]

Dear Jose Manuel, Juanjo, all,

We have just extended the options in the doodle to next week upon your request.

As said, this call is intended to discuss the overall approach of _how_ to continue. The detailed technical discussions will take place in other calls or by emails.

I agree that use cases for technical requirements should be provided, and we will do so.

Best regards
Tobias

From: JOSE MANUEL CANTERA FONSECA [mailto:josemanuel.canterafonseca at telefonica.com]
Sent: Donnerstag, 12. Mai 2016 09:24
To: Ernoe Kovacs
Cc: Martin Bauer; Tobias Jacobs; Lindsay Frost; JUAN JOSE HIERRO SUREDA; fiware-ngsi at lists.fiware.org
Subject: Re: Proposal to resolve NGSIv2 issues

Hi Ernoe, all,

Thanks for sending this. An important point missed here is that any new requirement or issue around existing spec should be supported by a use case and a real prove that such use case cannot solved by other mechanism. That would avoid complicating the API or representation for the sake of it, or entering into academic but, in practice, not very useful discussions. So before discussing on issues I would like to know use cases which support new requirements.

In particular I would like to know what's the use case behind the full alignment between JSON-LD and JSON representation  or what's the use case behind the "multiple value" issue, that, by the way we discussed in the past, and for which there are different and good alternatives already in the API.

Wrt conf. Calls I'm the rest of the week in a meeting and not available and I would like to postpone any call for the beginning of next week.

Thanks, best

De: Ernoe Kovacs <Ernoe.Kovacs at neclab.eu<mailto:Ernoe.Kovacs at neclab.eu>>
Fecha: jueves, 12 de mayo de 2016, 8:53
Para: JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>, "fiware-ngsi at lists.fiware.org<mailto:fiware-ngsi at lists.fiware.org>" <fiware-ngsi at lists.fiware.org<mailto:fiware-ngsi at lists.fiware.org>>
CC: Jose Manuel Cantera Fonseca <josemanuel.canterafonseca at telefonica.com<mailto:josemanuel.canterafonseca at telefonica.com>>, Martin Bauer <Martin.Bauer at neclab.eu<mailto:Martin.Bauer at neclab.eu>>, Tobias Jacobs <Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>>, Lindsay Frost <Lindsay.Frost at neclab.eu<mailto:Lindsay.Frost at neclab.eu>>
Asunto: Proposal to resolve NGSIv2 issues


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)


________________________________

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/20160512/e1efceca/attachment.html>