|
|
Post by qoo221 on Sept 27, 2022 7:23:31 GMT
Hi all,
For specific schema, I found some useful json at newer version, but I would not prefer to update it. Could I just add json file of new version of schema into old version of schema?
|
|
|
|
Post by qoo221 on Sept 27, 2022 8:49:59 GMT
What I mean is. New version json describes dependent version of schema (for example, version 1.1). My current version of schema is not new enough (verson 1.0). Could I just copy json into schema for using because I want to use some content of new version of json?
|
|
|
|
Post by qoo221 on Sept 27, 2022 9:52:57 GMT
redfishforum.com/thread/45/version-redfish-specification-refer?page=1&scrollTo=123According to comment #2, "From a schema perspective, you can tell what version of the resource is being used from the @odata.type property in the response. For example, this means the Chassis resource follows schema version 1.2.1 for Chassis:" Could I consider thar it is ok to use newer json with old version schema though the descripton of json mentions newer version of schema?
|
|
|
|
Post by mraineri on Sept 27, 2022 12:54:17 GMT
Just because a newer version of a schema is released, you are not required to update your service to match the latest version. The reality is you really only need to update your version when you find a new property defined in a newer version that you want to implement.
However, it's worth noting that our newer versions are backwards compatible. So, even if you simply update your version to match the latest version without making any other changes, you should still be conformant. There are a few exceptions though where we've introduced new required properties, but these situations are rare.
|
|
|
|
Post by qoo221 on Sept 28, 2022 4:14:36 GMT
Thanks a lot  |
|
