Remove keywords

comunica · Jan 29, 2024 · f23e042 · f23e042
1 parent 32ae4cb
commit f23e042
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 12 deletions.
diff --git a/content/abstract.md b/content/abstract.md
@@ -20,14 +20,6 @@ and uncovers opportunities for further optimizations in future work in terms of
 
 **Video**: [https://www.youtube.com/watch?v=4WHWgWWZ_aQ](https://www.youtube.com/watch?v=4WHWgWWZ_aQ)
 
-<span id="keywords" rel="schema:about"><span class="title">Keywords</span>
-Decentralized Knowledge Graphs,
-<a href="https://en.wikipedia.org/wiki/SPARQL" resource="http://dbpedia.org/resource/SPARQL">SPARQL</a>,
-Solid,
-<a href="https://en.wikipedia.org/wiki/Linked_Data" resource="http://dbpedia.org/resource/Linked_Data">Linked Data</a>,
-<a href="https://en.wikipedia.org/wiki/Resource_Description_Framework" resource="http://dbpedia.org/resource/Resource_Description_Framework">RDF</a>
-</span>
-
 <span class="printonly firstpagefooter">
 <span class="footnotecopyright">
 © 2024 Copyright held by the owner/author(s). Published in Proceedings of the 27th International Conference on Extending Database Technology (EDBT), 25th March-28th March, 2024, ISBN 978-3-89318-095-0 on OpenProceedings.org.

diff --git a/content/introduction.md b/content/introduction.md
@@ -24,15 +24,15 @@ by a *large* number (>1000) of *small* sources.
 Additionally, federated SPARQL query processing assumes sources to be known prior to query execution,
 which is not feasible in DKGs due to the lack of a central index.
 Hence, these techniques are ill-suited for the envisaged scale of distribution in DKGs.
-<span class="placeholder printonly">
-<span style="display: block; height: 5em;"></span>
-<!-- This is a dummy placeholder for the ACM first page footnote -->
-</span>
 
 To cope with these problems, alternative techniques have been introduced recently.
 [ESPRESSO](cite:cites espresso) was introduced as an approach that builds distributed indexes for Solid pods
 which can be accumulated in a single location.
 This accumulated index can then be queried using keyword search to find relevant pods to a query,
+<span class="placeholder printonly">
+<span style="display: block; height: 5em;"></span>
+<!-- This is a dummy placeholder for the ACM first page footnote -->
+</span>
 after which these relevant pods can be queried using federated SPARQL processing techniques.
 This approach depends on placing trust over personal data in this single accumulated indexer.
 [POD-QUERY](cite:cites podquery) is another approach that involves placing a SPARQL query engine agent in front of a Solid pod,