If I end up having enough time im September, sure, I can implement it,
but if not that's too much that's fine too.

I want one subsection for each component.

The contribution of this project is twofold. So we have two big
chapter for either for those two contribution: (1) Implementation
and (2) Applications.

Add a lot of \newpage

But not sure whether I'll follow through with it.

We are cutting away sample queries which do not add any insight. They
are slightly different but lead to similar conclusions. So it's better
to just have one.

I don't think I am going to use it as the table is way too big though.

Turns out: Honestly not that interesting. I think we can do better
with the evaluation.

As it appears many of the dcterms predicates remain unused. Even the
ones that do get used are used only very rarely.

Created using

 rdf4j-schema-generator/rdf4j-schema-generator -f application/xml \
   -c LOWER_UNDERSCORE -u http://purl.org/dc/terms/ -name dcterms \
   dublin_core_terms.rdf DCTerms.java

with the rdf4j-schema-generator [1] and the dcterms RDF file [2].

[1] https://github.com/ansell/rdf4j-schema-generator
[2] https://www.dublincore.org/specifications/dublin-core/dcmi-terms/dublin_core_terms.rdf