dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010b-specify-twin-interaction-direction

Differences

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

Link to this comparison view

dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010b-specify-twin-interaction-direction [2026/08/21 16:16] – created nick_didodido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010b-specify-twin-interaction-direction [2026/08/21 16:58] (current) – nick_dido
Line 15: Line 15:
 ===== Rationale ===== ===== Rationale =====
  
-An interaction permitted within a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] may not be permitted in every direction.+An interaction permitted within a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_relationship|Twin Relationship]] may be permitted in one direction, the reverse direction, or both directions.
  
-For example, a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] may be permitted to receive state information from a corresponding [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] without being permitted to modify that Node. Another interaction may permit exchange in both directions.+For example, a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] may receive state information from a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] without having permission to modify that Node.
  
-Explicit specification of interaction direction prevents bidirectional authority from being inferred from connectivity, observation capability, publication and subscription relationships, or access to a technically usable interface.+Explicit direction prevents bidirectional interaction from being inferred from connectivity, observation capability, DDS publication and subscription relationships, or access to an interface.
  
-Interaction direction is distinct from authorization. Direction specifies where an interaction may flow; authorization determines whether the interaction is permitted to execute under the governing conditions.+Interaction direction remains distinct from interaction permission and authorization. TWIN-010a identifies permitted interactions. TWIN-010b specifies their direction. TWIN-010c governs authorization requirements for state-changing interactions.
  
 ===== Applies To ===== ===== Applies To =====
Line 39: Line 39:
 Verification confirms that: Verification confirms that:
  
-  - Each permitted interaction identifies its permitted direction. +  - Each permitted interaction has a specified direction. 
-  - The specified direction identifies the participating source and destination entities.+  - The specified direction identifies the originating and receiving entities.
   - A unidirectional interaction does not imply permission for the reverse interaction.   - A unidirectional interaction does not imply permission for the reverse interaction.
   - A bidirectional interaction is distinguishable from a unidirectional interaction.   - A bidirectional interaction is distinguishable from a unidirectional interaction.
-  - Technical connectivity, DDS publication and subscription relationships, API availability, or Quality of Service compatibility does not override the specified interaction direction. +  - Communication connectivity, DDS publication and subscription relationships, interface availability, or Quality of Service compatibility do not override the specified interaction direction. 
-  - The specified direction is traceable to the governing Configuration.+  - The specified interaction direction is traceable to the governing Configuration.
  
-Verification includes at least one unidirectional interaction and confirms that the reverse interaction is not inferred as permitted.+Verification includes at least one unidirectional interaction and confirms that the reverse interaction is not treated as permitted.
  
 ===== Traceability ===== ===== Traceability =====
Line 54: Line 54:
 ===== ConOps Relationship ===== ===== ConOps Relationship =====
  
-This requirement establishes the permitted direction of interactions identified under TWIN-010a before authorization or execution of those interactions is evaluated.+This requirement establishes the permitted direction of interactions identified under TWIN-010a before authorization or execution is evaluated.
  
 ===== Delivery Phase ===== ===== Delivery Phase =====
  • dido/03-dido-te/99-annexes/annex-c-requirements/03-functional-requirements/03-03-twin-node-requirements/twin-010-control-twin-interaction/twin-010b-specify-twin-interaction-direction.1787354173.txt.gz
  • Last modified: 2026/08/21 16:16
  • by nick_dido