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:part1.03010803.03020005 at tid.es] 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/20130228/11fa507f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 13584 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20130228/11fa507f/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy