Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:i:interpretive_artefact [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:i:interpretive_artefact [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Interpretive Artifact ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An interpretive artifact identifies a governed construct that defines logic or rules applied during [[dido: | ||
| + | |||
| + | Interpretive artifacts support consistent interpretation by separating governed logic from implementation code, runtime technology, storage technology, and deployment environment. | ||
| + | |||
| + | An interpretive artifact differs from an implementation artifact. An implementation artifact realizes logic through a selected technology. An interpretive artifact defines the governed logic or rules that guide interpretation independently of the selected implementation mechanism. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //governed construct defining logic or rules applied during [[dido: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Structured Information Processing [[dido: | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An interpretive artifact provides a controlled basis for applying logic, rules, and semantic meaning during structured information processing. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A policy rule set, validation rule, interpretation rule, lifecycle rule, or semantic mapping is an interpretive artifact when the [[dido: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||