Difference between revisions of "GCube Web Specifications and Standards Compliance"
(→Data Consumption) |
(→OAI-PMH) |
||
| Line 11: | Line 11: | ||
|} | |} | ||
==OAI-PMH== | ==OAI-PMH== | ||
| − | * Use/Need/Relevance | + | * '''Use/Need/Relevance''' |
Through OAI-PMH protocol, gCube infrastructure acts as a 'Data Provider' and disseminates its hosted metadata records in a standard fashion, thus allowing for interoperation with other data e-Infrastructures that run autonomously. Other infrasturctures can harvest the metadata descriptions of gCube content in archives so that their services can exploit the gCube collections. The protocol provides an application-independent interoperability framework for metadata exchange between the online parties. | Through OAI-PMH protocol, gCube infrastructure acts as a 'Data Provider' and disseminates its hosted metadata records in a standard fashion, thus allowing for interoperation with other data e-Infrastructures that run autonomously. Other infrasturctures can harvest the metadata descriptions of gCube content in archives so that their services can exploit the gCube collections. The protocol provides an application-independent interoperability framework for metadata exchange between the online parties. | ||
| − | * Direction | + | * '''Direction''' |
Producer | Producer | ||
| − | * Specification Info | + | * '''Specification Info''' |
The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a well-established standard in the content management and library science worlds that is gaining in importance. It provides a low-barrier mechanism for repository interoperability and defines the following parties and software components: | The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a well-established standard in the content management and library science worlds that is gaining in importance. It provides a low-barrier mechanism for repository interoperability and defines the following parties and software components: | ||
| − | * Data Providers are repositories that expose structured metadata via OAI-PMH. A 'Data Provider' such as an academic library runs a Repository that supports OAI-PMH as a means of exposing metadata information about resources, for instance academic publications. | + | ** Data Providers are repositories that expose structured metadata via OAI-PMH. A 'Data Provider' such as an academic library runs a Repository that supports OAI-PMH as a means of exposing metadata information about resources, for instance academic publications. |
| − | * Service Providers then make OAI-PMH service requests to harvest that metadata. A 'Service Provider' uses Harvester software to harvest metadata from Data Providers. The harvested metadata can then be used to provide valued-added services, such as a website that allows browsing and searching through their catalog. | + | ** Service Providers then make OAI-PMH service requests to harvest that metadata. A 'Service Provider' uses Harvester software to harvest metadata from Data Providers. The harvested metadata can then be used to provide valued-added services, such as a website that allows browsing and searching through their catalog. |
OAI-PMH is a set of six verbs or services that are invoked within HTTP. An implementation of OAI-PMH must support representing metadata in Dublin Core, but may also support additional representations. | OAI-PMH is a set of six verbs or services that are invoked within HTTP. An implementation of OAI-PMH must support representing metadata in Dublin Core, but may also support additional representations. | ||
Revision as of 14:53, 18 September 2012
This area collects the Standard Specifications supported by the gCube system APIs, as part of the WP11 activities and towards meeting the integration and interoperability objectives for promoting the openness of the e-Infrastructure to other neighbouring and external ones. The collection focuses on the widely used, HTTP-based Specifications and generic interchange protocols (data/content standards, metadata standards, Web interface standards, security standards, data sharing protocols) that service both disseminating and consuming system's needs. This analysis is conducted per functional category and addresses the use, need and relevance of the standards tha fall under each area.
Contents
Data Consumption
| Specification Label | Direction towards the System (Producer/Consumer) | Status of System Adoption (Completed/ On going/ Planed) |
| OAI-PMH | Producer | Completed |
OAI-PMH
- Use/Need/Relevance
Through OAI-PMH protocol, gCube infrastructure acts as a 'Data Provider' and disseminates its hosted metadata records in a standard fashion, thus allowing for interoperation with other data e-Infrastructures that run autonomously. Other infrasturctures can harvest the metadata descriptions of gCube content in archives so that their services can exploit the gCube collections. The protocol provides an application-independent interoperability framework for metadata exchange between the online parties.
- Direction
Producer
- Specification Info
The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a well-established standard in the content management and library science worlds that is gaining in importance. It provides a low-barrier mechanism for repository interoperability and defines the following parties and software components:
- Data Providers are repositories that expose structured metadata via OAI-PMH. A 'Data Provider' such as an academic library runs a Repository that supports OAI-PMH as a means of exposing metadata information about resources, for instance academic publications.
- Service Providers then make OAI-PMH service requests to harvest that metadata. A 'Service Provider' uses Harvester software to harvest metadata from Data Providers. The harvested metadata can then be used to provide valued-added services, such as a website that allows browsing and searching through their catalog.
OAI-PMH is a set of six verbs or services that are invoked within HTTP. An implementation of OAI-PMH must support representing metadata in Dublin Core, but may also support additional representations.
- Information about status of adoption of Specification within Our system
Whether the specification has already been integrated and supported within the system, or it is under implementation, or soon to be implemented.
- List of components affected / relevant
Data Management
| Specification Label | Direction towards the System (Producer/Consumer) | Status of System Adoption |
| Protocol | Producer |
Protocol
- Use/Need/Relevance
Describe the use/need/relevance of the specification in respect to the functional area of the system.
- Direction
The direction towards the system (Producer/consumer).
- Specification Info
Description and useful information about the Specification.
- Information about status of adoption of Specification within Our system
Whether the specification has already been integrated and supported within the system, or it is under implementation, or soon to be implemented.
- List of components affected / relevant
Computation Consumption
| Specification Label | Direction towards the System (Producer/Consumer) | Status of System Adoption |
| Protocol | Producer |
Protocol
- Use/Need/Relevance
Describe the use/need/relevance of the specification in respect to the functional area of the system.
- Direction
The direction towards the system (Producer/consumer).
- Specification Info
Description and useful information about the Specification.
- Information about status of adoption of Specification within Our system
Whether the specification has already been integrated and supported within the system, or it is under implementation, or soon to be implemented.
- List of components affected / relevant
Infrastructure Management
| Specification Label | Direction towards the System (Producer/Consumer) | Status of System Adoption |
| Protocol | Producer |
Protocol
- Use/Need/Relevance
Describe the use/need/relevance of the specification in respect to the functional area of the system.
- Direction
The direction towards the system (Producer/consumer).
- Specification Info
Description and useful information about the Specification.
- Information about status of adoption of Specification within Our system
Whether the specification has already been integrated and supported within the system, or it is under implementation, or soon to be implemented.
- List of components affected / relevant
