Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ranges and Strong Typing of Measurement Values #103

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

jmkeil
Copy link
Contributor

@jmkeil jmkeil commented Aug 12, 2024

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) (45e8b68)
  • add properties om:hasNumericalValueGreaterOrEqual & om:hasNumericalValueLessOrEqual (0ec8d63 and ec49024)
  • apply om:hasNumericalValueGreaterOrEqual & om:hasNumericalValueLessOrEqualto existing approximate values (0ec8d63)
  • set range of om:hasValue to xsd:decimal (6e7e878)

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 .

@jmkeil jmkeil changed the title add hasMinimumNumericalValue & hasMaximumNumericalValue Ranges and Strong Typing of Measurement Values Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant