Hello Diego, That is possibly, but has some complications:
To make a dual licensing approach work in this case it would requires us to release Archie under the AGPL, combine it with adl2-core and get a license from Marand to use their contributions to the resulting library in our products combined with a license from us to them to use our contributions in their products. Also all future contributors will have to sign a document allowing to use their contribution to be released under a different license by Marand and Nedap. That would leave the resulting combined library still unusable for other non-GPL projects by others. I would prefer another way forward :) Regards, Pieter Bos On 18/05/16 11:10, "openEHR-technical on behalf of Diego Boscá" <[email protected] on behalf of [email protected]> wrote: >Nice wok Piter! > >I've seen quite a lot of open source projects with dual licensing. >Maybe this is the way to go so we can please everyone > >Regards > >2016-05-18 11:06 GMT+02:00 Pieter Bos <[email protected]>: >> Hi Ian, >> >> Good to hear this work is being appreciated. >> >> It could certainly be possible to merge Archie with the existing adl2-core >> library. I think the adl2-core library looks like it has good quality code >> and decent API. It could be interesting because although there is quite a >> bit of overlap in functionality, Archie has functionality that adl2-core >> does not have, and adl2-core has functionality Archie does not yet have. If >> the owners of that library are willing to relicense their code or at least >> parts of their code under a different license, it could be interesting. >> We’re open to releasing this code under a different license, but only if the >> resulting work can be used in non-GPL software. >> >> Regards, >> >> Pieter Bos >> Nedap Healthcare >> >> From: openEHR-technical >> <[email protected]<mailto:[email protected]>> >> on behalf of Ian McNicoll <[email protected]<mailto:[email protected]>> >> Reply-To: For openEHR technical discussions >> <[email protected]<mailto:[email protected]>> >> Date: Wednesday 18 May 2016 at 10:42 >> To: For openEHR technical discussions >> <[email protected]<mailto:[email protected]>> >> Cc: >> "[email protected]<mailto:[email protected]>" >> >> <[email protected]<mailto:[email protected]>> >> Subject: Re: Archie version 0.1.0 released >> >> Hi Pieter, >> >> This looks a really interesting and valuable piece of work. Many thanks for >> your efforts - hopefully others will want to contribute. It would be nice if >> we could somehow bring this work and the existing AOM2/ADL2 work together >> (or at least not duplicate work). I appreciate there is a different >> licensing approach but I don't think that is necessarily set in stone. >> >> Ian >> >> Dr Ian McNicoll >> mobile +44 (0)775 209 7859 >> office +44 (0)1536 414994 >> skype: ianmcnicoll >> email: [email protected]<mailto:[email protected]> >> twitter: @ianmcnicoll >> >> [https://docs.google.com/uc?id=0BzLo3mNUvbAjT2R5Sm1DdFZYTU0&export=download] >> Co-Chair, openEHR Foundation >> [email protected]<mailto:[email protected]> >> Director, freshEHR Clinical Informatics Ltd. >> Director, HANDIHealth CIC >> Hon. Senior Research Associate, CHIME, UCL >> >> On 17 May 2016 at 12:53, Pieter Bos >> <[email protected]<mailto:[email protected]>> wrote: >> A few months ago I announced the development of an open source Java openEHR >> library called Archie. It has progressed enough that I’m now pleased to >> announced the release of version 0.1.0 of Archie. It supports the latest ADL >> 2 and reference model versions and is licensed under the Apache license. >> >> The documentation and source can be found at >> https://github.com/nedap/archie. It’s available at Maven Central at >> com.nedap.healthcare:archie:0.1.0 . >> >> Why another library? >> >> The existing open source openEHR libraries were either ADL 1.4 or published >> under the Affero GPL. This means there is no library available for non-GPL >> ADL 2 openEHR projects. We are building a non-GPL openEHR implementation, so >> we needed a library and wrote it. We believe the openEHR community benefits >> from having up to date open source tools, so we decided to release Archie. >> >> Features: >> >> * ADL parser, including a generic ODIN to Java objects mapper >> * Archetype Object Model >> * The EHR part of the Reference Model >> * Basic APath-queries on AOM and RM objects >> * Flattener >> * Operational template creation >> * Easy to use APIs for object creation, terminology lookup, archetype >> model tree walking and constraint checking >> * RM serializes to XML in accordance with the openEHR-published XSD, or >> to JSON using jackson >> * AOM serialization to JSON for easy use in JavaScript based >> web-applications. >> * Tools for reference model object creation and attribute setting based >> on archetype constraints >> * Pluggable reference model architecture: the reference model can be >> swapped for some other implementation and the tools keep working >> >> Experimental features: >> >> These features are included, but the API and implementation of these >> features will probably change in the coming versions: >> >> * Rules evaluation (with some minor syntax changes for now, see the >> project readme) >> * Full APath and XPath expression evaluation on reference model objects >> using the JAXP–implementation of your choice >> >> Future releases and contributions >> >> We’re continuing the development, so there will be more releases in the near >> future. If you want to contribute: pull requests and issue reports are very >> welcome! >> >> Regards, >> >> Pieter Bos >> Nedap Healthcare >> >> >> _______________________________________________ >> openEHR-technical mailing list >> [email protected]<mailto:[email protected]> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> >> _______________________________________________ >> openEHR-technical mailing list >> [email protected] >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > >_______________________________________________ >openEHR-technical mailing list >[email protected] >http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
