pflow ontology

Petri-net vocabulary used across the pflow ecosystem. Namespace https://ontology.pflow.xyz/ns#, version 0.1.0, released 2026-10-26.

Documents

• /ns: content-negotiated (Turtle, JSON-LD, N-Triples, RDF/XML)
• ns.ttl · ns.jsonld · ns.nt · ns.rdf
• manifest.json: a hash for every file

These documents are the asserted ontology. Every term from the earlier pflow.xyz/schema# context is still here, declared equivalent to its old IRI.

Query

• /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>: one glossary concept, as Turtle, N-Triples or HTML.

Queries run over the materialized graph (998 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

Download

• pflow-ontology-0.1.0.tar: the whole release (ontology in four formats, pack, certificate, manifest, verifier)
• pack.json: the portable pack (graph + certificate)
• SHA256SUMS: one line per file, for sha256sum -c SHA256SUMS
• verify-pack.py: recomputes the pack's digests with only the Python standard library

How the checksums are computed

• SHA256SUMS: plain SHA-256 of each file's bytes, hash␣␣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.
• Pack sha256: SHA-256 of the pack's graph text, which is sorted N-Triples, UTF-8, one triple per line.
• Pack content_sha256 (1215f9bba6cc1353d9cb1a2f2a7d1347f02185a36b22e0441650dd4179ee8d77): 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.