Closed hlapp closed 3 years ago
Most of the xxxx_TU properties already have a range constraint on cdao:TU (including excludes_TU), so for consistency it seems those that don't (such as includes_TU) should have one, too. There doesn't seem to be a good reason why they shouldn't.
xxxx_TU
cdao:TU
excludes_TU
includes_TU
Originally posted by @hlapp in https://github.com/phyloref/phyloref-ontology/issues/46#issuecomment-806244296
Most of the
xxxx_TUproperties already have a range constraint oncdao:TU(includingexcludes_TU), so for consistency it seems those that don't (such asincludes_TU) should have one, too. There doesn't seem to be a good reason why they shouldn't.Originally posted by @hlapp in https://github.com/phyloref/phyloref-ontology/issues/46#issuecomment-806244296