[Fiware-ngsi] [Fiware-iot] Feedback about CampusParty [bad feedback regarding no JSON support in NGSI API...]

[Juanjo Hierro]

Hi all,

  I agree that defining a JSON binding for NGSI should be assigned the highest priority.    It will definitively lower the barriers for adoption.   Please start the discussion on the matter (I believe that fiware-ngsi is the proper list for doing so) so that we can publish a final open spec asap.

  Best regards,

-- Juanjo


On 11/09/13 18:01, Fermín Galán Márquez wrote:
Dear Talek,

(I'm CCing fiware-ngsi list, as I think the topic lies within its scope)

"By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward?"

I have direct feedback in that point from several talk with developers at Campus Party... and I'm afraid to tell that developers don't like XML rendering in REST APIs, as our current NGSI API is. In other words, developers love JSON (as is really easy to use from very popular languages as Python and JavaScript) and hate XML. However, nothing new here: we have been getting the same feedback from developers during about one year.

I think we desperately need a JSON rendering for NGSI to remove this adoption barrier. In this sense, our (TID) plan is the following:

  1.  Work on a .json "translation" for each one of the .xml in https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-9/ and https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-10/
  2.  Get feedback from you (i.e. people involved in NGSI in FI-WARE) in the hope we can reach a common agreement on the format
  3.  Implement the support of that format in Orion Context Broker

Best regards,

------
Fermín


El 11/09/2013 12:59, t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk> escribió:
Hello Carlos,

Looking back at the workshops, a guess a few points to look at would be:


·         To emphasize on example use cases on how the GEs can be used, in order to help better understand the purpose of the GEs and to stimulate ideas, by. The use case projects from at least the previous phase should provide a good reference for this.

·         To provide a "getting started" booklet  (hard copy...not just slides and wikis), from FI-LAB access to GE installation and instantiation to assure developers on how to setup, so they can focus on their idea and its implementation.

·         A running example for IoT.

Please correct me if any of these points were covered.

By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward?

Best regards,
Tarek



From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>
Sent: 11 September 2013 09:17
To: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: [Fiware-iot] Pictures from Campus Party

To have a look on how it was

Thierry Nagellen
Program Manager Future Internet
Orange Labs Networks & Carriers
905 rue Albert Einstein
06921 Sophia Antipolis Cedex
+33 492 94 52 84
+33 679 85 08 44


_________________________________________________________________________________________________________________________



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,

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, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.



_______________________________________________
Fiware-iot mailing list
Fiware-iot at lists.fi-ware.eu<mailto:Fiware-iot at lists.fi-ware.eu>
https://lists.fi-ware.eu/listinfo/fiware-iot



________________________________

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-iot mailing list
Fiware-iot at lists.fi-ware.eu<mailto:Fiware-iot at lists.fi-ware.eu>
https://lists.fi-ware.eu/listinfo/fiware-iot



________________________________

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/20130912/0b0fd4ef/attachment.html>