Closed yuhonglin closed 2 years ago
@anssiko
"MLModel" sounds good to me. Thanks for brining this up.
Thanks for thinking of naming in the broader context. The proposal sounds good.
As a reference for the future, you can consult the TAG guidance on naming: https://www.w3.org/TR/design-principles/#naming-is-hard
Cool, thank you both.
During implementation, we found the fact that the acronym of "Model Loader" is "ML" same as that of "Machine Learning" causes issues in naming the interfaces. After a discussion with @phoglenix, @wacky6 and @jbingham, there seem to be two choices.
During dev-trial, we will go with choice 2. Our vision is that, if someone (like WebNN) people decide to use the same "MLModel" name, they can consider sharing it. In this way, "MLModel" will be the umbrella interface to cover all the possible cases.
Thanks for discussion/inputs from @phoglenix, @wacky6 and @jbingham.