Make download details consistent

[cmungall]

I always point people to the OBO page for canonical downloads for an ontology as I frequently find each individual ontology presents things differently. But it can be hard to maintain consistenct.

https://obofoundry.org/ontology/uberon

Lists a number of products, some of which are necessarily unique to uberon.

Of note this includes uberon/basic.obo - this is a very standard product for many ontologies that is popular with bioinformatics users.

The download page
https://obophenotype.github.io/uberon/current_release/

Has this:

Variants:
For variants of Uberon, use the following pattern:

http://purl.obolibrary.org/obo/uberon/uberon-{variant}.{format}

Where variant is the type (eg base, simple, basic) and format is the file format (eg owl, obo, json)

For example, for a simple file in obo format, use http://purl.obolibrary.org/obo/uberon/uberon-simple.obo

This looks like generic ODK docs. It's quite confusing (and the URLs are just text not links). It leads the user to believe there is a "simple" file when in fact only "basic" is supported on the OBO page. In fact we do have both. And basic seems to be available from either uberon-basic.obo and basic.obo

I recommend

• the uberon docs take the OBO metadata as canonical, either copying or linking to the obo page
• keeping simple but weakly deprecating it (mention it in the documentation but not in the obo metadata)

[cmungall]

There is also a bit of confusion with what uberon-basic should contain:

INCATools/ontology-development-kit#1016

I think it should filter APs that connect to nodes (i.e those serialized as relationships in obo format)

[gouttegd]

the uberon docs take the OBO metadata as canonical, either copying or linking to the obo page

Actually the OBO metadata may need some updating as well:

• uberon/ext.owl does no longer exist; the link is automatically redirect to the canonical uberon.owl product;
• there is a new documentation page for the bridge files, that supersedes the Wiki page;
• it’s unclear to me why we specifically list the uberon-bridge-to-zfa.owl and the uberon-bridge-to-ma.owl, while we have a couple of dozens of bridges.

[gouttegd]

Download details have been updated both on the Uberon’s website (#3256) and in the OBO Foundry (OBOFoundry/OBOFoundry.github.io#2578).