Petri-net vocabulary used across the pflow ecosystem: net structure, reusable net patterns and the link kinds that compose them, the exported types inside go-pflow and pflow-rs, and the pieces of a game search. Namespace https://ontology.pflow.xyz/ns#, version 0.4.1, released 2026-11-11.
Graph explorer: expand a term's neighbors, walk the class hierarchy, find a path between two terms and filter by edge type. It runs in your browser from pack.json, with no queries sent anywhere. Sign in with GitHub to ask it a question in words: every claim cites a term or a triple, and it says so when the graph has no answer.
These documents are the asserted ontology. Every term from the earlier
pflow.xyz/schema# context is still here, declared equivalent to its old IRI.
/sparql: SPARQL 1.1 protocol, read-only. SELECT, ASK, CONSTRUCT and DESCRIBE;
results capped at 1000 rows and 5 seconds; rate limited./mcp: the same data as an MCP server (Streamable HTTP, read-only tools)./term/<slug>, /pattern/<slug>, /linkkind/<slug>: one term, as Turtle, N-Triples or HTML with a neighborhood diagram.Queries run over the materialized graph (8028 triples): the asserted ontology plus the RDFS/OWL-RL consequences, so subclass closure is already present.
curl -H 'Accept: application/sparql-results+json' \
--data-urlencode 'query=SELECT ?c WHERE { ?c a <http://www.w3.org/2002/07/owl#Class> } LIMIT 5' \
https://ontology.pflow.xyz/sparql
The ontology is dedicated to the public domain under CC0 1.0 Universal: use it for anything, no attribution required. This covers the ontology data, not the source code of the projects it describes.
sha256sum -c SHA256SUMShash␣␣path, paths relative to the release folder. The tar is deterministic (sorted members, zero timestamps, owner 0, uncompressed), so its digest is reproducible.manifest.json → files: the same per-file SHA-256 for every file in the build except manifest.json itself.sha256: SHA-256 of the pack's graph text, which is sorted N-Triples, UTF-8, one triple per line.content_sha256 (6c43e36a61a15272d0bfd2cfa865b80c6e78f36606e48ec041a2244a0193813a): SHA-256 over a length-prefixed framing of
"oo-pack-content/1\n", the graph, then the certificate (format, claimed profile, counts, and every file's name and body in sorted order). Each length is 8 bytes, little-endian. It binds the proof to the graph it travels with, so a certificate sound over someone else's assertions cannot be swapped in.cert/asserted.sha256: SHA-256 of cert/asserted.tsv, the assertions the certificate rests on.python3 -I verify-pack.py pack.json # exit 0 = every digest above reproduces
Matching digests prove the files are intact and belong together, not that the
ontology is correct. The certificate in release/cert/
can be re-checked with oo-cert without trusting this server. It covers: RDFS rules only (rdfs9, rdfs11, scm-*); OWL axioms are not covered.