[Fiware-ngsi] NGSI binding gap: format of 'reference' and 'providingApplication'

[thierry.nagellen at orange.com]

Dear all,

Please react before Tuesday, 28th of May EOB to comment the proposal. Without any comment the proposal will be adopted on Wednesday morning.

BR
Thierry

De : fiware-ngsi-bounces at lists.fi-ware.org [mailto:fiware-ngsi-bounces at lists.fi-ware.org] De la part de Tobias Jacobs
Envoyé : jeudi 22 mai 2014 16:45
À : fiware-ngsi at lists.fi-ware.eu
Objet : [Fiware-ngsi] NGSI binding gap: format of 'reference' and 'providingApplication'

Dear all NGSI-interested people,

in the IoT integration meeting a few weeks ago we identified an underspecified point in the NGSI 9 and NGSI 10 binding, regarding

-          the exact format of the 'providingApplication' field in the NGSI 9 ContextRegistration structure, and

-          the exact format of the 'reference' field in the NGSI 10 'subscribeContextRequest' and the NGSI 9 'subscribeContextAvailabilityRequest' operations.

In order to remove the ambiguity, our proposal is to

-          make mandatory for NGSI9 [ NGSI10 ] servers to provide NGSI9 [ NGSI10 ] functionality under the URL "{serverRoot}/ngsi9"  [ "/{serverRoot}/ngsi10" ]. This deviates from the current binding in that we use lowercase "ngsi" instead of uppercase "NGSI". Using lowercase seems to be more common in REST interfaces, and anyway all IoT GEs have implemented it with lowercase as far as we know.

-          Make mandatory to specify in the 'reference' and 'providingApplication' field only the {serverRoot} part, without the 'ngsi9' part.

o   For example, for announcing in a contextRegistration that context information can be retrieved by sending POST messages to  "http://www.coolContext.org/ngsi10/queryContext" as defined by the NGSI standard, the 'reference' field has to be http://www.coolContext.org/ngsi10<http://www.coolContext.org/ngsi10>.

Please let us know you are ok with that proposal, or if you want to propose an alternative way to remove the ambiguity.

Best regards
Tobias


_________________________________________________________________________________________________________________________

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/20140523/8f9d4b90/attachment.html>