PHIPO has started violating the iri-range validation rule from the ODK. I think this is because we're using plain text values (xsd:string) in the range of oboInOwl:inSubset annotation properties.
I've disabled the rule that checks for these for now (see commit 6287d894f95b36a245b59635b1809251f3c95dba), but we should really fix this.
Judging by what other ontologies seem to be doing, it seems like we should be using oboInOwl:SubsetProperty values as the range for the oboInOwl:inSubset annotation property: that's how FYPO has added its subsets. Although, the iri-range query doesn't make any reference to oboInOwl:SubsetProperty (only oboInOwl:inSubset), so I'm not sure this is the actual problem.
Shown below are the list of offending terms. Since there are so many, it would be better to use a script to replace the text values with oboInOwl:SubsetProperty values.
PHIPO has started violating the iri-range validation rule from the ODK. I think this is because we're using plain text values (
xsd:string) in the range of oboInOwl:inSubset annotation properties.I've disabled the rule that checks for these for now (see commit 6287d894f95b36a245b59635b1809251f3c95dba), but we should really fix this.
Judging by what other ontologies seem to be doing, it seems like we should be using oboInOwl:SubsetProperty values as the range for the oboInOwl:inSubset annotation property: that's how FYPO has added its subsets. Although, the iri-range query doesn't make any reference to oboInOwl:SubsetProperty (only oboInOwl:inSubset), so I'm not sure this is the actual problem.
Shown below are the list of offending terms. Since there are so many, it would be better to use a script to replace the text values with oboInOwl:SubsetProperty values.