Post by dmitry on Aug 12, 2023 10:08:59 GMT
Hello everyone,
Does the paradigm behind the schema specification for actions allow extending set of action parameters for specific resource instances?
Consider an example:
A JobDocument resource schema defines action "SubmitJob" which takes "JobCreator", "StartTime", and "PreferredExecutors" parameters common to all JobDocument instances. Theses parameters are defined in the schema.
A specific system is populated with a JobDocument resource "Bake Candy" which additionally requires parameters "Amount", "Shape", and "Color" to instantiate a Job which would bake certain amount of candies of specific color and shape.
Would compliance with the Specification/Schema maintained it these extended parameters are shown inside the "SubmitJob" @redfish.ActionInfo annotation while not defined in the schema or it would be considered a violation?
Regards,
Dmitry
Does the paradigm behind the schema specification for actions allow extending set of action parameters for specific resource instances?
Consider an example:
A JobDocument resource schema defines action "SubmitJob" which takes "JobCreator", "StartTime", and "PreferredExecutors" parameters common to all JobDocument instances. Theses parameters are defined in the schema.
A specific system is populated with a JobDocument resource "Bake Candy" which additionally requires parameters "Amount", "Shape", and "Color" to instantiate a Job which would bake certain amount of candies of specific color and shape.
Would compliance with the Specification/Schema maintained it these extended parameters are shown inside the "SubmitJob" @redfish.ActionInfo annotation while not defined in the schema or it would be considered a violation?
Regards,
Dmitry
