Dear Tobias, Thank you for your answers. However, I'm still doubtly regarding: [Fermin: ] Could you detail the example of discoverContextAvailability introduced in the "Usage in NGSI9 operations" section in the wiki? I mean, what should be sent as discoverContextAvailabilityResponse in the following cases: discoverContextAvailability on <entityId_1>.<attributeName_1> discoverContextAvailability on <entityId_2>.<attributeName_2> [Tobias:] If the association <entityId_1>.<attributeName_1> à <entityId_2>.<attributeName_2> has been registered, then this association should be returned for both discoverContextAvailability requests. You get exactly the same ContextRegistration. To be clear, considering the example of your wiki what would be the response in cases A.1, A.2 and B.1 and B.2 below? A) Query on the "starting end" of the association A.1) entity -> entity <discoverContextAvailabilityRequest> <entityIdList> <entityId type="Sensor" isPattern="false"> <id>Sensor_123</id> </entityId> </entityIdList> <attributeList> </attributeList> </discoverContextAvailabilityRequest> A.2) entity.attr -> entity.attr <discoverContextAvailabilityRequest> <entityIdList> <entityId type="Sensor" isPattern="false"> <id>Sensor_123</id> </entityId> </entityIdList> <attributeList> <attribute>measurment1</attribute> </attributeList> </discoverContextAvailabilityRequest B) Query on the "ending end" of the association: B.1) entity -> entity <discoverContextAvailabilityRequest> <entityIdList> <entityId type="Room" isPattern="false"> <id>Room_A</id> </entityId> </entityIdList> <attributeList> </attributeList> </discoverContextAvailabilityRequest> B.2) entity.attr -> entity.attr <discoverContextAvailabilityRequest> <entityIdList> <entityId type="Room" isPattern="false"> <id>Room_B</id> </entityId> </entityIdList> <attributeList> <attribute>temperature</attribute> </attributeList> </discoverContextAvailabilityRequest> Thanks! 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/20130307/3e9b6679/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy