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

NEVER MERGE: Test release Uberon (not to be merged!) #3298

Closed
wants to merge 1 commit into from

Conversation

matentzn
Copy link
Contributor

If you see this commit in the git history someone made a mistake, it was supposed to be for review purpose only.

This PR is the consequence of running the make uberon pipeline, omitting the faulty DMBA:16271 mapping which causes an inconsisteny. All release files are updated, but there are some interesting changes:

  • Lots of prefix changes
  • The consider axioms are changed to PURL syntax in OWL serialisation? that seems odd

OLD:

oboInOwl:considerEFO:0001015</oboInOwl:consider>

New:

<oboInOwl:consider rdf:resource="http://purl.obolibrary.org/obo/EFO_0001015"/>

If you see this commit in the git history someone made a mistake, it was supposed to be for review purpose only.

This PR is the consequence of running the `make uberon` pipeline, omitting the faulty `DMBA:16271` mapping which causes an inconsisteny. All release files are updated, but there are some interesting changes:

- Lots of prefix changes
- The consider axioms are changed to PURL syntax in OWL serialisation? that seems odd

OLD:

<oboInOwl:consider>EFO:0001015</oboInOwl:consider>

New:

<oboInOwl:consider rdf:resource="http://purl.obolibrary.org/obo/EFO_0001015"/>
Copy link

@balhoff
Copy link
Member

balhoff commented Jun 14, 2024

@matentzn that change is from a string to an IRI, and that is what we wanted to happen for replaced_by and consider.

@matentzn
Copy link
Contributor Author

matentzn commented Jun 14, 2024

@matentzn that change is from a string to an IRI, and that is what we wanted to happen for replaced_by and consider.

So for the EFO and FMA cases, we basically need to add idspace declarations into uberon-edit to make that work?

@balhoff
Copy link
Member

balhoff commented Jun 14, 2024

So for the EFO and FMA cases, we basically need to add idspace declarations into uberon-edit to make that work?

That sounds right.

@@ -222728,7 +222728,6 @@ def: "A hypothalamic region in rodents that is homologous to the lateral tuberal
comment: While lateral tuberal nucleus is often used interchangeably with tuberal nucleus in rodents, lateral tuberal nucleus is specific to humans and higher primates. In some cases, lateral tuberal nucleus is thought to be part of the tuberal nucleus in rodents, and could possibly be homologous to human tuberal region instead. {xref="PMID:29976824", xref="neuronames:1890", xref="PMID:1362279"}
synonym: "lateral tuberal nucleus (sensu Rodentia)" BROAD [neuronames:1890]
synonym: "lateral tuberal nucleus (sensu Rodentia)" EXACT [PMID:29976812]
xref: DMBA:16271
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just for the record: the proper way to workaround the issue caused by the problematic axiom in the DMBA bridge (which is something that ultimately must be fixed upstream, the problem is not in Uberon) is not to remove that cross-reference (the mapping here is correct) but to manually remove DMBA:16271 from the src/ontology/bridge/uberon-bridge-to-dmba.owl file, after that file has been refreshed from its original online location.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My personal preference would be to literally freeze the bridge in the makefile by commenting it out, but I guess I will try to put the screws on the upstream issue instead. Thanks for linking it!

Copy link
Collaborator

Choose a reason for hiding this comment

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

To be clear the fix must happen in this repository; I've linked the issue in the old repository only because it has a proper description of the problem, contrary to the new one that just states what the fix must be.

@matentzn
Copy link
Contributor Author

Superceded by #3300

@matentzn matentzn closed this Jun 14, 2024
@matentzn matentzn deleted the test-release-not-merge-14062024 branch June 14, 2024 19:34
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.

3 participants