Hello,<br /><br />We are implementing edk2 redfish support for our arm based SoC.&nbsp; One question that has come up is how is redfish schema versioning handled?&nbsp; We have a situation where a BMC had its software updated and that new software supported a newer version of the ComputerSystem schema.&nbsp; The UEFI redfish code in general that translates JSON to/from CS is very version specific and so we ran into some issues here.<br /><br />Given that redfish schema in general are normally "extended" for new versions I assume there is some backwards compatibility there?&nbsp; How would that work with the current edk2 redfish code base?&nbsp; 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?&nbsp; Without this, coordination between UEFI/edk2 and BMC redfish services becomes somewhat difficult.<br /><br />Regards,<br /><br />Russell