Order

This is perhaps the most easily overlooked, and hardest to address, fundamental relation. The concept of ordering lists, events, sequences, etc is a familiar activity in computing, engineering, information management, etc. However, addressing aspects of order is hard if we want to maintain internal consistency (within the model). Even the apparently simple notion of a relationship in data, as illustrated in the various node-edge diagrams, has an order to it (start - rel - end, sometimes referred to as the domains and ranges of each named relationship):

graph LR
  e7b2866d-7667-4e3c-b829-1a23ae21f1c1(("patterns <br> e7b2866d-7667-4e3c <br> -b829-1a23ae21f1c1"))--->|"<b> temporal_part_of"|a5a6ba71-b2bb-4ed5-b079-e7cab5dac94f(("patterns <br> a5a6ba71-b2bb-4ed5 <br> -b079-e7cab5dac94f"));

There are a number of applications of order in data models but for our integration data model we have 4-dimensionalist commitments. These include dealing with events (that are temporal boundaries of states, one at the start, beginning, and end, ending) and various ways of ordering those events (perhaps with a metric that represents time such as a date-time record):

graph LR
  e7b2866d-7667-4e3c-b829-1a23ae21f1c1(("patterns <br> e7b2866d-7667-4e3c <br> -b829-1a23ae21f1c1"))--->|"<b> beginning"|134d2714-dbee-45b2-9ff9-dbd57129f949(("patterns <br> 134d2714-dbee-45b2 <br> -9ff9-dbd57129f949"));
  e7b2866d-7667-4e3c-b829-1a23ae21f1c1(("patterns <br> e7b2866d-7667-4e3c <br> -b829-1a23ae21f1c1"))--->|"temporal_part_of"|a5a6ba71-b2bb-4ed5-b079-e7cab5dac94f(("patterns <br> a5a6ba71-b2bb-4ed5 <br> -b079-e7cab5dac94f"));
  e7b2866d-7667-4e3c-b829-1a23ae21f1c1(("patterns <br> e7b2866d-7667-4e3c <br> -b829-1a23ae21f1c1"))--->|"data_EntityName"|Example_state_of_Lunar_Lander_Module_Eagle_LM-5["Example_state_of <br> _Lunar_Lander_Module_Eagle_LM-5"];
  e7b2866d-7667-4e3c-b829-1a23ae21f1c1(("patterns <br> e7b2866d-7667-4e3c <br> -b829-1a23ae21f1c1"))--->|"<b> ending"|3a3962dd-59f5-4a60-b8c7-d57509b1314f(("patterns <br> 3a3962dd-59f5-4a60 <br> -b8c7-d57509b1314f"));
  e7b2866d-7667-4e3c-b829-1a23ae21f1c1(("patterns <br> e7b2866d-7667-4e3c <br> -b829-1a23ae21f1c1"))--->|"type"|state_of_functional_system(["hqdm <br> state_of_functiona <br> l_system"]);