Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh imports after removing obsoleted PR_000050567 from PRO slim #3462

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

aleixpuigb
Copy link
Collaborator

No description provided.

@aleixpuigb aleixpuigb requested a review from gouttegd January 15, 2025 10:49
@aleixpuigb aleixpuigb self-assigned this Jan 15, 2025
@@ -13106,7 +13106,7 @@ AnnotationAssertion(rdfs:label <http://www.geneontology.org/formats/oboInOwl#has
AnnotationAssertion(rdfs:label <http://www.geneontology.org/formats/oboInOwl#hasBroadSynonym> "has_broad_synonym")
AnnotationAssertion(rdfs:seeAlso <http://www.geneontology.org/formats/oboInOwl#hasBroadSynonym> "https://github.com/information-artifact-ontology/ontology-metadata/issues/18")

# Annotation Property: <http://www.geneontology.org/formats/oboInOwl#hasDbXref> (has cross-reference)
# Annotation Property: <http://www.geneontology.org/formats/oboInOwl#hasDbXref> (database_cross_reference)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For information: this is of no consequence. This change is because we got conflicting labels for oboInOwl:hasDbXref. It will probably take a little while before all conflicting definitions of that property across OBO ontologies are superseded by the now “official” definition in OMO.

@aleixpuigb aleixpuigb merged commit 06eecc1 into master Jan 15, 2025
1 check passed
@aleixpuigb aleixpuigb deleted the refresh_imports_updated_PRO_slim branch January 15, 2025 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants