Common Logical Data Model: Basis for Global ITS Innovation
Figure 3: Data Model Framework
who might have a great deal of experience in
tangential business areas but who are
focused on developing an interoperability
solution for one specific need in a timely
manner.
Each of these layers is described further
below, in the expected chronological order
of their development. 33,34,35
Physical Data Models
Practical business needs are generally the
driving factor behind the creation of
interface standards. When these business
needs arise, the stakeholder community
providing funds for the development of a
solution is usually less interested in
undertaking large cooperative efforts that
engage with tangential business interests;
instead, there are typically strong motivating
factors to keep a tight focus on their primary
business interest. The result is that interface
standards are developed by industry experts
Every interoperable solution for exchanging
information has an associated physical data
model, either explicitly or implicitly defined.
This data model simply identifies the data
structures and data elements exchanged
across the interface. These structures can be
represented in numerous ways including
XML schema, ASN.1 modules and UML class
diagrams, among others. This paper uses
UML class diagrams as a useful way to easily
compare alternative solutions. For example,
Figure 4 provides an example of a portion of
33 The Enterprise Data Model: A Framework for Enterprise Data Architecture, 2 nd Edition, A. Graham, Koios Associates, Ltd., 2012.
34 Data Architecture: From Zen to Reality, Charles Tupper, Elseview Inc., 2011.
35 Enabling Things to Talk: Designing IoT solutions with the IoT Architectural Reference Model, A Bassi, et al., Springer, 2013.
- 35 -
March 2020