|
|
Post by khanjyan on Feb 23, 2024 14:20:10 GMT
Hello,
Is it required (by specification) to have a local copy of the supported Redfish Schemas on the Redfish service implementation side ?
If yes, could you please clarify where exactly should those files be located on the service side and how should be used ?
Thanks
|
|
|
|
Post by mraineri on Feb 23, 2024 15:44:26 GMT
There's no requirement to have local copies of schemas.
However, if you do want to host local copies, we have this URI pattern specified in the "Redfish-defined URIs and relative reference rules" clause of the Redfish Specification for local schema files:
> /redfish/v1/Schemas/<SchemaFile>
|
|
|
|
Post by khanjyan on Feb 26, 2024 6:16:59 GMT
Thanks for the reply, could you please give a hint why anyone would want to host local copies ? Any use case ?
I just can't imagine why/when it can be useful for.
Thanks again for your time!
|
|
|
|
Post by mraineri on Feb 26, 2024 12:19:33 GMT
A few reasons.
In many environments, the internet is not accessible. A schema-driven client in these situations would need some other repository of schemas to decode information on the service.
Services implementing OEM extensions may not have a well-known publication URI for their service, and use the service itself as the repository.
In some cases, services will modify standard schema files per the "Schema modification rules" clause to prune out properties or other definitions not implemented by the service to describe to the client exactly what they implemented.
|
|
