DateTime::Incomplete seems to be about managing ambiguity. It seems to
me that what Kime is looking for is a data object with an additional
dimension of duration. Time spans are generally stored as two points
as exact as the date-time abstraction is use allows, and then there
are methods called things like "contains" and "overlaps." An
additional dimension is going to be required, if it is a second time
point, or an accuracy indicator, or what -- some additional
requirements gathering would be needed.  After he has rolled his own
solution, maybe he will share it?

Reply via email to