Yes, the limitations are often an issue for people doing things that aren't in the PMML spec yet; there could be room for suggesting new features in the spec by building them though, I suppose.
Also agree that XML is a lousy/bloated way of representing stuff like this, but in the end it's just a choice of representation so there may be reason to use some other encoding and then provide an XML-export function. On Wed, Mar 4, 2015 at 11:42 AM, Dmitriy Lyubimov <dlie...@gmail.com> wrote: > I am willing to +1 any contribution at this point. > > my previous company used pmml to serialize simple stuff, but i don't > have first hand experience. Its flexibility is ultimately pretty > limited, isn't it? And xml is ultimately a media which is too ugly and > too verbose at the same time to represent models with any more or less > decent number of parameters? > > > > On Tue, Mar 3, 2015 at 8:19 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > It makes sense to support PMML for classification and clustering tasks to > > be able to share and distribute trained models. Sean, Pat, Dmitriy and > Ted > > please chime in. > > > > PMML support in Mahout was talked about for a long time now but never > > really got any traction to take off. > > > > +1 to build this. > > > > On Tue, Mar 3, 2015 at 11:14 PM, Andrew Musselman < > > andrew.mussel...@gmail.com> wrote: > > > >> How much interest is there in a mahout-pmml module, with a starting > point > >> to be able to export a few analytic/scoring jobs to PMML representation? > >> > >> I've seen a lot of interest at in being able to use PMML to translate > >> analytic work into production(though I think people talk about it more > than > >> they do it), and it could be a benchmark as part of a "definition of > done" > >> for any existing/new method we include since there's a spec to build to. > >> > >> Best > >> Andrew > >> >
