EOSC Future working groups were set up to define the guidelines and standards for an EOSC architecture and interoperability framework that not only meets the functional requirements for cross-community utilisation but also is technically compatible.
A central pillar of the project, our working groups focused on what we need – right now – to meet 4 objectives:
- continuously enhance the overarching federated EOSC architecture by collecting functional cross-community requirements within/beyond the project
- liaise with the relevant project stakeholders (clusters, e-infrastructures, research infrastructures) and other stakeholders (RDA, EOSC Association, FIM4R, CODATA)
- define and continuously improve the Interoperability Framework
- ensure that functional requirements from the cross-community use cases are known, compatible and technically interoperable.
In practice, our working groups took a bottom-up approach to liaising and aligning with different clusters, project partners and other members of the EOSC community; specifically:
- science projects and use cases
- research product publishing framework
- metadata
- the compute continuum.
More working group proposals appeared in other areas of interest such as:
- persistent identifiers (PIDs)
- authentication and authorisation infrastructure (AAI)
- composability (EOSC Execution Framework to facilitate cross-cluster resource composition)
- container deployment (standard interfaces to deploy and manage container clusters in EOSC)
- security
- FAIR data.
Find out more
You can visit the EOSC Future working groups public wiki page.