Google introduces v0.1 of the Open Knowledge Format

Notes updated
Introducing-the-Google-Cloud-Knowledge-Catalog-Google-Cloud-Blog.png

I do like a standard, and in this case it was such an easy, obvious fit for Substrate that I added it immediately. So I can export a zip file in Open Knowledge Format, or one compatible with WordPress.

As published, OKF v0.1 represents knowledge as a directory of markdown files with YAML frontmatter, with a small set of agreed-upon conventions that let wikis written by different producers be consumed by different agents without translation.

That's it. No complex compression scheme, no new runtime, no required SDK. A bundle of OKF documents is:

  • Just markdown — readable in any editor, renderable on GitHub, indexable by any search tool
  • Just files — shippable as a tarball, hostable in any git repo, mountable on any filesystem
  • Just YAML frontmatter — for the small set of structured fields that need to be queryable: type, title, description, resource, tags, and timestamp

If you've used Obsidian, Notion, Hugo, or any of the LLM wiki patterns that have emerged over the past year, the shape will feel familiar. OKF formalizes the small set of conventions needed to make these patterns interoperable.

[...]

Three principles behind the design

  1. Minimally opinionated. OKF requires exactly one thing of every concept: a type field. Everything else (e.g., what types exist, what other fields to include, what sections the body has) is left to the producer. The spec defines the interoperability surface, not the content model.

  2. Producer/consumer independence. OKF cleanly separates who writes the knowledge from who consumes it. A bundle hand-authored by a human can be consumed by an AI agent. A bundle generated by a metadata export pipeline can be browsed in a visualizer. A bundle synthesized by one LLM can be queried by another. The format is the contract; the tooling at each end is independently swappable.

  3. Format, not platform. OKF is not tied to any specific cloud, database, model provider, or agent framework. It will never require a proprietary account or SDK to read, write, or serve. We're publishing it as an open standard because the value of a knowledge format comes from how many parties speak it, not from who owns it.


Source: Original article · Are.na block · AI / Stack channel


Comments (0)

No comments yet. Be the first.

Never shown publicly, used only for Gravatar