![](bg4.png)
4.3 Converting a Composite
Calendar to Another Composite
Calendar
To avoid loss of data in the conversion, the
corresponding complete calendar for the source
calendar will be utilized. This complete calendar
will be converted to the corresponding complete
calendar for the destination calendar. According to
the structure of the destination calendar, the time
intervals will be excluded from the complete
destination calendar by using the operation exclude.
An example is converting R:(year, month, day)
to R:(year, week, day). The converting process is
illustrated below:
Step1: The hierarchical structure of the source
calendar H:(year, month, day) will be converted to
H:(year, week, day).
Step2: The operation exclude is used to exclude
time intervals from the destination calendar
(complete).
exclude (union (holidays, weekends), P:(year,
week, day)) → R:(year, week, day).
5 CONCLUSION
In this paper, I proposed a systematic method that
enables effectively converting time-series data
appearing in enterprises. Time-series data is
modelled as an attribute that is associated with a
calendar. Therefore, this work focuses on converting
calendar systems. I presented a generalized
representing form, with which various complex
structures of calendar systems can be represented in
a consistent form. The converting processes and
operations are based on the representing form. The
conversion between different calendars is presented
in detail.
REFERENCES
Chandra, R., Segev, A. & Stonebraker, M., 1994.
Implementing Calendars and Temporal Rules in Next
Generation Databases. In Proc. 3rd Int’l Conf. On
Data Engineering, pp.264-273.
Dangelmaier, W. & Ketterer, 1995. Industrial
Manufacturing Management Data. ISO
TC184/SC4/WG8-P3.
Dreyer, W., Dittrich, A.K. & Schmidt, D., 1994. An
Object-Oriented Data Model for a Time Series
Management System. In Proc. 7th Int’l Working Conf.
On Scientific and Statistical Database Management,
pp.186-195.
Dreyer, W., Dittrich, A.K. & Schmidt, D., 1994. Research
Perspectives for Time Series Management Systems. In
ACM SIGMOD Record, Vol. 23, No. 1, pp.10-15.
Dreyer, W., Dittrich, A.K. & Schmidt, D., 1995. Using the
CALENDAR Time Series Management System. In
Proc. ACM SIGMOD Int’l Conf., pp.489-502.
Dyreson, C. E. & Snodgrass, R. T., 1993. Timestamp
Semantics and Representation. In Information
Systems, 18, No.3, pp.143-166.
Elmasri, R. & Wuu, G., 1990. A Temporal Model and
Query Language for ER Database. In IEEE Data
Engineering Conference.
Gadia, S. & Yeung, C., 1990. A Generalized Model for a
Temporal Relational Database. In ACM SIGMOD
Conference.
Lee, J. Y., Elmasri, R. & Won, J., 1996. Specification of
Calendars and Time Series for Temporal Databases. In
Conceptual Modeling – ER’96. pp.341-356.
Peng, L., 2001. Datenkonversion fuer den Datenaustausch
in verteilten Fertigungslenkungssystemen. HNI-
Verlagsschriftenreihe, Bd.98.
Rose, E. & Segev, A., 1991. TOODM – A Temporal
Object-Oriented Data Model with Temporal
Constraints. In Proc. 10th International Conference on
the Entity-Relationship Approach.
Snodgress, R., 1995. The TSQL2 Temporal Query
Language. Kluwer Academic Publisher.
2005
(2005, 1) (2005, 12)…
(2005, 1, 1), …, (2005, 1, 31), …, (2005, 12, 1), …, (2005, 12, 31)
Fi
ure 5: The hierarchical
omain of the Gre
orian calenda
.
ICEIS 2006 - DATABASES AND INFORMATION SYSTEMS INTEGRATION
292