This is an old revision of the document!
FX Validation Result Endpoint
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 evidence expectations. It carries FX Validation Result information that identifies validation status, errors or warnings, input reference, rule version, producing Node, timestamp, and provenance reference.
The FX Validation Result Endpoint participates primarily in the FX Logical Data Plane. It also relates to the FX Logical Audit and Provenance Plane because validation outcomes require traceability to the validated input, validation logic, rule version, and producing Node.
Definition
Communication Endpoint carrying validation outcomes for FX transaction information
Source
Specialisation of Logical Communication Endpoint from Part 2: Distributed Node-Based Logical Architecture, Section 7.2, and Communication Endpoint from Part 1: Conceptual Architecture, Section 7.6; generalised from validation result and data-plane material in the original FX Demo 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.