Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to choose the carrier data format (XML vs. JSON vs. YAML) in all end user-facing converter tools #15

Open
vruusmann opened this issue Feb 20, 2020 · 2 comments

Comments

@vruusmann
Copy link
Member

With the update to PMML schema version 4.4, it's time to shake things up some more!

In Scikit-Learn:

sklearn2pmml(pipeline, "MyPipeline.pmml.json", format = "json")

In R:

r2pmml(model, "MyModel.pmml.yaml", format = "yaml")
@vruusmann
Copy link
Member Author

Related to the fact that the pmml-maven-plugin has been removed in the JPMML-Model 1.5.X development branch: jpmml/jpmml-model@f436d10

Such a plugin would be completely unnecessary, if people had the technical means to export the model in the desired data format right from the start.

@vruusmann
Copy link
Member Author

One carrier data format could be "java", in which case the JPMML-Transpiler library is used to translate the PMML data structure into Java application code.

Related comment: jpmml/jpmml-model#23 (comment)

@vruusmann vruusmann changed the title Option to choose the carrier data format (XML vs. JSON vs. YAML) in all end-user facing converter tools Option to choose the carrier data format (XML vs. JSON vs. YAML) in all end user-facing converter tools Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant