#Vocabulary

Definitions for user-facing WWKG terms, organized by topic.

#Data model

Triple A statement in the form subject–predicate–object (e.g., “Alice knows Bob”). The fundamental unit of data in RDF.

Quad A triple plus a fourth component — the named graph it belongs to. WWKG stores all data as quads internally.

Named graph A labeled collection of triples within a workspace, used to organize data by topic, source, or purpose.

RDF Resource Description Framework. The W3C standard data model that WWKG uses. Data is expressed as triples connecting resources via relationships.

Identifier (IRI) A globally unique name for any resource, similar to a web address (e.g., http://example.org/Alice).

Graph pattern A set of conditions describing the shape of data you want to find. When you write a WHERE clause in SPARQL, the conditions inside it form a graph pattern.

#Query languages

SPARQL The primary query language for WWKG. A W3C standard for querying and updating RDF data. Supports SELECT, ASK, CONSTRUCT, DESCRIBE, INSERT, and DELETE.

Cypher A graph query language originally developed for Neo4j. WWKG supports Cypher as an alternative to SPARQL.

GQL Graph Query Language. An ISO standard graph query language. WWKG supports GQL as a third query language alongside SPARQL and Cypher.

#Storage

Fingerprint A unique identifier automatically computed for every piece of data. Two identical items always get the same fingerprint, regardless of where or when they were created.

Content ID A unique identifier for a specific version of your data. Like a receipt number — it proves exactly what your data looked like at that moment.

Index An optimization that speeds up specific types of queries. WWKG creates and manages indexes automatically.

Custom index An index you create for a specific query pattern to make it faster.

#Versioning

Branch A named line of work — just like a git branch. Branches can be merged, but they can also live independently and never merge back. Use them for parallel datasets, staging areas, personal drafts, import pipelines, or long-running experiments. The default branch is called main.

Commit A saved point in your data’s history. Every change creates a new commit. Works like git — you can view history, compare commits, and return to any previous commit.

Merge Combining changes from two branches into one. Optional — branches can also remain permanently independent.

Delta The set of insertions and deletions between two commits. Delta queries let you see exactly what changed over a range of history — like git diff for your data.

#Security and identity

Workspace A secure, self-contained collection of knowledge graphs. Each workspace has its own data, its own access controls, and its own encryption.

End-to-end encryption Your data is encrypted so that only workspace members can read it. Not even the servers that relay data can see its contents.

Access revocation When someone is removed from a workspace, new encryption keys are generated so the removed person cannot read future data.

Identity Your cryptographic identity in the WWKG network. No username or central account needed — your identity is yours alone.

Node A running instance of WWKG in the peer-to-peer network, either on your machine or on a server. Every node has its own cryptographic identity. Each node has a role — it is either a host or a gateway.

Host A node that stores workspace data, runs queries, and processes updates. Hosts own the encrypted block store and serve the SPARQL, Cypher, and GQL query protocols. When you install a node with wwkg install --node-only, the host daemon starts automatically.

Gateway A node that provides an HTTP frontend to the WWKG network. Gateways discover hosts, route requests to them, and make the network accessible from web browsers and REST clients. A gateway does not store workspace data itself — it proxies requests to the hosts that do.

Inference WWKG can automatically derive new facts from existing data using logical rules. For example, if “Alice is a Doctor” and “every Doctor is a Person”, WWKG infers “Alice is a Person”.

#Protocols

Graph Store Protocol A W3C standard REST API for managing named graphs via HTTP GET, PUT, POST, and DELETE. WWKG implements this at the /graphs endpoint.