I really believe we should be teaching using tools not reading syntax, specially for clinical modelers. If we are doing that right now is because tools lack usability, features and maturity.
For techies, we like to look at the syntax because we need to parse and process it. I'm not against improving the syntax, but since we don't have much resources as a community, shouldn't we focus were the real problem is with tools instead of patching the specs? Maybe clinical modelers can help software vendors on improving their tools and to create new ones to help on the modeling process, and there are some vendors creating such tools already but don't have input from the community. On Tue, May 16, 2017 at 4:35 PM, Thomas Beale <[email protected]> wrote: > not at all - a lot of people work with ADL, ODIN, BMM, JSON etc in plain > text for teaching, development of test archetypes, test data, looking at > data, making small systems etc. > > - thomas > > On 16/05/2017 13:22, Pablo Pazos wrote: > > it would be good to ask them why they do that, maybe is for limitations on > the modeling tools, or maybe they are cyborgs in disguise. > > On Tue, May 16, 2017 at 1:14 PM, Thomas Beale <[email protected]> > wrote: > >> >> sure. But there are a lot that do, just not the ones you know ;) We have >> to make things work for everyone. >> >> - thomas >> > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > -- Ing. Pablo Pazos Gutiérrez Cel:(00598) 99 043 145 Skype: cabolabs <http://cabolabs.com/> http://www.cabolabs.com [email protected] Subscribe to our newsletter <http://eepurl.com/b_w_tj>
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
