Open Knowledge Format as RDF Documents
type: CreativeWork
description: RDF-Turtle and HTML documentation collection derived from Google Cloud introduction of Open Knowledge Format. It models an RDF document alternative to Markdown OKF bundles, including ontology classes, ontology properties, instance documents, comparison dimensions, Linked Data principles, SPARQL recipes, FAQ, glossary, and provenance.
date created: 2026-06-14T19:33:22Z
date modified: 2026-06-14T19:33:22Z
author: this
about: Open Knowledge Format as RDF Documents

Open Knowledge Format as RDF Documents
type: CreativeWork
about: Introducing the Open Knowledge Format
about: OKF Markdown document pattern
about: RDF-Turtle document pattern
about: RDF OKF sales context bundle
about: Linked Data principles for RDF OKF
about: SPARQL query layer for RDF OKF documents
is based on: Introducing the Open Knowledge Format
has part: RDF OKF Document Ontology
has part: Ontology axiom examples
has part: RDF OKF sales context bundle
has part: OKF Markdown vs RDF-Turtle comparison
has part: Linked Data principles for RDF OKF
has part: FAQ: OKF as RDF documents
has part: Glossary: OKF RDF document collection
has part: How to build an RDF-Turtle OKF-style bundle
has part: Benefits of RDF, Linked Data, and SPARQL
has part: List context atoms
has part: Compare OKF and RDF dimensions
has part: Find semantic documents and resources

Introducing the Open Knowledge Format
type: Article
description: Google Cloud introduced Open Knowledge Format v0.1 as a vendor-neutral bundle of Markdown files with YAML frontmatter for portable agent and human knowledge.
date published: 2026-06-12
author: Sam McVeety
author: Amir Hormati
publisher: Google Cloud
about: OKF Markdown document pattern
about: knowledgeCatalogIngestion
about: agenticContext

RDF OKF Document Ontology
type: Ontology
description: Lightweight ontology for representing OKF-style context bundles as RDF-Turtle documents instead of Markdown files.
comment: Defines classes and properties for RDF document bundles, semantic documents, context atoms, comparison dimensions, SPARQL recipes, and Linked Data principles.
work example: Example: RDF Knowledge Bundle class axiom
work example: Example: Semantic Document class axiom
work example: Example: Context Atom class axiom
work example: Example: Comparison Dimension class axiom
work example: Example: SPARQL Recipe class axiom
work example: Example: Linked Data Principle class axiom
work example: Example: denotes resource property axiom
work example: Example: has context atom property axiom
work example: Example: queryable by property axiom
work example: Example: contrasts with property axiom
work example: Example: implements principle property axiom

Ontology axiom examples
type: CreativeWork
description: Concrete Turtle examples showing valid instance usage for every custom ontology class and property axiom.
has part: Example: RDF Knowledge Bundle class axiom
has part: Example: Semantic Document class axiom
has part: Example: Context Atom class axiom
has part: Example: Comparison Dimension class axiom
has part: Example: SPARQL Recipe class axiom
has part: Example: Linked Data Principle class axiom
has part: Example: denotes resource property axiom
has part: Example: has context atom property axiom
has part: Example: queryable by property axiom
has part: Example: contrasts with property axiom
has part: Example: implements principle property axiom
is part of: Open Knowledge Format as RDF Documents

RDF Knowledge Bundle
type: Class
comment: A deployable collection of RDF documents, ontologies, instance data, and query recipes that can be consumed by humans, agents, and SPARQL engines.
subclass of: CreativeWork
work example: Example: RDF Knowledge Bundle class axiom

Semantic Document
type: Class
comment: A document whose identity, type, metadata, body sections, and relationships are represented as RDF triples.
subclass of: DigitalDocument
work example: Example: Semantic Document class axiom

Context Atom
type: Class
comment: A reusable unit of agent context such as a table, metric, runbook, API, dataset, join path, or concept.
subclass of: CreativeWork
work example: Example: Context Atom class axiom

Comparison Dimension
type: Class
comment: A criterion used to compare OKF Markdown documents with RDF-Turtle documents.
subclass of: DefinedTerm
work example: Example: Comparison Dimension class axiom

SPARQL Recipe
type: Class
comment: A saved query over the RDF document collection.
subclass of: SoftwareSourceCode
work example: Example: SPARQL Recipe class axiom

Linked Data Principle
type: Class
comment: A principle for naming, dereferencing, and interlinking entities on the Web.
subclass of: DefinedTerm
work example: Example: Linked Data Principle class axiom

