Content validation process - SDMX InfoSpace


The content validation process assumes that the structural validation of the dataset has been successfully completed beforehand. The central part of the content validation process is performed by the Content Validation Service (CONVAL). However, the task of collecting all inputs and routing of the resulting validation report for further user input or production steps belongs to the validation business process manager component.

A nominal content validation process can be described by a number of steps:

  1. The content validation service is called by the process manager to validate the SDMX IM compliant input file.

  2. The validation task containing validation rules and rule sets predefined for the respective dataset are executed. The service executes these rules and generates a Validation Report with all validation failures detected. The maximum number of failures reported is configurable to achieve both optimal service performance and ease of use.

  3. The performance of the process is monitored and a Key Performance Indicator (KPI) is set to indicate the estimated time for the validation task completion. This time expectation is established empirically from historical data by measuring the duration of each validation task.

  4. When the validation process completes, the process manager observes severity levels of failures detected in the validation report. The three levels observed are Error, Warning, and Information.

    1. In case of Error severity level present, process continuity is based on the business decision of the domain manager. The Error severity may be downgraded to Warning or left in place, in which case the process is aborted.

    2. In case of no Error but at least one Warning severity level present,

      • the process may continue with further checks, or

      • the process may complete (if all rules have been executed) and message the service invoker that corrective steps are required, or

      • the domain manager may perform manual corrections.

    3. In case of only Information severity level present the validation process is not obstructed. Information may occur in the presence of failures with higher severity levels and serves to provide the service invoker with additional information on dataset content.

  5. Once the content validation has been executed a decision gate is reached regarding whether the dataset should be uploaded to production databases for further processing.

  6. STRUVAL and CONVAL results are also presented in separate Validation Reports.