Features & roadmap

What SchemaScope does today, and what we plan to build next.

11 available · 1 in progress · 12 planned · updated 27 Oct 2026

Catalog & discovery

  • Available
    Harvest from six registries

    Bioregistry, OBO Foundry, OLS, TIB, LOV and NeuroSchema, merged into one record per resource, with every field traced to its source.

  • Available
    Discovery beyond registries

    prefix.cc, w3id.org, Zenodo, GitHub and suggested URLs are probed by content negotiation, and only real ontologies, vocabularies and schemas are accepted.

  • Available
    Reproducible downloads

    Each registry download is archived with its checksum, so the catalog can be rebuilt offline, and a single registry can be refreshed on its own.

  • Available
    Submissions through GitHub

    The submission form opens an issue that a bot turns into a pull request, with link, DOI and registry checks on every change.

Evaluation

  • Available
    Rubric v4: source-neutral scoring

    A check whose only evidence source doesn't cover a resource is "not assessed" instead of failed, and no problem is penalised twice.

  • Available
    Our own quality checks

    ROBOT (report, ELK reasoner, OWL 2 DL profile) and OOPS! pitfall scans run on every ontology, with the OBO Dashboard shown side by side for comparison.

  • Available
    DOI verification across services

    Reference DOIs are checked against Crossref, DataCite, OpenAlex, Semantic Scholar and doi.org.

  • Available
    Quality checks for every ontology

    ROBOT (report, ELK reasoner, OWL 2 DL profile), pitfall scans and import reading run on every ontology with a download, several at a time. A full pass resumes where it stopped, and each run reports how many ontologies have been checked.

  • Available
    Read imports from the artefact

    owl:imports and the terms an ontology uses are read from the file itself, so upper-ontology alignment (BFO, COB, DOLCE, GFO, gUFO), RO use and vocabulary reuse are measured for every checked ontology, not only those listed in OLS or Bioregistry (rubric v4.1).

  • Available
    Rubric validation

    A published report of how sensitive grades are to the weights (random and one-at-a-time changes), how well our quality checks agree with the OBO Dashboard, and how scores compare with expert ratings.

  • Available
    Metrics across runs

    Each resource's page shows how its score, every criterion and the quality metrics changed from one evaluation run to the next.

  • In progress
    Expert ratings

    Collecting ratings from domain experts to compare with our scores. Get in touch if you'd like to rate resources in your field.

  • Planned
    Adoption evidence beyond OBO

    Count adopting projects from papers, software dependencies and data repositories, not only curated entries and OBO Foundry usages.

  • Planned
    Community standards per domain

    Score R1.3 against each field's own standards bodies and principles, not only the OBO Foundry's.

  • Planned
    Flag disagreements between portals

    Our checks are already shown next to the OBO Dashboard's on each page. Next: highlight where OLS, TIB and BioPortal report different versions or class counts.

Publication tracking

  • Planned
    Papers that cite each resource

    Collect citing papers from OpenAlex, Semantic Scholar and Crossref, with citation counts over time on each resource's page.

  • Planned
    Papers that use a resource

    Find papers that use a resource in their methods or data, not just cite it, to give adoption evidence across fields.

  • Planned
    New publications

    Detect new reference papers and versions of a resource and suggest them as catalog updates.

Recommendations

  • Planned
    Similar resources

    Suggest related resources on each page, based on domain, shared imports and overlapping terms.

  • Planned
    Which ontology should I use?

    A guided finder that recommends well-maintained, well-scored resources for a domain, data type or task.

  • Planned
    Alternatives to inactive resources

    Point to active replacements when a resource is archived, deprecated or no longer maintained.

For maintainers

  • Planned
    Score badges

    An embeddable badge with the current grade for READMEs and websites.

  • Planned
    Improvement reports

    A per-resource checklist of the changes that would raise its score the most, such as a PURL, a license or a version IRI.

  • Planned
    Change alerts

    Opt-in notices when a resource's links break or its score drops.

Ideas or priorities you'd like to see? Get in touch or suggest an idea on GitHub.