dido:public:ra:1.1_intro:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.1_intro:start [2021/08/05 14:37] murphy |
dido:public:ra:1.1_intro:start [2021/08/17 14:42] (current) murphy |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| </figure> | </figure> | ||
| - | As illustrated in the figure, the DIDO RA is an idealized general set of requirements and constraints. Each incarnation of the DIDO software (e.g., cryptocurrency or distributed ledger) uses a set of stakeholder requirements to filter the DIDO RA and tailor it to suit the unique needs and desires of its community of stakeholders. For example, the DIDO RA provides standards for logging, even though the logging requirements driven by DIDO software stakeholders may lead to a decision to opt not to include them. There are a plethora of DIDO software incarnations available, starting with the original Blockchain software that drives [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]], and moving onto IBM’s Distributed Ledger, [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]], and Iota. | + | As illustrated in the figure, the DIDO RA is an idealized general set of requirements and constraints. Each incarnation of the DIDO software (e.g., cryptocurrency or distributed ledger) uses a set of [[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder|stakeholder]] requirements to filter the DIDO RA and tailor it to suit the unique needs and desires of its community of stakeholders. For example, the DIDO RA provides standards for logging, even though the logging requirements driven by DIDO software stakeholders may lead to a decision to opt not to include them. There are a plethora of DIDO software incarnations available, starting with the original Blockchain software that drives [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]], and moving onto IBM’s Distributed Ledger, [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]], and Iota. |
| The DIDO software incarnations are adopted or used by another community of stakeholders that wish to leverage the DIDO software into a DIDO Network of Nodes to address requirements and needs of a specific domain. For example, one DIDO network community wants to provide a cryptocurrency and another public records. The DIDO software selected by the DIDO network stakeholders might be different depending on its intended purpose. In Figure 1, the bi-directional arrows communicate the notion that the DIDO RA influences not only the DIDO software and networks, but also that evolution of DIDO software and networks feeds back into subsequent versions of the DIDO RA. | The DIDO software incarnations are adopted or used by another community of stakeholders that wish to leverage the DIDO software into a DIDO Network of Nodes to address requirements and needs of a specific domain. For example, one DIDO network community wants to provide a cryptocurrency and another public records. The DIDO software selected by the DIDO network stakeholders might be different depending on its intended purpose. In Figure 1, the bi-directional arrows communicate the notion that the DIDO RA influences not only the DIDO software and networks, but also that evolution of DIDO software and networks feeds back into subsequent versions of the DIDO RA. | ||
dido/public/ra/1.1_intro/start.1628188633.txt.gz · Last modified: 2021/08/05 14:37 by murphy
