To align with the main themes for triples element-name is a class identifier and device-id is an instance identifier. DICE tcbinfo semantics are that vendor, type, model, layer and index are class-id fields. They identify measurements. Instance-id identifies instance measurements. It doesn't make sense to use class-id to name instance measurements. This sort of semantic is embedded in the triple predicate. As such it is less important for the data model to enforce these boundaries.
This issue motivates a PR that changes element-name to class-id and device-id to instance-id.
It also motivates changing element-value to measurement-value.
instance-value-group-choice are also measurement values. Possibly it makes sense to rename using 'measurement'?
To align with the main themes for triples element-name is a class identifier and device-id is an instance identifier. DICE tcbinfo semantics are that vendor, type, model, layer and index are class-id fields. They identify measurements. Instance-id identifies instance measurements. It doesn't make sense to use class-id to name instance measurements. This sort of semantic is embedded in the triple predicate. As such it is less important for the data model to enforce these boundaries.
This issue motivates a PR that changes element-name to class-id and device-id to instance-id.
It also motivates changing element-value to measurement-value.
instance-value-group-choice are also measurement values. Possibly it makes sense to rename using 'measurement'?