Mapping target checker
services/verify-mapping-targetsChecked 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)
- 2026-10-16 by
- Sources
- Depends on
- Related to
- Pointed to by
- Upstream watch (depends on)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/gist/knowledge/services/verify-mapping-targets- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Mapping target checker
Section titled “Mapping target checker”The mapping verifier only checks that each row reached the gist schema. just verify-mapping-targets checks the other end. It sparse-fetches each target’s schema folder at the commit pinned in the script’s TARGETS table (common_domain_model, dpv and iso22989, all under https://w3id.org/lmodel/). Then it fails a row when:
- its object prefix is not a pinned target;
- its object IRI names no class, slot, enum or type there;
- its
object_labelis not that element’s name, title or alias; - the target does not declare its
object_source_version.
It needs git and network access to GitHub.
--latest checks each target’s default branch instead of the pin, and --report FILE also writes a Markdown report. A pin behind its default branch is noted but does not fail the check. Re-pin a target when the mappings are revised against a newer release of it.
CI runs it on the Python 3.14 leg of .github/workflows/main.yaml, against the pins, and the weekly upstream watch runs it with --latest.