1. Towards a shared terminology Leonardo Candela CNR-ISTI

2. Towards a shared EOSC terminology
A shared terminology is of paramount importance to enact “interoperability” among people
Go for a controlled and shared “glossary”
To be developed across WP boundaries
Who? How?
A google doc was started in WP5
Evolving / challenging to develop
Many perspectives to reconcile
Do not reinvent the wheel yet customize when needed
fitness for purpose
Beyond a pure glossary, e.g. include a concept map, examples
Concepts can be specialized / grouped
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

3. EOSCPilot All Hands meeting, 8-9 March 2018, Pisa
Open issues
Key terms?
Who: Stakeholders, Users, Actors, Boards, …
How many specializations for users?
What: Resources, Services, Nodes, …
How many specializations for services?
EOSC Service vs EOSC Service Component vs Compatible/Compliant Service
EOSC Core Services vs …
How: Processes and Procedures, Policies, PoE, …
Development process
WP5 started the process and is willing to continue
Complete the analysis of existing deliverables
Contributions from all, openness
Liaise with RDA and others working on glossaries
Curator(s)/Editor(s) to be appointed
Escalation procedure
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa