Result Formats
Validation results can be exported to Excel, JSON, or CSV. All formats contain an indication if the model conforms and a list of information, warning, and error entries. The structure of the entries depends on the executed validation. There is one structure for the Compare and one for the SHACL validation.
SHACL validation result entry
| Excel column | CSV column | JSON field | Description |
|---|---|---|---|
| Focus Node | Focus node | focusNode | Identifier of the Node the entry is about. |
| Path | Path | resultPath | Field name in the XML. |
| Value | Value | value | Field value in the XML. |
| Source | Source | sourceShape | SHACL rule that triggered the entry |
| Constraint | Component | Constraint | Component |
| Details | Details | detail | |
| Message | Message | resultMessage | Message that describes the error, information, or warning. |
| Severity | Severity | resultSeverity | Severity level |
| Description | Description | description | |
| Order | Order | order | |
| Name | Name | name | |
| Group | Group | group |
Compare validation result entry
| Excel column | CSV column | JSON field | Description |
|---|---|---|---|
| Item | Item | item } Item that will be compared. | |
| Property | Property | property | Field name in the XML. |
| Model A | Model A | valueModelA | Value in Model A. |
| Model B | Model B | valueModelB | Value in Model B. |
| Severity | Severity | resultSeverity | Severity level |
| Message | Message | resultMessage | Message that describes the error, information, or warning. |
| Deviation | Deviation | deviation | Deviation between the two values. |
Excel
The first four lines contain the information if the model conforms and how many entries have the severity levels error, warning, and information. Below this, all result entries are listed.
JSON
The schemas for the structure can be found in the Appendix.
CSV
The first line contains the information if the model conforms. Below this, all result entries are listed.
Workflow
The validation module provides a use case for each validation type. The use cases can be configured to use different mapping configurations. These mapping configurations will be used to map the data during loading of the data models. Supported mapping configurations are “file mapping”, “RDF file mapping” and “no mapping”. The workflows in the use cases follow the same structure. At first the provided data is loaded. During this process the data is filtered based on the provided configuration. Afterwards a union model is created if the validation data consists of multiple files. When all needed data is loaded the validation engine starts the validation and produces a result object. This result object is returned by the use case.