Hi Konrad, Following your specs we have detailed in the googledoc linked below some tests on Gateway-Backend ETSI-M2M interaction. Let us know your comments and suggestions (maybe to add/delete/modify tests) so we get all ready for this week meeting in Madrid. Googledoc is at: https://docs.google.com/document/d/1qRWx8XKdwlgXNjkIbtDoL8fr28oWqsqcCu5f9bb Bflo/edit?pli=1# (our section is labeled as "Messages exchanged by GW Dev MAN and DCA/IDAS (BE Dev MAN)" at the end of the document). Best regards, -- --------------------------------------------------------------------------- --------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Blog: http://the-internet6.blogspot.com.es <http://the-internet6.blogspot.com.es/> Telefónica I+D SAU Madrid, Spain --------------------------------------------------------------------------- --------------------------------------------- Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu <http://www.fi-ware.eu/> Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 --------------------------------------------------------------------------- --------------------------------------------- El 24/03/14 16:11, "Konrad Campowsky" <konrad.campowsky at fokus.fraunhofer.de> escribió: >Hi Carlos, > >> Our question is if GW Dev Man GE has followed/is following that >> recommendation. In case they don't , could they please forward one with >> the same level of detail and XML examples ? > >The current GW Dev Man version actually implements said interfaces with >JSON as exchange data (which is also specified by ETSI). XML is planned >for R3.3. > >I'm attaching a document that has some examples in it. > >Best regards, >Konrad > >Am 20.03.2014 12:28, schrieb CARLOS RALLI UCENDO: >> Hi Thierry, >> >> As you already know, we are facing the implementation of ETSI-M2M >> protocol in IDAS as committed for R3.3. We have encountered the >>following: >> >> 1) In the FI-WARE specs description (URL right below) you can see the >> URL to be used but not specific examples of XMLs for devices >> registration/observations >> >> >>https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/ETSI_M2 >>M_mId_Open_RESTful_API_Specification_(PRELIMINARY) >> >> 2) However, in the standard document ETSI TR 102 966 V1.1.1 (2014-02) >> (downloaded >> from >>http://www.etsi.org/index.php/technologies-clusters/technologies/m2m) >> we can see how this can be implemented in detail and specific XML >>examples. >> >> Our idea then is to proceed with our implementation following the >> standard as described in the second point above. >> Our question is if GW Dev Man GE has followed/is following that >> recommendation. In case they don't , could they please forward one with >> the same level of detail and XML examples ? >> >> As we do not want to delay more this (it was planned for previous >> releases in the beginning), we have already started to implement it >> according to (2). However, any feedback *before 1 week * would be >> useful, as first there is some common code we need to do anyway. >> >> Thanks a lot for your feedback. >> Best regards, >> -- >> >> >>------------------------------------------------------------------------- >>----------------------------------------------- >> >> Carlos Ralli Ucendo (ralli at tid.es <mailto:ralli at tid.es>) >> >> Cell: +34696923588 >> >> Twitter: @carlosralli >> >> Blog: http://the-internet6.blogspot.com.es >> <http://the-internet6.blogspot.com.es/> >> >> Telefónica I+D SAU >> >> Madrid, Spain >> >> >>------------------------------------------------------------------------- >>----------------------------------------------- >> >> Follow FI-WARE project (Future Internet Services Core Platform): >> >> Website: http://www.fi-ware.eu <http://www.fi-ware.eu/> >> >> Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >> >> Twitter: @fiware >> >> LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >> >> >>------------------------------------------------------------------------- >>----------------------------------------------- >> >> >> ------------------------------------------------------------------------ >> >> 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 >> 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
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy