Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:f:formal_semantics [2026/07/11 11:14] – ↷ Links adapted because of a move operation nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:f:formal_semantics [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 9: / Line 9: @@
 Formal semantics separates meaning from implementation syntax, storage technology, programming language, exchange mechanism, deployment environment, or runtime platform.
-Formal semantics supports consistent interpretation across implementations, tools, organisations, and governance contexts. It provides a basis for traceability, conformance evaluation, controlled interpretation, and semantic consistency within the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]].
+Formal semantics supports consistent interpretation across implementations, tools, organizations, and governance contexts. It provides a basis for traceability, conformance evaluation, controlled interpretation, and semantic consistency within the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]].
 ===== Definition =====
@@ Line 25: / Line 25: @@
 ===== Example =====
-A [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] defines the meaning of an [[dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point]], [[dido:99_annexes:annex-b-terms-and-definitions:c:conformance_point]], lifecycle state, or governed artefact independently of the software mechanism that implements it.
+A [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] defines the meaning of an [[dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point]], [[dido:99_annexes:annex-b-terms-and-definitions:c:conformance_point]], lifecycle state, or governed artifact independently of the software mechanism that implements it.
 ----