Databases Reference
In-Depth Information
16
CONCLUSION
Seamless Access to Temporal Data
381
Encapsulation of Temporal Data Structures and Processes
383
Design Encapsulation
384
Maintenance Encapsulation
386
Query Encapsulation
387
The Internalization of Pipeline Datasets
388
Performance
390
Enterprise Contextualization
390
Asserted Versioning as a Bridge and as a Destination
391
Asserted Versioning as a Bridge
391
Asserted Versioning as a Destination
392
Ongoing Research and Development
393
Going Forward
396
Glossary References
396
In the Preface, we listed four objectives for this topic. Those
objectives were to explain how to support:
(i) Seamless access to temporal data;
(ii) The encapsulation of temporal data structures and pro-
cesses;
(iii) The internalization of pipeline datasets; and
(iv) The enterprise contextualization of this functionality.
Let's see whether we have achieved these objectives.
Seamless Access to Temporal Data
We've known all along that, with enough hard work, we can
almost always pull together any data that the business asks
for—past or present versions of objects of interest, current data
about those versions or past data about them. And we now know
how to extend the range of what we can pull together to include
future data as well, in either or both of our two temporal
dimensions—although we emphasize, again, that it is only the
