 Well, Togaf is a framework, so it provides guidance on how to deliver EA following the ADM as a consistent process and information flow. It also provides a set of guides and techniques to support EA practices covering areas such as how to build EA capability, how to handle governance and set the repository, and how to deliver architecture descriptions following the content framework. What it doesn't go into in detail is the relationship of how to construct and deliver architecture descriptions with a specific notation. And here's where Archimate can be used to support Togaf in providing a standard modeling notation and language for the delivery of models and an architecture. On the other hand, Archimate focuses on the modeling processes, therefore it does not recommend or address any specific methodology, process, or framework to support EA as a practice. In these areas, Togaf is an appropriate support mechanism for Archimate. Archimate can also be used to implement models, tools, reference models that give both standards the visualization and the models to support implementation and executable standards in a real sense, in a practical deployed sense. Well, our vision is to keep Togaf and Archimate as separate standards while providing guidance about how they can be successfully used together. This means that Togaf can be used along with any other modeling notation or language notation, for example, with UML. And in the other direction, Archimate can also be used to support an EA implementation that's aligned with any other EA framework or combination of different frameworks. So we're keeping them separate but related to each other. At the end of the day, the application of standards depends very much on a particular context for every organization or enterprise. The management frameworks and the tooling that they have in place, this is the reason why standards like Togaf and Archimate are designed to be adapted to fulfill the specific needs of a given enterprise. And most of the time, they're used along with other practices and modeling notations such as governance or project management frameworks, requirements frameworks, and in notations such as UML or others. So which way best practices should be used must be based on an assessment of how they will deliver value to the particular enterprise and organization, both for a short term and a long term.