Skip to content

KTL Federation Knowledge Bundle

This bundle is the domain of the Knowledge Trust Ladder (KTL) federation. Its concepts are the knowledge bundles the federation admits, each named by one released zip and that zip’s checksum; the domain that admits them; and the policy that says what admission requires and what the build does with a link no member owns. A person confirms each membership. The workspace, the graph a reader queries, is built from the releases these concepts name, never from a copy of them. The design is on the KTL context layer page.

The root file declares
Base IRI https://w3id.org/ktl/federation/knowledge/
JSON-LD context https://w3id.org/lokf/context.jsonld
Licence CC BY 4.0
Publisher Noel McLoughlin
Concepts 15

The bundle health page gives each concept’s label. The counts, computed from frontmatter when the site was built:

  • Confirmed by a person: 6 of 15
  • Checked by automation only: 6
  • Nobody has checked: 1
  • Drafts: 7
  • Reopened: 2
  • Past review date: 0
  • Edited since confirmed: 2
  • Retired: 0
  • concepts.jsonld: every concept’s frontmatter and body under one JSON-LD context.
  • graph.nt: the whole bundle as N-Triples.
  • graph.json: the typed relations as cytoscape.js elements, which the knowledge graph draws.
  • datasets.jsonld: a schema.org Dataset description for each Dataset or Table concept.
  • index.md: the bundle’s root file, which declares the header above.
  • log.xml: the bundle log as an Atom feed, its newest 20 days.
  • previews.json: each concept’s title, type, genre, trust label and definition, which a link to the concept shows before it is followed.
  • Each concept page links the concept’s own Markdown file and its JSON-LD, at the concept’s path with .md or .jsonld added.
  • The bundle as it stood at each release is a zip on the releases page.
  • The KTL federation domain - The domain of the KTL federation. Its builds start here, and another domain may name it as a member. It admits knowledge bundles by release, and its gate policy fails the build on a link no member owns.
  • Federation policy - What admits a knowledge bundle to this domain, what a member adds, which release a member names, what a person’s confirmation attests, and who arbitrates a claim across bundles. It also says what the build does with a target that names no member’s concept or a bundle two domains name.
  • Knowledge Trust Ladder knowledge bundle - The bundle of the knowledge-trust-ladder repository, which publishes the KTL skills, as released at v0.56.1 on 2026-10-26.
  • AI-LinkMO knowledge bundle - The bundle of the ai-linkmo repository, a reference implementation of operational AI governance over open AI-governance data, as released at v0.4.10 on 2026-10-19.
  • gist knowledge bundle - The bundle of the lmodel/gist repository, a LinkML rendering of Semantic Arts’ gist upper ontology, as released at v0.3.13 on 2026-10-23 under the name gist-linkml.
  • KTL Curator knowledge bundle - The bundle of the noelmcloughlin/obsidian-ktl-curator repository as released at 1.6.9 on 2026-10-26.
  • KTL Registrar knowledge bundle - The bundle of the noelmcloughlin/obsidian-ktl-registrar repository as released at 1.7.10 on 2026-10-26.
  • linkml-sidecar Knowledge Bundle - The bundle of the noelmcloughlin/linkml-sidecar repository as released at v0.3.2 on 2026-10-26.
  • Confirming a member change - How a person confirms a member’s move to a new release, or a new member, with ktl-curator or the KTL Curator plugin. It names what you need, the steps on the change’s branch, the checks to run before the merge, and how to draft a new member with the members script.
  • Knowledge sources - Map of the repository paths and outside pages this domain bundle is derived from, the concepts each yields, the files left out on purpose, and how to re-check each on a later refresh.
  • Contributing to this domain - How to set up a clone, what to check before a pull request to this domain, and the rules for AI-assisted changes. It names the gate’s two checks, the lint CI runs, the sidecar copies never edited here, and the changelog entry a change in behaviour needs.
  • Releasing this domain - How a merge to main releases this domain and rebuilds the workspace. It names the commit types that release, the changelog rule, the release job’s Environment, the two workflows the release dispatches, and the repository settings that hold main.
  • The knowledge website - How the site at noelmcloughlin.github.io/ktl-federation is built from the bundle, the README, docs/ and the changelog, how to preview it, what to edit for each part, and why the federation workflow deploys it on this host, not the website workflow.
  • The KTL federation workspace - The graph each release of this domain builds from its members, one named graph per bundle plus a graph for the lock. It names the build’s checks, what the release’s workspace zip and the site’s /workspace/ folder hold, the stored queries, and the serve, mcp and Oxigraph ways to read it.
  • The domain schema - The LinkML schema in .lokf/domain.yaml that adds Domain, MemberBundle, MemberDomain, ReleaseDistribution and ReleaseChecksum over LOKF core, so lokf validate checks a member’s namespace, release and checksum. Its namespace is KTL’s, and a host that needs more classes imports it.