2012.02 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 February 2012 by Beneficiary and Task.

It is part of February 2012 Activity Report.

T11.1 Application Programming Interfaces Framework Definition

NKUA Activities

During this period, NKUA finalized the composition of the working groups for all the layers of the framework targetted by the WP. Part of the activities focused on the analysis of the current Application Services Layer components and their architecture to identify the evolution needs towards integration and interoperability. Moreover, the design model of the CL layer of the framework has been of main concern and was prioritised through the discussions started within the CL working group.

In the context of the CL layer, the work done for clarifying the scope of the activities lead to the definition of the cross-cutting concerns for the design of the framework . This analysis guided the necessity for a distinguisment between a design model and a development model for the infrastructure CLs, for which participation in parallel discussions has been carried out.

In the context of the Application Service Layer framework, the initial discussions and the early analysis conducted the definition of the objectives and the actions of the related working group. Inspecting the adoption and development of ASL has been identified as the most deficient functionality and consequently as a main point of interest within the WP objectives.

The HTTP API framework has been revisited in terms of the current architecture and the design offered by Application Services Layer HTTP. The investigation lead to identification of needs for design extension, use and development control as well as extensions of rules governing the compliance to specifications and the adoption of standard data interchange formats (JSON). Finally, in the context of the Xsearch services analysis that will function on top of gCUbe Search system, the use cases analysis lead to the description of the conditions for the use of the OpenSearch implementation for gCube to satisfy the framed requirements.


None


None

CNR Activities

As member of WG 11.1, CNR participated in the discussion and gave feedback for the first draft of a model for Java client API (edited by FAO).

As assigned reviewer of D11.1, CNR provided input for and revised the table of content of the deliverable.


None to report


CERN Activities

CERN joined ASL and HTTP API Working Groups. Few discussions have been performed during the month.

CERN in collaboration with FAO spotted a missing NotificationLibrary integration on the new ghn-client-runtime library and helped in the testing of the Notification functionalities.


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.


None to report

FAO Activities

FAO has lead the definition of the charter for WG 11.1 and has produced a first draft of a model for Java client API that mediate access system services.

Still a work in progress, the draft already details:

  • the motivations, scope, assumptions that underlie the model, with corresponding terminology;
  • the proxy pattern that characterises its design;
  • the lifetime of service proxies;
  • the direct and discovery operation modes of service proxies;
  • the caching strategy required for service proxies that operate in discovery mode;
  • a discussion on the design scope for the API of service proxies with an example that illustrate possibilities;
  • a model of failures and a corresponding approach to failure handling;

A model for bulk operations, a model for a asynchronous operations, a model for access to lifetime operations and state properties of service instances, and models for scope and security management will follow.

The current draft can be found here and will migrated to the gCube wiki as soon as it reaches sufficiently stability and coverage.


None to report.


The definition of the WG charter and the first draft of the Client API Model.

T11.2 Data Management APIs

According to the methodology established in T11.1, this task provides input for the bottom-up approach of the framework definition process. The timeline of the task has been aligned to T11.1 and the activities on the Data Management API will be intensified in the next period of the project.


Activities of the task are essentially referenced in the work done in T11.1.


Alignment to the progress of T11.1.


None

T11.3 Data Consumption APIs

According to the methodology established in T11.1, this task provides input for the bottom-up approach of the framework definition process. The timeline of the task has been aligned to T11.1 and the activities on the Data Consumption API will be intensified in the next period of the project.


Activities of the task are essentially referenced in the work done in T11.1.


Alignment to the progress of T11.1.

Personal tools