WEBVTT 00:00.000 --> 00:12.840 Good morning, so I'm Valentina Stavary, I'm working in the cloud and software unit in 00:12.840 --> 00:19.440 DJConnect European Commission, and I'm here to talk about Simple, which is an open source 00:19.440 --> 00:26.120 software, can I just ask in the audience who has heard about Simple before? 00:26.120 --> 00:27.120 Yeah. 00:27.120 --> 00:32.520 So I'm here to explain you a bit more. 00:32.520 --> 00:40.440 I want to be too long into the EU policy context, but just to put a bit back in the overall 00:40.440 --> 00:41.600 context. 00:41.600 --> 00:49.040 So you heard a few regulations, of course, that are implying in the digital, single market, 00:49.040 --> 00:51.440 and they are very important for this. 00:51.440 --> 00:55.320 And the commission is also financing the common European data spaces. 00:55.320 --> 01:01.800 So the really, the sectorial data spaces that will help data sharing and facilitate 01:01.800 --> 01:03.880 an accelerated data sharing. 01:03.880 --> 01:07.880 And in parallel, you have also a reason for the initiatives that are financed in order 01:07.880 --> 01:13.520 not to recreate from scratch every time the technical solution behind data spaces and 01:13.520 --> 01:14.520 data sharing. 01:14.520 --> 01:19.240 And this is, if you see in the middle of the slide, Simple. 01:19.240 --> 01:25.280 But more recently, we had also the adoption of data union strategy, which enforced 01:25.720 --> 01:30.800 the fact of Simple being key in the data sharing initiatives and being the technical 01:30.800 --> 01:32.360 enable for this. 01:32.360 --> 01:36.200 So this is a bit to give you a bit of context. 01:36.200 --> 01:38.040 But now, what is Simple? 01:38.040 --> 01:42.800 Simple is an open source software that enable data sharing. 01:42.800 --> 01:51.120 And that is indeed enabling, sorry, to create, to reuse components that are existing 01:51.120 --> 01:54.080 in the market and develop what is missing. 01:54.120 --> 01:59.280 So in order to have the core functionalities for data sharing for all the sectorial data 01:59.280 --> 02:02.600 initiatives and even beyond. 02:02.600 --> 02:07.800 So just for those who are not familiar with data spaces, in any case, the slide will be 02:07.800 --> 02:12.720 available, is just to explain what is the data space and what are the key components 02:12.720 --> 02:14.520 of data spaces. 02:14.520 --> 02:22.160 So with these governance that is key in the, in the, this framework of data space to ensure 02:22.160 --> 02:26.960 secure data sharing. 02:26.960 --> 02:30.160 And if we go deeper into Simple, what is Simple? 02:30.160 --> 02:34.200 It's composed by the three products, Simple Open, being the middleware. 02:34.200 --> 02:37.160 So that is free to use open source. 02:37.160 --> 02:43.680 And you can, of course, contribute us of today to it's evolution. 02:43.680 --> 02:46.160 You have Simple Labs being the testing environment. 02:46.160 --> 02:51.720 So to enable you to test Simple Open components and also to test the interoperability 02:51.760 --> 02:54.360 of solutions that are already existing. 02:54.360 --> 02:59.760 So you're that as space, you're that initiative and you want to try the components of Simple 02:59.760 --> 03:05.960 in order to potentially use or enhance your already existing data space. 03:05.960 --> 03:11.560 And Simple Live, I will come back a bit later, is the fact of accompanying the data 03:11.560 --> 03:17.160 spaces that are financed by the EU in order to help them understand how to integrate 03:17.160 --> 03:23.320 Simple in their solution, in order to accelerate either their internal business processes 03:23.320 --> 03:28.920 or being interoperable with other data spaces, which is key, of course, in some sectors, 03:28.920 --> 03:32.160 like mobility, like like tourism, like energy. 03:32.160 --> 03:38.560 Of course, this is key, in order to be able to share data with other sectors. 03:38.560 --> 03:45.480 Just very briefly, the architecture principle behind Simple, in order to repeat 03:45.480 --> 03:51.200 a bit that this is components, so it's based on components, so it's very modular. 03:51.200 --> 03:52.200 It's open. 03:52.200 --> 03:53.200 It's for free. 03:53.200 --> 03:59.320 It's, of course, security, the secure and ensuring all the EU values is a data protection 03:59.320 --> 04:06.640 and security, of course, by default, and interoperable because it's the essence of course 04:06.640 --> 04:09.480 of Simple. 04:09.480 --> 04:14.600 These, I will not keep longer in case the time is short, but just to give a bit, this is 04:14.600 --> 04:20.760 the core functionalities of Simple Open, so what should enable the data space and data 04:20.760 --> 04:25.880 sharing initiatives to be able to function. 04:25.880 --> 04:30.600 Apart from that, so here you have the roadmap that is available and we'll be updating on 04:30.600 --> 04:37.680 the website very soon, next week, and so giving a bit the timeline, so everything should 04:37.680 --> 04:44.520 be finalized by this year, 2026, so for the core functionalities. 04:44.520 --> 04:50.000 On top of this, we also launch recently, what we call the Simple Open Extensions, being 04:50.000 --> 04:58.480 also able to accelerate also data sharing ready for AI and machine learning and also to 04:58.480 --> 05:06.560 give the possibility to a sustainable business model of data spaces being the monetization. 05:06.560 --> 05:13.760 So when you have data intermediary, that is enabling data sharing for different data spaces 05:13.760 --> 05:21.600 and in the technical implementation, then you are also able to be monetized for this service. 05:21.600 --> 05:26.760 And this just to give you a bit an idea of what is the journey of a data space that wants 05:26.760 --> 05:32.480 to integrate Simple, so what we are doing is the fact that we go into a study in order 05:32.480 --> 05:39.680 to understand the processes of the space and to see what where Simple Open can facilitate 05:39.920 --> 05:47.200 actually the integration and the business processes of the data space. 05:47.200 --> 05:54.040 I invite you, of course, to join our LinkedIn group and also to check the repository, 05:54.040 --> 05:58.840 so you have the QR code for the LinkedIn group, and most importantly, it's an open source 05:58.840 --> 05:59.840 project. 05:59.840 --> 06:09.240 We need your contribution, so the code repository is there, so you have the QR code, 06:09.240 --> 06:15.880 the code repository is there available for all the processes are there, every documentation 06:15.880 --> 06:22.920 is there, so please contribute because this is a key evolution also that we need and to 06:22.920 --> 06:28.840 be sustained and just also related to the conversation that just happened before on public 06:28.840 --> 06:29.840 procurement. 06:29.840 --> 06:36.480 We are this new way of procuring at the European Commission where we procure, we have companies 06:36.480 --> 06:42.680 that are the usual players, let's say, in the IT services of the Commission, but also need 06:42.680 --> 06:48.440 to develop as an open source, so we are more and more going into that direction, and this 06:48.440 --> 06:57.240 is simply an example of this, so developing with procurement but an open source, so this 06:57.240 --> 07:04.240 is to say, please visit the website, the GitLab and contribute today. 07:04.240 --> 07:07.240 Thank you. 07:07.240 --> 07:22.240 If you have questions, any questions, I see a few, yeah, there is one, two, a few. 07:22.240 --> 07:26.240 Thank you very much for the presentation, finally very interesting ago. 07:26.240 --> 07:31.240 Can you hear me better now? 07:31.240 --> 07:37.240 Thanks for the presentation for the very interesting and I have an observation on a question, 07:37.240 --> 07:42.240 one is, probably it will soon work as soon or replacement for the team, so you can post it 07:42.240 --> 07:47.240 to post the link somewhere that is more open source and then the way to go. 07:47.240 --> 07:53.240 The other question that comes to mind is, well at this point, we don't need gay eggs in terms 07:54.240 --> 08:01.240 of managing data spaces and so on, so there is an overlap over the improvement on gay eggs, 08:01.240 --> 08:03.240 by this answer. 08:03.240 --> 08:11.240 Of procurement, is there a whole platform of improvement, though? 08:11.240 --> 08:18.240 It's a kind of, let's say, an improvement or the way something that can be overlapping with 08:18.240 --> 08:23.240 the AIX project is doing, looking at data spaces. 08:23.240 --> 08:25.240 I understand, okay, sorry. 08:25.240 --> 08:32.240 It's parallel to the grants, usually it's a grant that is implementing the data space, 08:32.240 --> 08:38.240 so it's an excited, well, the simple has been launched to enable the data spaces, 08:38.240 --> 08:43.240 but in the data space landscape, you have different maturity, so you have that 08:43.240 --> 08:48.240 started a long time ago, but you have also a very recent one. 08:48.240 --> 08:52.240 And of course, we will not reinvent the wheel for those that are already developed 08:52.240 --> 08:58.240 and have a technical solution, but for the ones starting to start recently, 08:58.240 --> 09:03.240 of course, we have the possibility to help them and to accelerate the development, 09:03.240 --> 09:08.240 because of course, if you have components that are already existing that are already 09:09.240 --> 09:13.240 any integrated, and we say this is quite important to be integrated, 09:13.240 --> 09:17.240 so to have to cover your core functionality, of course, 09:17.240 --> 09:21.240 this is accelerating the development of the data space. 09:21.240 --> 09:24.240 Thank you for your question. 09:24.240 --> 09:34.240 Thank you. 09:34.240 --> 09:38.240 What are your priorities for a call of action to European developers, 09:38.240 --> 09:40.240 because you said contribute, right? 09:40.240 --> 09:43.240 But what are you looking for, more core developers, 09:43.240 --> 09:47.240 people to help adoption in data spaces, extension writers, 09:47.240 --> 09:53.240 testers, I don't know, so you have kind of a mini roadmap for external contributions. 09:54.240 --> 10:00.240 The contribution are covering, I would say, all the functionalities that we are developing, 10:00.240 --> 10:05.240 so it's of course free for any developer to contribute, 10:05.240 --> 10:10.240 so if you consider that we miss the major process, for instance, 10:10.240 --> 10:17.240 if you consider that we are not prioritizing the right components in the first place, 10:17.240 --> 10:19.240 because you need that. 10:19.240 --> 10:24.240 Yes, the freedom I agree, but you can also push some priorities, 10:24.240 --> 10:28.240 because since it's a tender, it's opaque, not to the community. 10:28.240 --> 10:33.240 So if you want something, I say, it's useful to know, 10:33.240 --> 10:37.240 but maybe the developers could concentrate on what you know is needed, 10:37.240 --> 10:41.240 otherwise it's generic contribution, I understand which is good. 10:41.240 --> 10:47.240 So to give an indeed, we have a very busy roadmap this year, 10:47.240 --> 10:53.240 and I think one of the key identified components that are critical for the data spaces is the federation. 10:53.240 --> 10:58.240 So the federation of the data space is meaning that in the common European, 10:58.240 --> 11:01.240 so in the data space at the European level, for instance, 11:01.240 --> 11:05.240 you have a lot of local initiatives that are already created. 11:05.240 --> 11:10.240 So the common European in the space is federation, 11:10.240 --> 11:13.240 what are the different organizations, 11:13.240 --> 11:17.240 and data space initiatives that are happening locally, 11:17.240 --> 11:20.240 or were sub-sector, if I may. 11:20.240 --> 11:27.240 So this is key, and of course this contribution would be very relevant to accelerate the development, 11:27.240 --> 11:30.240 of the requirements, and then of the development. 11:30.240 --> 11:33.240 So that's one of the things. 11:33.240 --> 11:39.240 Okay, thank you very much, and you're nowhere to find us.