range_min / range_max are bespoke annotation properties (non-numeric IRIs, unlabeled, redundant with bin datatype facets)

[turbomam]

Browsing the local OLS load surfaced two helper annotation properties on the numeric-bin classes:

• https://w3id.org/metpo/range_min
• https://w3id.org/metpo/range_max

Three problems:

1. The IRIs are bare names, not the bare-numeric scheme https://w3id.org/metpo/, so they violate the METPO IRI convention.
2. They have no rdfs:label or definition, so OLS shows them as bare range_min / range_max.
3. They are redundant: each bin already encodes its interval as an owl:equivalentClass datatype restriction (xsd:decimal with min/max facets); these annotations duplicate the bound (e.g. metpo:range_max 42.65) in a non-standard way.

Options: (a) drop the annotations and rely on the equivalentClass datatype facets (the canonical OWL way to express a numeric range), or (b) if a human-readable bound is wanted, replace them with properly numbered and labeled data properties following the existing pattern (METPO already has has minimum/maximum cell width value as numbered, labeled data properties).

Surfaced via the local OLS load, 2026-06-06. Related: #228, #204.