Links
OKF v0.2 §5 defines two link forms:
Absolute links (recommended)
Start with / and are resolved from the bundle root, regardless of which file contains them:
See the [customers table](/tables/customers.md) for the join key.This is the recommended form because it stays stable when documents are moved within their subdirectory.
Relative links
Standard Markdown relative paths, resolved against the linking file's own directory:
See the [neighboring concept](./other.md).Official OKF specification requirement
A broken internal link does not make a bundle non-conformant — "a link whose target doesn't exist in the bundle is not malformed; it may simply represent knowledge not yet written." Link health is a quality signal, checked by the Link Checker, not the Validator.
No inherent relationship type
A link from concept A to concept B asserts a relationship — but what kind (parent/child, join, dependency) is conveyed by the surrounding prose, not the link syntax itself. OKF links are not automatically "depends-on", "owns", or "contains" unless a producer explicitly encoded that relationship in frontmatter or body text.
OKF Tools recommendation
The Knowledge Graph renders every edge generically for exactly this reason — never inferring semantics a producer didn't state.