Tim Churches wrote: > Thomas Beale wrote: > > > Thomas, > I provided fairly extensive, and I thought constructive, criticism on > the licenses which you indicated (and which teh openEHR web site seems > to suggest) apply to openEHR archetype definitions, which are not > software. As far as I can divine, based on your previous statement and > what it says on the Web site, openEHR archetypes are not licensed under > the GPL/LGPL/Mozilla triple license, but rather under the > openEHR-specific licenses discussed at length in previous posts to this > list. > You are right, sorry I skimmed some posts too fast. I don't have time to respond for a few days due to the MedInfo deadlines and other events. However, I would like people here to perhaps consider a repositioning of attitudes. I don't see the need for adversarial criticism; I do see a need for constructive criticism and collaboration. As far as archetypes go (for example) we probably do need a better license. My invitation to this community on this topic is as follows: have a think about what archetypes are useful for (see resources links below), and based on the assumption that the intent of any license for archetypes is of the 'open free use, but keeping original copyright intact' nature, make a suggestion for a license. It may be that Tim's post already solves the problem.
Archetype design activities are occurring all over the place, but a key international one is here: http://detailedclinicalmodels.org/wiki/index.php?title=Main_Page The latest ADL workbench (reference parser and viewer) you can get it here: http://svn.openehr.org/ref_impl_eiffel/TRUNK/apps/doc/adl_workbench_help.htm The Ocean Archetype Editor (VB.Net/Eiffel) is at http://oceaninformatics.biz/archetype_editor/ArchetypeEditor_download.html The Linköping editor (Java) is at http://www.imt.liu.se/mi/ehr/ All of these are open source software. - thomas beale
