1. EOSC services architecture
DoNatella CastelLI
CNR-ISTI
RDA Synchonization Assembly, 28 February 2017, Brussels

2. 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

3. RDA Synchonization Assembly, 28 February 2017, Brussels
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

4. RDA Synchonization Assembly, 28 February 2017, Brussels
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)
Scientific communication
Collaboration
Thematic services
…..
EOSC
RDA Synchonization Assembly, 28 February 2017, Brussels

5. EOSC “System of Systems”
An ecosystem of interoperating infrastructures
uses
serves
RDA Synchonization Assembly, 28 February 2017, Brussels

6. EOSC “Certified”Services EOSC Services
Service Consumers
EOSC “Certified”Services
EOSC Services
EOSC Lightweight Mediator
Service Providers
RDA Synchonization Assembly, 28 February 2017, Brussels

7. 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

8. An evolutionary process
Currently existing e-/RI infrastructures +
a minimal set of enablers and necessary bridges
New and revised e-/RI infrastructures +
an established set of standards and bridges
RDA Synchonization Assembly, 28 February 2017, Brussels

9. RDA Synchonization Assembly, 28 February 2017, Brussels
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

10. RDA Synchonization Assembly, 28 February 2017, Brussels
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

11. RDA Synchonization Assembly, 28 February 2017, Brussels
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, eInfraCentral, EINFRACall12 and horizontal (e.g. GEANT, EUDAT & OpenAIRE) and VRE projects
RDA Synchonization Assembly, 28 February 2017, Brussels

12. RDA Synchonization Assembly, 28 February 2017, Brussels
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

13. 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
(de-facto) standards/ best practices
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)
Usability: The user entity must be able to use the exchanged information to perform the tasks that depend on the utilization of this information
Mediators
Data structures, functionality, policies, protocols, ……..
RDA Synchonization Assembly, 28 February 2017, Brussels

14. RDA Synchonization Assembly, 28 February 2017, Brussels
RDA support
EOSCPilot will initially survey and analyse the services of horizontal e- infrastructures (EGI, EUDAT, OpenAIRE, 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

15. Thanks & Discussion
RDA Synchonization Assembly, 28 February 2017, Brussels