Automated evaluation

Which version is evaluated?

Each run records the exact version it looked at, in this order of preference: the owl:versionIRI or owl:versionInfo declared inside the artefact (or data-version / version for OBO, YAML and JSON files); the version reported by OLS; the latest GitHub release; a git tag on the evaluated commit; and otherwise the exact commit of the default branch. The artefact's ETag is stored too. Every entry page shows this under “Version evaluated”, and each run's snapshot keeps it permanently.

Sources & provenance

• Links: HTTP checks of each homepage, repository and download URL.
• Artefact: the first 256 KB of the download, read for version IRI / version info.
• Git refs: default-branch commit and release tags via git's HTTP endpoint.
• GitHub REST API: stars, forks, open issues, last push, latest release, detected license.
• OLS (EMBL-EBI) v2 API: classes, properties, individuals, imports and exports, ontology and version IRI, languages, load time.
• TIB Terminology Service: the same metrics from a second OLS instance, often holding a different release.
• BioPortal (with an API key): latest submission and metrics.
• Bioregistry: cross-portal identifiers (OLS, BioPortal, TIB, FAIRsharing, Wikidata…), dependencies and reuse.
• OBO Foundry registry: activity status, license and registered usages (shown as adopters).
• OBO Dashboard: OBO principle checks, ROBOT report, reasoner consistency and unsatisfiable classes, ontologies that reuse it.
• SchemaScope CI: for ontologies outside the OBO Dashboard, ROBOT reasons (ELK) and reports on the artefact; every ontology is also sent to the OOPS! pitfall scanner.
• Crossref: citation counts of each resource's reference paper.
• Curated data: adopting projects, modules and tooling submitted through GitHub and reviewed before merge.

Each fact stores its source URL and retrieval time. Every run is archived as an immutable JSON snapshot, so any score can be traced back to the data behind it. If a source fails, the last good value is carried forward with its original timestamp and flagged. A low score often just means information is missing; adding a license, a PURL, a download link or documented adopters will raise it.