2012.05 WP11: Data e-Infrastructures Integration and Interoperability Facilities Development Monthly Activity By Task and Beneficiary

From IMarine Wiki

Jump to: navigation, search

Contents

This WP11 Activity Report described the activities performed in May 2012 by Beneficiary and Task.

It is part of the Monthly Activity Report.

T11.1 Application Programming Interfaces Framework Definition

NKUA Activities

NKUA has continued work on HTTP Front End layer of the framework by extending the API to support both JSON and XML as standard interchange formats and by restructuring the whole architecture of the previous ASL HTTP component, based on the analysis performed during the previous month. Two new components have been developed within the HTTP Framework which offer common utils for managing the context of the HTTP operations to gCube, as well as handling common HTTP errors. Moreover, three new applications that derived from the previous analysis and logically group related functionality have been built and based on the principles of the framework and the common utilities offered. As predicted, the new components are: ASLHTTPAccessManagement, ASLHTTPInfrastructureLogin, ASLHTTTPInformationRetrieval, ASLHTTPContentAccess, ASLOAI_PMH, ASLOpenSearch

NKUA has also contributed in the production of D11.2 by documenting the functionalities and the components of the software released in the context of the Integration and Interoperability framework as well as their utility towards meeting the objectives of the framework.

Finally NKUA has collaborated closely with FAO to complete the design model for CLs and proceed with the impementation of a framework that complies with the design model. The implementation of a sample client library for the Search Service is ongoing and aims to provide more feedback to the framework design and usability.


None to report


Newly implemented components for HTTP Front End layer of the Integration and Interoperability Framework:

  • ASLHTTTPInformationRetrieval (ready to release)
  • ASLHTTPContentAccess (ready to release)
  • ASLOpenSearch (ready to release)

CNR Activities

CNR worked on the production of D11.2 describing the novelties and evolution of the Application Programming Interface Software up to M6.

The deliverable reports on the software released by WP11 as part of gCube release 2.9.0 and covering the following objectives:

  • decrease development costs
  • implement design solutions that simplify client usage
  • have the HTTP Front End as a layer of the Integration and Interoperability Framework
  • have new tools for developing consumers of features offered by gCube Services


D11.2 has not been released yet. It is still under review at FAO.


None to report.

CERN Activities

No activity to report.

E-IIS Activities

The design of client security API has been completed and has been added to the wiki page. After a first review and comments by some partners a discussion has been started in order to decide if minor improvements are necessary to better meet the requirements. ENG has accepted some proposals but the discussion is currently ongoing and the final version of the document should be available by the first days of June.


Discussion on the improvements of the client API model


A first version of Client Security API specification

FAO Activities

FAO has completed the design model for Client Libraries, insofar as the first iteration is concerned. The model is presented here: https://gcube.wiki.gcube-system.org/gcube/index.php/Integration_and_Interoperability_Facilities_Framework:_Client_Libraries_Design_Model. This reflects a close collaboration with NKUA and a contribution from ENG.

FAO has also completed the implementation of a framework for Client Libraries that comply with the design model. The framework is available in SVN as two libraries: common-clients and common-gcore-clients. FAO has also completed the WIKI documentation of the framework, now available here: https://gcube.wiki.gcube-system.org/gcube/index.php/Integration_and_Interoperability_Facilities_Framework:_Client_Libraries_Framework.

FAO has also started the verification of model and framework through implementations, including a a sample client library available in SVN as sample-gcore-client-lib and the re-factorisation of the tree-manager-library, which is ongoing. Verification has provided feedback to the model and the framework, which have evolved accordingly.


None to report.


- the completion of the design model, which marks its official release.

T11.2 Data Management APIs

FAO Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

CNR Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

NKUA Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

CERN Activities

Started adapting the CL Data Transfer Library to the CL Framework designed in the context of T11.1


None


None

E-IIS Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

FORTH Activities

No activity to report


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

Terradue Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

T11.3 Data Consumption APIs

CNR Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

NKUA Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

FORTH Activities

No activity to report


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

Terradue Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

FAO Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

Personal tools