Difference between revisions of "Data Consumption APIs"
From Gcube Wiki
(Created page with '== Overview == gCube Data Consumption APIs provide access to the consumption facilities of the e-Infrastructure resources by facilitating the integration of technology external t…') |
m |
||
(3 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
+ | [[Category:gCube Features]] | ||
== Overview == | == Overview == | ||
gCube Data Consumption APIs provide access to the consumption facilities of the e-Infrastructure resources by facilitating the integration of technology external to the e-Infrastructure. Towards the directions of openness and interoperability, consumption APIs move along: | gCube Data Consumption APIs provide access to the consumption facilities of the e-Infrastructure resources by facilitating the integration of technology external to the e-Infrastructure. Towards the directions of openness and interoperability, consumption APIs move along: | ||
Line 29: | Line 30: | ||
Data Consumption APIs are collectively delivered by the following sets of software subsystems: | Data Consumption APIs are collectively delivered by the following sets of software subsystems: | ||
− | [[Data Retrieval | + | [[Data Retrieval APIs]] |
− | [[Data Manipulation | + | |
− | + | [[Data Manipulation APIs]] | |
− | + | ||
− | [[Semantic Data Analysis | + | [[Semantic Data Analysis APIs]] |
Latest revision as of 10:26, 24 July 2013
Overview
gCube Data Consumption APIs provide access to the consumption facilities of the e-Infrastructure resources by facilitating the integration of technology external to the e-Infrastructure. Towards the directions of openness and interoperability, consumption 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 Consumption APIs are collectively delivered by the following sets of software subsystems: