Background | Scope: The EOSC Interoperability Framework aims to provide a set of recommendations on the components that need to be provided in the ecosystem and on the principles that guide resource producers and/or consumers on their use, in order for the framework to set a foundation for an efficient machine-actionable exchange of resources within EOSC and between EOSC and the outside world. The EOSC Interoperability Framework governing bodies described herein shall be in place for the duration of the EOSC Future project, and it was envisaged that the composition and charter of the bodies for governance beyond the EOSC Future project would be determined by the HORIZON-INFRA-2023-EOSC-01-05 EOSC Architecture and Interoperability Framework call. Objectives: Maintain and promote a set of guidelines to support interoperability and composability between resources (e.g. services and research artefacts) within EOSC. Offer a platform for communities and RIs to promote their guidelines within EOSC. Principles:
Types of guideline:
Procedure: 1. Proposal submission - Proposer requests inclusion of new guidelines to be included in the EOSC IF |
EOSC Interoperability Advisory Board (EIAB) | EOSC Interoperability Area Chairs EIAC | EOSC IF Editorial Board | |
---|---|---|---|
Main aims | The overarching goal of the EOSC Interoperability Advisory Board is to oversee the evolution of the EOSC IF; its outputs are based on the recommendations of the EIAC and result in:
The EIAB will contribute to the practical and tangible aspects of establishing interoperability for EOSC services and resources. | The overarching goal of the EOSC Interoperability Area Chairs (EIAC) is to perform the initial assessment of proposed guidelines, making recommendations for inclusion/exclusion to the EIAB. | Support the EIAC in reviewing Guidelines and Best Practices proposed as EIGs against the acceptance criteria |
Remit |
|
|
|
Outside Remit |
|
| Performing a peer reviewer role for specific Guidelines; it is assumed that community guidelines are peer reviewed prior to their submission as EOSC Interoperability Guidelines. |
Core activities | The core activities of the EIAB include:
| The core activities of the EIAC include:
| Support the EIAC in reviewing Guidelines and Best Practices proposed as EIGs against the acceptance criteria |
Working methodology | The day-to-day collaboration of the EIAB will happen through a proprietary mailing list. A regular video conference call will be used to coordinate the work. The time slot and frequency of calls will be decided by the members with the focus to allow for short incremental steps and quick feedback cycles. | The day-to-day collaboration of the EIAC will happen through a proprietary mailing list. A regular video conference call will be used to coordinate the work. The time slot and frequency of calls will be decided by the members with the focus to allow for short incremental steps and quick feedback cycles. | |
Inputs: |
*TBD |
| |
Outputs: |
|
| |
Interfaces: |
|
| Editorial Board to assist the EIAC; no direct interaction with EIAB |
Decisions | Decisions in the EIAB will be based on the principle of rough consensus to be determined by the members and will be communicated via formal EOSC communication channels as appropriate. | Decisions in the EIAC will be based on the principle of rough consensus to be determined by the members and will be communicated via proprietary channels*, such as open 'EOSC IF Announce'-style mailing lists via which proposed guidelines and accepted guidelines are communicated. *TBD | |
Dependencies | |||
Membership | Initially, the EOSC Future TCB. After that:
| Initially, the EOSC Future WP3 Task Leads. Michelle Williams, WP3 WPL and T1 Christos Kanellopoulos, WP3 T1 and WP7 (for AAI) Mark van de Sanden, WP3 (for RoP and PID) Diego Scardaci, WP3 T2 Kostas Koumanatros, WP3 T2 Mark Dietrich, WP3 T2 Jonathan Tedds, WP3 T3 Paolo Manghi, WP4 Pavel Weber, WP4 Roksana Wilk, WP4/5 George Papastefanatos, WP4/5 After that:
| Volunteers from WP3 in the first instance. Members must not be members of either the EIAC or EIAB. |
Responsibilities of the Proposer/Guardian:
- To ensure that the registered guideline is well-maintained.
- To be the single liaison point for the EIAB in the event of any queries raised regarding either the proposal or the proposed guideline.
- Upon acceptance, to maintain the related metadata with appropriate frequency, particularly regarding versioning or lifecycle status.
Change log:
Date | Change | Made by |
---|---|---|
20220607 | Updated the scope to reflect comment from the TCB to ensure that it is clear that this governance is scoped to the governance of the EOSC IF under the EOSC Future project. | M. Williams |
20220720 | Updated the members of the initial EIAC | M. Williams |
20230221 | Updated the members of the initial EIAC to remove L.Florio (no longer WP3 Lead). | M. Williams |
20230829 | Update to Scope section | M. Williams |