-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Added support for ML #209
Added support for ML #209
Conversation
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Steve Springett <steve@springett.us>
…ON schema. Added test cases. Signed-off-by: Steve Springett <steve@springett.us>
❗ I see a lot of newly introduced "MUST", "MUST NOT" in XML documentations. I'd recommend creating a followup-task that takes care of this, after this PR was merged. |
@stevespringett - what is the best way to reference model versioning? In case data, the version information i assume would be in its BOM? |
That is correct @dasarpjonam. The ML component can have a version, and if the ML component refers to a data component, then the data component can have its own version independent of the ML component that uses it. |
Signed-off-by: Steve Springett <steve@springett.us>
Closes #112