Dear Tobias, In our side (Orion Context Broker) it is also a feature that has never been used by developers (neither heavily nor lightly :). In fact, from the 54470 entities stored in orion.lab.fiware.org Orion instance only 1 has an attribute with ID! Thus, we would deprecate special semantics on ID it in a next Context Broker version, i.e. using ID as part of the attribute identification (of course, the user could still use ID as custom metadata, but Context Broker will not provide any special processing or meaning on it). From now on, the attribute name will be the only identification field for attributes. We also suggest to remove special metadata ID semantics in next version of the NGSI FIWARE binding standard (it only complicates things with a feature that nobody uses). By the way, regarding new versions of the NGSI FIWARE standard, we (TID) are working now in a proposal for the v2 (the current -and unique- version is v1.0, see http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI:_publicly_available_documents). We plan to send it in the next days/weeks... stay tuned ;) Best regards, ------ Fermín El 29/05/2015 a las 9:16, Tobias Jacobs escribió: Hi Fermin, I have no access to the documents right now and the last time we discussed about this is years ago (and we never heavily used that feature either). But as far as I remember your interpretation is right in the sense that multiple providers can each maintain an own "instance" of the same attribute value. I think we have also described how to query a specific value instance and how to query all value instances, and accordingly how to update/delete a specific value instance, and how to delete all value instances. There were quite some discussions about this, so I hope that the concepts are rather mature and consistent... Best Tobias Sent from phone On 28 May 2015, at 17:25, Fermín Galán Márquez <fermin.galanmarquez at telefonica.com<mailto:fermin.galanmarquez at telefonica.com>> wrote: Dear Tobias, Reviewing the current FIWARE Binding we some doubts on this paragraph on Ngsi10-RestfulBinding.pdf section 1.2.2: In typical IoT environments there can be multiple providers delivering values of the same attribute. Therefore, NGSI-10 allows the existence of multiple attributes having the same name. The way to distinguish these attribute values - called value instances in this document - is to include an ID in the form of metadata. More specifically, the ID of an attribute value is determined by the unique value of a metadata with Name “ID”. Does this means different Context Providers, each one managing an instance of the attribute, each Context Provider associated to a different IP? I mean, if we have "temperature" in 3 CPrs (CPr1, CPr2, CPr3) then we have attrName=temperature, ID=CPr1 managed by CPr1 attrName=temperature, ID=CPr2 managed by CPr2 attrName=temperature, ID=CPr3 managed by CPr3 Maybe my interpretation is incorrect. If you could provide a more detailed one and/or examples of a typical scenario or use case using attribute IDs, it would be great. Thanks! Best regards, ------ Fermín ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20150602/ceda109e/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy