Semantic Web and Web 3.0 · class 12 · demo
The integration check and the reproducibility test
The example project of the class (examples/01-check): three sources, the class 10 pipeline,
seven competency queries and the class 11 chain records. At start-up this server rebuilt the graph from the sources, as
./scripts/load-semantics.sh does, and ran the checks of ./check.sh over it. This is what came out:
reproducibility check -- 2026-11-01T13:21:28Z [skip] no Docker reachable: the health of the services was not checked [ok] graph with 122 triples in 5 graphs, no SHACL violations [ok] 7/7 competency queries return results [ok] contract answered in block 8412991 (2 records indexed) [skip] interface not reachable at http://localhost:8080 (nothing listening) everything that can be checked here passed; 2 check(s) skipped (on the day of the defence there can be none skipped)
Exit code 0. Two lines are [skip]: this demo is one process, with no compose stack and no interface. A skipped check is not a passed check — on the day of the defence there can be none.
122
triples in graph.trig
5
graphs (4 named + the provenance)
7/7
competency queries with results
8412991
block of the 2 chain records
The way through
1 · The report
The five lines of check.sh, computed live: three run, two skipped, and why.
2 · The complete path
The slide «Integration check»: the event, the graph, the crossing query, the chain record, the result only the crossing gives.
3 · The competency queries
Each .rq of the project, with its result — and what happens to it when one graph is taken away.
4 · Break it on purpose
One fault on a copy — an empty chain graph, a negative price, a wrong prefix — and the [failure] it produces.
5 · Closing
The three cases on one grid, and the 20 minutes of the presentation.