Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| dido:99_annexes:annex-b-terms-and-definitions:p:portability [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:p:portability [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Discussion ===== | ===== Discussion ===== | ||
| - | Portability describes the ability of a governed function implementation to move across approved platforms, runtimes, deployment environments, | + | Portability describes the ability of a governed function implementation to move across approved platforms, runtimes, deployment environments, |
| Portability does not mean that a Qualified Node may move without review. A movement that changes jurisdiction, | Portability does not mean that a Qualified Node may move without review. A movement that changes jurisdiction, | ||
| ===== Definition ===== | ===== Definition ===== | ||
| - | //ability of a governed function implementation to operate across approved platforms, runtimes, or deployment environments while preserving the required | + | //ability of a governed function implementation to operate across approved platforms, runtimes, or deployment environments while preserving the required |
| ===== Source ===== | ===== Source ===== | ||
| Line 19: | Line 19: | ||
| ===== Example ===== | ===== Example ===== | ||
| - | A semantic validation Node runs in one approved container environment and later runs in another approved container environment. The Node preserves interface | + | A semantic validation Node runs in one approved container environment and later runs in another approved container environment. The Node preserves interface |