Bert,
if you serialise a AOM archetype to any object dump format, you need
typing information for the simple reason that there is polymorphism in
the model, mainly places where the static type is C_OBJECT,
C_DEFINED_OBJECT or C_PRIMITIVE_OBJECT but the attached type in a real
archetype can be a number of descendant types.
W.r.t. the naming convention of RM types, attributes etc, I assume you
are referring to the fact that openEHR archetypes use the published RM
type and attribute name format, which is so-called 'snake-case' rather
than 'camelCase'. To make archetypes that refer to data objects usable
across software written in different languages using different case
conventions, it may make sense to add an option to OPT generation which
indicates the flavour of RM casing. I had not thought of this before but
it would be easy to implement in an OPT generator.
BMM is getting more powerful by the way. I have recently extended it so
that it allows types to be annotated with a 'value-set' identifier,
which can be used to limit the values of e.g. data fields of type
CodePhrase or TerminologyCode to particular terminologies.
- thomas
On 15/02/2019 22:03, Bert Verhees wrote:
I was thinking about the type information ADL has, if it has function
in validating datasets.
I don't think so, and I think it can be omitted. For
validating-purpose it is not needed.
An archetype is a tree of properties to properties ending via
cardinality to leaf nodes. That is the information that is needed and
JSON can deliver that without diverging from the object dump idea. All
that information is already in AOM. This has as result that archetypes
can be read in AOM without need of parsing.
I was also thinking about the name-convention, but that is a reference
model (BMM) issue. The naming convention in the reference model will
be used in datasets.
BMM is very powerful, it extends the purpose of reference models and
archetypes to virtually every domain, also OpenEhr 😉.
It is in fact a wonderful invention, especially in combination with
NoSql databases, but it needs a simplicity overhauling for efficiency
and general connection to programming eco systems or standards can be
achieved by using its conventions.
Bert
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
