|
Post by AMI_Mani on Dec 29, 2023 4:26:15 GMT
Hi, Odata.id is not available in redfish.dmtf.org/registries/Redfish_1.1.0_PrivilegeRegistry.json. Redfish-URI-Validator is throwing error as Fail: Missing "@odata.id" and/or "@odata.type" from the payloadRedfish-URI-Validator tool is deprecated in favor of URI checking functionality that has been folded into the the Redfish-Service-Validator. When we checked in Redfish-Service-Validator , this issue is not coming in report. Hope this is issue with Redfish-URI-Validator and let me know if any where this information available. Do we have any plan to add odata.id for PrivilegeRegistry in latest schema? I checked latest schema redfish.dmtf.org/registries/Redfish_1.4.0_PrivilegeRegistry.json and odata.id is not available and if we have any information related to odata.id not required for registries, please point to that document Thanks, Mani
|
|
|
Post by mraineri on Dec 29, 2023 14:03:15 GMT
Yes, that is an issue with the Redfish-URI-Validator. We fully expect that registries themselves may not have @odata.id since they are linked from a string property rather than a reference object. We also cannot enforce how services package their on-chip registry database, so we do not want to require the usage of @odata.id with strict URI patterns. It is allowable to have it though.
In the "Resource identifier (@odata.id) property" clause of the Redfish Specification, we state that registries MAY include @odata.id (optional, not required), and all other resources SHALL include @odata.id (mandatory).
|
|