Agenda:
Notes:
Present: Matthew Dovey, Tiina Kupila-Rantala, Yannick Legré, Natalia Manola, Mike Mertens, Dale Robertson
Apologies: Tiziana Ferrari, Wolfram Horstmann, Damien Lecarpentier, Paolo Manghi, Najla Rettberg
Agree agenda
The agenda was agreed
2. Recap/agree aims and scope of Initial Discussion Paper for 30 June
Andreas Veispak (DG CNCT) is understood to require, by 30 June, input about the federating core services, consisting of what the federating core includes, use cases, costings and the role of e-Infrastructures in operating them. This will input to DG CNCT’s contribution to the EOSC strategy and DG CNCT’s funding strategy for the phase after Horizon 2020. Primarily, he would like information about what capabilities the federating core should provide. The view was expressed that the more considered input we can give at this stage to Andreas Veispak, the more scope there will be in developing the above funding strategy.
There was agreement that the input provided at the end of June is only initial input whose circulation should be kept limited and is likely to need to be refined thereafter for other, wider, audiences (e.g. EOSC governance, WGs etc). It will be positioned as a Briefing Paper, allowing room for it to be altered/updated subsequently.
The paper will provide an opportunity for the e-Infrastructures to put their view of the federating core and its value. We could propose a layered model - 2, 3 or 4 layers - with the core services each one should contain. How we believe the services should be run. Business models may be too specific/detailed for the end of June but we could describe the approach we think should be taken and also say what role CNCT should have.
Use cases should be provided to illustrate/contextualise the need for the services and provide specific information to Andreas for the next funding round, with an accent on indicating the broader sustainability factors for these services to be included in the use cases: for example, the role and position of the RIs, academic communities and the research and data policies of member states. Their purpose in these use case contexts needs to be very clear and a template needs to be agreed.
Scenarios (drawn from EOSC-hub D2.1) may be of some use as a framework, since we will be referring to an already familiar language but we need to refine them with real-world examples drawn from EOSC-HUB and OpenAIRE to avoid their becoming too abstract.
3. Discuss proposed process to 30 June with the aim of signing it off:
The proposed process was signed off, recognising that the timescale is very tight.
4. Agree the main elements of the paper:
The main elements of the paper will be altered along the lines of the discussion. A layered model will be drafted and populated with proposed core services, for discussion.
5. AOB
None.
Actions:
Agree template for use cases by 7 June - DR and MM to collect templates, discuss, circulate.
Use cases - DR and MM to collect asap and share by email/online by 7 June if poss.
DR to circulate a Doodle poll to schedule two meetings for w/c 10 June, the first to discuss the use cases and the second (if possible) to discuss on the basis of a draft “straw person” document.