On 19-03-18 16:16, Thomas Beale wrote:
On 19/03/2018 08:57, GF wrote:
Again my thoughts
Duration is not a Data Type in many computer languages.
So we need to model it in an Archetype (Chairos)
that's true, but in databases and XML it is, and it is mostly treated
like a primitive data type - i.e. a non-identified, instance-only type
- in most language libraries. Note - here I am talking about a
primitive type 'Duration' (also Iso8601_duration), not types like
DV_DURATION. For AOM2, we treat it and the other date/time primitives
as proper primitive types, also Uri, etc, and it makes life much easier.
- thomas
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
My opinions:
First: I agree with the distinction in datatypes between AOM and RM. The
AOM should live as much as possible independent from the RM (I prefer
completely independent), the RM should only deal with data-constructions
and datatypes to describe target-data in.
Second: The archetype should be independent from the used computer
language to build the AOM in. In many languages Duration is a valid
datatype.
Java has it, Golang has it, C++ has it. And if it is not in a
programming language, that language should be extended by a library
which delivers the datatype.
Best regards
Bert
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
