T31 Telco April 25th 2013
Iosif, Michael, Fenareti (NTUA)
Philip (Betabond)
Meletis, Timotheos (Velti)
Johannes, Lukasz (FOKUS)
Suzana, Beatriz, Claudia (CGI)
Iosif starts with an introduction on the telco. He suggests that the implementation should be extendable and agnostic of the services.
Johannes makes a presentation about class based API
Johannes agrees in interoperability. He suggests that the unification of APIs will not work. He shows his presentation on cloudlet data ( class based approach . Each developer should declare their own schema for every application, and a new application should be inline with another schema if it needs to access the same data. Talking about a hybrid approach, both fixed schema and an extensibility on attributes. All agree that the schema should first agree with all the use cases. Philip O'Brien agrees on this approach.
Timos asks how other developers will be able to find out about the schema of the data they need. And he also asks about free text queries.
Johannes discusses about scalability issues of the above approach and the graph one. Namespaces. Register and schema Lookup.
Iosif comments about the usage of the recommender and suggests it should be developed outside the main process. He agrees on the xmpp approach, also as a solution for the namespaces
He suggest to move forward with a Generic API with static objects, and a Cloudlet API which will be more dynamic and will allow developers to create schemas, depending on the implementation.
Meletis Margaritis asks about query language on schema. Johannes answers that the schema could be open, or open with restrictions. Discovery service for schemas. Share access with other applications.
Iosif describes the Facebook approach, where developers have to get approval for new objects and verbs, while every developer can see only his objects & verbs.
Partners agreed to study Johannes' approach and come back later with WP3 partners, to reach an agreement, as there is dependency with architectural and implementation decisions.
Suzana makes a presentation on the service enablers
Suzana presented on Redmine, the identification of all service enablers. For them, Logica has chosen based on Developers' interaction and priorities for platforms which APIs are going to be described for 3.1. Authentication, Authorization and Monitoring are the first three categories they will focus as agreed on previous telco.
NTUA & Velti are going to give feedback based on their wiki entry and leave comments. Iosif pointed out that the Context API is considered something different than described in the wiki, but a position will be presented after discussion with Velti.
Conclusions:
A class based approach for APIs, with developers to be capable to create schemas, objects & verbs are grouped under the Cloudlet API. The generic APIs continue to be described, and static structures will be described, even if all these resolve under the same schema. Partners will work on the suggested approaches and will share their views on Tuesday telco.