Gerard, is there a relation between the introduction of AOM2.0, and the coincidence of the renewal process of ISO13606, which has the potential that AOM2.0 will be a part of the renewed ISO13606, and your strong effort to make us aware of your concern about IP risk in using OpenEHR related technologies?
I ask this because your complaint of OpenEHR in your point not being free must be very old because nothing much has changed in this, except, the (for many) unrelated situations are coming together. Why else would your effort at this very moment be so strong, you spent today, quite a few emails in public space to make this point. It must be, that for you, your complaint, must also concern AOM2.0, because it is an OpenEHR related technology released under the same terms as the other specifications. In that case, you could consider being glad that AOM2.0 being a part of the renewed 13606. Because that would bring it under ISO, which would make the ISO members be the owner. That would exactly be what you want. Or don't you? That could only be explained from some other reason, which I don't know. I hope you can enlighten us about the reason of your sudden effort of warning us. Why now, why so strong? Best regards Bert
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
