oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi Diego,


On Tue, 2010-11-30 at 19:00 -0200, Diego Manhães Pinheiro wrote:
> 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 ?

A partial datetime magnitude can only be calculated based on the
smallest unit available. 

For example:
a magnitude for 1953-10 would be the number of months 0001-01 to 1953-10


> 
> 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 ?

Apologies.  I thought this was settled.  The openEHR specs are
incorrect.  There is no year zero. 

> 
> 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.
> 

Excellent.  :-)


--Tim

Attachment: signature.asc
Description: This is a digitally signed message part