Fix OBI:0000070 incorrectly declared as owl:AnnotationProperty in component files#3579
Draft
Fix OBI:0000070 incorrectly declared as owl:AnnotationProperty in component files#3579
Conversation
…component files
OBI:0000070 ('assay') is a class in OBI but was being incorrectly declared
as owl:AnnotationProperty in bgo-cl-comp.owl and wmbo-cl-comp.owl. This
declaration was also used as a predicate in axiom annotations throughout
both files.
Fix: Replace owl:AnnotationProperty declaration for OBI_0000070 with
oboInOwl:evidence in bgo-cl-comp.owl, and replace all usages of
<obo:OBI_0000070 rdf:resource="..."/> with <oboInOwl:evidence rdf:resource="..."/>
in both files. The wmbo-cl-comp.owl already had oboInOwl:evidence declared,
so only the OBI_0000070 declaration was removed there.
Resolves the issue where CL was punning OBI:0000070 as both a class and
an annotation property, which OWL treats in completely different ways.
Signed-off-by: GitHub Copilot
Co-authored-by: cmungall <50745+cmungall@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix assay class declaration in CL component files
Fix OBI:0000070 incorrectly declared as owl:AnnotationProperty in component files
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OBI:0000070(the OBI 'assay' class) was being declared asowl:AnnotationPropertyinbgo-cl-comp.owlandwmbo-cl-comp.owl, then used as a predicate in axiom annotations. This creates illegal OWL punning between a named class and an annotation property.Changes
bgo-cl-comp.owl: Replaceowl:AnnotationPropertydeclaration forOBI_0000070with a properoboInOwl:evidencedeclaration; replace all 57 predicate usages accordingly.wmbo-cl-comp.owl: Removeowl:AnnotationPropertydeclaration forOBI_0000070(oboInOwl:evidencewas already declared); replace all 250 predicate usages accordingly.Before:
After:
The intent of these annotations — recording the assay type (EFO:0008992) as evidence for location axioms — is preserved using
oboInOwl:evidence, a proper OBO annotation property.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.