 It's my first time presentation in English. You know, I must introduce myself first. My name is Gao Kun in Chinese. You can call me King in English. And I'm really glad to see all of you here. And so, you know, I'm OpenChain board members. I previously, I want to give my first time to OpenChain. But I'm sorry. As PDX mini submitted earlier, OpenChain, thanks, Kate, for giving me the opportunity to present the issue here. Thank you. Okay, thank you. Okay, let me start my presentation. So this is the whole presentation. We divided into five parts. You know, just Gobi, my colleague, he has to explain the second and the third parts. So I will explain, I will talk about the issue and the challenge in the AI data license complaints. And the excellent practice about the AI data complaints and the display of S-BOM in OpenURA, I record a little video. You can see it. Okay, this is the first. Because in the AI area, it's very, grow very fast. You can see this market. This is the demo diagram. The UI exceeds the 3.1 billion and the continue to at the, sorry, cut graph of the 17%. Okay, and this is the, AI is drive very fast. This is very important in this slide. We conclude the AI into three risk area. The first is the IPR complaints. Look at the picture like this. This is a GitHub called Palette. And the code generated by AI contains the LGPL. Because it generated by AI automatically contains the LGPL open source code, state page to users. It's very, it has a lot of risk for the users. And the AI generated code does not fool the open source obligations. This is very important. Look at this picture. This picture has a copyright by the commercial company, but it's opened to websites and everybody can use it. It's also the IPR complaints here. And the second is the privacy leak. For example, also the GitHub called Palette is you to obtain the data from the GitHub and the AI generated code contains the ID card information. For example, this is the full name. You can get the full name. And it's, you can find the full name of the users and the address of the users. It's a privacy leakage. It's very important in this area. The secondary security, okay. So we may draw the risk into the current AI data and list it here. First, the IPR complaints. The second is the privacy leakage. The third is the security and the sensitive information. That's very important for AI area. And it's a challenge here. Okay, so face this challenge, the different governments and the organization, they know this challenge and they want to do something for this. For example, European, here is the European and the Italian data protection, authorated state as the creativity should be strict checked. When you separate the followed, you know this is very famous in the European. And of course in China and the US government do the same things here. And okay, the conclusion is in this area. It's a very new area and we must do a lot of challenge here. We must do some things. This, I will jump the part two and part three because the Gobi just told, just a speech, how we contribute in the standard and how we contribute in the two links, okay. Okay, so the, okay. This is our the AI, two links detection to find the same column, same column, you know. This is a chain face. I will translate the process for you. This is the training phase and inject the column code here and the calculates the similar metrics is the next step. So the similar metrics and we go through the visualization phase. We can see it on our dashboard and yeah. And we deploy here in the inference phase and they divided the data column and the noted column. We can recognize it, identify which one is the. So this is the end of the result of the real data. You can see it, okay. Okay, this is, oh, this is SPDX. We contributed in the FAI and the over 37,000, they said my data are captured using SPDX, they said profile. In order to conduct the license complaints and analyze the part of the open data knowledge project. This is a snapshot of the open FAI open data knowledge project. And so I will introduce some back practice in community, Huawei OpenDate. And this is my sport. It's named the she-he. Okay, sorry. It's named the she-he platform. What do we do in this platform? Okay, sorry. Okay, we support the complaints using the method data. Share the platform. First is sharing platform. Second is the license recommendation. And third is the data site review. You can see the first, okay, we, okay, this is the platform of the shared data. The lessons to analyze the data about more than 50 data site integration accuracy, break down rights, limitation and obligations. Which input the license avaliate the capital of users. We share this. And the second, a license recommendation to adapt the air bombs and it's completed with the SPDX pre-release standard yet, which can provide nine item to check to have other obtains complaints license at a low cost. This is the process of the license recommendation. For example, you want to choose a license. We can help you in these tools. And the third is the data site review tools. This is a, this tool is a system that online Mainsball foundation, model platform and the lawyer in review decide in batch and reduce data hosting risk. Okay, we supply these three tools and make the community more health. The risk, reduce the risk AI bomb. Yeah. Okay. The rules for familiar and the standard extract in practice of Mainsball community pro provide feedback to SPDX standard community. SPDX 3.0 RC version. Yeah. Now it's 3.0 RC version. I think it adds the AI bomb in this version. I think it will release recently. Yeah. Good. Thank you, Kate. Last time without AI bomb, we also implemented the S-Bomb in open Eurora community. Open Eurora is, okay. Open Eurora is a diamond sponsor of this meeting. Yeah. I will, I will record the video. I will share the video to all of you. This is the open Eurora website and you can choose the community version and the, okay, the format. You can see the format have two format, is ISO format and another is, sorry, second DX format. And this is, okay. Again, this is version and the format and the mirror and the architecture. And this is the result, the dashboard of the S-Bomb. You can see it. This is Voluntary Build and this is Voluntary Build Chant and this is the license. License risk and license layout. Yeah. And you can see the different color is a different risk of the license and the Voluntary Build. Yeah. But it's Chinese. We will translate it into English. Okay. So this is the detail of the Voluntary Build you can click into it. And this is the S-Bomb metadata, license and the vulnerability and the dependence on the software package. You can see who depends on this, depends on this component and this component depends what. Okay. This is the, okay. We can find the Voluntary Build from the backend, from the Voluntary Build to find the component. We can find the vulnerability in component. Yeah. Okay. I think it's all of the video. My speech is over. Thank you.