Rather than classifying 'something' an aspect should classify a set or group of things - at a higher metalevel than 'quality' in BFO, for example. This impacts the Classifiers ontology. An instance of a classifier might specialize quality in BFO.

One example of this is hasNumericValue. It is currently declared to be functional, but could be the parent property for several properties of some class. In this case, the resulting ontology could be logically inconsistent if the values are not the same (and even if they are, by coincidence, that's still a problem). Other properties that are also declared as functional should be reviewed for the same issue.

This would assist in alignment with SysML v2, but more importantly allows alignment of some quantity value with a more general measurement reference rather than only a measurement unit, for representation of IU in pharma, for example.

There is a gap in the quantities and units ontology whereby we cannot represent counts of things, which do not necessarily have units, nor can we properly represent ratio values, which may involve scalar quantity values that do not have units. There is also a challenge in representing ratio values more generally, since there is no numeric value representing the ratio on the class.

This is needed for representation of tensor and vector quantities for the quantities and units ontology, and for representation of certain machine learning algorithms, among other requirements.