When I say official I refer to AOM. If AOM/ADL let's you say something we try to support it. We always 'eat' what others tools produce, and have implemented export mechanisms to be compatible with the things other tools can handle. In this particular case you mentioned, an exported archetype from LinkEHR can be opened in any other archetype editor directly. We also gave support for OPT & OET import/export, and even OPTs generated this way are virtually identical to the ones coming from the template designer.
So yes, we have tweaked the parser to support more things, but the archetype creation is completely RM driven (archetypes created with LinkEHR are always compliant with the RM you choose). That created archetype can be then saved to different representations depending of your needs (ADL for specific tools, XML, etc). Regards El mié., 12 dic. 2018 15:09, Bert Verhees <bert.verh...@rosa.nl> escribió: > On 12-12-18 14:49, Diego Boscá wrote: > > These are modifications on the parser, which parses more things than > > your standard parser. In fact, the editor supports legal things in ADL > > that other parsers don't (e.g. explicit node identifiers or > > existence). The generated ADL is completely fine ADL. There are tools > > that don't comply with this general ADL, and we provided an export > > version of archetypes that produces a modified version of the ADL > > syntax that other older and not maintained tools can parse. > > If you want to call this subset "official archetypes" be my guest. > > The word "official" was used by you, I used it (in quotes) to indicate > that we refer to the same. > > But it may get confusing, also because in the past there were > discussions about LinkEhr and the Ocean archetype-editor which had > different interpretations of the prevailing definitions. They did not > always eat each others archetypes. > > I think at this point it is important to state in a simple way, then > there will be no reason for doubt about intentions: > > Does the LinkEhr editor produce archetypes which are always intended to > be completely conforming the official ADL/AOM and RM definitions? > > Best regards > > Bert > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > El mié., 12 dic. 2018 15:09, Bert Verhees <bert.verh...@rosa.nl> escribió: > On 12-12-18 14:49, Diego Boscá wrote: > > These are modifications on the parser, which parses more things than > > your standard parser. In fact, the editor supports legal things in ADL > > that other parsers don't (e.g. explicit node identifiers or > > existence). The generated ADL is completely fine ADL. There are tools > > that don't comply with this general ADL, and we provided an export > > version of archetypes that produces a modified version of the ADL > > syntax that other older and not maintained tools can parse. > > If you want to call this subset "official archetypes" be my guest. > > The word "official" was used by you, I used it (in quotes) to indicate > that we refer to the same. > > But it may get confusing, also because in the past there were > discussions about LinkEhr and the Ocean archetype-editor which had > different interpretations of the prevailing definitions. They did not > always eat each others archetypes. > > I think at this point it is important to state in a simple way, then > there will be no reason for doubt about intentions: > > Does the LinkEhr editor produce archetypes which are always intended to > be completely conforming the official ADL/AOM and RM definitions? > > Best regards > > Bert > > > > _______________________________________________ > openEHR-technical mailing list > 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
