 |
JSR 310 Date and Time - Discussion
Design principles:
Decisions:
- Choices - the main choices (decisions) to be taken
These model items are considered in scope for consideration in the JSR:
- Instant/Timestamp - a point in time not to be accessed by calendar fields, typically a duration from an epoch
- Datetime/Timepoint - datetimes/dates which are accessed primarily by calendar fields
- Calendar and duration fields - the calendar and duration fields themselves
- Duration - the scientific quantity of time
- Period - a descriptive form of time, such as a day, which may vary in duration
- Interval - the interval between a start point and an end point - could be instant or datetime based
- Recurrent time - such as day of week or time of day, which recurs repeatedly
- Time zones - zone support is needed
- Calendar systems -many different systems exist, should we pick a default
These areas are also considered in scope for consideration in the JSR:
These items may be considered however they are potentially large areas in their own right
- Recurrence - general case of recurrences - RFC 2445
- Working weeks - defining which days are work days and which are not
- Business days - highly related to working weeks, but also should exclude holidays
- SQL changes - updating JDBC and JPA to support direct storage to the correct database types. It will have to be handled by a new release of those APIs; we cannot change these packages/specs
- Time zone updates - improving the way in which time zone rule changes are handled
- Altering the system clock - allowing time based test cases to be written (a very common need)
- Leap seconds - the occasional leap seconds are generally ignored by programmers
The following terms are being discussed for adoption within the spec. Please note that not all concepts represented by these terms will necessarily be included in the final API / spec.
|