FAIR signals on this page follow a public-first policy: local build artefacts improve readiness, but full findability and accessibility require publicly established publication infrastructure. External OOPS! and FOOPS! results are reported separately as observability signals so service outages do not masquerade as ontology quality.
Current Release Status
This summary shows the current release state using a public-first FAIR interpretation together with the current ODK governance and QC state.
- Overall validation GOOD pass
Combined metadata, namespace, mapping, and SHACL validation checks. - SHACL GOOD True
Local SHACL shape execution when pyshacl is available. - ODK parity GOOD aligned
ODK artefacts are technically aligned, show no IRI drift, and have been explicitly promoted out of shadow mode. - Publication establishment GOOD published
Public FAIR credit requires explicitly established publication and resolver infrastructure, not just local build artefacts. - Release build freshness GOOD in sync
FAIR, validation, HDO, and ODK snapshots were generated close enough together to represent one coherent build.
Report Freshness
These timestamps help confirm that the dashboard is rendering one coherent build rather than mixing older report files.
- FAIR snapshot GOOD 2026-04-24T10:17:37+00:00
Loaded from reports/fair_readiness_report.json. - Validation snapshot GOOD 2026-04-24T10:17:37+00:00
Loaded from reports/validation_report.json. - HDO snapshot GOOD 2026-04-24T10:17:46+00:00
Loaded from reports/hdo_alignment_report.json. - ODK snapshot GOOD 2026-04-24T10:17:22+00:00
Loaded from odk/manifest.json. - ODK artefact build time GOOD 2026-04-24T10:17:22+00:00
Reported directly by the ODK manifest. - FAIR snapshot build time GOOD 2026-04-24T10:17:32.398172+00:00
Reported directly by the FAIR readiness snapshot.
FAIR Signals
FAIR signals are public-first release indicators. Local artefacts and metadata improve readiness, but full Findable and Accessible credit requires publication to be explicitly established.
- F / Findable GOOD 100 / 100
Public-first release score for identifiers, versioning, citation, and publication establishment. Local build assets alone do not yield full credit. - A / Accessible GOOD 100 / 100
Public-first release score for machine-readable outputs, documentation, resolver state, and publication establishment. Local files alone do not yield full credit. - I / Interoperable GOOD 100 / 100
Purely internal release-quality score for reuse of imports, mappings, namespace hygiene, and standards-based serializations. - R / Reusable GOOD 90 / 100
Purely internal release-quality score for license, provenance, versioning, definitions, examples, and release packaging.
External Service Status
External service rows report what third-party assessment services returned, or state clearly when they were unavailable.
- OOPS! ontology pitfall scan UNAVAILABLE external service unreachable
OOPS! something went wrong. There was an unexpected error. - FOOPS! FAIR assessment GOOD 75.0 / 100
External FAIR-oriented ontology assessment against the release candidate. File mode does not assess accessibility.
ODK / ROBOT QC
ODK / ROBOT signals reflect standard ontology engineering QC and are reported in addition to H2KG-specific FAIR and publication checks.
- ROBOT status GOOD completed
ROBOT/ODK commands completed and actual ODK artefacts were collected. - ROBOT errors GOOD 0
Shadow-mode ROBOT summary from the nested ODK workbench. - ROBOT warnings GOOD 0
Warnings indicate shadow scaffolding or follow-up work still required before promotion. - Import refresh health GOOD 10 configured
Imports are tracked through the nested ODK workbench and surfaced here alongside H2KG-specific checks. - Parity status GOOD aligned
ODK base artefact currently matches the curated schema and vocabulary baseline closely enough for shadow-mode review. - IRI drift GOOD none
Shadow mode should preserve existing H2KG identifiers. - HDO review coverage GOOD 96
Local H2KG terms reviewed against HDO for data, metadata, identifier, schema, validation, and digital-object semantics. - HDO mapping coverage GOOD 5
Mappings or reuse proposals that currently point to HDO anchors. - H2KG terms still local after HDO review OPTIONAL 92
Informational count of reviewed terms intentionally kept local until direct HDO reuse is accepted or a more precise HDO target is loaded.
FOOPS! Assessment
FOOPS! is an external FAIR-oriented ontology validator. It is informative when reachable, but not authoritative for release gating. In file mode it does not run accessibility checks.
- Status GOOD assessed
FOOPS! assessment completed in file mode. Accessible checks may remain unassessed. - Overall score GOOD 75.0 / 100
Returned directly by the FOOPS! service when reachable. - F / Findable ACTION 60.0 / 100
Returned directly by the FOOPS! service when reachable. - A / Accessible UNAVAILABLE not assessed
In file mode this dimension is commonly not assessed by FOOPS! and is not used to penalize the internal Accessible score. - I / Interoperable GOOD 100.0 / 100
Returned directly by the FOOPS! service when reachable. - R / Reusable GOOD 91.2 / 100
Returned directly by the FOOPS! service when reachable. - FOOPS! follow-up 1 WATCH F1
the ontology URI does not follow any of the schemes followed by known registers of persistent URIs. We checked w3id, purl, DOI, W3C, perma.cc, linked.data.gov.au, data.europa.eu and dbpedia.org - FOOPS! follow-up 2 WATCH F2
The following metadata was not found: version iri - FOOPS! follow-up 3 WATCH R1
The following metadata was not found: citation - FOOPS! follow-up 4 WATCH R1
The following metadata was not found: doi, logo, status, source, issued. Warning: The following OPTIONAL detailed metadata could not be found: backwards compatibility. Please consider adding them if appropriate. - FOOPS! follow-up 5 WATCH R1.2
The following provenance information was not found: issued - FOOPS! follow-up 6 WATCH F1
Version IRI not defined. Version info found (1.0.0).
OOPS! Pitfalls
OOPS! is an external ontology pitfall scanner. Service errors are shown as external availability problems rather than as ontology defects or zero pitfalls.
- Status UNAVAILABLE unavailable
OOPS! something went wrong. There was an unexpected error. - Pitfall count UNAVAILABLE not assessed
Returned directly by the OOPS! service when the scan succeeds.
Validation Signals
Validation signals summarize local structural, metadata, namespace, mapping, SHACL, and optional non-blocking hook checks on the release candidate.
- Overall validation status GOOD pass
Combined metadata, namespace, mapping, and SHACL validation checks. - SHACL conforms GOOD True
Local SHACL shape execution when pyshacl is available. - Duplicate @id conflicts GOOD 0
Duplicate source nodes are tolerated only when they merge without schema-type conflicts. - Missing labels GOOD 0
Release-time missing labels on local schema terms. - Missing definitions GOOD 0
Release-time missing definitions or comments on local schema terms. - Namespace violations GOOD 0
Violations against the active namespace policy. - Mapping issues GOOD 0
Mappings that remain risky or inconsistent after local checks. - OWL consistency hook OPTIONAL not enabled in current environment (owlready2 not installed)
Optional OWL reasoner hook. It is non-blocking and only runs when owlready2 is installed. - EMMO checks OPTIONAL not enabled in current environment (EMMOntoPy not installed)
Optional EMMO convention hook. It is non-blocking and only runs when EMMOntoPy is installed. - OOPS! hook UNAVAILABLE external service unreachable
OOPS! something went wrong. There was an unexpected error. - FOOPS! hook GOOD assessed
FOOPS! assessment completed in file mode. Accessible checks may remain unassessed.
Publication Assets
Publication asset rows distinguish assets that were prepared locally from those explicitly treated as publicly established.
- HTML reference page GOOD published
Generated documentation assets. Public availability is tracked separately from local generation. - Machine-readable source GOOD published
Primary Turtle serialization for the release candidate. - JSON-LD source GOOD published
JSON-LD serialization for the release candidate. - Alignment mappings GOOD published
Conservative alignment output for review and publication. - Examples module GOOD published
Separated example and data-like instances. - Release bundle WATCH not built in docs-only run
Bundle status depends on whether the current command executed the release-bundle stage. - w3id artifacts GOOD published
Resolver templates may be prepared locally even when public resolver registration is still pending.
Publication Establishment
These rows separate locally prepared publication artifacts from explicitly established public publication infrastructure.
- Overall publication status GOOD published
This is the canonical release-state signal for whether the current ontology publication is treated as publicly established. - Resolver status GOOD established
The public resolver status tracks whether the ontology namespace is established through the configured persistent identifier service. - Documentation publication status GOOD published
Documentation publication tracks whether the human-readable HTML documentation is publicly established as part of the current release. - Machine artefact publication status GOOD published
Machine artefact publication tracks whether the ontology serializations and release bundle are treated as publicly established release artifacts.
