dido:public:ra:1.3_gov:1_communities
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.3_gov:1_communities [2021/07/30 13:03] murphy |
dido:public:ra:1.3_gov:1_communities [2021/08/05 14:28] (current) murphy |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:ra:1.3_gov| Return to the Governance page]] | [[dido:public:ra:1.3_gov| Return to the Governance page]] | ||
| - | As introduced in [[dido:public:ra:1.2_views:1_stakeholder|Section 2.1]], a DIDO community is a [[dido:public:ra:xapend:xapend.a_glossary:c:coi|Community of Interest (CoI)]] responsible for the architecture, design, implementation, maintenance, and eventual sunset (yes, all good things come to an end) of DIDO networks and its DIDO nodes. DIDO communities should have a well-documented, repeatable, traceable, transparent, and unbiased process that is managed and run by a governing board (or hierarchy of governing boards). Often the DIDO community is divided into two organizations: one responsible for the software, usually as an open source software (OSS) project, and the other responsible for managing the [[dido:public:ra:xapend:xapend.a_glossary:f:fungible| fungible]] data (e.g., currency or commodity) managed by the software. Most DIDO communities choose or select DIDO software designed, implemented, and maintained by another party. For example, Ethereum, Hyperledger, and IOTA all provide their software for others to use as OSS. | + | As introduced in [[dido:public:ra:1.2_views:1_stakeholder|Section 2.1]], a DIDO community is a [[dido:public:ra:xapend:xapend.a_glossary:c:coi|Community of Interest (CoI)]] responsible for the architecture, design, implementation, maintenance, and eventual sunset (yes, all good things come to an end) of DIDO networks and its DIDO nodes. DIDO communities should have a well-documented, repeatable, traceable, transparent, and unbiased process that is managed and run by a governing board (or hierarchy of governing boards). Often the DIDO community is divided into two organizations: one responsible for the software, usually as an open source software (OSS) project, and the other responsible for managing the [[dido:public:ra:xapend:xapend.a_glossary:f:fungible| fungible]] data (e.g., currency or commodity) managed by the software. Most DIDO communities choose or select DIDO software designed, implemented, and maintained by another party. For example, [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]], Hyperledger, and IOTA all provide their software for others to use as OSS. |
| Some DIDO communities may support multiple kinds of immutable data objects within a single DIDO network, or they can support multiple networks that each have different kinds of immutable data object types. For example, one DIDO community’s OSS might support cryptocurrencies on one DIDO network and support immutable data objects representing supply chain commodities on another. | Some DIDO communities may support multiple kinds of immutable data objects within a single DIDO network, or they can support multiple networks that each have different kinds of immutable data object types. For example, one DIDO community’s OSS might support cryptocurrencies on one DIDO network and support immutable data objects representing supply chain commodities on another. | ||
dido/public/ra/1.3_gov/1_communities.1627664632.txt.gz · Last modified: 2021/07/30 13:03 by murphy
