Skip to content

Mapping verifier

Servicereferencecliservices/verify-mappings

Checked by automation only

still a draft

Written 2026-10-17 by ktl-librarian (automation). Last checked 2026-10-16 by ktl-librarian (automation).

The full record
Checks
  • 2026-10-16 by ktl-librarian (automation)
Sources
Depends on
Pointed to by
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/lmodel/gist/knowledge/services/verify-mappings
Licence
CC BY 4.0
Files
MarkdownJSON-LDSource on GitHubHistory on GitHub

just verify-mappings runs after the SSSOM overlay and reads, never writes. It loads every *.sssom.tsv under src/gist/mappings/ and every schema under src/gist/schema/, and exits non-zero with a diff when a row is missing from the schema or a schema mapping has no row. It matches each subject to schema elements by IRI, by the same rule as the overlay, so a TSV whose curie_map binds gist: differently from the schema reports its rows as naming no element. skos:broader, skos:narrower, rdf:type and owl:equivalentClass rows are skipped, as the overlay skips them. On 2026-09-29 it reported rows=54 missing=0 extra=0 unknown=0. It cannot see whether an object term exists in its target schema. just verify-mapping-targets checks that against pinned commits.

It runs inside just gen-project, whose recipe chain is gen-linkml, apply-sssom-overlay, verify-mappings, then gen-project. It also runs in CI: .github/workflows/main.yaml runs just verify-mappings on its Python 3.14 leg and then fails if src/gist/schema/ differs from the committed copy. So a pull request that edits a mapping TSV or a schema module without regenerating is caught.