 So the main changes in Archimate 3.2 are in two places. One is in the notation of the language, it's made more consistent. And there are some changes in the internals of the language, the structure that you use for analyzing your models. And next to that, there are all sorts of smaller changes, in definitions, in the structure of the document, in explanations, examples, etc. If you look at the future of Archimate, it's becoming more and more important, you could say, because of the complexity of the whole digital ecosystem that organizations have to deal with. If you look at the language itself, it's quite mature. So we don't expect any major changes in the short term. But the Archimate Forum is really focusing on providing more guidance around the standard and using it in practice for all the users out there. Looking at the future of Archimate, it's becoming more and more important, I would say. The complexity of the whole digital ecosystem for organizations is growing. To get a grip on that, to manage, maintain, design that future, these architectures, they need a language-like Archimate that provides you with that consistency and quality of your architectures. Of course Archimate is a visual language, so you can share the models with others just to look at, if they read the language, write the language, they can understand the model. But next to that, it also offers an exchange format, so that tools using Archimate can exchange these architectures between them. So you can share models with people using other tools in other organizations in your whole digital ecosystem. The Archimate Forum is member-led, so that the members of the Open Group, the members in the Archimate Forum, other ones to decide on where the language is going. But it's not limited to that, if you look at the Archimate User Community, they have provided input to version 3.2 of the standard. We've identified three areas we want to focus on first. One is the, well, we call it the Archimate 101 Guide, so a guide for people starting with Archimate, how they deploy it in your organization. The second is, let's call it the Archimate Executive Guide, it's for people managing that, like chief architects or IT managers or CIOs that want to start using Archimate in their organization. Why is it important? And the third is an Archimate Patterns Library, providing modeling patterns for people using Archimate in practice. So we want to set that up and make that part of the community website.