Google proposes Open Knowledge Format based on Markdown

verdverm

A bunch of broken (slopped?) links in the original post, here is the repo https://github.com/GoogleCloudPlatform/knowledge-catalog Spec: https://github.com/GoogleCloudPlatform/knowledge-catalog/blo...

mrkiouak

I love revisiting RDF/OWL Semantic Web formats every 10 years. One of these years will be the one! https://en.wikipedia.org/wiki/Semantic_Web

sadschnitzel

I love the simplicity of this OKF spec, but I'm not sure everything can be represented well in "just Markdown". I've recently become intrigued by representing concepts so that AI can co-contribute effectively and token-efficiently (typically: find a good way to represent something as semi-structured sequential text), but also without compromising the human lens on the representation. We shouldn't accept a downgrade of the human knowledge representation experience just to make it AI-accessible. That's especially true if traditionally non-dev personas need to contribute, and they almost certainly find "weird text format + git" much worse than their current authoring/viz tools. I'm excited to see how standards for semantically representing different kinds of knowledge emerge in the next few years! Successful examples I can think of to mix in are open standards like DBML for schemas/E-R, LikeC4 for architecture, diagrams-as-code ideas like Mermaid, all of which LLMs seem to "get" well (or can be told about from a short EBNF prompt). Crucially, they also have pretty human viz forms, and you can you can just ```code block``` inline them in Markdown next to natural language. And you can get LLMs to help you author the syntax. Harder to crack is stuff where there's implicit human meaning in spatial layout and colour, like in complex spreadsheets or Miro. I haven't found good alternatives for those yet. My own attempt in my (data engineering) domain is https://equalexperts.github.io/satsuma-lang/ for AI-and-human source-to-target mappings and transforms. A succinct structured text representation that allows natural language, but also nice viz and LSP/grammar tooling that helps agents not to have to slice and dice big docs token-inefficiently to reason about things like lineage or completeness or undefined sources.

bsimpson

Is the flavor of Markdown (e.g. CommonMark) specified? Didn't see anything about it by perusing the first few pages, but that feels important for a spec.

matthewbarras

Check out barrasindustries.com/okfind/ Just an idea for an OKF bundle registry