Hi Bert, I was saying ISO8601 do support this - it is openEHR that constrains to milliseconds.
In my case it is action potential measurement from myocytes Cheers, -koray From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Bert Verhees Sent: Tuesday, 2 February 2016 10:59 p.m. To: openehr-technical@lists.openehr.org Subject: [FORGED] Re: Representing microseconds in DateTime Just for the record, which medical requirement makes measuring micro-seconds necessary? By the way, ISO allows one or more digits to represent a decimal fraction of a second. I don't have the original standard at hand, but Wikipedia says: https://en.wikipedia.org/wiki/ISO_8601 There is no limit on the number of decimal places for the decimal fraction. Bert On 02-02-16 10:51, Koray Atalag wrote: Hi, I have a requirement to capture timeseries data which happens at 250 microseconds - that is 0.000250 seconds. While many programming languages, and the ISO8601 spec, supports this openEHR RM<http://www.openehr.org/releases/RM/latest/docs/support/support.html#_iso8601_time_class> seems to be constrained to milliseconds: hh:mm:ss[,sss][Z | ±hh[mm]] Any particular reason we dump microseconds? If not can we add this capability - I think it won't break any existing code (I hope!) Cheers, -koray _______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
