Welcome to the EOSC Future wiki!

On this page, you can find all the information related to the EOSC Future Horizon 2020 project (2021-2023).
Please note: This page contains information on the EOSC Portal and EOSC Catalogue and Marketplace, which have been phased out. For updates on the next phase of EOSC, please consult the official EOSC EU Node website: https://open-science-cloud.ec.europa.eu/

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: 

  • EOSC IF guidelines are based on existing mature  guidelines (do not reinvent the wheel)
  • EOSC IF guidelines are widely adopted recommendations within the research community
  • EOSC IF  guidelines are accepted on basis of the consensus principle
  • EOSC IF guidelines should be based on well-adopted open standards. 

Types of guideline:

  • EOSC IF Core guidelines: Interoperability guidelines that need to be followed and implemented in order to make use of and/or integrate with EOSC Core provided services and capabilities
  • EOSC IF Interoperability guidelines: Generic Interoperability guidelines and best practices. These guidelines are organised in Interoperability Areas.
  • EOSC IF Community guidelines: Community defined and maintained guidelines. EOSC provides a platform via where Communities can register and promote their guidelines for adoption in EOSC.

Procedure:

1. Proposal submission - Proposer requests inclusion of new guidelines to be included in the EOSC IF
2. Review process - New requests are reviewed in terms of technical quality and clarity, and are assessed as to whether they are consistent with the expectation of EOSC IF guidelines
3. Endorsement process - New guidelines are discussed within the EIAC and if approved submitted to the EIAB for endorsement
4. Publication process - Adopted guidelines are announced via the EOSC channels


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:

  • endorsement of new guidelines
  • deprecation of guidelines, 

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
  • Ensuring the EOSC IF is fit for purpose.
  • Ownership of the inclusion criteria for guidelines to become included in the EOSC IF.
  • Assessment and consideration of EIAC's recommendation for the inclusion/exclusion of EOSC Interoperability Guidelines.
  • Process owner (Process for Inclusion in Interoperability Registry)
  • Ownership of the Data Model for recording an interoperability guideline in the EOSC IF Registry.
  • Ownership of the EOSC Core Guideline template
  • Initial review and assessment of proposed EOSC Interoperability Guidelines (inline with the agreed inclusion criteria*)
  • Process manager (Process for Inclusion in Interoperability Registry)
  • Contribute to developing the EOSC Core Guideline template
  • Own the EOSC IF Glossary
Outside Remit
  • Technical assessment of proposed/recommended EOSC Interoperability Guidelines
  • Oversight or assessment of services/resources' compliance towards EIGs
  • Detailed technical validation of proposed/recommended EOSC Interoperability Guidelines*
  • Oversight or assessment of services/resources' compliance towards EIGs
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:

  • Liaison with the EIAC.
  • Consideration of proposals recommended by the EIAC.
  • Documenting and communicating the decision to the EIAC,

The core activities of the EIAC include:

  • Liaison with the Proposer and resolution of queries throughout the process
  • Consideration of proposals submitted by Interoperability Guideline owners/guardians based on:
    • Impact analysis
    • Maturity assessment
    • Interoperability assessment
    • Uptake assessment
  • Identify the need for additional community consultation
  • Apply agreed acceptance criteria to each proposal considered
  • Documenting the outcome of the review and provision of feedback to the proposer
  • Preparing for any further community consultation
  • Ratification and post-ratification activities, including the mobilisation of communications collaborators to publish the outcome and ensuring registration is administered in the agreed format.
Support the EIAC in reviewing Guidelines and Best Practices proposed as EIGs against the acceptance criteria
Working methodologyThe 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:
  • Recommendations from the EOSC Interoperability Area Chairs (EIAC)
  • Feedback from stakeholder forums* as regards the fitness for purpose of the EIF and the EIF Registry.

*TBD

  • EIG Proposals

Outputs:
  • Endorsement/rejection of recommended EOSC Interoperability Guidelines
  • Policies to facilitate interoperability, including inclusion criteria.
  • Recommendations for inclusion/exclusion to the EIAB

Interfaces:
  • The EIAB
  • EOSC Interoperability Core Guideline Owners/Guardians/Proposers
  • Community channels, where it will be possible for stakeholders to comment on proposals.

Editorial Board to assist the EIAC; no direct interaction with EIAB

DecisionsDecisions 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:

  • Composition - TBD during the EOSC Future project
  • Tenure - TBD during the EOSC Future project

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:

  • Composition - TBD during the EOSC Future project
  • Tenure - TBD during the EOSC Future project

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.

From: https://wiki.eoscfuture.eu/display/EOSCF/EOSC+Future+Project+Deliverables?preview=/9046291/18940504/EOSC%20Future-WP3-GEANT-D3.2a%20EOSC%20Architecture%20and%20Interoperability%20Framework-2021-12-22.pdf

Change log:

DateChangeMade 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
20220720Updated the members of the initial EIACM. Williams
20230221Updated the members of the initial EIAC to remove L.Florio (no longer WP3 Lead).M. Williams
20230829Update to Scope sectionM. Williams
  • No labels

Privacy Policy