A specification which cites Transmodel needs to include comparisons of the specification against the Transmodel reference data model in at least two conformance levels:
- level 1 (the global level) identifies which data domains within the specification are drawn from the Transmodel data domains, and which are not;
- level 2 (the detailed level) compares the data model within the specification against the Transmodel entities.
The level 1 conformance statement should be presented as a table based on one of the following:
- the Transmodel data domains as described in the normative part of the document. This covers the description of the network, versions/validity/layers, tactical planning components, vehicle scheduling, driver scheduling, schedules and versions, rostering, personnel disposition, operations monitoring and control, passenger information, fare collection, management information, multi-modal operation, multiple operators’ environment; or
- the corresponding UML diagrams as presented in the Standard [note: UML models were an informative annex in v5.1 of Transmodel, but will be in the normative documentation of v6 of Transmodel].
The level 2 conformance statement should be presented as a table in which the data concepts used in the specification are described as:
- “Unmodified”: concepts in the specification which have the same definition, properties and relationships as in the corresponding Transmodel domain;
- “Modified”: concepts in the specification which are similar to a Transmodel concept but which differ in the details of certain attributes and/or relationships (e.g. attributes added);
- “Alternative”: concepts or groups of concepts in the specification which model the same concepts as in Transmodel but in a significantly different way;
- “Additional”: concepts in the specification which are not covered by, and therefore cannot be drawn from, Transmodel;
- “Omitted”: concepts in Transmodel which are not used in the specification.