denotes resource
type: Property
comment: Connects a semantic document or context atom to the entity it identifies.
domain: Semantic Document
range: Context Atom
sub property of: about
work example: Example: denotes resource property axiom

has context atom
type: Property
comment: Connects a bundle or document to a reusable unit of context.
domain: RDF Knowledge Bundle
range: Context Atom
sub property of: hasPart
work example: Example: has context atom property axiom

queryable by
type: Property
comment: Connects a bundle or entity group to a SPARQL recipe.
domain: RDF Knowledge Bundle
range: SPARQL Recipe
sub property of: hasPart
work example: Example: queryable by property axiom

contrasts with
type: Property
comment: Connects one representation strategy to another in a comparison.
domain: Comparison Dimension
range: CreativeWork
sub property of: mentions
work example: Example: contrasts with property axiom

implements principle
type: Property
comment: Connects an RDF document pattern to a Linked Data principle.
domain: CreativeWork
range: Linked Data Principle
sub property of: about
work example: Example: implements principle property axiom

Example: RDF Knowledge Bundle class axiom
type: CreativeWork
description: Shows a valid bundle instance with semantic documents, context atoms, and SPARQL recipes.
about: RDF Knowledge Bundle
example of work: RDF Knowledge Bundle
text: :rdfBundle a :RdfKnowledgeBundle ; schema:hasPart :doc-sales-index ; :hasContextAtom :atom-bigquery-table ; :queryableBy :query-context-atoms .
mentions: RDF OKF sales context bundle
mentions: sales/index.ttl
mentions: BigQuery table
mentions: List context atoms
is part of: Ontology axiom examples

Example: Semantic Document class axiom
type: CreativeWork
description: Shows a semantic document instance denoting a reusable context resource.
about: Semantic Document
example of work: Semantic Document
text: :doc-orders-table a :SemanticDocument ; schema:name "sales/tables/orders.ttl"@en ; :denotesResource :resource-orders-table .
mentions: sales/tables/orders.ttl
mentions: sales/tables/orders
is part of: Ontology axiom examples

Example: Context Atom class axiom
type: CreativeWork
description: Shows a context atom as a reusable unit of agent context inside the RDF bundle.
about: Context Atom
example of work: Context Atom
text: :atom-metric a :ContextAtom ; schema:name "Metric"@en ; schema:isPartOf :rdfBundle .
mentions: Metric
mentions: RDF OKF sales context bundle
is part of: Ontology axiom examples

Example: Comparison Dimension class axiom
type: CreativeWork
description: Shows a comparison dimension contrasting the Markdown and RDF-Turtle representation patterns.
about: Comparison Dimension
example of work: Comparison Dimension
text: :dim-query a :ComparisonDimension ; schema:name "Query model"@en ; :contrastsWith :okfMarkdownPattern, :rdfTurtlePattern .
mentions: Query model
mentions: OKF Markdown document pattern
mentions: RDF-Turtle document pattern
is part of: Ontology axiom examples

Example: SPARQL Recipe class axiom
type: CreativeWork
description: Shows a query recipe typed as both the local class and schema.org source code.
about: SPARQL Recipe
example of work: SPARQL Recipe
text: :query-context-atoms a :SparqlRecipe, schema:SoftwareSourceCode ; schema:programmingLanguage "SPARQL"@en ; schema:target <https://linkeddata.uriburner.com/sparql> .
mentions: List context atoms
is part of: Ontology axiom examples

Example: Linked Data Principle class axiom
type: CreativeWork
description: Shows a Linked Data principle represented as a reusable defined term in the collection.
about: Linked Data Principle
example of work: Linked Data Principle
text: :principle-http-iris a :LinkedDataPrinciple ; schema:name "Use HTTP IRIs as names"@en ; schema:isPartOf :linkedDataPrinciples .
mentions: Use HTTP IRIs as names
mentions: Linked Data principles for RDF OKF
is part of: Ontology axiom examples

Example: denotes resource property axiom
type: CreativeWork
description: Shows the domain/range intent: a semantic document denotes a context atom.
about: denotes resource
example of work: denotes resource
text: :doc-orders-table :denotesResource :resource-orders-table .
mentions: sales/tables/orders.ttl
mentions: sales/tables/orders
is part of: Ontology axiom examples

Example: has context atom property axiom
type: CreativeWork
description: Shows the domain/range intent: a bundle contains a reusable context atom.
about: has context atom
example of work: has context atom
text: :rdfBundle :hasContextAtom :atom-bigquery-table .
mentions: RDF OKF sales context bundle
mentions: BigQuery table
is part of: Ontology axiom examples

