oship-dev team mailing list archive
-
oship-dev team
-
Mailing list archive
-
Message #01629
Re: Last issues about date/time classes
On Tue, 2010-11-30 at 21:49 -0200, Diego Manhães Pinheiro wrote:
> > For example:
> > a magnitude for 1953-10 would be the number of months 0001-01 to 1953-10
> I think you missed an important point : magnitude must be a numeric
> value as days (page 58 on data_types spec.) on DV_DATE objects and in
> the seconds( page 59 ) for DV_TIME and DV_DATE_TIME (page 60), being
> able to accept a partial or non-partial date/time format. So, How
> should I proceed ?
The openEHR specs are wrong or incomplete. You cannot do this without
further guidance from the specs. So we deviate and document the
differences. As I said, I think the rational thing to do is go with the
smallest units available in a partial datetime. In any case where you
might find data that is YYYY-MM-??:HH you cannot go with hours. Months
is the small full unit you have.
Does that make sense?
> Thanks. I didn't have any options, unless ask on the mailing list.
> This topic is totally messed up both on the specification and on the
> Internet.
That is what happens when thoughtless people design standards :-)
--Tim
Attachment:
signature.asc
Description: This is a digitally signed message part
Follow ups
References