 I will just give a brief update of what happened with the partner tools, where we are, and what will be coming next. First, brief overview. It's actively developed by the XPX community and it just recently was released in version 0.8.1 which was a pet release which improved performance and fixed some bugs. And before that, 0.8 brought a huge effect ring and made it ready for SPX3. It currently supports, in its latest version, SPX2.2 and 2.3, and earlier releases also support older versions of SPX, if you need that. And it has an experimental implementation of the 3.0 RC1 state of the model. So it can be used to play around with SPX3. And it can generate files and I think that are the current capabilities. And despite its name as tools, it's also a library or it's maybe the most useful as a library if you want to build your own application, if you want to give your own application SPX generation support. And I think that's the fastest path if you are already using Python to use the Python tools to get support for that. But it also comes with some standalone applications that can be used for validation of files and conversion between formats and conversions between versions of SPDX. So that's the high level, what are the Python tools? What are the next steps after this huge effect ring after this move? I think the one plan is to now tell more projects, hey, you can use the Python tools. They are now more mature than before. They are rather complete. And at the same time, we are focusing on stabilizing and performance. So they are right now a few minor bugs open that are actively worked on to get fixed and we will soon have release 0.8.2 that hopefully resolves most of them. And so that's the main goal. But we are interested in getting feedback. Is that what you expected? Does that solve your issue? Or what other features would you need to have so that you can use this library, these tools? Maybe a little bit misplaced, but in the end there will be links with how to contact, where to reach out, where to give that feedback. But yeah, please, if you have feedback, give that to us so that we can improve and direct the development towards your needs. On the other side, maybe more interesting, what are the next step with looking at SPX3, which is very, very interesting for most of us here, probably, the Python tools already come with a functionality that can convert SPX2 to three. So there is a very defined way how to convert that and that is implemented in the Python tools so you can use them to lift your current use cases to SPX3 and see how they would look like. There is a draft open that moves the implementation towards being generated out of the model. I think Gary will also talk about something similar for the Java tools, but that helps to guarantee that the implementation is in line and up to date with the model development. And there are some features still missing to be complete and usable. So passing of JSON-LD, passing in generation of other formats is still on the roadmap. And the goal is to have that so seamless, in a seamless way integrated, so that if you already use the Python tools and use them for generating SPX2.3, you can, with not a lot of effort, support SPX3 additionally, so that's the goal. And that's the promised side with links and resources. We have a repository, we have a latest release. We have a few guides, there's a quick start guide and there's how to use guide that is also linked from the new homepage. There is a guide how to update but you still have an old version. We have a bi-weekly community call, there are no coordinates for that on the slides, but I will find a way to broadcast them and announce them like releases are usually broadcasted via the SPDX tech mailing list. So if you are subscribed to that, you will get notified. And that was very short and fast and is the update regarding Python tools. As I understood, questions in the end, so carry on next.