EOSC services architecture DONATELLA CASTELLI CNRISTI RDA SYNCHONIZATION

EOSC services architecture DONATELLA CASTELLI CNR-ISTI RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS

Open Science “Open science makes scientific processes more efficient, transparent and effective by offering new tools for scientific collaboration, experiments and analysis and by making scientific knowledge more easily accessible” • Open collaborative science • scientists can use outcomes produced by others • scientists can contribute to the work initiated by someone else • Entire knowledge production chain • Validation & Reproducibility RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

EOSC Facts EOSC will be developed as a service-based commons; built as an ecosystem of existing and developing infrastructure and resources “with lightweight international guidance and governance and a large degree of freedom regarding practical implementation”. “Where public and private partners can offer FAIR services and components for the IFDS, under internationally agreed ‘Rules of Engagement’” (from GO-FAIR) EOSC will be open and dynamic (as any ecosystem) i. e. with respect to the services that it provides, the way in which the services are implemented, the users/communities it serves, in its components (infras and other resources) RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

EOSC services A variety of heterogeneous services § Identity related services § Discovery & access of resources (i. e. compute and storage, data, tools, services, workflows, …. ) § Resource management services § Data collection, integration, curation, … § Data analytics § Data publication § Data preservation (for different type of data e. g tabular, geospatial, statistcal, semantic, images, documents) EOSC § Scientific communication § Collaboration § Thematic services § …. . RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

“System of Systems” An ecosystem of interoperating infrastructures EOSC uses serves RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

Service Consumers EOSC “Certified”Services EOSC Lightweight Mediator Service Providers RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS

EOSCPilot Architecture Task To define a “Reference Architecture” Identification of • initial elements of the ecosystem • interconnections between these elements • necessary enabling components • existing gaps • best practices & recommendations RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

An evolutionary process New and revised e-/RI infrastructures + an established set of standards and bridges Currently existing e-/RI infrastructures + a minimal set of enablers and necessary bridges RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

RDA role • RDA as Open Science communication platform for • sharing the EOSCPilot proposed Architecture Task outcomes • gathering external contribution and validation RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

EOSC “own services” Service Catalogue • Mediators facilitating interoperability between infrastructures • Identity, authentication and authorization • Data Catalogue? , Infra/Provider Catalogue? • …. • RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

Service Catalogue It involves many aspects: ◦ ◦ ◦ How to define a service (terminology) How to describe services How to “certify” them How to implement the catalogue What protocol must be supported to collect items from other catalogues ……… Activity addressed in the context of many other projects: - EGI-ENGAGE, e. Infra. Central, EINFRACall 12 and horizontal (e. g. GEANT, EUDAT & Open. AIRE) and VRE projects RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

RDA support • Can the different projects involved cooperate through an RDA WGs? • Can this topic be addressed also at international level? • Can the CS scientific communty be more involved e. g. Research Data Service Discoverability Workshop: 21 -22 April 2016, Santorini, Greece RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

Interoperability between ecosystem components Interoperability (IEEE definition) The ability of two or more systems or components to exchange information and to use the information that has been exchanged Exchangeability: The two entities must be able to exchange meaningful information Compatibility: The two entities must be able to exchange logically consistent information (when the exchanged information is a description of functionality, policy, or behavior) (de-facto) standards/ best practices Mediators Usability: The user entity must be able to use the exchanged information to perform the tasks that depend on the Data structures, functionality, utilization of this information policies, protocols, ……. . RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

RDA support EOSCPilot will initially survey and analyse the services of horizontal einfrastructures (EGI, EUDAT, Open. AIRE, GEANT) and of a selected number of Research Infrastructures (e. g. CLARIN, EPOS, ICOS) to find out how they support exchangeability, compatibilty and usability. Can RDA can offer a more general forum to the selected and other e- & RIs for § discussing /agreeing on best practices § identify necessary mediators RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS CC BY-SA 4. 0

Thanks & Discussion RDA SYNCHONIZATION ASSEMBLY, 28 FEBRUARY 2017, BRUSSELS