[Fiware-ngsi] JSON

[fano.ramparany at orange.com]

Hi Laurent and all,

De : ARTUSIO Laurent OLNC/OLPS
Envoyé : mardi 5 février 2013 11:33
...

We have a first question about this: is there a reason for introducing 2 different values of this element related to geolocation? Namely: parcelGeo, geolocation? Why don't we simply use geolocation?



Laurence and I made these queryContextResponse examples. There is no particular reason for which we set the attributeDomainName with the values you mentioned. The EntityId type has a strong meaning to us (group of all possible attributes for a given EntityId), whereas the attributeDomainName field was filled in mainly for xml parsing testing purposes.



[FR]: About the meaning of EntityId, this echoes with a discussion we had at the beginning of the project about a generic data model and about the distinction between data, event and context. If I remember well,  context is data that should always be related to an entity.



The OMA NGSI spec defines the AttributeDomainName as a the "name of the attribute domain that logically groups together set of Context Information attributes". But when querying an entityId with the ngsi-10 queryContext method, you don't have the possibility to pass an attributeDomainName in argument. Instead you directly ask for the names of the requested attributes, as an array of strings.



[FR]: does it mean that this element "attributeDomainName" might sometimes be absent in the queryResponse? (which is what Tobias recent feedback to this thread suggests).



If you prefer to use "geolocation" as attributeDomainName for both messages you mentioned, it is not a problem for us. It makes sense:both messages feature location ContextAttributes (latitude, longitude)



I would like to correct this in the svn according to your remark, but I can't get connected to it, probably because of Orange proxy issues. Hope it's temporary.



[FR]: no worries, if we finally use this element in the parser which might not be a good idea according to the above discussion, it simply means that we'll have to handle synonyms.



Best regards,

Fano



_________________________________________________________________________________________________________________________

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,
France Telecom - 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, France Telecom - 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/20130207/2a2f4ebf/attachment.html>