Multiple qudt quantity kinds for a single Brick class?

[Sarah MacDougall]

Does Brick recommend against associating multiple Brick quantities or Qudt quantity kinds with a single Brick class.

 

For example, the Angle_Sensor has a qudt quantity kind of Angle, which include includes degree and radians.

 

There is a scenario where we want to associate  percentage as a possible unit for Angle_Sensor because blind angle could have a value from 0-100%.

Would it be OK to add dimensionless ratio qudt as another quantity kind associated with Angle_Sensor?

Thanks,

Sarah

[Steve Ray]

I can't speak with any authority about Brick, but I can about QUDT.

The only constraint within QUDT on the relation between QuantityKind and Unit is that they must both share the same dimension vector. In your example, that is the case (dimensionless), so a unit of percentage is perfectly valid as a unit for the quantity kind Angle. Your application would need to define what the percentage is of, however. That is, does 100% mean 360 degrees or what?

In your Brick context, if you declare your sensor as an Angle_Sensor, I don't know if there are any cardinality constraints on how many quantity kinds can be specified. The QUDT quantity kinds often have a skos:broader relationship to other quantity kinds, so in that sense applications already have a choice of multiple possible quantity kinds, and of associated units.

Steve