Redfish Schema Versioning

Redfish Schema Versioning

[peterson.russell]

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

Hello,

We are implementing edk2 redfish support for our arm based SoC.  One question that has come up is how is redfish schema versioning handled?  We have a situation where a BMC had its software updated and that new software supported a newer version of the ComputerSystem schema.  The UEFI redfish code in general that translates JSON to/from CS is very version specific and so we ran into some issues here.

Given that redfish schema in general are normally "extended" for new versions I assume there is some backwards compatibility there?  How would that work with the current edk2 redfish code base?  I mean, if we simply want to read or post a JSON attribute that exists in both the old and new schema version... how would that work?  Without this, coordination between UEFI/edk2 and BMC redfish services becomes somewhat difficult.

Regards,

Russell

[-- Attachment #2: Type: text/html, Size: 931 bytes --]