This page will be used to host templates and other useful information during the course of the EOSC Future project.
EOSC-Core Interoperability Guideline Template
- What? A template that is used when describing specifications for the purposes of interoperating with EOSC-Core services. EOSC-Core guidelines should provide context and description in order to provide technical instructions to Providers that would like to integrate their services and/or resources with (or be interoperable with) one or more EOSC-Core Services (EOSC Federated AAI, Monitoring, Accounting, Helpdesk, Metrics, service and resource registries, Provider Portal, Marketplace, PIDs for services and the Knowledge Base registry).
- Who? For operators of EOSC-Core Services to provide guidance to Service and Resource Providers who wish to benefit from the functionalities that the EOSC-Core services offer.
EOSC-Exchange Interoperability Guideline Template
An EOSC-Exchange Interoperability Guideline (thematic/community) refers to where thematic or community services and resources interoperate with each other, usually at a domain level such as Cluster specific. These guidelines are understood to be created by scientific community experts to provide guidance to their communities and highlight the importance of their interoperability efforts at the European wide EOSC level. They are further intended to increase awareness of the existing thematic and community accomplishments to facilitate/increase interoperability relating to specific domains.
An EOSC-Exchange Interoperability Guideline (horizontal) refers to where services and resources interoperate with each other across communities and infrastructures. These are important at the EOSC Exchange level to help EOSC facilitate cross-linking of services and resources while staying domain agnostic. These are of wider applicability than the thematic/horizontal guidelines and have a much wider scope. These guidelines are understood to be created by scientific community experts to provide guidance to their own community and highlight their importance at the European wide EOSC level.
It is assumed that horizontal/thematic/community Interoperability Guidelines will be already established and published by an Infrastructure or Scientific Domain/Community, and therefore an author might not intend to write a new Interoperability Guideline for submission to the EOSC Interoperability Framework. However, it is conceivable that an existing Interoperability Guideline or collection of Guidelines would benefit from being structured into an EOSC Interoperability Guideline. In this case, a Word Template has been provided that is tailored towards Interoperability Guidelines produced under the EOSC Future project.