[Fiware-ngsi] NGSI9 registerContext "update" interpretation

Tobias Jacobs Tobias.Jacobs at neclab.eu
Fri Mar 1 09:11:48 CET 2013


Hi Fermin,

Yes, I would agree that the update of a registration should completely replace the previous version of the same registration, as here there are no updateActionTypes defined like in NGSI 10.

By the way, an analogous question is the notifyContextAvailability operation, where for a given subscription id a number of registrations are specified. Also here the registration information specified in the notifyContextAvailability operation should completely replace the previous registration information this particular subscription.

Best regards
Tobias

From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Fermín Galán Márquez
Sent: Donnerstag, 28. Februar 2013 09:47
To: fiware-ngsi at lists.fi-ware.eu
Subject: [Fiware-ngsi] NGSI9 registerContext "update" interpretation

Hi,

OMA specification section 5.3.1 doesn't specifies how the Context Registration list has to be processed in the case of a registerContext "update" (i.e. a registerContext in which RegistrationId is present).

Our proposal is to interpret this case in the following way:

  *   The Context Registration list in the request replaces the previous Context Registration list associated to the given RegistrationId.
Follows an illustration on how it works for two example cases:

[cid:image001.jpg at 01CE165C.CD6F5170]

Compared with other alternatives (e.g. that the Context Registration list in the request would be added to the ones already associated to the given RegistrationId), our approach allows a full control of the elements associated to the RegistrationId. We can assume that the client sending the registerContext "update" knows the previous status of elements associated to the given RegistrationId, so it can control which exact Context Registration elements he wants to have after the update is processed. In fact, the solution based on replacing is the only way of removing elements already existing.

What do you think?

Best regards,

------
Fermín
________________________________

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/20130301/8a5685ba/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 28993 bytes
Desc: image001.jpg
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20130301/8a5685ba/attachment.jpg>


More information about the Fiware-ngsi mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy