Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:i:interoperability_activity [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:i:interoperability_activity [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Interoperability Activity ====== | ||
| + | |||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Interoperability Activity is a coordinated set of actions through which identified entities exchange and use information under governed conditions. It provides the organizing context that relates the participating entities, governing [[public: | ||
| + | |||
| + | An Interoperability Activity may include: | ||
| + | |||
| + | * Establishing an interaction | ||
| + | * Exchanging requests and responses | ||
| + | * Publishing or receiving information | ||
| + | * Invoking or providing a service | ||
| + | * Interpreting exchanged information | ||
| + | * Handling an error or exception | ||
| + | * Terminating an interaction | ||
| + | |||
| + | An Interoperability Activity remains distinct from an individual [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc., derived for DIDO-TE from the interoperability concepts in ISO/IEC 25010:2023 | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An Interoperability Activity may complete successfully, | ||
| + | |||
| + | An Interoperability Activity may contain subordinate interactions and may involve multiple Nodes, Test Environments, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | Two Nodes perform an Interoperability Activity in which one Node requests a Test Result and the other returns information conforming to their governing Interface Contract. The receiving Node interprets the returned information and records the resulting Interoperability Outcome. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||