Of the 1412 prefixes in the Bioregistry that have both an example local unique identifiers and at least one URI format string, 378 (26.8%) were able to resolve with a HTTP 200. This comes with a few caveats:
- Some websites do not send appropriate HTTP statuses, and may return HTTP 200 even when redirecting to a default “Page Not Found” page.
- There are several reasons why resolution might fail, some of which are false positives (see below).
Why Does Resolution Fail?
- The website has been updated, and the URI format does not correspond to an existing endpoint anymore (solvable with additional curation).
- The website has been fully taken down
- The website has been replaced with another unrelated website, and the URI
format does not correspond to an existing endpoint anymore (e.g., the old
atfdb.familyhas been replaced by something unrelated).
- The website suffered from a temporary issue and failed to resolve during check, but still works. Because this is possible, it’s better to compare the last few checks for any newly failing prefixes.
- The website never existed in the first place. Some URI format strings are generated as artifacts of ontology curation, e.g., with Protégé, and were not meant to resolve. Ontologies typically use IRIs (a superset of URIs), which do not necessarily imply that their content are resolvable as a URL.
- The URI corresponds to a redirect that is misconfigured in the redirection service (e.g., this happened for several CropOCT ontologies (ref: #527) and sporadically for the OBO PURL service).
- The URI format string was curated incorrectly.
Why Store URI Formats for Dead Resources?
It’s still valuable to store URI format strings, even if the websites don’t work anymore (or never did in the first place), because URIs based on these URI format strings may appear in biomedical resources like ontologies or databases. This makes the Bioregistry a more valuable tool for parsing these URIs and ultimately for standardizing data.
There are 1027 prefixes that remain passing and 366 that remained failing.
New failures (passing in the previous check but not in the current check):
Revived (i.e., failed in the previous check but passed in the current check):