Technology audience
One graph engine for RDF, LPG, Datalog-grade inference, search, and distribution.
WWKG unifies the query and infrastructure split that usually separates semantic graph teams from property graph teams. SPARQL, Cypher, and GQL share one operating layer with RDFS, OWL-RL, Datalog rules, vector embeddings, full-text search, temporal graph queries, branch history, per-workspace activity journals, advanced replication, and peer-to-peer distribution.
SPARQL, Cypher, and GQL in one engine.
Historic graph state can be queried over time instead of treating history as an external audit log.
Task events, commit production, and fact derivations form a queryable provenance chain.
RDFS, OWL-RL, and Datalog inference available to property graph users.
Vector embeddings and full-text search in the same graph infrastructure.
Replication can move graph data close to edge workloads for high availability and offline operation on remote devices.
Content-addressed, encrypted, versioned, peer-to-peer workspaces.
Datalog-grade deductive AI for LPG users
Semantic reasoning should not be locked inside the RDF world. WWKG makes RDFS, OWL-RL, and Datalog inference useful from Cypher and GQL as well, so property graph teams can benefit from ontology-backed meaning and rule-based derivation without switching religions.
Branch-sensitive everything
Queries, inference, validation, embeddings, and search belong to graph state. Change the branch, and the active knowledge context changes with it.
Task events as provenance
The workspace activity journal is an encrypted, replicated stream of task events, commit-production records, failed attempts, and fact-derivation records. It supports task panels, provenance reads, trace lineage, and audit questions without relying on a node-local log.
Replication close to the edge
Content-addressed blocks, workspace keys, signed history, and advanced peer-to-peer replication let nodes place graph data close to the work. That supports high availability, disconnected or intermittently connected remote devices, and edge operations without forcing every organization into one central server.
Continue reading