| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:f:fx_semantic_interpretation_endpoint [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:f:fx_semantic_interpretation_endpoint [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| | ====== FX Semantic Interpretation Endpoint ====== |
| | |
| | [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| | |
| | ===== Discussion ===== |
| | |
| | The FX Semantic Interpretation Endpoint carries FX semantic interpretation results from the FX Semantic Interpretation Node to downstream FX logical Nodes. |
| | |
| | The endpoint supports semantic interpretation, contract state processing, policy evaluation, audit, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] expectations. It carries FX Semantic Assertion information that identifies interpreted meaning, semantic source, semantic version, input reference, producing [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], timestamp, and provenance reference. |
| | |
| | The FX Semantic Interpretation Endpoint participates primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]]. It also relates to the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] because semantic assertions require [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to input information, governed semantic definitions, semantic versions, and interpretation context. |
| | |
| | ===== Definition ===== |
| | |
| | //[[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] carrying semantic interpretation results for FX transaction information// |
| | |
| | ===== Source ===== |
| | |
| | Specialization of Logical Communication Endpoint from [[fxdemo:02-part:start]], Section 7.2, [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]] from [[fxdemo:01-part:start]], Section 9.4, and [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]] from [[fxdemo:01-part:start]], Section 9.5; generalised from semantic interpretation and local authoritative ontology material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. |
| | |
| | ===== Note ===== |
| | |
| | The FX Semantic Interpretation Endpoint does not prescribe FIBO, SBVR, OWL, RDF, a semantic repository, a rules engine, DDS, REST, RPC, or another implementation mechanism. |
| | |
| | ===== Example ===== |
| | |
| | The FX Semantic Interpretation Node publishes an FX Semantic Assertion that the FX Contract State Node consumes when establishing or updating contract state. |
| |