This is an old revision of the document!
The perspectives of Domain and Ecosystem Communities of Interest (CoIs) are different. Whereas a Domain CoI focuses on a specific, real world solution or implementation to a specific concrete problem (i.e., a thing), an Ecosystem CoI focuses on the interactions and links between subordinate Ecosystems (i.e., sub-Ecosystems) and Domain CoIs. Governance of the overall enterprise Data Model (DM) and individual datastores for the enterprise should remain unchanged from the pre-DIDO or non-DIDO state; it is still hierarchical in nature with a definite chain of command and specific responsibility attributed to individuals within the organization. The primary focus of the DIDO Ecosystem is coordination of various other CoIs. For example, one Ecosystem CoI could coordinate other sub-Ecosystem and Domain CoIs to ensure consistent perspective and context across for interoperability across all the CoIs.
A well run DIDO CoI should have a charter that documents:
Ideally, a DIDO CoI should have a chairperson and a board of directors. Some DIDO CoIs may add a technical board or architectural board to oversee technical changes in the product and dedicate the board of directors to oversee governance of the DIDO CoI.
The following diagram represents the various kinds of DIDO CoIs and their relationship to each other.