Ranges and Strong Typing of Measurement Values

[jmkeil]

I suggest the following changes to OM:

• where possible change datatype of om:hasNumericValue literals from xsd:string to xsd:decimal (including transformation of lexical representation) (45e8b684093fd6246403d6b3b1135d8d888d1f7f)
• add properties om:hasNumericalValueGreaterOrEqual & om:hasNumericalValueLessOrEqual (0ec8d63b568dab3ad61de75e343349c1bd8d8424 and ec4902458a8f70c58dd6901ebe491b75ccc6b6d9)
• apply om:hasNumericalValueGreaterOrEqual & om:hasNumericalValueLessOrEqualto existing approximate values (0ec8d63b568dab3ad61de75e343349c1bd8d8424)
• set range of om:hasValue to xsd:decimal (6e7e8786ea17806830aeed2bb00a05fc785c9e4d)

This will enable

1. the machine readable definition of approximate values or ranges, and
2. a strong typing of numerical values making OM easier to use, as software/queries can make more assumptions on the literals to expect.

om:hasNumericalValueGreaterOrEqual & om:hasNumericalValueLessOrEqualare defined as super property of om:hasNumericValue. That way,

_:a om:hasNumericValue 1.0 .

entails:

_:a om:hasNumericalValueGreaterOrEqual 1.0 .
_:a om:hasNumericalValueLessOrEqual1.0 .