Structure
These pages should be seen as the normative description of the classes described. In case of any conflict, the most specific description will always apply. For example, the description on the lines of a specific element takes precedence of the description at document level. Hence, the descriptions at document level are default values for the lines. The examples in the document and related common guidelines should be seen as descriptive. The guideline text takes precedence of the figures. The actual specification of a class is composed of:
A figure showing the class elements that are included in OIOUBL.
A text specification of the class.
A list of the fields that are included in the class with a corresponding table of key data such as definitions, names, references, and business rules for each of the class fields.
A list of the sub-classes that are included in the class with a corresponding table of key data such as definitions, names, references, and business rules for the sub-classes of the class.
An example of the class
A list of the UBL elements that from a business perspective make no sense in the specific context.
Figure definitions
In the class specifications, the class is shown as schema documentation.