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.
Evaluation Evidence
5486 automated consistency checks are published separately from the 134-item external application audit, whose current status is review pending. The comparator contains 20 author-curated capability judgments verified only for graph parsing and cited-IRI presence.
The retrieval outputs are competency demonstrations, not a precision, recall, or retrieval-improvement evaluation. No DECODE-local concept is promoted into H₂KG by either the machine checks or the application audit.
TIB Collection Benchmark
Review the reproducible H₂KG comparison with NFDI4Cat, NFDI4Energy, and NFDI4Ing, including collection- and ontology-level percentages and downloadable Excel evidence.
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.
- TIB metadata preflight GOOD passed
Official TIB mandatory warnings/violations: 0; recommendation notices remain reported separately. - 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 WATCH out of sync
Report timestamps differ by more than five minutes, so the page may be mixing build generations. - Parameter-property role separation GOOD 100.0% migrated
4418 of 4418 legacy workflow assertions have documented outcomes; canonical conflations: 0. - Canonical class-to-class workflow assertions GOOD 0
Canonical workflow use is expressed through SHACL paths and occurrence records rather than object-property assertions between OWL classes.
Report Freshness
These timestamps help confirm that the dashboard is rendering one coherent build rather than mixing older report files.
- FAIR snapshot GOOD 2026-11-02T20:08:06+00:00
Loaded from reports/fair_readiness_report.json. - Validation snapshot GOOD 2026-11-02T20:08:06+00:00
Loaded from reports/validation_report.json. - HDO snapshot GOOD 2026-11-02T20:08:14+00:00
Loaded from reports/hdo_alignment_report.json. - Semantic-role migration GOOD 2026-11-02T19:57:27+00:00
Loaded from reports/semantic_role_validation.json. - ODK snapshot GOOD 2026-11-02T19:58:32+00:00
Loaded from odk/manifest.json. - ODK artefact build time GOOD 2026-11-02T19:58:32+00:00
Reported directly by the ODK manifest. - FAIR snapshot build time GOOD 2026-11-02T19:59:01.726155+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! service unavailable: HTTPSConnectionPool(host='oops.linkeddata.es', port=443): Max retries exceeded with url: /rest (Caused by ConnectTimeoutError(<HTTPSConnection(host='oops.linkeddata.es', port=443) at 0x7cb16fc6ecd0>, 'Connection to oops.linkeddata.es timed out. (connect timeout=45)')) - FOOPS! FAIR assessment UNAVAILABLE external service unreachable
FOOPS! service unavailable: HTTPSConnectionPool(host='foops.linkeddata.es', port=443): Max retries exceeded with url: /assessOntologyFile (Caused by ConnectTimeoutError(<HTTPSConnection(host='foops.linkeddata.es', port=443) at 0x7cb16d997390>, 'Connection to foops.linkeddata.es timed out. (connect timeout=180)'))
ODK / ROBOT QC
ODK / ROBOT signals reflect standard ontology engineering QC and are reported in addition to H₂KG-specific FAIR and publication checks.
- ROBOT status WATCH pending nested ODK execution
Shadow artefacts were generated successfully. ROBOT profile and reasoner checks still need an explicit ODK run. - ROBOT errors GOOD 0
Shadow-mode ROBOT summary from the nested ODK workbench. - ROBOT warnings WATCH 1
Warnings identify import or technical follow-up work without changing the published H₂KG IRIs. - Import refresh health GOOD 10 configured
Imports are tracked through the nested ODK workbench and surfaced here alongside H₂KG-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 H₂KG identifiers. - HDO review coverage GOOD 141
Local H₂KG terms reviewed against HDO for data, metadata, identifier, schema, validation, and digital-object semantics. - HDO mapping coverage GOOD 8
Mappings or reuse proposals that currently point to HDO anchors. - H₂KG terms still local after HDO review OPTIONAL 135
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 UNAVAILABLE unavailable
FOOPS! service unavailable: HTTPSConnectionPool(host='foops.linkeddata.es', port=443): Max retries exceeded with url: /assessOntologyFile (Caused by ConnectTimeoutError(<HTTPSConnection(host='foops.linkeddata.es', port=443) at 0x7cb16d997390>, 'Connection to foops.linkeddata.es timed out. (connect timeout=180)')) - Overall score UNAVAILABLE not assessed
Returned directly by the FOOPS! service when reachable. - F / Findable UNAVAILABLE not assessed
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 UNAVAILABLE not assessed
Returned directly by the FOOPS! service when reachable. - R / Reusable UNAVAILABLE not assessed
Returned directly by the FOOPS! service when reachable.
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! service unavailable: HTTPSConnectionPool(host='oops.linkeddata.es', port=443): Max retries exceeded with url: /rest (Caused by ConnectTimeoutError(<HTTPSConnection(host='oops.linkeddata.es', port=443) at 0x7cb16fc6ecd0>, 'Connection to oops.linkeddata.es timed out. (connect timeout=45)')) - 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 checks on the H₂KG release.
- 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! service unavailable: HTTPSConnectionPool(host='oops.linkeddata.es', port=443): Max retries exceeded with url: /rest (Caused by ConnectTimeoutError(<HTTPSConnection(host='oops.linkeddata.es', port=443) at 0x7cb16fc6ecd0>, 'Connection to oops.linkeddata.es timed out. (connect timeout=45)')) - FOOPS! hook UNAVAILABLE external service unreachable
FOOPS! service unavailable: HTTPSConnectionPool(host='foops.linkeddata.es', port=443): Max retries exceeded with url: /assessOntologyFile (Caused by ConnectTimeoutError(<HTTPSConnection(host='foops.linkeddata.es', port=443) at 0x7cb16d997390>, 'Connection to foops.linkeddata.es timed out. (connect timeout=180)'))
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 H₂KG release. - JSON-LD source GOOD published
JSON-LD serialization for the H₂KG release. - 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
Generated reference files document the established H₂KG resolver configuration.
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.