====== 2.1.3 Ecosystem View ======
[[dido:public:ra:1.2_views:1_stakeholder|return to Stakeholder Views ]]

The concepts of a **Ecosystem View** are captured within the [[dido:public:ra:xapend:xapend.a_glossary:d:dido_ecosystem_community]].


The perspectives of Domain and Ecosystem [[dido:public:ra:xapend:xapend.a_glossary:c:coi| Communities of Interest (CoIs)]] are different. Whereas a [[dido:public:ra:xapend:xapend.a_glossary:d:dido_domain_community]] 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 Community. [[dido:public:ra:xapend:xapend.a_glossary:g:governance]] of the overall enterprise [[dido:public:ra:xapend:xapend.a_glossary:d:dm]]  and individual [[dido:public:ra:xapend:xapend.a_glossary:d:datastore| 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 Communities to ensure consistent perspective and context across for [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability|interoperability]] across all the CoIs.

A well run DIDO Community should have a [[dido:public:ra:xapend:xapend.a_glossary:c:charter|charter]] that documents: 
  * the rules of engagement between DIDO CoI members 
  * the approval processes for changes to the charter and for releases, such as software and configuration 
  * trouble report procedures (capturing, distributing, resolving, disseminating afterwards) 
  * maintenance procedures (requesting, frequency, dissemination of maintenance reports) 

  * **Note** for the Ecosystem, the Charter and Bylaws are inherited from the encapsulating [[dido:public:ra:1.2_views:1_stakeholder:3_ecosystem]]. Often, the Ecosphere is [[dido:public:ra:1.3_gov:1_legaldocs:1_charter | Charter]], [[dido:public:ra:1.3_gov:1_legaldocs:2_bylaws | Bylaws]] and [[dido:public:ra:1.3_gov:1_legaldocs:3_pp | Policies and Procedures]] are subsets of the Ecosphere. 

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.

  * DIDO Ecosystem is comprised of 1 or more DIDO Platforms
  * DIDO Ecosystem is comprised of 1 or more DIDO Domains
  * DIDO Domain community is comprised of of 1 or more [[dido:public:ra:xapend:xapend.a_glossary:i:immutable|immutable]] data objects
  * DIDO Exchange can [[dido:public:ra:xapend:xapend.a_glossary:b:bridge|bridge]] 1 or more immutable data objects within a DIDO community
  * DIDO Exchange can bridge 1 or more DIDO communities
  * DIDO Exchange can bridge 1 or more DIDO Ecosystems

<figure>
{{    dido:public:ra:1.2_views:1_stake:ecosystem_community.png?500  |}}
<caption>DIDO Ecosystem
</caption>
</figure>

   :**NOTE:**   Refer to [[dido:public:ra:1.2_views:1_stakeholder:7_stds]] for this view.

/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~