When I’n not mistaken: Duration is not the same concept as Calendar. IsoTime and Calendar are both data types defining an absolute point on the time line, but in different ways.
Duration is the difference between points on the time line. My point is that some times we can not/want not use points on the time line but use fussier terms like: begin of an event somewhere in 2015, or a duration of one month, or Gerard Freriks +31 620347088 [email protected] Kattensingel 20 2801 CA Gouda the Netherlands > On 21 Mar 2018, at 15:02, Bert Verhees <[email protected]> wrote: > > I don't mind how you call it, programmers call it Duration and Calendar, both > are well known datatypes, but they have other semantics. > > > On 21-03-18 14:53, GF wrote: >> >> You gave proof that there are different kinds of time. >> Chrono-time as used fro time stamping at one exact point in time. >> And Chairos-time used for imprecise relative time as used by humans, >> >> Chrono-time is one primitive data type. >> Chairos-time is defined using archetype/patterns >> >> >> >> Gerard Freriks >> +31 620347088 >> [email protected] <mailto:[email protected]> >> >> Kattensingel 20 >> 2801 CA Gouda >> the Netherlands >> >>> On 21 Mar 2018, at 12:25, Bert Verhees <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>> On 21-03-18 10:50, GF wrote: >>>> Does including Duration in the RM fit with the scope for the RM? >>>> >>>> Why do we have archetypes? >>>> Why not include every thing in the RM? >>>> Do we want the HL7v3 Reference Model as it existed many years ago and that >>>> could not be inspected without a magnifying glass on a sheet of paper that >>>> was 2 by 1 meters? >>>> >>>> Is there one kind of duration? >>>> 24 minutes, 5 seconds? >>>> For 2 hours past midnight? >>>> For 2 hours after (clinical) event x >>>> For 2 months after (clinical) event y >>> 2 months cannot be technically represented in a duration, because month is >>> not a stable time-definition. It is a Calendar definition. >>> It is therefor that most major programing languages have a Duration and a >>> Calendar class. >>> Or you say that OpenEhr has no valid Duration-datatype, so always express >>> Duration in an archetype (your way), >>> or say that OpenEhr has a valid Dv_Duration type, and do it right (I prefer >>> this way), >>> or express months as if it is a stable time-indicator and ignore it is not >>> (like it is now) >>> >>> Those are the three possible ways to solve this problem, I think >>> I am curious to learn what the community will decide. >>> >>> Bert >> >> >> >> _______________________________________________ >> openEHR-technical mailing list >> [email protected] >> <mailto:[email protected]> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> <http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org> > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
