Skip to content
This repository was archived by the owner on May 18, 2022. It is now read-only.
This repository was archived by the owner on May 18, 2022. It is now read-only.

Coordinate on strategy for atlas region URIs? #55

Open
@cmungall

Description

@cmungall

With each uberon release we create bridge axiom ontologies for 5 allen atlases

There are various importers that will pull in the uberon backbone and hang off the ABA classes

We have also started folding these into the composite metazoan build, see:
http://uberon.github.io/release/2016/06/12/release.html

A prequisite to this is a semantic representation of the atlases in obo/owl. Here is how it currently works, it's not sophisticated:

https://github.com/obophenotype/uberon/blob/master/Makefile#L1314-L1336

They are placed here:
https://github.com/obophenotype/uberon/tree/master/source-ontologies

Note that we translate to a partonomy. Years ago Allen published the MBA (then just "ABA") as an OWL file, but this was a subclass hierarchy, which only makes sense if you read each class X as somethig like 'regional-part-of-X'

We always use the structure_ids (as requested by the Allen people - https://twitter.com/tgilhou/status/531912044464066560). We prefix these with {D}{H,M,P}BA, and have these fall into the OBO base URI for now.

There are a number of issues here:

  • the 5 prefixes are not officially OBO registered
  • the ontology URIs should be resolvable (you need a catalog xml for the importer right now)
  • the ontology class URIs should be resolvable
  • the translation and publication should be separated from the uberon repo
  • the Allen folks should be involved

It may be an idea to sync our requirements here first and approach the Allen folks. I'm guessing you will want URIs and probably a standard prefix for loading into your SG instance.

Note that previous neurolex minted entirely new IDs for brain atlas regions. While this is perhaps justified for systems that don't provide them, the IDs provided by Allen now seem stable, and they it would be better to use these in combination with a sensible URI prefix

One possibility is that we make these OBOs - we register each individually with the OBO Library (and would automatically be visible with the growing number of browsers that use this registry). Each atlas could have its own GH repo, or a shared repo, with a CI job or manual release manager making periodic releases, using the current uberon procedure, or a more robust variant of it.

cc @dosumis @mellybelly

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions