|
Post by kilgorep on Mar 1, 2024 21:19:16 GMT
Reading clause 8.4.3.5.3 of DSP0272 regarding compare properties, it appears that the definition for CompareProperty imposes a constraint that the given CompareProperty must exist somewhere within the current resource being described. Is there a way to build a property condition based on the value of a property in a parent resource?
For example, the DriveMetrics schema has a property called NVMeSmart, and I'd like to express that its ReadRequirement is conditional on the parent Drive resource's Protocol property having a value NVMe. Can that be done with the existing definitions for CompareProperty?
|
|
|
Post by mraineri on Mar 1, 2024 21:35:43 GMT
At this time, you're correct with the current constraint; profiles only allow a comparison to be done against another property in the same resource. Comparing outside of the resource is currently not supported. However, given your use case, I can see how it would be needed. We can certainly bring this up for further discussion.
|
|