The certification of a data producing product such as an electronic logbook requires that it meet standards, business rules, and expected results.
We assume that the data will be exchanged in XML files.
The layers from the most concrete to the most abstract are:
- Encoding - is the XML file encoded correctly. The top level element includes an encoding attribute, the file encoding must match that attribute. In practice, the eLandings system seems to require that UTF-8 encoding is required. See !PR_UTF-16.xml! for an example of non-compliant encoding.
- Well-formed XML - does the XML file meet the standard of XML. Does each tag have a closing tag, etc.
- XML meets Schema - does the structure of the XML file adhere to the XML schema for the particular exchange. This layer needs to comprehend changes in the XML schema over time. Does the data in the XML document match the data type rules specified by the schema.
- Data meets Business Rules - does the data in the XML file meet the requirements of the business rules in terms of required data, rules for data content of each elements, and rules for how the data elements interact.
These layers are checked both in the certification of a product and each time data from the product is submitted to the acquiring system. That is, the XML must be valid and the data must pass the business rules each time data is submitted.
...