Difference between revisions of "Data Management APIs"
From Gcube Wiki
(→Key Features) |
m |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:gCube Features]] | ||
== Overview == | == Overview == | ||
gCube Data Management APIs provide access to the management of the e-Infrastructure resources by facilitating the integration of technology external to the e-Infrastructure. Towards the directions of openness and interoperability, management APIs move along: | gCube Data Management APIs provide access to the management of the e-Infrastructure resources by facilitating the integration of technology external to the e-Infrastructure. Towards the directions of openness and interoperability, management APIs move along: | ||
| Line 6: | Line 7: | ||
==Key Features== | ==Key Features== | ||
| − | ;Consistency | + | ;Consistency across different client APIs |
:Uniformity for APIs across standalone framework layers in inputs and outpus, context management, fault management, operation modes provision, etc. | :Uniformity for APIs across standalone framework layers in inputs and outpus, context management, fault management, operation modes provision, etc. | ||
| − | ;Transparent system | + | ;Transparent system integration |
:Design of APIs simplifying client usage, with respect to requirements specific to the system | :Design of APIs simplifying client usage, with respect to requirements specific to the system | ||
| Line 15: | Line 16: | ||
:Operational information among services transparently propagated over a range of protocols (SOAP, HTTP/S, and more) | :Operational information among services transparently propagated over a range of protocols (SOAP, HTTP/S, and more) | ||
| − | ;Testability | + | ;Testability ensuring |
:Design solutions that facilitate testing for clients | :Design solutions that facilitate testing for clients | ||
| Line 21: | Line 22: | ||
:Crucial functionalities are accessible via recognized standards in order to enhance interoperability | :Crucial functionalities are accessible via recognized standards in order to enhance interoperability | ||
| − | ; | + | ;Compatibility endorsement |
| − | : | + | :Exploitation of framework simplifying building of modular systems |
| + | |||
| + | ; | ||
==Subsystems== | ==Subsystems== | ||
Data Management APIs are collectively delivered by the following sets of software subsystems: | Data Management APIs are collectively delivered by the following sets of software subsystems: | ||
| − | |||
| − | |||
[[Data Access and Storage APIs]] | [[Data Access and Storage APIs]] | ||
[[Data Transfer APIs]] | [[Data Transfer APIs]] | ||
| + | |||
| + | [[Data Assessment and Harmonisation APIs]] | ||
Latest revision as of 09:25, 24 July 2013
Overview
gCube Data Management APIs provide access to the management of the e-Infrastructure resources by facilitating the integration of technology external to the e-Infrastructure. Towards the directions of openness and interoperability, management APIs move along:
- the adoption of standards
- the implementation of a variety of protocols (e.g. Java, REST, SOAP, depending on the need and relevance)
- the compliance to the Integration and Interoperability Facilities Framework
Key Features
- Consistency across different client APIs
- Uniformity for APIs across standalone framework layers in inputs and outpus, context management, fault management, operation modes provision, etc.
- Transparent system integration
- Design of APIs simplifying client usage, with respect to requirements specific to the system
- Environment propagation
- Operational information among services transparently propagated over a range of protocols (SOAP, HTTP/S, and more)
- Testability ensuring
- Design solutions that facilitate testing for clients
- Support to standards
- Crucial functionalities are accessible via recognized standards in order to enhance interoperability
- Compatibility endorsement
- Exploitation of framework simplifying building of modular systems
Subsystems
Data Management APIs are collectively delivered by the following sets of software subsystems:
