[Fiware-i2nd] proposal for S3C API harmonization

[jeanpierre.lerouzic at orange.com]

Hi Pier, Hans and all,

Philippe  and myself just discussed with about how to harmonize S3C's various components APIs.
We could provide a API specification that tries to harmonize most of (now) S3C internal APIs in a way loosely related to OneAPs  and building on existing APIs standards as much as possible.
Possible S3C internal APIs that could be harmonized are:
*       OpenEPC Platform<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/OpenEPC_Platform> (Jean-Pierre in charge).
*       Device Connection Platform<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Device_Connection_Platform>
*       Fast Telecom Service helper<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Fast_Telecom_Service_helper>.
*       Voicemail enabler<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Voicemail_enabler>.
*       Intelligent Network Identity Management <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Intelligent_Network_Identity_Management> .
*       Network-centric Resource Management <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Network-centric_Resource_Management> .
*       Seamless Network Connectivity <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Seamless_Network_Connectivity> .
*       Positioning Enabler <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Positioning_Enabler> .

We don't intend to provide an implementation for this new API overlay. We propose just to provide a specification of the API, without providing implementations for to connectors to S3C internal components. Our proposal is just to work for harmonization, as far it's practically possible, to extend GSMA's OneAPI with S3C internal components. Quite likely it will not cover all S3C components but it will improve the thing a bit further.

The outcome of that effort could be in December. To achieve it means we can access a comprehensive presentations of each internal APIs.

There are outcome possible:
*       To standardize this OneAPI extension
*       To create an implementation
Other people are probably more apt than us for those tasks.

What is your opinion on this proposal?

Best regards,

Philippe & Jean-Pierre



_________________________________________________________________________________________________________________________

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/old-fiware-i2nd/attachments/20120608/2dcda212/attachment.html>