Smalltalk-80: the language and its implementation
Smalltalk-80: the language and its implementation
Automatic deduction of temporal information
ACM Transactions on Database Systems (TODS)
Temporal modules: an approach toward federated temporal databases
SIGMOD '93 Proceedings of the 1993 ACM SIGMOD international conference on Management of data
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Time modeling in office information systems
SIGMOD '85 Proceedings of the 1985 ACM SIGMOD international conference on Management of data
Maintaining knowledge about temporal intervals
Communications of the ACM
Calendrical Calculations: the millennium edition
Calendrical Calculations: the millennium edition
Object Database Standard: ODMG-93
Object Database Standard: ODMG-93
Test Driven Development: By Example
Test Driven Development: By Example
Temporal Data Management Systems: A Comparative View
IEEE Transactions on Knowledge and Data Engineering
Extending the ODMG Object Model with Time
ECCOP '98 Proceedings of the 12th European Conference on Object-Oriented Programming
Object-oriented units of measurement
OOPSLA '04 Proceedings of the 19th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Arithmetic with measurements on dynamically-typed object-oriented languages
OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
| Hi-index | 0.00 |
Time is an important aspect of all real world entities; temporal information is crucial in many computer-based applications. The Smalltalk community does not have a good model of the time domain. Smalltalk-80 and its commercial implementations provide only the classes Date and Time to model time domain entities. Squeak augmented the model with the abstractions Timespan, Year, Month and Week. These models fall short when complex situations of the time domain have to be programmed, forcing the programmers to create their own and repetitive solutions. In this paper, we present a model of the Gregorian Calendar based on a metaphor that maps time entities into points of lines, each line with its own resolution. The model addresses a great amount of functionality and reifies almost all the Gregorian Calendar entities. It allows programmers to design and program time related issues better than current time domain implementations, and in a more natural way.