Existing XML schema cannot be found. about redfish-service-validator HOT 2 CLOSED

The issue here is that specifically, this $metadata reference refers to "ServiceRoot.v1_1_1", but the URI frag on "/redfish/v1/$metadata#ServiceRoot" refers to the namespace "ServiceRoot", which is not in this $metadata.

A correction could be:

<edmx:Reference Uri="/redfish/v1/metadata/ServiceRoot.xml">
    <edmx:Include Namespace="ServiceRoot.v1_1_1"/>
    <edmx:Include Namespace="ServiceRoot"/>
</edmx:Reference>

Unrelated to the issue, the frag to the right of $metadata is defined in the spec (and the tool only supports such) to be 'MetadataUrl#ResourceType', ResourceType being "the fully qualified name of the unversioned resource type", such that it should be "ServiceRoot.ServiceRoot" As it stands, the validator does not support other $metadata frags, however this example works with the tool. The design of the validator to be stricter on these regards if the spec demands it, but it doesn't seem to notice this, thank you.

from redfish-service-validator.

In this case, the @odata.context property is following the more formal OData format where the context spells out the entity hierarchy for how the client reached the resource in relation to the entry point.

While this is valid, I should point out that we have moved away from this model in Redfish and strongly recommend others to use the more simplistic format for context.

from redfish-service-validator.