Example: queryable by property axiom
type: CreativeWork
description: Shows the domain/range intent: a bundle is queryable by a SPARQL recipe.
about: queryable by
example of work: queryable by
text: :rdfBundle :queryableBy :query-context-atoms .
mentions: RDF OKF sales context bundle
mentions: List context atoms
is part of: Ontology axiom examples

Example: contrasts with property axiom
type: CreativeWork
description: Shows the comparison relationship between a dimension and the two representation patterns.
about: contrasts with
example of work: contrasts with
text: :dim-query :contrastsWith :okfMarkdownPattern, :rdfTurtlePattern .
mentions: Query model
mentions: OKF Markdown document pattern
mentions: RDF-Turtle document pattern
is part of: Ontology axiom examples

Example: implements principle property axiom
type: CreativeWork
description: Shows an RDF document pattern implementing Linked Data principles.
about: implements principle
example of work: implements principle
text: :rdfTurtlePattern :implementsPrinciple :principle-http-iris .
mentions: RDF-Turtle document pattern
mentions: Use HTTP IRIs as names
is part of: Ontology axiom examples

Sam McVeety
type: Person
description: Tech Lead, Data Analytics, Engineering, Data Cloud, Google Cloud, and co-author of the source article.

Amir Hormati
type: Person
description: Tech Lead, BigQuery, Engineering, Data Cloud, Google Cloud, and co-author of the source article.

Google Cloud
type: Organization
description: Publisher of the Open Knowledge Format article and related data analytics tooling.

BigQuery
type: Organization
description: Google Cloud analytics platform mentioned through the OKF enrichment-agent reference implementation.

Google Cloud Knowledge Catalog
type: Organization
description: Google Cloud catalog system updated to ingest Open Knowledge Format and serve it to agents.

OKF Markdown document pattern
type: CreativeWork
description: The source article describes OKF v0.1 as a directory of Markdown files with YAML frontmatter fields including type, title, description, resource, tags, and timestamp.

RDF-Turtle document pattern
type: CreativeWork
description: This collection demonstrates an alternate pattern where each document is Turtle, every concept has an IRI, relationships are typed predicates, ontology terms are declared, and SPARQL recipes query the bundle.
implements principle: Use HTTP IRIs as names
implements principle: Dereference names into descriptions
implements principle: Describe things with RDF
implements principle: Include links to other things

RDF OKF sales context bundle
type: RDF Knowledge Bundle
description: A sample RDF-Turtle bundle mirroring the article sales directory example with index, datasets, tables, metrics, and runbooks represented as semantic documents.
has part: sales/index.ttl
has part: sales/datasets/orders_db.ttl
has part: sales/tables/orders.ttl
has part: sales/tables/customers.ttl
has part: sales/metrics/weekly_active_users.ttl
has part: ops/runbooks/incident_response.ttl
has context atom: BigQuery table
has context atom: Dataset
has context atom: Metric
has context atom: Join path
has context atom: Runbook
has context atom: API
has context atom: Provenance record
queryable by: List context atoms
queryable by: Compare OKF and RDF dimensions
queryable by: Find semantic documents and resources

sales/index.ttl
type: Semantic Document
description: Collection index for the sales context bundle.
is part of: RDF OKF sales context bundle
denotes resource: sales/index

sales/index
type: Context Atom

sales/datasets/orders_db.ttl
type: Semantic Document
description: Dataset profile for the sales orders database.
is part of: RDF OKF sales context bundle
denotes resource: sales/datasets/orders_db

sales/datasets/orders_db
type: Context Atom

sales/tables/orders.ttl
type: Semantic Document
description: Table profile for completed customer orders.
is part of: RDF OKF sales context bundle
denotes resource: sales/tables/orders

sales/tables/orders
type: Context Atom

sales/tables/customers.ttl
type: Semantic Document
description: Table profile for customer records.
is part of: RDF OKF sales context bundle
denotes resource: sales/tables/customers

sales/tables/customers
type: Context Atom

sales/metrics/weekly_active_users.ttl
type: Semantic Document
description: Metric definition and lineage for weekly active users.
is part of: RDF OKF sales context bundle
denotes resource: sales/metrics/weekly_active_users

sales/metrics/weekly_active_users
type: Context Atom

ops/runbooks/incident_response.ttl
type: Semantic Document
description: Runbook context for agent-assisted incident response.
is part of: RDF OKF sales context bundle
denotes resource: ops/runbooks/incident_response

ops/runbooks/incident_response
type: Context Atom

BigQuery table
type: Context Atom
description: A data warehouse table represented as a typed entity with schema, resource URL, owners, and relationships.
is part of: RDF OKF sales context bundle

