Module 2 · Lecture 2.4
VKL: Under the Hood
VKL is the text format the Knowledge Graph is written in: the four layers, the file tree, and built-in version control.
In the previous lecture the co-builder edited the Knowledge Graph. But what did it actually touch? VKL is the Veezoo Knowledge Language, the text format the Knowledge Graph is written in, stored as version-controlled files.
This lecture looks under the hood: the four layers of Veezoo, the file tree in Studio with its knowledge-base and database layers, and the built-in version control that can roll back any change.
Key points
- VKL is the Veezoo Knowledge Language, the text format the Knowledge Graph is written in and kept in files.
- Four layers: chat, the Knowledge Graph, the Veezoo database layer that maps between them, and your data warehouse.
- The
dblayer holds one file per table, with each column, its database identifier, and its field type. - The
kblayer holds the classes with their properties, plus the entities synced from the data. - The
sqlproperty in a class definition references columns from thedblayer, and that link keeps the Knowledge Graph independent of the warehouse. - A table file can become a virtual table with its own SQL, changing how Veezoo reads that table.
- Version control is built in: review past changes in detail and roll back to any point with one click.
Check your understanding
What is VKL?
VKL, the Veezoo Knowledge Language, is how the Knowledge Graph is written down, and those files sit under version control.
How does a class in the Knowledge Graph reach the data in your warehouse?
The db layer defines tables and columns, the kb layer defines classes, and the sql property links them. That mapping layer is what keeps the Knowledge Graph independent of the warehouse.
A series of Knowledge Graph changes turns out to be a mistake. What does Studio offer?
Version control is built in. Review the changes over time, pick a point, and roll back with one click.