The code, the specifications, and where to ask.
We publish the foundations of our work as open source: an RDF 1.2 toolkit, an ontology for knowledge and reasoning, a graph transport format, and the smaller tools that grew up around them. This page is the way in. The documentation, specifications and source live with each project; what follows points at them.
Start here
PurRDF is the shortest path to running something. Install it in the language you already use, or open the playground and run RDF 1.2 in the browser with nothing installed. The PurRDF Book takes it from there.
cargo add purrdf
pip install purrdf
npm i @blackcatinformatics/purrdf
Documentation
- The PurRDF Book - the user guide: getting started in each language, concepts, and every engine. Published in English.
- RDF 1.2 playground - a zero-install browser console that parses, queries, validates, serializes, and canonicalizes RDF 1.2 entirely client-side on the WebAssembly build.
- PurRDF - the project page: install lines, interfaces, conformance and releases.
- GMEOW - the ontology's namespace document, with its terms, slices and RDF serializations.
- GMEOW documentation - the full generated reference: getting started, learning paths, examples and diagrams. Published in English.
- GTS - the project page: install, quick start, CLI and conformance for the four engines.
- docs.rs/purrdf - API reference for the umbrella crate; each member crate links its own page.
- docs.rs/purrassist - API reference for PurRAssist.
- docs.rs/visual-hashing - API reference for visual-hashing.
Specifications
- GTS-SPEC.md - the normative graph-transport wire format.
- GTS-CONFORMANCE.md - the conformance fixtures every GTS engine must pass.
- RDF12-CANON-PROFILE.md - the
purrdf-rdfc12canonicalization profile and how it differs from RDFC-1.0. - SPARQL-GOVERNOR-PROFILE.md - the normative charge schedule for governed execution.
- PURREMB.md - the embedding companion format behind nearest-neighbour search.
- CONFORMANCE.md - the full conformance scoreboard and how to run each suite.
Projects
| Project | Language | Licence | Status |
|---|---|---|---|
| GMEOW Ontology Research ontology for attributed claims, provenance, reasoning assumptions, and explicit preservation or loss across knowledge representations. Source |
Rust / Python / RDF 1.2 | CC BY 4.0 / AGPL-3.0-only | pre-release · 0.2.0 |
| PurRDF RDF 1.2 querying, validation, and reasoning in Rust, with Python, WebAssembly, and C interfaces; documented conformance and execution limits. Source |
Rust / Python / WebAssembly / C | MIT OR Apache-2.0 | active · 2.0.2 |
| gmeow-gts Portable RDF 1.2 graph transport with cross-language conformance fixtures. Source |
Rust / Python / Go / TypeScript | MIT OR Apache-2.0 | active · 0.9.0 |
| PurRAssist Recovers intent from imperfect AI output: JSON, tool calls, names, paths and Markdown edits. Give it a schema and an effort level; it searches composed corrections, validates the complete result and returns evidence of what changed. One engine, offered as a Rust crate, an MCP server and a CLI. Source · Docs |
Rust | MIT OR Apache-2.0 OR MulanPSL-2.0 | active · 0.1.0 |
| visual-hashing Human-friendly visual fingerprints for keys and checksums: a nameable 64-emoji BLAKE3 hash that two people can read aloud to each other, and the OpenSSH-style randomart grid. Both are deterministic and byte-for-byte stable. Source · Docs |
Rust | MIT OR Apache-2.0 OR MulanPSL-2.0 | active · 1.0.0 |
| RAF Rust Agentic Foundations: dev-dependency libraries and cargo subcommands, not yet published, that keep Rust repositories free of duplicated helpers and keep their documentation an accurate, current account of the system. Built to be driven by humans and coding agents alike. Source · Docs |
Rust | MIT OR Apache-2.0 OR MulanPSL-2.0 | pre-release |
Community
#developers:blackcat.ca- our public developer room on Matrix, for questions, design discussion and release notes.- github.com/Blackcat-Informatics - every repository, with issues open on each. GMEOW and GTS also run GitHub Discussions.
Contributing and security
Each repository carries its own CONTRIBUTING.md and SECURITY.md; read those before opening a pull request or reporting a vulnerability. For anything that should not be public, our security.txt lists the encrypted route.