Differences

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

--- dido:05-semantics:01-kinds-of-semantics:11-rule-semantics [2026/07/08 03:02] – ↷ Page moved from dido:01-semantics:01-kinds-of-semantics:11-rule-semantics to dido:05-semantics:01-kinds-of-semantics:11-rule-semantics nick_dido
+++ dido:05-semantics:01-kinds-of-semantics:11-rule-semantics [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Rule Semantics ======
-[[fxdemo:99_part_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
@@ Line 7: / Line 7: @@
 Rule semantics defines meaning through rules, conditions, constraints, decisions, obligations, prohibitions, permissions, derivations, validations, and consequences.
-A rule expresses semantic content when it constrains what an artefact, system, actor, process, message, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:report|report]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:schema|schema]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:o:ontology|ontology]], or implementation behaviour means in a defined context. Rule semantics identifies the meaning of the condition, the required outcome, the prohibited outcome, the permitted outcome, and the consequence of rule satisfaction or violation.
+A rule expresses semantic content when it constrains what an artifact, system, actor, process, message, [[dido:99_annexes:annex-b-terms-and-definitions:r:report|report]], [[dido:99_annexes:annex-b-terms-and-definitions:s:schema|schema]], [[dido:99_annexes:annex-b-terms-and-definitions:o:ontology|ontology]], or implementation behavior means in a defined context. Rule semantics identifies the meaning of the condition, the required outcome, the prohibited outcome, the permitted outcome, and the consequence of rule satisfaction or violation.
-Rule semantics differs from rule syntax. Rule syntax provides the form of the rule. Rule semantics defines what the rule means and how the rule constrains interpretation or behaviour.
+Rule semantics differs from rule syntax. Rule syntax provides the form of the rule. Rule semantics defines what the rule means and how the rule constrains interpretation or behavior.
 Rule semantics also differs from implementation logic. Implementation logic executes or enforces selected rules. Rule semantics establishes the meaning that implementation logic preserves, validates, derives, or enforces.
-Rules appear in several forms, including natural-language business rules, decision tables, validation rules, policy rules, conformance rules, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:sbvm|Semantic Business Vocabulary Model (SBVM)]] vocabulary constraints, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:sbrm]] reporting rules, schema constraints, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:o:owl|OWL]] axioms, runtime checks, and executable rule engines.
+Rules appear in several forms, including natural-language business rules, decision tables, validation rules, policy rules, conformance rules, [[dido:99_annexes:annex-b-terms-and-definitions:s:sbvm|Semantic Business Vocabulary Model (SBVM)]] vocabulary constraints, [[dido:99_annexes:annex-b-terms-and-definitions:s:sbrm]] reporting rules, schema constraints, [[dido:99_annexes:annex-b-terms-and-definitions:o:owl|OWL]] axioms, runtime checks, and executable rule engines.
 Rule-processing architectures express rule semantics through defined responsibilities. A policy administration point records or manages governed rules. A policy information point supplies facts, attributes, or context used during rule evaluation. A policy decision point evaluates rules and produces decisions. A policy enforcement point enforces decisions.
@@ Line 43: / Line 43: @@
   * Traceability to semantic sources
-A governed architecture preserves [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] from rule semantics to the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], vocabulary, policy source, schema, ontology, report model, implementation artefact, or conformance test that expresses or validates the rule meaning.
+A governed architecture preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] from rule semantics to the [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model|conceptual model]], vocabulary, policy source, schema, ontology, report model, implementation artifact, or conformance test that expresses or validates the rule meaning.
 ===== Definition =====
@@ Line 51: / Line 51: @@
 ===== Source =====
-DIDO Solutions usage, informed by business rule practice, policy modelling, validation practice, conformance testing, semantic modelling practice, and model-driven architecture principles.
+DIDO Solutions usage, informed by business rule practice, policy modeling, validation practice, conformance testing, semantic modeling practice, and model-driven architecture principles.
 ===== Note =====