tx-view
tx-view reads one canonical Turtle graph file and renders a named
packaged projection. It is the local, offline presentation step after
cq-rdf body (or its deprecated
tx-graph compat alias) has emitted .ttl.
tx-view - packaged-view dispatcher over canonical Turtle graphs
Usage: tx-view --graph FILE [--view NAME] [--out FILE]
Available options:
--graph FILE Canonical Turtle graph file (from cq-rdf body).
--view NAME Packaged view name. Default: "cli-tree".
--out FILE Output destination. Default: stdout.
-h,--help Show the help text.
Inputs
--graph FILE must point at a single .ttl file in the canonical Turtle
subset emitted by cq-rdf body. The command has no network access and
does not read CBOR, an overlay, or a directory of graphs.
The file may be a one-transaction graph or a merged lattice assembled by
concatenating cq-rdf body Turtle output. The json-ld and
entity-occurrences views project the parsed file as a whole. The
transaction-shaped text views, cli-tree and asset-flow, render the
first cardano:Transaction subject found by the current in-repo reader;
for per-transaction presentation, run them against individual .ttl
files emitted with cq-rdf body --out FILE.
Use --out FILE to write the rendered bytes to a file instead of stdout:
Packaged Views
cli-tree
Text tree for a transaction body: inputs, reference inputs, outputs, assets, datum/reference-script details, minting, withdrawals, certificates, proposals, collateral, and fee. This is the default view.
asset-flow
Tab-separated rows summarising value movement as
assetClass quantity source destination, including ADA, native assets,
mint rows, and withdrawals.
entity-occurrences
Tab-separated rows summarising operator-declared entities and the number of explicit identifier leaf sites on each declaration.
json-ld
Deterministic JSON-LD projection of the parsed Turtle graph, with the same
subjects, predicates, and objects represented under @context and
@graph.
Shipped SPARQL Contract
views/no-stub-triples.rq is shipped with the repository as a SPARQL
gate/query contract. It finds cardano:Input or cardano:Output subjects
that have only their rdf:type triple, which would indicate an emitted
stub. It is not a current tx-view --view name.
Run it directly with a SPARQL engine:
Direct SPARQL
Packaged views are convenience projections. For custom analysis, query the same Turtle graph directly:
This is the right path for questions that are not one of the packaged
tx-view --view names.