Dataset
type: Context Atom
description: A collection of tables, views, or data products with ownership and usage metadata.
is part of: RDF OKF sales context bundle

Metric
type: Context Atom
description: A reusable business measure with a formula, provenance, grain, source tables, and governance notes.
is part of: RDF OKF sales context bundle

Join path
type: Context Atom
description: A relationship showing how two data entities are connected by keys or graph predicates.
is part of: RDF OKF sales context bundle

Runbook
type: Context Atom
description: Operational instructions that agents can retrieve, traverse, and update.
is part of: RDF OKF sales context bundle

API
type: Context Atom
description: A service interface represented as a discoverable entity with operations and examples.
is part of: RDF OKF sales context bundle

Provenance record
type: Context Atom
description: A trace of source, author, timestamp, and derivation for a context atom.
is part of: RDF OKF sales context bundle

Relevant context limits agentic systems
type: Claim
claim reviewed: Foundation models can write code, summarize documents, and analyze data, but accurate action still depends on context.
is part of: Open Knowledge Format as RDF Documents

OKF formalizes the LLM-wiki pattern
type: Claim
claim reviewed: OKF v0.1 turns a directory of Markdown files with YAML frontmatter into a portable, vendor-neutral knowledge format.
is part of: Open Knowledge Format as RDF Documents

Enterprise context is fragmented
type: Claim
claim reviewed: Schemas, metrics, runbooks, APIs, joins, code comments, documents, and expert memory live across incompatible surfaces.
is part of: Open Knowledge Format as RDF Documents

The problem needs a format, not another service
type: Claim
claim reviewed: OKF emphasizes producer and consumer independence over a new runtime, SDK, or proprietary platform.
is part of: Open Knowledge Format as RDF Documents

OKF uses file paths as concept identity
type: Claim
claim reviewed: In the v0.1 design, each Markdown file represents a concept and the file path is the concept identity.
is part of: Open Knowledge Format as RDF Documents

Markdown links make a graph
type: Claim
claim reviewed: Concept documents link to each other with Markdown links, creating richer relationships than the directory tree alone.
is part of: Open Knowledge Format as RDF Documents

OKF is a starting point
type: Claim
claim reviewed: The specification is intentionally versioned, open, and expected to evolve as producers and consumers appear.
is part of: Open Knowledge Format as RDF Documents

RDF upgrades path identity to Web identity
type: Claim
claim reviewed: RDF-Turtle documents can use HTTP IRIs for concepts, allowing names to remain stable across repositories, products, and organizations.
is part of: Open Knowledge Format as RDF Documents

RDF turns links into typed relationships
type: Claim
claim reviewed: Markdown links say that two pages are connected; RDF predicates say how the entities are connected.
is part of: Open Knowledge Format as RDF Documents

SPARQL makes the document collection queryable
type: Claim
claim reviewed: SPARQL can query claims, types, provenance, relationships, and document metadata without bespoke parsers for every repository convention.
is part of: Open Knowledge Format as RDF Documents

Ontologies support explicit schema evolution
type: Claim
claim reviewed: RDF can publish classes and properties alongside instance data so extensions are visible and reusable.
is part of: Open Knowledge Format as RDF Documents

Linked Data makes context portable beyond a bundle
type: Claim
claim reviewed: Dereferenceable IRIs let a context atom join public or private graphs without translation into a vendor catalog schema.
is part of: Open Knowledge Format as RDF Documents

Turtle remains inspectable text
type: Claim
claim reviewed: RDF-Turtle keeps a readable text-file workflow while adding formal semantics, validation options, and graph querying.
is part of: Open Knowledge Format as RDF Documents

OKF Markdown vs RDF-Turtle comparison
type: CreativeWork
has part: Identity
has part: Relationship semantics
has part: Query model
has part: Portability
has part: Validation
has part: Schema evolution
has part: Human authoring
has part: Agent consumption

Identity
type: Comparison Dimension
description: OKF Markdown: file path is identity. RDF-Turtle: HTTP IRIs identify entities independent of local storage paths.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Relationship semantics
type: Comparison Dimension
description: OKF Markdown: links are readable but mostly untyped. RDF-Turtle: predicates make relationships explicit and machine-actionable.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Query model
type: Comparison Dimension
description: OKF Markdown: search tools and conventions. RDF-Turtle: SPARQL over typed triples, named graphs, provenance, and ontology terms.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Portability
type: Comparison Dimension
description: OKF Markdown: portable files and Git repositories. RDF-Turtle: portable files plus Web-scale entity references and graph federation.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Validation
type: Comparison Dimension
description: OKF Markdown: frontmatter fields and repository rules. RDF-Turtle: parser validation plus optional SHACL and ontology constraints.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Schema evolution
type: Comparison Dimension
description: OKF Markdown: conventions evolve through spec versions. RDF-Turtle: ontologies publish classes and properties that can be extended incrementally.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Human authoring
type: Comparison Dimension
description: OKF Markdown: familiar writing workflow. RDF-Turtle: more structured, but still text-based and readable when authored carefully.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Agent consumption
type: Comparison Dimension
description: OKF Markdown: agents parse directories and frontmatter. RDF-Turtle: agents traverse typed graphs and execute SPARQL queries.
contrasts with: OKF Markdown document pattern
contrasts with: RDF-Turtle document pattern

Linked Data principles for RDF OKF
type: CreativeWork
has part: Use HTTP IRIs as names
has part: Dereference names into descriptions
has part: Describe things with RDF
has part: Include links to other things

Use HTTP IRIs as names
type: Linked Data Principle
description: Things should be named with HTTP IRIs so people and agents can refer to the same entity across documents and systems.
is part of: Linked Data principles for RDF OKF

Dereference names into descriptions
type: Linked Data Principle
description: Looking up an IRI should lead to useful information about the named entity.
is part of: Linked Data principles for RDF OKF

Describe things with RDF
type: Linked Data Principle
description: Descriptions should use RDF statements so data from many sources can merge into one graph.
is part of: Linked Data principles for RDF OKF

Include links to other things
type: Linked Data Principle
description: RDF should connect entities to other IRIs so graph discovery and reuse improve over time.
is part of: Linked Data principles for RDF OKF

Benefits of RDF, Linked Data, and SPARQL
type: DefinedTermSet
has defined term: Global joinability
has defined term: Precise relationship meaning
has defined term: Cross-document questions
has defined term: Provenance as data
has defined term: Agent planning substrate
has defined term: No required SDK

Global joinability
type: DefinedTerm
description: A table, metric, runbook, and API can be related through IRIs rather than trapped in one repository tree.
in defined term set: Benefits of RDF, Linked Data, and SPARQL

Precise relationship meaning
type: DefinedTerm
description: Predicates distinguish schema:about, schema:isPartOf, prov:wasDerivedFrom, okfx:denotesResource, and business-specific links.
in defined term set: Benefits of RDF, Linked Data, and SPARQL

Cross-document questions
type: DefinedTerm
description: SPARQL can ask which metrics depend on a deprecated table or which runbooks mention a failing API.
in defined term set: Benefits of RDF, Linked Data, and SPARQL

Provenance as data
type: DefinedTerm
description: Authors, publication dates, derivations, source URLs, and generation steps can be queried rather than hidden in prose.
in defined term set: Benefits of RDF, Linked Data, and SPARQL

Agent planning substrate
type: DefinedTerm
description: Agents can traverse known relationships, inspect ontology terms, and choose next actions from graph shape.
in defined term set: Benefits of RDF, Linked Data, and SPARQL

No required SDK
type: DefinedTerm
description: Like OKF, Turtle files can live in Git, tarballs, object stores, or WebDAV, while remaining more formally queryable.
in defined term set: Benefits of RDF, Linked Data, and SPARQL

FAQ: OKF as RDF documents
type: FAQPage
main entity: What did Google Cloud introduce?
main entity: What problem does OKF address?
main entity: Why does this collection use RDF-Turtle instead of Markdown?
main entity: What is the main benefit of RDF over Markdown links?
main entity: Does RDF replace OKF?
main entity: Why are Linked Data principles important here?
main entity: How does SPARQL improve agent consumption?
main entity: What tradeoff does RDF introduce?
main entity: How can humans still read RDF docs?
main entity: What should a practical RDF OKF bundle contain?

What did Google Cloud introduce?
type: Question
accepted answer: q1-answer

q1-answer
type: Answer
text: Google Cloud introduced Open Knowledge Format v0.1, an open specification for representing agent and human knowledge as Markdown documents with YAML frontmatter.

What problem does OKF address?
type: Question
accepted answer: q2-answer

q2-answer
type: Answer
text: OKF addresses fragmented enterprise context: schemas, metrics, runbooks, APIs, joins, documents, and expert knowledge split across incompatible systems.

Why does this collection use RDF-Turtle instead of Markdown?
type: Question
accepted answer: q3-answer

q3-answer
type: Answer
text: It demonstrates how the same document-collection idea can be represented as linked, typed RDF documents with ontology and instance data.

What is the main benefit of RDF over Markdown links?
type: Question
accepted answer: q4-answer

q4-answer
type: Answer
text: RDF links are typed predicates between identified things, so an agent can know whether a link means about, depends on, joins to, derives from, or implements.

Does RDF replace OKF?
type: Question
accepted answer: q5-answer

q5-answer
type: Answer
text: Not necessarily. RDF can be an alternate OKF serialization, an enrichment layer, or the source-of-truth format for teams that need graph queries and Linked Data interoperability.

Why are Linked Data principles important here?
type: Question
accepted answer: q6-answer

q6-answer
type: Answer
text: Linked Data makes context atoms portable beyond a local folder by using dereferenceable IRIs and RDF descriptions that can join other graphs.

How does SPARQL improve agent consumption?
type: Question
accepted answer: q7-answer

q7-answer
type: Answer
text: SPARQL gives agents a standard way to ask graph-shaped questions across documents, types, relationships, provenance, and examples.

What tradeoff does RDF introduce?
type: Question
accepted answer: q8-answer

q8-answer
type: Answer
text: RDF-Turtle is more explicit and structured than Markdown, which improves machine actionability but requires more care in authoring and validation.

How can humans still read RDF docs?
type: Question
accepted answer: q9-answer

q9-answer
type: Answer
text: Turtle is a text format with prefixes, compact triples, labels, comments, and descriptions; a companion HTML view can provide the friendly reading surface.

What should a practical RDF OKF bundle contain?
type: Question
accepted answer: q10-answer

q10-answer
type: Answer
text: It should contain ontology terms, typed instance documents, provenance, cross-links, glossary terms, query recipes, and a small set of conformance rules.

Glossary: OKF RDF document collection
type: DefinedTermSet
has defined term: Open Knowledge Format
has defined term: RDF
has defined term: RDF-Turtle
has defined term: Linked Data
has defined term: SPARQL
has defined term: Ontology
has defined term: Named graph
has defined term: SHACL

Open Knowledge Format
type: DefinedTerm
description: A Google Cloud open specification for portable Markdown-plus-frontmatter knowledge bundles for agents and humans.
in defined term set: Glossary: OKF RDF document collection

RDF
type: DefinedTerm
description: A W3C graph data model based on subject, predicate, object statements.
in defined term set: Glossary: OKF RDF document collection

RDF-Turtle
type: DefinedTerm
description: A compact, human-readable RDF serialization suitable for text-file document collections.
in defined term set: Glossary: OKF RDF document collection

Linked Data
type: DefinedTerm
description: A set of Web practices for naming and interlinking things with dereferenceable IRIs and RDF descriptions.
in defined term set: Glossary: OKF RDF document collection

SPARQL
type: DefinedTerm
description: The standard query language and protocol for RDF graphs.
in defined term set: Glossary: OKF RDF document collection

Ontology
type: DefinedTerm
description: A published vocabulary of classes and properties that describes the meaning of graph data.
in defined term set: Glossary: OKF RDF document collection

Named graph
type: DefinedTerm
description: An RDF graph identified by an IRI, useful for provenance, partitioning, and query scoping.
in defined term set: Glossary: OKF RDF document collection

SHACL
type: DefinedTerm
description: A W3C constraints language that can validate RDF graphs against shape rules.
in defined term set: Glossary: OKF RDF document collection

How to build an RDF-Turtle OKF-style bundle
type: HowTo
step: Keep the folder bundle
step: Mint stable IRIs
step: Declare the ontology
step: Write instance data
step: Type every relationship
step: Add SPARQL recipes
step: Render HTML from RDF
step: Validate the graph

Keep the folder bundle
type: HowToStep
position: 1
text: Preserve OKF’s simple bundle shape: directories, index documents, and version control still work for RDF-Turtle files.

Mint stable IRIs
type: HowToStep
position: 2
text: Give every concept, metric, table, runbook, and API a durable HTTP IRI rather than relying only on a local file path.

Declare the ontology
type: HowToStep
position: 3
text: Publish classes and properties for bundle, document, context atom, comparison dimension, and query recipe terms.

Write instance data
type: HowToStep
position: 4
text: Represent each document as a named entity with type, title, description, source resource, tags, timestamps, and typed relationships.

Type every relationship
type: HowToStep
position: 5
text: Replace ambiguous Markdown links with predicates such as schema:isPartOf, prov:wasDerivedFrom, okfx:denotesResource, and okfx:hasContextAtom.

Add SPARQL recipes
type: HowToStep
position: 6
text: Store useful query patterns as first-class entities so agents can inspect, run, and adapt them.

Render HTML from RDF
type: HowToStep
position: 7
text: Generate the human-friendly documentation view from the Turtle graph so prose and graph data stay aligned.

Validate the graph
type: HowToStep
position: 8
text: Parse Turtle, test links, optionally apply SHACL shapes, and run example SPARQL queries before publishing.

SPARQL query layer for RDF OKF documents
type: CreativeWork
has part: List context atoms
has part: Compare OKF and RDF dimensions
has part: Find semantic documents and resources

List context atoms
type: SPARQL Recipe
type: SoftwareSourceCode
programming language: SPARQL
code sample type: SPARQL query recipe
target: sparql
text: PREFIX schema: <http://schema.org/> PREFIX okfx: <https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing/#> SELECT ?atom ?name ?description WHERE { GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/open-knowledge-format-rdf-docs-gpt5-chat-1.ttl> { ?atom a okfx:ContextAtom ; schema:name ?name ; schema:description ?description . } } ORDER BY ?name

Compare OKF and RDF dimensions
type: SPARQL Recipe
type: SoftwareSourceCode
programming language: SPARQL
code sample type: SPARQL query recipe
target: sparql
text: PREFIX schema: <http://schema.org/> PREFIX okfx: <https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing/#> SELECT ?dimension ?name ?description WHERE { GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/open-knowledge-format-rdf-docs-gpt5-chat-1.ttl> { ?dimension a okfx:ComparisonDimension ; schema:name ?name ; schema:description ?description . } } ORDER BY ?name

Find semantic documents and resources
type: SPARQL Recipe
type: SoftwareSourceCode
programming language: SPARQL
code sample type: SPARQL query recipe
target: sparql
text: PREFIX schema: <http://schema.org/> PREFIX okfx: <https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing/#> SELECT ?doc ?name ?resource WHERE { GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/open-knowledge-format-rdf-docs-gpt5-chat-1.ttl> { ?doc a okfx:SemanticDocument ; schema:name ?name . OPTIONAL { ?doc okfx:denotesResource ?resource } } } ORDER BY ?name

is based on
subject: Open Knowledge Format as RDF Documents
predicate: is-based-on
object: Introducing the Open Knowledge Format

author
subject: Introducing the Open Knowledge Format
predicate: author
object: Sam McVeety

author
subject: Introducing the Open Knowledge Format
predicate: author
object: Amir Hormati

publisher
subject: Introducing the Open Knowledge Format
predicate: publisher
object: Google Cloud

mentions
subject: Introducing the Open Knowledge Format
predicate: mentions
object: BigQuery

mentions
subject: Introducing the Open Knowledge Format
predicate: mentions
object: Google Cloud Knowledge Catalog

defines class
subject: Open Knowledge Format as RDF Documents
predicate: defines-class
object: RDF Knowledge Bundle

defines class
subject: Open Knowledge Format as RDF Documents
predicate: defines-class
object: Semantic Document

defines class
subject: Open Knowledge Format as RDF Documents
predicate: defines-class
object: Context Atom

defines class
subject: Open Knowledge Format as RDF Documents
predicate: defines-class
object: Comparison Dimension

defines class
subject: Open Knowledge Format as RDF Documents
predicate: defines-class
object: SPARQL Recipe

defines class
subject: Open Knowledge Format as RDF Documents
predicate: defines-class
object: Linked Data Principle

defines property
subject: Open Knowledge Format as RDF Documents
predicate: defines-property
object: denotes resource

defines property
subject: Open Knowledge Format as RDF Documents
predicate: defines-property
object: has context atom

defines property
subject: Open Knowledge Format as RDF Documents
predicate: defines-property
object: queryable by

defines property
subject: Open Knowledge Format as RDF Documents
predicate: defines-property
object: contrasts with

defines property
subject: Open Knowledge Format as RDF Documents
predicate: defines-property
object: implements principle

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: RDF Knowledge Bundle class axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: Semantic Document class axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: Context Atom class axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: Comparison Dimension class axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: SPARQL Recipe class axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: Linked Data Principle class axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: denotes resource property axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: has context atom property axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: queryable by property axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: contrasts with property axiom

has example
subject: RDF OKF Document Ontology
predicate: has-example
object: Example: implements principle property axiom

example of
subject: Example: RDF Knowledge Bundle class axiom
predicate: example-of
object: RDF Knowledge Bundle

example of
subject: Example: Semantic Document class axiom
predicate: example-of
object: Semantic Document

example of
subject: Example: Context Atom class axiom
predicate: example-of
object: Context Atom

example of
subject: Example: Comparison Dimension class axiom
predicate: example-of
object: Comparison Dimension

