Feature Request
Currently we have introduced a way to configure external JSON-Schema for management api objects eg.. PolicyDefinition in #5772
But the schema validation is applied globally. It would be cool if we could also configure the schema to be applied under a specific or multiple dataspace profile. It requires some digging since for example in Asset and PolicyDefinition, which are the most extensible objects that impact also the DSP layer we do not have a concept of data space profile there.
Since the most important validation should be in the policy definition, currently we will only target the profile based approach on policies. We will use the field profile in the odrl policy to drive the schema validation selector.
Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
If possible, provide a (brief!) solution proposal.
Feature Request
Currently we have introduced a way to configure external JSON-Schema for management api objects eg.. PolicyDefinition in #5772
But the schema validation is applied globally. It would be cool if we could also configure the schema to be applied under a specific or multiple dataspace profile. It requires some digging since for example in Asset and PolicyDefinition, which are the most extensible objects that impact also the DSP layer we do not have a concept of data space profile there.
Since the most important validation should be in the policy definition, currently we will only target the profile based approach on policies. We will use the field
profilein the odrl policy to drive the schema validation selector.Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
If possible, provide a (brief!) solution proposal.