oship-dev team mailing list archive
-
oship-dev team
-
Mailing list archive
-
Message #01626
Last issues about date/time classes
Hi folks,
Once again, I'm stuck on a new problem about date/time object : How
calculate a partial date/time magnitude ? Is It must be different from
a complete date/time ? At the moment, I'm considering a partial
date/time such as a timeline. For example : the magnitude from 1953-10
partial date is the days sum from 0000/01/01 to 1953/10/31, according
to the algorithm that I implemented. Other example : The 1953 partial
date means the timeline from 0000/01/01 until 1953/12/31 . Do you mean
that is a good behavior ? If not , how it should be ?
Tim:
Do have any progress about the issues related to the ISO8601 standard,
Gregorian Calendar and "year zero" that I asked here ? After read lots
of sources on the Internet, now I'm wondering the openEHR
specification could be wrong on consider the year 0000 as a valid
year. Which part of specification you mean that's correct and which
part is not ?
I'm just finding a way to fix these problems in order to push all code
changes on date/time classes from the quantity module to the Launchpad
repository.
Any help will be appreciated.
Regards
Follow ups