purl.obolibrary.org PURLs for METPO terms dead-end at HTTP 404

[turbomam]

http://purl.obolibrary.org/obo/METPO_<id> does not resolve to anything useful. METPO is not registered in OBO Foundry's ontologies.yml, so these PURLs fall through the obolibrary → oclc → archive.org → berkeleybop.org fallback chain and end at HTTP 404. Same for http://purl.obolibrary.org/obo/metpo.owl.

Verified 2026-05-18:

$ curl -sIL "http://purl.obolibrary.org/obo/METPO_1004005" -o /dev/null \
    -w "Final URL: %{url_effective}\nFinal HTTP: %{http_code}\nRedirects: %{num_redirects}\n"
Final URL: https://berkeleybop.org/ontologies/METPO_1004005
Final HTTP: 404
Redirects: 5

Meanwhile https://w3id.org/metpo/<id> redirects correctly to BioPortal.

Decision needed between:

1. Register METPO in OBO Foundry. Requires meeting OBO principles; would give working PURLs and broader visibility. Related Prepare METPO for EBI OLS submission #213 (OLS submission already planned).
2. Document https://w3id.org/metpo/ as the only canonical resolution and add explicit guidance in README and ontology header steering users away from purl.obolibrary.org PURLs.

Related: #16, #149, #213, #433.

🤖 Generated with Claude Code

[turbomam]

Decision: https://w3id.org/metpo/ is canonical; METPO will not claim obolibrary PURLs and is not pursuing OBO-Foundry IRI registration for resolution (option 2 in this issue). #458 removes the obolibrary ontology/term-IRI claims from the source files. Remaining here: README + ontology-header guidance pointing users to https://w3id.org/metpo/ and away from purl.obolibrary.org.

[turbomam]

Resolved via #462 (option 2). The README now declares https://w3id.org/metpo/ the only canonical resolution base and explicitly steers users away from purl.obolibrary.org/obo/METPO_<id> PURLs (which 404 because METPO is not OBO-registered). Option 1 (OBO Foundry registration) remains a separate, larger decision tracked under #213 if ever pursued.