Knowledge Structure · Open Knowledge Format

Open Knowledge Format

Exchange and reuse knowledge through an open specification.

Open Knowledge Format (OKF) represents linked knowledge in human-readable files. It offers a shared format for exchanging knowledge between producers and consumers, helping organizations retain access to the content they build.

Why It Matters

Make knowledge easier to exchange

Knowledge stored in different tools often needs conversion before another application can use it. An open file format can reduce this dependence by making content, metadata and links available outside the original system. It does not, by itself, transfer an application’s integrations, permissions or behavior.

How It Works

The approach

Google Cloud introduced OKF in June 2026. Its file-based specification uses Markdown content, YAML metadata and links between concept files. This provides a portable representation without requiring a particular database or cloud merely to read the files.

Example of an OKF bundle. Each concept is written in its own Markdown file, with the required field type in the YAML front matter at the top. Markdown links between the files form a knowledge graph as they are.OKF BUNDLEOne concept = one Markdown filesupport/returns.md---type: proceduretitle: Handling returnstags: [support]---# Handling returns1. Confirm the order number2. Terms: see [Return policy]3. Fees: see [Shipping rates]linkHandling returnsreturns.mdReturn policypolicy.mdShipping ratesshipping.mdLinked files form a knowledge graph as they are
Example of an OKF bundle: a knowledge graph built from Markdown files and links (conceptual diagram)
  1. Represent concepts: Organize units of knowledge as Markdown files with structured metadata.
  2. Link related content: Use links to express connections within a bundle of files.
  3. Retain provenance: Where supported, metadata can record sources and generation or verification history. These records are signals to assess, not proof that content is correct.
  4. Exchange knowledge: Map the bundle to the requirements of the importing application.
Benefits

Business value

  • Readable outside the application

    People can inspect the underlying content with standard file tools.

  • Support portability

    A shared representation can reduce conversion effort when moving knowledge between compatible systems.

  • Track changes

    File-based knowledge can be managed with version control and an agreed maintenance process.

Considerations

Application considerations

  • OKF is an evolving specification. Confirm the supported version, content mappings and import/export scope for each integration.
  • Access control, encryption and sensitive-data handling are separate deployment responsibilities. Portability of knowledge does not guarantee compatibility of every application feature.
Related Products

Related products

  • AIKNOW

    Supports configured OKF import and export for portable structured knowledge.

  • AIKNOW Security

    Adds network, authorization and distributed source-text protection for confidential knowledge deployments.

References

References

Let’s Talk

Explore the right approach
for your business.

Tell us about your information sources, intended use and deployment requirements.
We can assess suitable technologies and a practical evaluation scope.