Closed hlapp closed 3 years ago
Looks like this works actually if the TCAN import is updated to the latest version. In the logical definitions used here, tc:hasName
already has a domain constraint on tc:TaxonConcept
, which TCAN asserts as a subclass of cdao:TU
. Hence, any TU instance defined as tc:hasName some tn:TaxonName
will necessarily be an instance of cdao:TU
.
That said, most of the xxxx_TU
properties already have a range constraint on cdao:TU
(including excludes_TU
), so for consistency it seems includes_TU
should have one, too.
At least using the gators.ofn example. I thought this used to work. Perhaps range constraints need to be added to
includes_TU
etc, or some other means to assert that the object of it is in fact an instance ofTU
.