 So as you've probably gathered, there's quite a lot of cross-pollination between different projects in Linux Foundation. And for those of you who are familiar with it, the Open Chain project has been collaborating with projects like SPDX for a long time. Open Chain operates at a very high level. It's focused on what? Around some business process standards. The Open Chain's founding focus was license compliance. More recently, it's been working on security assurance or security compliance. And I wanted to flag the second item as something for your attention. You may be familiar with Open Chain on the license compliance front. And as you can see, some of the ideas and work products from Open Chain that go from what into how, then go into projects like SPDX and implementation. On the security side, we've got something that's been cooking for a while and maybe of interest to you. This is a security standard, a sister standard to the license compliance that we've had in market for several years. This particular process standard has completed its ISO ballots. It describes the process management for a quality security assurance program. And it's already available as a de facto standard. There's already self-certification material out there. There's already companies conforming to it, such as LG Electronics and BlackBerry. It's a bit of a milestone for the Open Chain project to go from making one process standard into two. It's a transformation for us into having these sister standards. And of course, that kicks off other discussions about should Open Chain or could Open Chain make more sister standards. Those discussions, of course, are happening inside the Open Chain project itself. And you're very welcome to be part of it. As Gary said, with SPDX, you can very quickly find out where their meetings are and anyone can join in. Open Chain is the same. Go to openchainproject.org forward slash participate and then do so if you wish. But the reason I wanted to flag security for you now today is that as a business process standardization project, we are in a slightly different place to many other projects. We're involved in a long tail of the supply chain. And as organizations meet our standards, our specifications, and as they begin to adopt the idea of, well, what should we do? They naturally turn to the how. So when it comes down to the details of managing open source security and naturally you need S-bombs, we will, of course, be redirecting people into this project where hopefully they can not only use SPDX, but also benefit from this community's experience of how do you implement something like SPDX, what do you do next, and so on and so forth. If you are interested in the very high level what process side, we would appreciate your feedback. We do have active discussions already about the next iteration of this standard, as with our license compliance standard. And we don't have any particular requirements for people to contribute except that they show up. Now if you're familiar with ISO standards, you may be familiar that there's often a cost to get an ISO standard. In our case, there isn't. We're not only providing the standards on our website for free, but ISO has a specific page for the type of ISO standard we are where you can download them from ISO for free as well, which mean, and as SPDX. I think if I recall correctly, so the first. Yes, I was getting to that. So 14 years, 15 years ago now, I think the Linux Foundation made Linux standard base as a standard. And then many years later, Open Chain became an ISO standard in 2020, SPDX almost immediately after in 2021. And if I recall correctly, I think our security standard is standard number three, though there is a much larger pipeline. And in case you're not familiar with it, the Linux Foundation has the Joint Development Foundation, which does a lot of standardization work. Anyway, a lot of that's very high level. Won't have thanked you too much, but we are here in Open Chain doing process management around security as well as license compliance. We're very high level. We're about what, not how. We have extensive reference material, but we also redirect people into projects like this for implementation. And for that reason, I hope we'll be sending you many new friends. And I hope also that you will look at what we're doing, how it can impact the supply chain, and help us make it better in the next revisions. That's all. Thanks very much for making Space Cave, man, bros. It was much appreciated. And I'll be around if you have any questions.