example of
subject: Example: SPARQL Recipe class axiom
predicate: example-of
object: SPARQL Recipe

example of
subject: Example: Linked Data Principle class axiom
predicate: example-of
object: Linked Data Principle

example of
subject: Example: denotes resource property axiom
predicate: example-of
object: denotes resource

example of
subject: Example: has context atom property axiom
predicate: example-of
object: has context atom

example of
subject: Example: queryable by property axiom
predicate: example-of
object: queryable by

example of
subject: Example: contrasts with property axiom
predicate: example-of
object: contrasts with

example of
subject: Example: implements principle property axiom
predicate: example-of
object: implements principle

has semantic document
subject: Open Knowledge Format as RDF Documents
predicate: has-semantic-document
object: sales/index.ttl

has semantic document
subject: Open Knowledge Format as RDF Documents
predicate: has-semantic-document
object: sales/datasets/orders_db.ttl

has semantic document
subject: Open Knowledge Format as RDF Documents
predicate: has-semantic-document
object: sales/tables/orders.ttl

has semantic document
subject: Open Knowledge Format as RDF Documents
predicate: has-semantic-document
object: sales/tables/customers.ttl

has semantic document
subject: Open Knowledge Format as RDF Documents
predicate: has-semantic-document
object: sales/metrics/weekly_active_users.ttl

has semantic document
subject: Open Knowledge Format as RDF Documents
predicate: has-semantic-document
object: ops/runbooks/incident_response.ttl

has context atom
subject: Open Knowledge Format as RDF Documents
predicate: has-context-atom
object: BigQuery table

has context atom
subject: Open Knowledge Format as RDF Documents
predicate: has-context-atom
object: Dataset

has context atom
subject: Open Knowledge Format as RDF Documents
predicate: has-context-atom
object: Metric

has context atom
subject: Open Knowledge Format as RDF Documents
predicate: has-context-atom
object: Join path

has context atom
subject: Open Knowledge Format as RDF Documents
predicate: has-context-atom
object: Runbook

has context atom
subject: Open Knowledge Format as RDF Documents
predicate: has-context-atom
object: API

has context atom
subject: Open Knowledge Format as RDF Documents
predicate: has-context-atom
object: Provenance record

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Identity

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Relationship semantics

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Query model

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Portability

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Validation

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Schema evolution

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Human authoring

compares by
subject: Open Knowledge Format as RDF Documents
predicate: compares-by
object: Agent consumption

implements principle
subject: Open Knowledge Format as RDF Documents
predicate: implements-principle
object: Use HTTP IRIs as names

implements principle
subject: Open Knowledge Format as RDF Documents
predicate: implements-principle
object: Dereference names into descriptions

implements principle
subject: Open Knowledge Format as RDF Documents
predicate: implements-principle
object: Describe things with RDF

implements principle
subject: Open Knowledge Format as RDF Documents
predicate: implements-principle
object: Include links to other things

has benefit
subject: Open Knowledge Format as RDF Documents
predicate: has-benefit
object: Global joinability

has benefit
subject: Open Knowledge Format as RDF Documents
predicate: has-benefit
object: Precise relationship meaning

has benefit
subject: Open Knowledge Format as RDF Documents
predicate: has-benefit
object: Cross-document questions

has benefit
subject: Open Knowledge Format as RDF Documents
predicate: has-benefit
object: Provenance as data

has benefit
subject: Open Knowledge Format as RDF Documents
predicate: has-benefit
object: Agent planning substrate

has benefit
subject: Open Knowledge Format as RDF Documents
predicate: has-benefit
object: No required SDK

queryable by
subject: Open Knowledge Format as RDF Documents
predicate: queryable-by
object: List context atoms

queryable by
subject: Open Knowledge Format as RDF Documents
predicate: queryable-by
object: Compare OKF and RDF dimensions

queryable by
subject: Open Knowledge Format as RDF Documents
predicate: queryable-by
object: Find semantic documents and resources

denotes resource
subject: sales/tables/orders.ttl
predicate: denotes-resource
object: BigQuery table

denotes resource
subject: sales/metrics/weekly_active_users.ttl
predicate: denotes-resource
object: Metric

depends on
subject: sales/metrics/weekly_active_users.ttl
predicate: depends-on
object: Join path

implements principle
subject: RDF upgrades path identity to Web identity
predicate: implements-principle
object: Use HTTP IRIs as names

implements principle
subject: Linked Data makes context portable beyond a bundle
predicate: implements-principle
object: Include links to other things

about
subject: SPARQL makes the document collection queryable
predicate: about
object: SPARQL