Or a Java app with rest api and a JavaScript frontend. Let the java application take care of parsing, validating, flattening, operational template creation etc and send json to your front end. Archie has built-in json serialization and deserialization support.
Pieter Op 3 feb. 2018 om 12:05 heeft Seref Arikan <serefari...@kurumsalteknoloji.com<mailto:serefari...@kurumsalteknoloji.com>> het volgende geschreven: Hi Peter, Presumably via use of a transpiler or a bytecode to js/webassembly compiler. On Sat, Feb 3, 2018 at 10:56 AM, Peter Gummer <peter.gum...@gmail.com<mailto:peter.gum...@gmail.com>> wrote: On 1 Feb 2018, at 05:13, Thomas Beale <thomas.be...@openehr.org<mailto:thomas.be...@openehr.org>> wrote: ... But the main interest is that we will be able to build new tools such as a Java/JS replacement for the ADL Workbench, and of course things like a high-quality, BMM-driven runtime archetype validating kernel for EHR systems, workflow implementations and many other components. Hi Thomas, does “JS” stand for JavaScript? If so, I don’t understand how Archie (written in Java, disappointingly) would enable JavaScript implementations. JavaScript has nothing in common with Java (apart from the name). Peter _______________________________________________ openEHR-technical mailing list openehr-techni...@lists.openehr.org<mailto:openehr-techni...@lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ 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
