GCube Integration and Interoperability Working Groups
The following working groups contribute to the definition and implementation of the gCube Integration and Interoperability Facilities.
In particular, the following ones have been established:
- Framework Definition WG
- Level-driven Working Groups
- Functionality-driven Working Groups
Framework Definition Working Group
The objective of the Framework Definition Working Group is to deliver the specification of the Integration and Interoperability Framework.
TO BE REFINED AND COMPLETED
Tasks
- Coordination of activity
- Establishment of principles of framework, by homogenization of products of other working groups.
- Establishment of procedures for framework development, evolution and maintenance.
- Delivery of overall framework specification
Group Members
- George Kakaletris (NKUA)
- to be defined
- to be defined
- to be defined
Client Libraries Working Group
The Client Libraries (CL) WG objective is to establish the principles for delivering uniform, consistent client libraries for services that comprise the gCube system.
Tasks
The tasks of the group are to:
- analyze existing CLs, either by experience of the group members or by querying gCube developers for contribution.
- analyze and comprehend the plans for the development of new CLs that will emerge from other RTD workpackages.
- identify heterogeneities in existing CLs.
- identify opportunities and needs for homogenization of CLs.
- suggest the principles for CL development, laying out guidelines in topics such as: API design, architecture, documentation, development and release procedure.
- suggest the implementation of a common toolkit to support the principles for CL development.
- sugest a formal CL development framework, as a combination of principles in design, tools and procedures.
- suggest a plan for evolution of existing CLs into the new framework.
- suggest a procedure for validation of CL development along the lines of the new framework.
- apply the procedure for validation of CL development, via monitoring the application of the CL development framework.
- evolve the framework throughout the project lifetime, as a response to feedback and further development.
Group Members
- Fabio Simeoni (FAO)
- Manuele Simi (CNR)
- Ciro Formisano (ENG)
- Rena Tsantouli (NKUA)
Application Service Layer Specification Working Group
The objective of the Application Service Layer Working Group is to update the specification of the ASL along the principles of the Integration and Interoperability Framework Methodology.
TO BE REFINED AND COMPLETED
Tasks
- ----
- ----
- ----
- ----
Group Members
- Rena Tsantouli (NKUA)
- Andrea Manzi (CERN)
- Massimiliano Assante (CNR)
HTTP APIs Working Group
The objective of the Framework Definition Working Group is to coordinate and validate the work of Case-specific working groups for delivering public HTTP APIs.
TO BE REFINED AND COMPLETED
Tasks
The tasks of the Working Group include:
- Establish the principles for the design, development of
- Analyze existing APIs, either by experience of the group members or by querying gCube developers for contribution.
- Analyze and comprehend the plans for the development of new HTTP APIs that will emerge from other RTD workpackages.
- Identify opportunities and needs for homogenization of HTTP APIs.
- Suggest the principles for HTTP API development, laying out guidelines in topics such as: API design, architecture, documentation, deployment, specification adoption, development and release procedure.
- suggest the implementation of a common toolkit to support the principles for HTTP API development (if needed).
- sugest a formal HTTP API development framework, as a combination of principles in design, tools and procedures.
- suggest a plan for evolution of existing HTTP APIs into the new framework, if needed.
- suggest a procedure for validation of HTTP API development along the lines of the new framework.
- apply the procedure for validation of HTTP API development, via monitoring the application of the framework principles.
- evolve the framework throughout the project lifetime, as a response to feedback and further development.
- maintain an agreegated HTTP API report, enumerating the standards compliant with the gCube system
Group Members
- Rena Tsantouli (NKUA)
- Andrea Manzi (CERN)
- To be defined
Functionality-driven Working Groups
Data Management APIs
Members of this Working Group are called to
- contribute to the definition of Integration and Interoperability: Data Management APIs
Group Members
- FAO: Fabio Simeoni
- CNR: Federico Defaveri, Lucio Lelii
- NKUA: Gerasimos Farantatos, Yannis Gerbesiotis
- E-IIS: Ciro Formisano
- FORTH: Yannis Marketakis
- Terradue: Fabrice Brito, Fransesco Barchetta
- CERN: Andrea Manzi
Data Consumption APIs
Members of this Working Group are called to
- contribute to the definition of Integration and Interoperability: Data Consumption APIs
Group Members
- CNR: Gianpaolo Coro, Fabio Sinibaldi
- NKUA: Alex Antoniadis, Gerasimos Farantatos
- FORTH: Yannis Marketakis
- Terradue: Francesco Barchetta, Fabrice Brito
- FAO: Erik Vaningen, Claudio Baldassarre
Computation Consumption APIs
Members of this Working Group are called to
- contribute to the definition of Integration and Interoperability: Computation Consumption APIs
Group Members
- NKUA: Gerasimos Farantatos
- Terradue: Francesco Barchetta, Fabrice Brito
Infrastructure Management APIs
Members of this Working Group are called to
- contribute to the definition of Integration and Interoperability: Infrastructure Management APIs
Group Members
- CERN: Andrea Manzi
- CNR: Manuele Simi
- E-IIS: Ciro Formisano
