[Fiware-ngsi] ConfMan GE associations detailed interaction

[Fermín Galán Márquez]

Dear Raihan,

The main part to agree was in the XML request/responses so I'm happy to see that it's ok with you. I don't think that the current discussion about interpretation of TARGET scope impacts in these XMLs (as I told in previous emails, no matter the resolution of that discussion, IoTBroker-ConfMan use case it doesn't affected).

Regarding Content-Type, currently we only support "application/x-www-form-urlencoded", but we are considering to support also "application/xml" in the future.

Thanks!

Best regards,

------
Fermín

El 25/04/2013 17:09, Raihan Ul-Islam escribió:
Hi Fermin,


We prefer to use "application/xml" as "Content-Type" instead of "application/x-www-form-urlencoded". Otherwise, the examples seems to be ok based on the scenario.

As we are still discussing on the association concept, there might be change in the xml schema.  If any changes is required I hope we can address it.


Thanks
Raihan
From: Fermín Galán Márquez [mailto:fermin at tid.es]
Sent: 25 April 2013 15:58
To: Raihan Ul-Islam; Tobias Jacobs
Cc: fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu>
Subject: Re: [Fiware-ngsi] ConfMan GE associations detailed interaction

Dear Raihan, Tobias,

Have you had a look on this? We are about to start the work to implement associations in ConfMan and it will be great if we could know if the sequence in the .test files is ok with you.

Thanks!

Best regards,

------
Fermín

El 23/04/2013 9:49, Fermín Galán Márquez escribió:
Hi,

We have defined a couple of files with the expected interaction for ConfMan GE to implement the IoT Broker uses cases related with query and update, based on the Raihan document:

https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-9/associations-examples/assoc-query-things-case.test
https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-9/associations-examples/assoc-update-things-case.test

In each one of these files there are two sections:

  *   SHELL: contains a sequence of request to be sent to ConfMan GE. Each request is "encapsulated" withing a curl common (in the real case, IoT Broker will do these requests). It is assumed that before starting the first request in the SHELL section, the ConfMan GE has no previous state (i.e. as it is has been just started).
  *   REGEXPECT: the expected output that will be obtained when the SHELL section is executed, literally except for the REGEX() tokens, which match regular expressions within the parenthesis. In particular, we use REGEX([0-9a-f]{24}) (i.e. 24 hex digits) for IDs.

We will use these files to guide our implementation (in fact, these files will feed our test harness framework in charge of automatic testing our software) so it would be great if you could have a look to it to know if they are ok with you or if you detect any problem (so we don't get any undesirable surprise at integration time ;).

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>

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

________________________________

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


________________________________

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/20130426/4f7eee05/attachment.html>