Dear Madhavi, That is a fascinating, and very pointed, question. As an open source project, and as a software system that explicitly has built an infrastructure to allow 3rd parties to build their own modules, Kepler is nicely situated for 3rd parties to build high quality extensions that work well with other modules. Kepler's release as an open source code base in particular makes it straightforward for any interested party to fully understand how the software works and whether a particular module is implemented well. However, Kepler is also explicitly licensed under the BSD license with explicit disclaimers of warranty and fitness for purpose. This is the opposite of certification. So I would have to conclude that it does not follow certification model that you describe.
Matt On Mon, Feb 7, 2011 at 9:42 PM, Madhavi Tikhe < madhavi_tikhe at persistent.co.in> wrote: > Hi > > Is Kepler OEM-Ready? > > ( OEM-ready typically means that there is a way in which a component > developed by a third party can be certified to work with the tool in > question. ) > > > > Thanks, > > Madhavi > > > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If > you are not the intended recipient, you are not authorized to read, retain, > copy, print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for > virus infected mails. > > _______________________________________________ > Kepler-users mailing list > Kepler-users at kepler-project.org > http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/attachments/20110207/c67cdfbd/attachment.html>