WEBVTT 00:00.000 --> 00:12.760 Okay. Everybody good? Yep. Okay, we're going to go ahead because we are already behind 00:12.760 --> 00:19.440 schedule. So we're going to start with the DSAT, my think, and they're going to present 00:19.440 --> 00:26.080 their findings, answers to the question. Lots of crazy ideas on how the open source 00:26.080 --> 00:37.840 community and can help foster you compliance. Sorry. Yeah, it's as you will see, it's 00:37.840 --> 00:47.440 like more than an open source, it's like open approach ideas. So we have many ideas on the 00:47.440 --> 00:55.760 user interaction with the platform. So for example, sorry. So we have a lot of ideas on how 00:55.760 --> 01:03.360 users should interact with the platform. So the like methods or API that platform should 01:03.360 --> 01:10.000 expose that for the user. For example, to export the data to another platform. So I sort of 01:10.000 --> 01:18.800 federation for personal data. And then there is also the idea to have platforms to automatically 01:18.800 --> 01:28.400 expose APIs or endpoints to do GDPR like data donation. So for the user to donate its data 01:28.400 --> 01:40.400 to either the investigative team or CSO running a test or a study, etc. Then there was also something 01:40.480 --> 01:49.200 about how can platform check their compliance. So like a sort of sell service checkbox to check 01:50.160 --> 01:58.640 if the platform is compliant or not with the regulation. There was also an idea about if you are 01:58.640 --> 02:07.680 big enough or like bigger than a threshold. Then all of your patents and models etc are public 02:07.760 --> 02:18.800 domain, which is a very good wiflist. But let's see. And then coming back to the user content, 02:18.800 --> 02:25.520 the idea to allow or to enforce a bring your model, especially for a recommender system, which is 02:25.520 --> 02:34.080 already done in some like open like social media. And then one really interesting one is also 02:34.080 --> 02:45.760 to apply this API terms of service. So to standardize the way terms of service are written, 02:46.320 --> 02:54.480 to have them to be like programmatically inspectable and to expose like in an open in the creative 02:54.560 --> 03:04.960 come on a way, the features of the license with an introducing also a SPAT SPDX identifier for the 03:04.960 --> 03:12.720 license. And then last one will be to have a unified repository for the advertisement libraries 03:12.720 --> 03:18.640 that are scattered through the platforms now and they use different schemas, different names 03:18.720 --> 03:27.840 for the features etc. So these are the, yeah, the ideas. That sounds pretty great. There have 03:27.840 --> 03:32.800 been some amazing ideas and maybe we'll see some of them implemented in the coming years. Who 03:32.800 --> 03:39.440 knows? A hand I've been out to Taipei to do the CRI wrap up. Thank you very much. So we were 03:39.440 --> 03:44.560 trying to answer the question, how I mean how how might we make sure that the implementation 03:44.560 --> 03:50.480 of the series of disaster? And frankly you have delivered. So congratulations to all of you. 03:52.720 --> 03:59.760 Yeah, so we'll figure out a way to put them online, right? But for example, I see here remove 03:59.760 --> 04:07.840 all incentives to be a Stuart. That's a pretty good one. Ignore all open source producing SMEs. 04:08.480 --> 04:12.640 Okay, that's another good one. Right, so there are lots of those. And then they're really interesting 04:12.640 --> 04:17.200 solutions to each of one of those, right? So we'll figure out how to share it with the working 04:17.200 --> 04:21.840 group and make it a publicly available resource. And I'm sure there are some really good 04:21.840 --> 04:24.080 ideas in there. But yeah, thank you very much. This was fun. 04:29.520 --> 04:35.920 Okay, so on AI we went a bit all over the place, but the discussion was really, really interesting. 04:35.920 --> 04:43.920 We, you can see from the chaotic whiteboard, we started talking about what makes open open. 04:43.920 --> 04:50.720 And had the discussion around reproducibility and the challenges opposed with reproducibility 04:50.720 --> 04:59.200 for AI is actually borderline impossible. It's the challenge. But then we've done to discover 04:59.200 --> 05:04.000 discuss other things like the importance of ethics, you know, should there be ethical considerations 05:04.080 --> 05:09.520 in AI? And we kind of concluded as well that, well, with proprietary out, you'll never know 05:09.520 --> 05:14.080 if it's ethical or not. We've open AI, you actually have an opportunity in a chance to find out. 05:15.600 --> 05:21.200 We also talked about the importance of building AI that's reason to born non-discriminatory 05:21.200 --> 05:28.400 and how we could go around achieving that. Finally, we talked about building stuff at the end of the 05:28.400 --> 05:33.600 day and emphasise the importance that all of the open source code that we have around AI already, 05:34.240 --> 05:38.800 all of the open source libraries that we've got around it are a great starting point. And that 05:39.600 --> 05:45.120 we're essentially bootstrapping a community, because people who've never done AI before are 05:45.120 --> 05:49.840 coming in using the existing open source stuff and building on top of that, which is really, really cool. 05:50.400 --> 05:59.520 Yeah, so I think that's about it. And I think that brings our workshops to a close 05:59.520 --> 06:01.680 and we'll be moving on to the next block.