A typical PMML file will describe (1) variables of the model; (2) built model; (3) some self-definitions.
-----邮件原件----- 发件人: Isabel Drost (JIRA) [mailto:[EMAIL PROTECTED] 发送时间: 2008年3月19日 14:56 收件人: [email protected] 主题: [jira] Commented: (MAHOUT-18) Embrace interoperability with other softwares [ https://issues.apache.org/jira/browse/MAHOUT-18?page=com.atlassian.jira.plug in.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580254#action_1 2580254 ] Isabel Drost commented on MAHOUT-18: ------------------------------------ > How does this relate to MAHOUT-8? Seems like that is a similar thing, trying to define common I/O, or am I misinterpreting? I think this is misinterpreted. Maybe the explanation on the PMML website helps: PMML describes the inputs to data mining models, the transformations used prior to prepare data for data mining, and the parameters which define the models themselves. I wonder whether "the inputs" here means meta information to input data or the dataset itself. According to the FAQ is implemented by JSR-73 (see Mahout-8): > PMML is complementary to many other data mining standards. It's XML interchange formats is supported by several other standards, such as > XML for Analysis, JSR 73, and SQL/MM Part 6: Data Mining. Karl, you had a look at the FAQ, can you confirm this? > What are the criteria that we should use to decide which formats to support? I think one criterion should be how expressive the format is, the second should be the number of tools supporting the format. Of course there is an obvious criterion as well: The format should at least be open ;) The group developing the format is part of the standards group xml.org, so there is some standardization process backing it up. I what is supported by the format and what cannot be expressed. > Embrace interoperability with other softwares > --------------------------------------------- > > Key: MAHOUT-18 > URL: https://issues.apache.org/jira/browse/MAHOUT-18 > Project: Mahout > Issue Type: New JIRA Project > Reporter: Shunkai Fu > Priority: Minor > > This is an open issue. It is related with all possible components existing or to born in the future. > ML or DM models normally have two phases: training and scoring (or predicting). If we agree "updating" is an independent one, we will have 3 phases. > There are many softwares about ML/DM outside. We want the users of Mahout be able to import models got built from other software here, update them and/or use them for scoring. To achieve this goal, we need to recognize the commonly used formats. > Besides, users may choose Mahout because Mahout is speedy in learning. After a model is ready, they may export the model trained, view it with some visualization tool, or import it into other software or application for scoring (or predicting). In this case, exporting into widely recognized format is expected. > Finally, I want to say that the importing and exporting will not influence the ongoing projects, so developers of other components need not worry about this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
