`OCPLiquidCoolingBaseline.v1_0_0.json` and `OCPCoolantDistributionUnit.v1_0_0.json` profile diverge from Redfish Data Model 2025.4

[npossamai]

The Redfish Data Model 2025.4 documents that the Coolant property both in CoolantConnector 1.3.0 and CoolingUnit 1.5.0 should contain a "Link to a Coolant resource." of type CoolingLoop under @odata.id

https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2025.4.html#coolantconnector-130

If doing that the Redfish Interop Validator with OCP Profiles OCPLiquidCoolingBaseline.v1_0_0.json and OCPCoolantDistributionUnit.v1_0_0.json fails because missing properties

• CoolantType
• DensityKgPerCubicMeter
• SpecificHeatkJoulesPerKgK

For this kind of properties which is the right implementation?

The one from the Redfish Data Model 2025.4?

"Coolant": {
    "@odata.id": "/redfish/v1/ThermalEquipment/CoolingLoops/1"
},

Or the one required from the OCP profiles?

"Coolant": {
    "CoolantType": "Water",
    "DensityKgPerCubicMeter": 1000,
    "SpecificHeatkJoulesPerKgK": 4.18
},

[npossamai]

cc @federicorred

[mraineri]

The doc generator that produces DSP2046 is incorrect. "Coolant" is defined as an object in schema. Here's the schema definition.

        <Property Name="Coolant" Type="CoolingLoop.Coolant" Nullable="false">
          <Annotation Term="OData.Description" String="Details about the coolant used in this unit."/>
          <Annotation Term="OData.LongDescription" String="This property shall contain details regarding the coolant contained or used by this unit."/>
        </Property>

The profile is correct; there is no "@odata.id" property in the "Coolant" object.

[jcleung5549]

John to file an issue in the Redfish-Tools repository.