public:99_annexes:annex-b-terms-and-definitions:n:node

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
public:99_annexes:annex-b-terms-and-definitions:n:node [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:n:node to public:99_annexes:annex-b-terms-and-definitions:n:node nick_didopublic:99_annexes:annex-b-terms-and-definitions:n:node [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Node ====== ====== Node ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
  
-A Node is an identifiable participant that performs one or more assigned roles in a [[private:99_annexes:annex-b-terms-and-definitions:d:distributed_system|Distributed System]].+A Node is an identifiable participant that performs one or more assigned roles in a [[public:99_annexes:annex-b-terms-and-definitions:d:distributed_system|Distributed System]].
  
 A Node provides a stable point of responsibility for: A Node provides a stable point of responsibility for:
Line 22: Line 22:
   * Traceability   * Traceability
  
-A Node performs one or more [[private:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Roles]] and has a [[private:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]] that distinguishes it from other participants in the Distributed System.+A Node performs one or more [[public:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Roles]] and has a [[public:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]] that distinguishes it from other participants in the Distributed System.
  
 A Node can exchange information through one or more Communication Endpoints. The Node remains distinct from the Communication Endpoints it uses. A Node can exchange information through one or more Communication Endpoints. The Node remains distinct from the Communication Endpoints it uses.
Line 28: Line 28:
 A Node can maintain or process: A Node can maintain or process:
  
-  * [[private:99_annexes:annex-b-terms-and-definitions:d:data_object|Data Objects]] +  * [[public:99_annexes:annex-b-terms-and-definitions:d:data_object|Data Objects]] 
-  * [[private:99_annexes:annex-b-terms-and-definitions:i:immutable_data_object|Immutable Data Objects]] +  * [[public:99_annexes:annex-b-terms-and-definitions:i:immutable_data_object|Immutable Data Objects]] 
-  * [[private:99_annexes:annex-b-terms-and-definitions:d:dido|Distributed Immutable Data Objects (DIDOs)]]+  * [[public:99_annexes:annex-b-terms-and-definitions:d:dido|Distributed Immutable Data Objects (DIDOs)]]
   * Messages   * Messages
   * Transactions   * Transactions
Line 71: Line 71:
   * DIDO Reference Architecture glossary and Node taxonomy   * DIDO Reference Architecture glossary and Node taxonomy
   * DIDO Solutions shared Terms and Definitions, previous Node definition   * DIDO Solutions shared Terms and Definitions, previous Node definition
-  * [[private:99_annexes:annex-b-terms-and-definitions:d:distributed_system|Distributed System]] +  * [[public:99_annexes:annex-b-terms-and-definitions:d:distributed_system|Distributed System]] 
-  * [[private:99_annexes:annex-b-terms-and-definitions:d:dido|Distributed Immutable Data Object (DIDO)]] +  * [[public:99_annexes:annex-b-terms-and-definitions:d:dido|Distributed Immutable Data Object (DIDO)]] 
-  * [[private:99_annexes:annex-b-terms-and-definitions:d:dido-te|Distributed Immutable Data Object Test Environment (DIDO-TE)]]+  * [[public:99_annexes:annex-b-terms-and-definitions:d:dido-te|Distributed Immutable Data Object Test Environment (DIDO-TE)]]
  
 The previous shared definition restricted Node to an architectural participant in a distributed financial system. This revision removes the financial-domain restriction while preserving identification, responsibility, role, communication, monitoring, governance, and traceability as characteristics of a Node. The previous shared definition restricted Node to an architectural participant in a distributed financial system. This revision removes the financial-domain restriction while preserving identification, responsibility, role, communication, monitoring, governance, and traceability as characteristics of a Node.
Line 93: Line 93:
   * A network address   * A network address
   * A data structure   * A data structure
-  * A [[private:99_annexes:annex-b-terms-and-definitions:d:data_object|Data Object]]+  * A [[public:99_annexes:annex-b-terms-and-definitions:d:data_object|Data Object]]
   * An implementation artifact   * An implementation artifact
  
Line 113: Line 113:
   * The Evidence the Node produces   * The Evidence the Node produces
  
-Within a [[private:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]], a Node can act as part of the System Under Test, as a supporting test participant, or as a test instrument.+Within a [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]], a Node can act as part of the System Under Test, as a supporting test participant, or as a test instrument.
  
 ===== Example ===== ===== Example =====
Line 119: Line 119:
 A DIDO network contains five Nodes. Each Node validates proposed state transitions and maintains the DIDO states assigned to it by the governing architecture. A DIDO network contains five Nodes. Each Node validates proposed state transitions and maintains the DIDO states assigned to it by the governing architecture.
  
-A [[private:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] Test Environment realizes four Nodes using containers and one Node using a physical machine.+A [[public:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] Test Environment realizes four Nodes using containers and one Node using a physical machine.
  
 The realization technologies differ, but each participant remains a Node because it has a distinct Node Identity and performs assigned roles within the Distributed System. The realization technologies differ, but each participant remains a Node because it has a distinct Node Identity and performs assigned roles within the Distributed System.
  • public/99_annexes/annex-b-terms-and-definitions/n/node.1789260159.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido