Post by malbolge on Mar 29, 2023 17:21:37 GMT
I noticed the use of nodes like @redfish.Settings and @redfish.SupportedApplyTime in sample Resources.
Then I checked out the CSDL where those types are defined. They're defined as regular ComplexTypes.
Is there anything inherently "magical" about Settings.Settings that permit it to be inserted into other schemas as an @redfish.property annotations? Or can any schema decide to legally add any other complex type from any other (already referenced) schema as an annotation?
And if there is something special about EDM types that can be used as annotations versus ones that can't, is this coming just from plaintext spec or is this machine-parseable, like a usedForAnnotations=TRUE in some supplementary file?
Then I checked out the CSDL where those types are defined. They're defined as regular ComplexTypes.
Is there anything inherently "magical" about Settings.Settings that permit it to be inserted into other schemas as an @redfish.property annotations? Or can any schema decide to legally add any other complex type from any other (already referenced) schema as an annotation?
And if there is something special about EDM types that can be used as annotations versus ones that can't, is this coming just from plaintext spec or is this machine-parseable, like a usedForAnnotations=TRUE in some supplementary file?
