<?xml version="1.0"?>
<table>
<row>
<column>OK</column>
<column>OK</column>
<column>The formal validation did NOT detect any data constellations that would indicate (a) data incompleteness or incorrectness, e.g. inconsistency, and/or (b) described activities&apos; or objects&apos; lack of compliance with requirements, e.g. legal regulations or official constraints.</column>
<column>The validation protocol is empty, i.e. it contains neither INFO, WARNING nor ERROR entries.</column>
<column>Successful processing of the technical interaction/operation: The result of formal validation by itself does NOT impair the software&apos;s processing of the technical interaction/operation.</column>
<column></column>
<column></column>
</row>
<row>
<column>INFO</column>
<column>Info</column>
<column>The formal validation has detected data constellations that indicate (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints; or (c) the described activity or object has unusual properties which occur rarely in practice.</column>
<column>The validation protocol contains at least one INFO entry, but neither WARNING nor ERROR entries.</column>
<column>Successful processing of the technical interaction/operation: The result of formal validation by itself does NOT impair the software&apos;s processing of the technical interaction/operation.</column>
<column>The software has detected a data constellation that indicates (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints; or (c) the described activity or object has unusual properties which occur rarely in practice.</column>
<column>Successful processing of the technical interaction/operation: The data constellation by itself does NOT impair the software&apos;s processing of the technical interaction/operation.</column>
</row>
<row>
<column>WARNING</column>
<column>Warning</column>
<column>The formal validation has detected data constellations that indicate (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints.</column>
<column>The validation protocol contains at least one WARNING entry, but no ERROR entries. The validation protocol may also contain INFO entries.</column>
<column>Successful processing of the technical interaction/operation: The result of formal validation by itself does NOT impair the software&apos;s processing of the technical interaction/operation.</column>
<column>The software has detected a data constellation that indicates (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints.</column>
<column>Successful processing of the technical interaction/operation: The data constellation by itself does NOT impair the software&apos;s processing of the technical interaction/operation.</column>
</row>
<row>
<column>ERROR</column>
<column>Error</column>
<column>The formal validation has detected data constellations that indicate (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints.</column>
<column>The validation protocol contains at least one ERROR entry. The validation protocol may also contain WARNING and/or INFO entries.</column>
<column>Rejection/abortion of the technical interaction/operation: The result of the formal validation is such that the software does NOT carry out the technical interaction/operation, i.e. it aborts or rejects the technical interaction/operation. In particular, in the case of data transmissions, addressees do NOT have access to the transmitted data.</column>
<column>The software has detected a data constellation that indicates (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints.</column>
<column>Rejection/abortion of the technical interaction/operation: The data constellation is such that the software does NOT carry out the technical interaction/operation, i.e. it aborts or rejects the technical interaction/operation. In particular, in the case of data transmissions, addressees do NOT have access to the transmitted data.</column>
</row>
</table>
