dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result_endpoint

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result_endpoint [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result_endpoint [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== FX Validation Result Endpoint ======
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +The FX Validation Result Endpoint carries FX validation outcomes from the FX Validation Node to downstream FX logical Nodes.
 +
 +The endpoint supports validation review, semantic interpretation, contract state processing, audit, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] expectations. It carries FX Validation Result information that identifies validation status, errors or warnings, input reference, rule version, producing [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], timestamp, and provenance reference.
 +
 +The FX Validation Result 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 validation outcomes require [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to the validated input, validation logic, rule version, and producing Node.
 +
 +===== Definition =====
 +
 +//[[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] carrying validation outcomes for FX transaction information//
 +
 +===== Source =====
 +
 +Specialization of Logical Communication Endpoint from [[fxdemo:02-part:start]], Section 7.2, and [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] from [[fxdemo:01-part:start]], Section 7.6; generalised from validation result and data-plane material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
 +
 +===== Note =====
 +
 +The FX Validation Result Endpoint is not a validation engine, schema validator, DDS Topic, REST resource, RPC method, message queue, event stream, file, or database table.
 +
 +===== Example =====
 +
 +The FX Validation Node publishes an FX Validation Result that the FX Semantic Interpretation Node and FX Audit and Provenance Node consume.