[Fiware-ngsi] OMA consistency for a joined action to CR or R2 of OMA NGSI

[Juanjo Hierro]

Hi,

  As mentioned since the very beginning, we should be ready to fix anything in the original OMA NGSI spec that we find inconsistent.   That's why we should use the term "FI-WARE NGSI" to refer to the spec we are implementing, which should stick to the original OMA NGSI spec as much as possible but not at the price of doing things we know are wrong or can clearly be improved.

  In this respect, I propose the following changes in the wiki page dealing with the specification:


  *   Change contents of the "FI-WARE NGSI 10 API Core " section so that it reads:

The FI-WARE NGSI-10 API is a RESTful API based on the OMA NGSI-10 specification that enables the exchange of context information.    ... (rest of the section as it stands now)


  *   Change contents of the "Additional Resources" section so that it reads:

The OMA NGSI-10 interface specifications can be downloaded<http://www.openmobilealliance.org/Technical/release_program/docs/NGSI/V1_0-20101207-C/OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf> from the website of the Open Mobile Alliance<http://www.openmobilealliance.org/>.   A number of Changes with respect to the OMA NGSI specifications<http://wiki.fi-ware.eu> have been defined dealing with coverage of gaps/bugs/ambiguities/improvements identified in the original OMA spec.  ... (rest of the section as it stands now)

(note: I have illustrated how the paragraph may look like when you browse it ... "Changes with respect to the OMA NGSI-10 spec" should direct to a page on the wiki with that title containing a description of the changes introduced in the OMA spec, therefore the source of the page should be [[Changes with respect to the OMA NGSI specifications]])

  As part of our exploitation plan, concretely the standardization plan, we shall submit these changes to the OMA NGSI WG at OMA for fast-track adoption.   I guess we have the relevant stakeholders at our side to make this happen smoothly ;-)

  Best regards,

-- Juanjo

On 06/06/12 16:57, Moltchanov Boris wrote:
Hi Everyone,

During NGSI wrapper implementation we have found an inconsistency in the naming of structures within OMA NGSI specification, which has been used for the binding of FI-WARE NGSI, therefore inherited also there. Salvatore Longo from NECLabs already aware of what I'm talking about.

Thus, I suggest we collect the list of those consistencies in order to "de-froze" the OMA NGSI spec and either proceed with a CR (Change Request) or to produce the second Release of the Enabler. I'm not speaking here about the extension of the OMA specs with a certain binding, as this might be out-of-scope of OMA as far as there is no specific official standard binding for such matter yet (like location interfaces defined in 3GPP and then used as a binding in OMA MobLoc). I'm speaking about improving of the high-level OMA spec in order to resolve mistakes as far as this will create less headache for the developers of our NGSI build on OMA and will eliminate the questions and doubts such as "Why have I implemented something based on OMA if the OMA spec is stupid?"

It would be nice to have back your opinion on this.

Thanks.

Best Regards,
Boris
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.



________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120703/32c157a3/attachment.html>