Interaction with a JavaScript front-end could be done with any back-end programming language — it doesn’t have to be Java.
So your point is that Archie's serialisation and deserialisation to JSON will will assist this? I believe Thomas’s Eiffel implementation already has JSON serialisation, since about 5 years ago. Peter > On 3 Feb 2018, at 23:03, Pieter Bos <pieter....@nedap.com> wrote: > > 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-implementers mailing list openEHR-implementers@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
