Hi Seref, About licensing, I think Software as a Service is a more flexible approach than source code / library reuse, because we are just users of the service, we don't distribute it with our projects. And to use the code to create services, we must have written permission from the owner. Maybe I'm over simplifying the problem. BTW our project is Apache 2.0 http://code.google.com/p/open-ehr-gen-framework/ so I think sometime we can talk about what we have and what parts can be abstracted as services, but that's for another discussion topic. Just to let you know my personal agenda :D I need to do this to encourage openEHR adoption here in South America. -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos
Date: Fri, 11 May 2012 01:04:03 +0100 Subject: Re: How about creating an openEHR test base? From: serefari...@kurumsalteknoloji.com To: openehr-technical at lists.openehr.org Pablo, Let me first say that I really appreciate all the constructive discussions you've initiated, and your work. To be honest, I was hoping that my points sould ring other bells :) Open source licenses are quite different beasts, and their combinations in projects is a nightmare. If you take licences seriously (which we'd better do), you can end up in some pretty frustrating situations, where you can use someone else's code, but can't distribute it with your work, etc etc. I have no objection to exposing services, remember Bosphorus? It is happily running as a service out there for some months now. However, to work together, we need to handle licensing issues. I'm going to move Opereffa to Apache 2.0. Shinji has done the same. I do not want to push anyone towards a particular open source license, but I'd at least like to know the licenses of all projects that would be included in what you're suggesting. Believe me, I understand the urge to actually do stuff, I share the same urge, but at this day and age, one can never be too careful about licensing. Seeing what you're trying to do, I just wanted to save you from a lot of headache :) Kind regards Seref On Fri, May 11, 2012 at 12:42 AM, pablo pazos <pazospablo at hotmail.com> wrote: Hi guys, Seref, I was thinking a lot about what you said "There are various bits of functionality implemented in different projects...", and that rang a bell somewhere. I think we are implementing the same things again and again because the technology we choose can't handle what is already implemented, and I believe this is a great opportunity to start creating common services providing this funcionality to our systems, so we only implement service clients not the same functionality in an alternative way. There is a great deal of functionality developed by Rong & company (and other projects, .Net, Ruby, ...), and some of the functionality can be exposed as public services somewhere (like archetype flattening, AOM 2 ADL serialization, RM 2 XML serialization, etc.). Is there some posibility that the foundation could host those services? What do you think? I'm willing to dedicate time to this, because I think this will be beneficial for all (also for creating the proposed "test set" that started this topic). -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos Date: Tue, 8 May 2012 08:52:04 +0100 Subject: Re: How about creating an openEHR test base? From: serefari...@kurumsalteknoloji.com To: openehr-technical at lists.openehr.org Interesting point again. There are various bits of functionality implemented in different projects, but the projects have different open source licences. I'm not Rong of course, but his code uses mpl, and since I've used his code when I started Operaffa, Opereffa is mpl too (though it'll be apache very soon). So you'd need to check how licensing issues need to be handled if you use Rong's code, assuming your work is not under mpl. I think you've touched another important point Pablo Kind regards Seref On Mon, May 7, 2012 at 10:37 PM, pablo pazos <pazospablo at hotmail.com> wrote: Hi Rong, That's great news, but we have our own RM implementation because it handles ORM too.But I think I can adapt your xml-binding component to use our RM impl, what do you think? -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos > Date: Mon, 7 May 2012 21:08:57 +0200 > Subject: Re: How about creating an openEHR test base? > From: rong.acode at gmail.com > To: openehr-technical at lists.openehr.org > > On 7 May 2012 16:39, pablo pazos <pazospablo at hotmail.com> wrote: > > Hi Seref, I've a tool that generates composition instances from archetypes > > and data, what I don't have is a way to generate a valid XML form from those > > compositions. > > > > Hi Pablo, > The xml-binding component in the Java reference implementation does > just that. It binds RM object instance to generated XML objects that > can be serialized according to published XSD. > /Rong _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120510/d4219648/attachment-0001.html>