The domain schema

Overview

.lokf/domain.yaml is this host’s domain schema, a LinkML file that lokf validate reads beside LOKF core. The schema := "domain.yaml" line of .lokf/justfile names it. ktl-sidecar lays it down on a host whose bundle is a domain, beside a pinned copy of lokf.yaml.

The five classes

• Domain is a Dataset that is a dcat:Catalog of bundles. It carries unowned_targets, max_depth, sensitivity and private_addresses, the settings the federation build reads. The domain concept says what each one means and what this domain sets.
• MemberBundle is a Dataset that names one released bundle. It requires a base_iri and a distribution, and carries the release page and a sensitivity.
• MemberDomain is a MemberBundle whose bundle is itself a domain, so a dcat:Catalog in turn.
• ReleaseDistribution is LOKF’s Distribution with its checksum required, so each further distribution, a schema or a workspace, carries a checksum of its own.
• ReleaseChecksum is LOKF’s Checksum, an spdx:Checksum, with sha256 as its only algorithm, since the build stores each file it fetches under its sha256 digest. A member concept writes it as checksum: {algorithm: sha256, checksum_value: <64 hex digits>}.

So lokf validate checks a member’s namespace, release and checksum.

Its namespace

The schema’s namespace is KTL’s, https://w3id.org/ktl/schema/domain, so every domain host shares one meaning for these classes. A host that needs more writes a schema of its own that imports this one.

Neither Obsidian plugin can read the file, because it sits outside the knowledge_bundle vault. The curator’s domain bundle page in KTL’s bundle describes each class.