Should the parent-child relationship to be unique?

[JordanCHW]

I was trying to validate a subprocessor which its URL would be like /redfish/v1/Systems/system0/Processors/cpu0/SubProcessors/core0 and want to leverage the SubordinateToResource to specify its location in the Redfish tree. In my imagination it should be

SubordinateToResource = [
    "ComputerSystemCollection",  # /redfish/v1/Systems
    "ComputerSystem",            # /redfish/v1/Systems/system0
    "ProcessorCollection",       # /redfish/v1/Systems/system0/Processors
    "Processor",                 # /redfish/v1/Systems/system0/Processors/cpu0
    "ProcessorCollection"        # /redfish/v1/Systems/system0/Processors/cpu0/SubProcessors
]

But it seems the validator builds the parent of /redfish/v1/Systems/system0/Processors/cpu0 by the Link property in Chassis resource, so the actual relationship built by validator would be:

[
    "ChassisCollection",       # /redfish/v1/Chassis
    "Chassis",                 # /redfish/v1/Chassis/chassis0
    "Processor",               # /redfish/v1/Systems/system0/Processors/cpu0
    "ProcessorCollection"      # /redfish/v1/Systems/system0/Processors/cpu0/SubProcessors
]

Is that an expected behavior?

[mraineri]

Your usage is correct; the Link property in Chassis is not supposed to have an effect in this since resources found inside "Links" are not subordinate to that resource.

[mraineri]

To clarify, this does appear to be a bug in the tool; the tool should be building the subordinate resource list without stepping into Links.