Apache Ossie (formerly Open Semantic Interchange) (OSI) vs Open Knowledge Format (OKF)
They sit at the same step and overlap in purpose; the fields above are the basis for choosing.
| Apache Ossie (formerly Open Semantic Interchange) OSI | Open Knowledge Format OKF | |
|---|---|---|
| Lifecycle step | 4 Read: Give me the content | 4 Read: Give me the content |
| Answers | How can an AI agent or BI tool read a metric or data-model definition and get the same meaning another tool intended? | How can an organization package durable, structured knowledge (schemas, metrics, playbooks, runbooks) so both humans and agents can read, produce, and trust it without a bespoke SDK? |
| Governed by | Apache Software Foundation, Apache Incubator (Ossie Podling Project Management Committee); formerly a Snowflake-led multi-vendor working group | Google Cloud open-source project; canonical repository is GoogleCloudPlatform/open-knowledge-format on GitHub (moved out of the GoogleCloudPlatform/knowledge-catalog monorepo in August 2026, which now carries only a frozen, unmaintained snapshot) |
| Status (issuer's words) | Undergoing incubation at the Apache Software Foundation ('Apache Ossie (incubating)'); not yet a top-level ASF project. Core spec is marked DRAFT. | "An open specification; contributions, alternative implementations, and adoption beyond Google products are all explicitly welcomed" |
| Version | 0.2.0.dev0 (draft, in development); last tagged pre-release osi-0.1.1-rc1 | v0.2 (2026-08) |
| Form / transport | document format | document format |
| Found at | none | /okf/index.md |
| Implementation | prototype | shipping — Google Cloud (Knowledge Catalog and 4 sample bundles: GA4, Stack Overflow, Bitcoin, Acme Retail), OpenKnowledge (OKF linter plugin), and agenticweb.wiki (163-concept OKF v0.2 knowledge bundle at /okf/index.md) |
| Evidence | 5 verified | 4 verified |
| Primary use case | Serve readable content to agents | Serve readable content to agents |
| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |
| Specification | https://github.com/apache/ossie | https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md |
When to use which
- Choose Apache Ossie (formerly Open Semantic Interchange) when your question is “How can an AI agent or BI tool read a metric or data-model definition and get the same meaning another tool intended?” and you accept its maturity: status "Undergoing incubation at the Apache Software Foundation ('Apache Ossie (incubating)'); not yet a top-level ASF project. Core spec is marked DRAFT.", implementation prototype.
- Choose Open Knowledge Format when your question is “How can an organization package durable, structured knowledge (schemas, metrics, playbooks, runbooks) so both humans and agents can read, produce, and trust it without a bespoke SDK?” and you accept its maturity: status ""An open specification; contributions, alternative implementations, and adoption beyond Google products are all explicitly welcomed"", implementation shipping (Google Cloud (Knowledge Catalog and 4 sample bundles: GA4, Stack Overflow, Bitcoin, Acme Retail), OpenKnowledge (OKF linter plugin), and agenticweb.wiki (163-concept OKF v0.2 knowledge bundle at /okf/index.md)).
Read the full articles
- Apache Ossie (formerly Open Semantic Interchange): How can an AI agent or BI tool read a metric or data-model definition and get the same meaning another tool intended?
- Open Knowledge Format: How can an organization package durable, structured knowledge (schemas, metrics, playbooks, runbooks) so both humans and agents can read, produce, and trust it without a bespoke SDK?