[Fiware-ngsi] JSON

[laurent.artusio at orange.com]

Hi Fano,



My answer inline.



Best regards,



Laurent



-----Message d'origine-----
De : fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] De la part de fano.ramparany at orange.com
Envoyé : lundi 4 février 2013 19:44
À : Fermín Galán Márquez; fiware-ngsi at lists.fi-ware.eu
Objet : Re: [Fiware-ngsi] JSON



Hi,



In the context of the development of the semantic extension of the the PubSub GE semantic, we are developing a NGSI/XML to RDF/XML translator. To start with we are focusing on the NGSI/XML queryContextResponse...xml messages related to geolocation. We plan to use the "attributeDomainName" element as an hint to identify a geolocation context information.



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.



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.



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.



More generally, could we assume that the value of the "attributeDomainName" could be used as a way to anticipate what the "contextAttribute" names (in the "contextAttributeList") will be?



If it is the case, we can use this element to identify which ontology the target rdf will comply to and to use the corresponding "contextAttribute"s names as properties of the ontology or to find in an existing ontology the mapping between the properties of this ontology and the "contextAttribute" names.



Apart from geolocation, in the examples we have found messages tagged with "parcelStep" "attribute DomainName". We assume that we should elaborate the corresponding RDF in compliance with some supply chain ontology.



It would be interesting to do this translation exercise, with more NGSI/XML examples coming from UC projects which are using the PubSub GE, although the policy we currently foresee is that each UC project define its domain ontologies and we supply the project with a method to automate the transformation of the NGSI/XML content into RDF complying to this domain ontology.



Any feedback on this is more than welcome,



Thanks,



Fano



-----Message d'origine-----

De : fiware-ngsi-bounces at lists.fi-ware.eu<mailto:fiware-ngsi-bounces at lists.fi-ware.eu> [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] De la part de Fermín Galán Márquez Envoyé : mercredi 30 janvier 2013 15:32 À : fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu> Objet : [Fiware-ngsi] JSON



Hi,



We have a bunch of XML examples for our NGSI binding at https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/

but, what about JSON? Is there any similar bunch of example available in some place, please?



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

_______________________________________________

Fiware-ngsi mailing list

Fiware-ngsi at lists.fi-ware.eu<mailto:Fiware-ngsi at lists.fi-ware.eu>

http://lists.fi-ware.eu/listinfo/fiware-ngsi



_________________________________________________________________________________________________________________________



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.



_______________________________________________

Fiware-ngsi mailing list

Fiware-ngsi at lists.fi-ware.eu<mailto:Fiware-ngsi at lists.fi-ware.eu>

http://lists.fi-ware.eu/listinfo/fiware-ngsi

_________________________________________________________________________________________________________________________

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/20130205/17a42dc5/attachment.html>