Semantic Web and Web 3.0 · class 12 · demo

Three layers, one solution

In none of the three cases was the technology chosen first. In all of them, the constraint of the domain determined the architecture. The last column is the group's — and it is what the defence will ask about.

Criterion	Electronic commerce	Social networks and content	Healthcare	Your project
Driver of the semantics	Integration	Federation	Regulation	…
Vocabulary	schema.org, GS1	ActivityStreams 2.0	SNOMED CT, LOINC	…
Is a chain justified?	Sometimes	No	Only for consent	…
Greatest risk	Data quality	Moderation	Privacy	…
What the semantic layer resolved	…	…	…	…
What was left unresolved	…	…	…	…

Layer	What it resolves	At what cost
Distribution (microservices, micro frontends)	Organisational autonomy	Operational complexity
Semantics	Shared meaning	Modelling and maintenance
Decentralisation	Verification without an intermediary	Throughput and irreversibility

Which of these three layers would your project use if it could keep only one?
And what were the other two actually resolving?

The presentation: 20 minutes, plus the individual discussion

Moment	Time	Content
Problem	2 min	Domain, constraint and what the solution resolves.
Architecture	4 min	Decisions and discarded alternatives, with justification.
Demonstration	8 min	The complete path, live, with the three layers.
Semantics	3 min	Ontology, competency queries and quality.
Decentralisation	2 min	What stayed on chain and why.
Appraisal	1 min	What you would do differently and what was left undone.

The demonstration is the centre: eight minutes for the path on the second page of this demo — live, from a clean clone, with ./check.sh showing no [failure] and no [skip]. From examples/05-cases/cases-grid.md and examples/03-presentation/presentation-guide.md.