Hi Pablo, Seref and all, I think many implementation on the same API would make competitive and innovative environment. While re-invention of wheel is considered as waste of time, implementation by many ways sometimes makes innovation. Ruby on Rails is a web development framework, which affect many development framework, but web frameworks has been generated before/after RoR. All of them aim to product Web with ease, but approaches are not same. I am glad to have such environment with you on the openEHR. Licensing is a sensitive matter to share artefacts. It subjects not only code bases, but also on API like Oracle/Google issues. However, my artefacts are under Apache 2.0 or other open licenses.
Cheers, Shinji. 2012/5/11 pablo pazos <pazospablo at hotmail.com>: > 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: serefarikan at 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
