Skip to content

problems in the modeling of Dimension, specific measure props, Measure

Created by: VladimirAlexiev

  • untp-core:Dimension is currently a parasitic node because it has no payload except some outgoing relations: ProductPassport - dimension - Dimension - (weight, height, etc) - Measure
  • The modeling of Measure is doubtful because its specific incoming props (weight, height, etc) can be contradicted by unit. There's nothing stopping data from looking like this:
<passport/1> a ProductPassport; height <passport/1/height>.
<passport/1/height> a Measure; value 1; unit <unitOfMeasure#kilogram>.

IMHO it's better to roll the specific prop (called quantityKind in QUDT) into Measure, eg:

<passport/1> a ProductPassport; measure <passport/1/height>.
<passport/1/height> a Measure; quantityKind <quantityKind/height>; value 1; unit <unitOfMeasure#meter>.

It's still possible to have a contradiction in quantityKind and unit but:

  • the contradiction is now in the same node so easier to detect
  • UoM ontologies like QUDT have the allowed combinations quantityKind-units. (UNCEFACT Rec20 is not an ontology because it doesn't have these combinations, and the dimensionVector for each quantityKind)