[Fiware-ngsi] Pub/Sub GE WP6 vs OMA NGSI & IoT

CARLOS RALLI UCENDO ralli at tid.es
Wed Feb 8 15:45:31 CET 2012


Thanks Boris,

We'll check the new conrib in the wiki.
Is it possible to have the .ppt you mention as well ?

Best regards,
--
------------------------------------------------------------------------------------------------------------------------
Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>)
Cell: +34696923588
Twitter: @carlosralli
Telefónica I+D SAU
Madrid, Spain
------------------------------------------------------------------------------------------------------------------------
Follow FI-WARE project (Future Internet Services Core Platform):
Website:  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 08/02/2012, a las 15:05, Moltchanov Boris escribió:

Dear All,

Telecom Italia is evaluating its Context Broker asset exposed as a core platform of the Publish/Subscribe interfaces against the “formal” OMA NGSI specification.

The most of the NGSI-9 and NGSI-10 functions are already supported by TI’s asset laying as basis of NGSI’s RD spec hence by Publish/Subscribe GE, however the API signatures are different. Therefore a certain decision regarding Publish/Subscribe GE vs (formal) NGSI will be taken soon and communicated to FI-WARE.

Meanwhile I’m also working on the Arch deliverable and soon will make it publicly announced within FI-WARE. Most probably we will start with what we have (context broker supporting most functions of NGSI, already RESTful with difference in names and parameters of the API calls) and then adapt it to both “formal” NGSI, even if there is no formal binding at all (thus any implementation is “valid” and not interworking) and ESPECIALLY to IoT specific reqs.

I wish then to have a rigorous evaluation of the currently exposed P/S GE description in forge FI-WARE wiki made me known over email, this thread or backlog registry, as far as we’re going to have one unique architectural P/S GE for entire FI-xxx domain maybe at maximum differently instantiated and implemented.

Stay tuned.

Best Regard,
Boris
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

<logo Ambiente_foglia.jpg>Rispetta l'ambiente. Non stampare questa mail se non è necessario.


<ATT00001..txt>


________________________________
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/20120208/9c9c47b2/attachment.html>


More information about the Fiware-ngsi mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy