I mean OPT2, which is according to the ooenehr specifications a flattened archetype with extra operations performed on it, such as including and flattening all archetype roots in the same tree, including their terminologies,and replacing all use_node with a copy of the tree to be used. Very useful. Can be expressed in ADL.
Archie does not support the 1.4 xml OPT format. Note that xml bindings are in place for the AOM, but I wouldn't use them for interoperability because they were written before an official xsd has been published - I'm actually not sure if an official AOM 2 xsd currently exists. Note that there is also the concept of a template, which is also an archetype, but is different from an operational template - templates are authored, opts are generated, often generated from a template. Regards, Pieter Bos Op 12 feb. 2019 19:12 schreef Seref Arikan <serefari...@kurumsalteknoloji.com>: Hi Pieter, Excellent work, many thanks for all the effort your team put into this library. Could you clarify something? When you say an operational template, do you mean a flattened archetype as per ADL 2.0? (that's the impression I got looking at the code) I'm a bit behind re adl 2.0; does your implementation imply that an opt according to 2.0 specs is no different than an archetype? I can see that you declared some xml bindings in your OperationalTemplate class which seam to refer to type names from opt 1.4 . In summary I'm a bit confused :) Could you briefly explain how Archie team sees the relationship between opt 1.4 and 2.0 ? All the best Seref On Tue, Feb 12, 2019 at 1:04 PM Pieter Bos <pieter....@nedap.com<mailto:pieter....@nedap.com>> wrote: Today I’m pleased to announce another major release of the Archie library. This release brings a number of new features and improvements: * A tool that constructs valid json example instances of RM Objects, based on an operational template. Can be parsed to RM Objects. * Native ODIN serialization of arbitrary java objects using the Jackson library, now used in Archetype and P_BMM serialization * The library is now supported on Android, Android 8.0/API level 26 and higher, including faster initialization time * The RM implementation has been verified against the 1.0.4 BMM models, and fixed where needed * A complete rewrite of the P_BMM implementation, with improved validation. The new implementation is much easier to understand and maintain Because of the last two features, this version may require some changes to your existing code. For more information, see https://github.com/openEHR/archie/releases/tag/0.6.0 and the readme. Regards, Pieter Bos Nedap Healthcare _______________________________________________ openEHR-implementers mailing list openEHR-implementers@lists.openehr.org<mailto:openEHR-implementers@lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
_______________________________________________ openEHR-implementers mailing list openEHR-implementers@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
