Post by nschellenberger on Jul 24, 2023 20:57:40 GMT
I'm probably making this more complicated than it actually is, but I'm uncertain as to how to represent the canonical URI for the value of the navigation property FabricAdapter/Ports/EnvironmentMetrics.
Since none of the uses of EnvironmentMetrics appear to have a ContainsTartget=true and there is neither a Singleton nor EntityContainer for the default entity-set (nor an EnvironmentMetrics property in ServiceRoot) I'm not certain what the canonical, normative Redfish entity-id, Read URL, or navigationLink ought to be.
In our particular case, having the default ContainsTarget=false is actually entirely reasonable, since multiple ports can ride the same QSFP, but does that mean we should use an Oem URI, one for each physical QSFP? (Aside: why is the Port/SFP property a ComplexType rather than a navigation property to an EntityType?) Or can we just treat each of these as though they each defined an implicit entity set and have a notionally uniquely identifiable EnvironmentMetrics, one for each port (even if implemented as a single temperature read from the QSFP in our firmware, so are physically the same thing) via Port/EnvironmentMetrics/{EnvironmentMetricsId}.
Note that, as usual, we don't really mind how this is modelled, we're just trying to avoid making a trivial mistake in doing so.
Since none of the uses of EnvironmentMetrics appear to have a ContainsTartget=true and there is neither a Singleton nor EntityContainer for the default entity-set (nor an EnvironmentMetrics property in ServiceRoot) I'm not certain what the canonical, normative Redfish entity-id, Read URL, or navigationLink ought to be.
In our particular case, having the default ContainsTarget=false is actually entirely reasonable, since multiple ports can ride the same QSFP, but does that mean we should use an Oem URI, one for each physical QSFP? (Aside: why is the Port/SFP property a ComplexType rather than a navigation property to an EntityType?) Or can we just treat each of these as though they each defined an implicit entity set and have a notionally uniquely identifiable EnvironmentMetrics, one for each port (even if implemented as a single temperature read from the QSFP in our firmware, so are physically the same thing) via Port/EnvironmentMetrics/{EnvironmentMetricsId}.
Note that, as usual, we don't really mind how this is modelled, we're just trying to avoid making a trivial mistake in doing so.
