Great news!

Apache 2 is a good licensing choice, that is what we recommend for openEHR
open source projects, although some contributors have felt reasons to use
other licences.

Apache 2 for example makes it easier for some companies to allow staff to
spend paid working time on improving industry/community-shared open source
components that they use in their closed or open platforms. Nowadays I'd
guess more openEHR software implementation work is done by business
employees during paid time than by volunteers using their spare time.

Having more ADL2 parsers does bring some extra benefits:
- compatibility tests and discussions can clarify the specification if
needed
- more of the possible design space is explored by more teams that can
learn from each other

However having a dozen of open source ADL2 parsers would probably be a
waste of developer effort.

I think the same goes for archetype/template editing tools, having a
handful of tools explores more options and brings up more good discussions
than having a single one, but having too many would potentially be a waste
of developer effort.

If you want to, then please to tell us a little bit more about the
context/product that you will be using the parser in.

Best regards,
Erik Sundvall
Ph.D. Medical Informatics. Information Architect. Tel: +46-72-524 54 55 (or
010-1036252 in Sweden)
Region Östergötland: erik.sundv...@regionostergotland.se (previously lio.se)
http://www.regionostergotland.se/cmit/
Linköping University: erik.sundv...@liu.se, http://www.imt.liu.se/~erisu/

On Wed, Oct 28, 2015 at 7:34 PM, Bert Verhees <bert.verh...@rosa.nl> wrote:

> Thanks very much, Pieter, great job!
>
> Bert
> Op 28 okt. 2015 18:20 schreef "Pieter Bos" <pieter....@nedap.com>:
>
> I would like to announce a new open source ADL2 library, written in Java.
>> It is based on the ANTLR-grammar released very recently by Thomas Beale.
>>
>> You can find it at https://github.com/nedap/archie
>>
>> It is still very much in development, but it is now at a state where it
>> could be of use to people. It currently features:
>>
>> - an ADL2-parser that parses the full definition, specialises,
>> terminology, value sets and (a subset of) rules sections
>> - an archetype object model implementation
>> - a flattener that can also make operational templates - still needs
>> testing and work!
>> - basic path queries with node ids and node meanings.
>> - an experimental Archetype treewalker for openEHR reference models ­ it
>> can save you many instanceof calls.
>>
>> It parses most valid ADL2 files i¹ve tested it with into an archetype
>> object model. That includes most of the content of the clinical knowledge
>> manager. We¹re currently using this same library for an openEHR
>> implementation and we will add features, fixes and tests to it as we
>> progress.
>>
>> You might ask, why a new library? Don¹t we have adl2-core already? The
>> answer is quite simple: licensing.
>> We could not use the adl2-core library for our projects, because it would
>> require us to release the entire project under the (A)GPL. So we ignored
>> the existing library and built our own. And now we release Archie under
>> the Apache license. This means you should be able to use it in any project
>> you like.
>>
>> Want to help? Great! There¹s a list of missing functionality on the github
>> page. Just fork and create a pull request. Or just report any issues you
>> find on the github issue tracker.
>>
>> Regards,
>>
>> Pieter Bos
>> Nedap Healthcare
>>
>>
>> _______________________________________________
>> openEHR-implementers mailing list
>> 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
>
_______________________________________________
openEHR-implementers mailing list
openEHR-implementers@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org

Reply via email to