Validator errors when moving to Release 2020.1

Hi!

I am trying to move OpenBMC to 2020.1. Excited to add 2020.1 features like AutomaticRetry and ResetToDefaults to our Redfish implementation.

gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/32188

OpenBMC uses the latest Task Event Message Registry
redfish.dmtf.org/registries/TaskEvent.1.0.1.json

and after moving to 2020.1, I see several Redfish-Service-Validator errors in the Task Event Message Registry:
ERROR - Messages.TaskAborted.MessageSeverity: Mandatory prop does not exist
ERROR - Messages.TaskCancelled.MessageSeverity: Mandatory prop does not exist
ERROR - Messages.TaskCompletedOK.MessageSeverity: Mandatory prop does not exist
ERROR - Messages.TaskCompletedWarning.MessageSeverity: Mandatory prop does not exist
....

Also, see these in the Base Message Registry, even after moving to the latest, redfish.dmtf.org/registries/Base.1.8.0.json

I see there is a new required property, MessageSeverity, in MessageRegistry.v1_4_0.json, I don't see any new Registries that have this property?

Looked at redfish.dmtf.org/registries/, along with "2020.1 Redfish Registry Bundle" at redfishforum.com/thread/321/redfish-release-network-device-registry but both Base.1.8.0.json and TaskEvent.1.0.1.json do not have this property.

Is Redfish planning on releasing new Registries addressing this soon?

Could the Redfish-Service-Validator be enhanced to read the required properties and if that property was added after the version of schema you are using, don't throw an error?
OpenBMC runs the Redfish-Service-Validator as part of our continuous integration.

Also, see new Warnings around the use of the Severity property in these registries:
WARNING - Messages.TaskStarted.Severity: The given property is deprecated by revision: This property has been deprecated in favor of MessageSeverity, which ties the values to the enumerations defined for the Health property within Status.

Thanks!
Gunnar