qlever 0.5.25__tar.gz

qlever-0.5.25/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

qlever-0.5.25/PKG-INFO

@@ -0,0 +1,112 @@
+Metadata-Version: 2.4
+Name: qlever
+Version: 0.5.25
+Summary: Command-line tool for using the QLever graph database
+Author-email: Hannah Bast <bast@cs.uni-freiburg.de>
+License: Apache-2.0
+Project-URL: Github, https://github.com/ad-freiburg/qlever
+Keywords: Graph database,Triplestore,Knowledge graphs,SPARQL,RDF
+Classifier: Topic :: Database :: Database Engines/Servers
+Classifier: Topic :: Database :: Front-Ends
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: psutil
+Requires-Dist: termcolor
+Requires-Dist: argcomplete
+Requires-Dist: pyyaml
+Requires-Dist: rdflib
+Requires-Dist: requests-sse
+Dynamic: license-file
+
+# QLever
+
+QLever is a very fast SPARQL engine, much faster than most existing engines. It
+can handle graphs with more than hundred billion triples on a single machine
+with moderate resources. See https://qlever.cs.uni-freiburg.de for more
+information and many public SPARQL endpoints that use QLever
+
+This project provides a Python script that can control everything that QLever
+does, in particular, creating SPARQL endpoints for arbitrary RDF datasets. It
+is supposed to be very easy to use and self-explanatory as you use it. In
+particular, the tool provides context-sensitive autocompletion of all its
+commands and options. If you use a container system (like Docker or Podman),
+you don't even have to download any QLever code, but the script will download
+the required image for you.
+
+NOTE: There has been a major update on 24.03.2024, which changed some of the
+Qleverfile variables and command-line options (all for the better, of course).
+If you encounter any problems, please contact us by opening an issue on
+https://github.com/ad-freiburg/qlever-control/issues.
+
+# Installation
+
+Simply do `pip install qlever` and make sure that the directory where pip
+installs the package is in your `PATH`. Typically, `pip` will warn you when
+that is not the case and tell you what to do.
+
+# Usage
+
+Create an empty directory, with a name corresponding to the dataset you want to
+work with. For the following example, take `olympics`. Go to that directory
+and do the following. After the first call, `qlever` will tell you how to
+activate autocompletion for all its commands and options (it's very easy, but
+`pip` cannot do that automatically).
+
+```
+qlever setup-config olympics   # Get Qleverfile (config file) for this dataset
+qlever get-data                # Download the dataset
+qlever index                   # Build index data structures for this dataset
+qlever start                   # Start a QLever server using that index
+qlever query                   # Launch an example query
+qlever ui                      # Launch the QLever UI
+```
+
+This will create a SPARQL endpoint for the [120 Years of
+Olympics](https://github.com/wallscope/olympics-rdf) dataset. It is a great
+dataset for getting started because it is small, but not trivial (around 2
+million triples), and the downloading and indexing should only take a few
+seconds.
+
+Each command will also show you the command line it uses. That way you can
+learn, on the side, how QLever works internally. If you just want to know the
+command line for a particular command, without executing it, you can append
+`--show` like this:
+
+```
+qlever index --show
+```
+
+There are many more commands and options, see `qlever --help` for general help,
+`qlever <command> --help` for help on a specific command, or just the
+autocompletion.
+
+# Use with your own dataset
+
+To use QLever with your own dataset, you should also write a `Qleverfile`, like
+in the example above. The easiest way to write a `Qleverfile` is to get one of
+the existing ones (using `qlever setup-config ...` as explained above) and then
+change it according to your needs (the variable names should be self-explanatory).
+Pick one for a dataset that is similar to yours and when in doubt, pick `olympics`.
+
+# For developers
+
+The (Python) code for the script is in the `*.py` files in `src/qlever`. The
+preconfigured Qleverfiles are in `src/qlever/Qleverfiles`.
+
+If you want to make changes to the script, or add new commands, do as follows:
+
+```
+git clone https://github.com/ad-freiburg/qlever-control
+cd qlever-control
+pip install -e .
+```
+
+Then you can use `qlever` just as if you had installed it via `pip install
+qlever`. Note that you don't have to rerun `pip install -e .` when you modify
+any of the `*.py` files and not even when you add new commands in
+`src/qlever/commands`. The exceutable created by `pip` simply links and refers
+to the files in your working copy.
+
+If you have bug fixes or new useful features or commands, please open a pull
+request. If you have questions or suggestions, please open an issue.

qlever-0.5.25/README.md

@@ -0,0 +1,91 @@
+# QLever
+
+QLever is a very fast SPARQL engine, much faster than most existing engines. It
+can handle graphs with more than hundred billion triples on a single machine
+with moderate resources. See https://qlever.cs.uni-freiburg.de for more
+information and many public SPARQL endpoints that use QLever
+
+This project provides a Python script that can control everything that QLever
+does, in particular, creating SPARQL endpoints for arbitrary RDF datasets. It
+is supposed to be very easy to use and self-explanatory as you use it. In
+particular, the tool provides context-sensitive autocompletion of all its
+commands and options. If you use a container system (like Docker or Podman),
+you don't even have to download any QLever code, but the script will download
+the required image for you.
+
+NOTE: There has been a major update on 24.03.2024, which changed some of the
+Qleverfile variables and command-line options (all for the better, of course).
+If you encounter any problems, please contact us by opening an issue on
+https://github.com/ad-freiburg/qlever-control/issues.
+
+# Installation
+
+Simply do `pip install qlever` and make sure that the directory where pip
+installs the package is in your `PATH`. Typically, `pip` will warn you when
+that is not the case and tell you what to do.
+
+# Usage
+
+Create an empty directory, with a name corresponding to the dataset you want to
+work with. For the following example, take `olympics`. Go to that directory
+and do the following. After the first call, `qlever` will tell you how to
+activate autocompletion for all its commands and options (it's very easy, but
+`pip` cannot do that automatically).
+
+```
+qlever setup-config olympics   # Get Qleverfile (config file) for this dataset
+qlever get-data                # Download the dataset
+qlever index                   # Build index data structures for this dataset
+qlever start                   # Start a QLever server using that index
+qlever query                   # Launch an example query
+qlever ui                      # Launch the QLever UI
+```
+
+This will create a SPARQL endpoint for the [120 Years of
+Olympics](https://github.com/wallscope/olympics-rdf) dataset. It is a great
+dataset for getting started because it is small, but not trivial (around 2
+million triples), and the downloading and indexing should only take a few
+seconds.
+
+Each command will also show you the command line it uses. That way you can
+learn, on the side, how QLever works internally. If you just want to know the
+command line for a particular command, without executing it, you can append
+`--show` like this:
+
+```
+qlever index --show
+```
+
+There are many more commands and options, see `qlever --help` for general help,
+`qlever <command> --help` for help on a specific command, or just the
+autocompletion.
+
+# Use with your own dataset
+
+To use QLever with your own dataset, you should also write a `Qleverfile`, like
+in the example above. The easiest way to write a `Qleverfile` is to get one of
+the existing ones (using `qlever setup-config ...` as explained above) and then
+change it according to your needs (the variable names should be self-explanatory).
+Pick one for a dataset that is similar to yours and when in doubt, pick `olympics`.
+
+# For developers
+
+The (Python) code for the script is in the `*.py` files in `src/qlever`. The
+preconfigured Qleverfiles are in `src/qlever/Qleverfiles`.
+
+If you want to make changes to the script, or add new commands, do as follows:
+
+```
+git clone https://github.com/ad-freiburg/qlever-control
+cd qlever-control
+pip install -e .
+```
+
+Then you can use `qlever` just as if you had installed it via `pip install
+qlever`. Note that you don't have to rerun `pip install -e .` when you modify
+any of the `*.py` files and not even when you add new commands in
+`src/qlever/commands`. The exceutable created by `pip` simply links and refers
+to the files in your working copy.
+
+If you have bug fixes or new useful features or commands, please open a pull
+request. If you have questions or suggestions, please open an issue.

qlever-0.5.25/pyproject.toml

@@ -0,0 +1,41 @@
+[build-system]
+requires = ["setuptools>=61.0", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "qlever"
+description = "Command-line tool for using the QLever graph database"
+version = "0.5.25"
+authors = [
+    { name = "Hannah Bast", email = "bast@cs.uni-freiburg.de" }
+]
+readme = "README.md"
+license = { text = "Apache-2.0" }
+requires-python = ">=3.8"
+
+keywords = ["Graph database", "Triplestore", "Knowledge graphs", "SPARQL", "RDF"]
+
+classifiers = [
+ "Topic :: Database :: Database Engines/Servers",
+ "Topic :: Database :: Front-Ends"
+]
+
+dependencies = [ "psutil", "termcolor", "argcomplete", "pyyaml", "rdflib", "requests-sse"]
+
+[project.urls]
+Github = "https://github.com/ad-freiburg/qlever"
+
+[project.scripts]
+"qlever" = "qlever.qlever_main:main"
+
+[tool.setuptools]
+license-files = ["LICENSE"]
+package-data = { "qlever" = ["Qleverfiles/*"] }
+
+[tool.pytest.ini_options]
+pythonpath = ["src"]
+
+[tool.ruff]
+line-length = 79 
+[tool.ruff.lint]
+extend-select = ["I"]

qlever-0.5.25/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

qlever-0.5.25/src/qlever/Qleverfiles/Qleverfile.dblp

@@ -0,0 +1,35 @@
+# Qleverfile for DBLP, use with QLever CLI (`pip install qlever`)
+#
+# qlever get-data  # ~1 min, ~5 GB compressed, 1.3 B triples
+# qlever index     # ~30 min, ~20 GB RAM, ~25 GB index size on disk
+# qlever start     # ~3 s, adjust MEMORY_FOR_QUERIES as needed
+#
+# Measured on an AMD Ryzen 9 5950X with 128 GB RAM, and NVMe SSD (25.10.2024)
+
+[data]
+NAME         = dblp
+DATA_TARFILE = dblp_KG_with_associated_data.tar
+GET_DATA_URL = https://sparql.dblp.org/download/${DATA_TARFILE}
+GET_DATA_CMD = (curl -LROC - ${GET_DATA_URL} && tar -xf ${DATA_TARFILE}) 2>&1 | tee ${NAME}.download-log.txt && rm -f ${DATA_TARFILE}
+VERSION      = $$(date -r dblp.ttl.gz +"%d.%m.%Y %H:%M" || echo "NO_DATE")
+DESCRIPTION  = DBLP computer science bibliography + citations from OpenCitations, data from ${GET_DATA_URL} (version ${VERSION})
+FORMAT       = ttl
+
+[index]
+INPUT_FILES      = *.gz
+MULTI_INPUT_JSON = { "cmd": "zcat {}", "for-each": "*.gz" }
+SETTINGS_JSON    = { "ascii-prefixes-only": false, "num-triples-per-batch": 5000000, "prefixes-external": [""] }
+
+[server]
+PORT               = 7015
+ACCESS_TOKEN       = ${data:NAME}
+MEMORY_FOR_QUERIES = 10G
+CACHE_MAX_SIZE     = 5G
+TIMEOUT            = 300s
+
+[runtime]
+SYSTEM = docker
+IMAGE  = docker.io/adfreiburg/qlever:latest
+
+[ui]
+UI_CONFIG = dblp

qlever-0.5.25/src/qlever/Qleverfiles/Qleverfile.dblp-plus

@@ -0,0 +1,33 @@
+# Qleverfile for DBLP Plus, use with https://github.com/ad-freiburg/qlever-control
+#
+# qlever get-data    downloads .gz file of size ~3 GB (as of 31.07.2022)
+# qlever index       takes ~30 minutes and ~20 GB RAM (on an AMD Ryzen 9 5900X)
+# qlever start       starts the server
+#
+# Also builds a text index for fast kewyword search in literals.
+
+[data]
+NAME              = dblp-plus
+GET_DATA_CMD      = wget -nc -O dblp.ttl.gz https://dblp.org/rdf/dblp.ttl.gz
+DESCRIPTION       = Publication data from https://dblp.org, with affiliations from https://www.wikidata.org and citations from https://opencitations.net
+TEXT_DESCRIPTION  = All literals, search with FILTER KEYWORDS(?text, "...")
+
+[index]
+INPUT_FILES       = dblp.ttl.gz affiliations.nt affiliations.additions.nt citations.nt
+CAT_INPUT_FILES   = zcat -f ${INPUT_FILES}
+SETTINGS_JSON     = { "ascii-prefixes-only": false, "num-triples-per-batch": 1000000, "prefixes-external": [ "<https://w3id.org", "<https://doi.org", "<http://dx.doi.org" ] }
+TEXT_INDEX        = from_literals
+
+[server]
+PORT                        = 7027
+ACCESS_TOKEN                = ${data:NAME}_169238202
+MEMORY_FOR_QUERIES          = 20G
+CACHE_MAX_SIZE              = 10G
+CACHE_MAX_SIZE_SINGLE_ENTRY = 2G
+
+[runtime]
+SYSTEM = docker
+IMAGE  = docker.io/adfreiburg/qlever:latest
+
+[ui]
+UI_CONFIG = dblp-plus

qlever-0.5.25/src/qlever/Qleverfiles/Qleverfile.dbpedia

@@ -0,0 +1,30 @@
+# Qleverfile for DBpedia, use with https://github.com/ad-freiburg/qlever-control
+#
+# qlever get-data  # ~14 GB, ~850 M triples (as of 30.07.2024)
+# qlever index     # ~20 min (on an AMD Ryzen 9 5900X)
+# qlever start     # ~3 sec
+
+[data]
+NAME         = dbpedia
+DATABUS_URL  = https://databus.dbpedia.org/dbpedia/collections/latest-core
+GET_DATA_CMD = curl -X POST -H "Accept: text/csv" --data-urlencode "query=$$(curl -s -H "Accept:text/sparql" https://databus.dbpedia.org/dbpedia/collections/latest-core)" https://databus.dbpedia.org/sparql | tail -n+2 | sed 's/\r$$//' | sed 's/"//g' | while read -r file; do wget -P rdf-input $$file; done
+DESCRIPTION  = RDF data from ${DATABUS_URL}
+
+[index]
+INPUT_FILES     = rdf-input/*
+CAT_INPUT_FILES = (cat rdf-input/*.nt; lbzcat -n2 rdf-input/*.bzip2 rdf-input/*.bz2)
+SETTINGS_JSON   = { "ascii-prefixes-only": true, "num-triples-per-batch": 1000000, "prefixes-external": [""] }
+WITH_TEXT_INDEX = false
+
+[server]
+PORT               = 7012
+ACCESS_TOKEN       = ${data:NAME}
+MEMORY_FOR_QUERIES = 10G
+CACHE_MAX_SIZE     = 5G
+
+[runtime]
+SYSTEM = docker
+IMAGE  = docker.io/adfreiburg/qlever:latest
+
+[ui]
+UI_CONFIG = dbpedia

qlever-0.5.25/src/qlever/Qleverfiles/Qleverfile.default

@@ -0,0 +1,51 @@
+# Default Qleverfile, use with https://github.com/ad-freiburg/qlever-control
+#
+# If you have never seen a Qleverfile before, we recommend that you first look
+# at the example Qleverfiles on http://qlever.cs.uni-freiburg.de/qlever-control/
+# src/qlever/Qleverfiles . Or execute `qlever setup-config <dataset>` on the
+# command line to obtain the example Qleverfiles for <dataset>.
+
+# As a minimum, each dataset needs a name. If you want `qlever get-data` to do
+# something meaningful, you need to define GET_DATA_CMD. Otherwise, you need to 
+# generate (or download or copy from somewhere) the input files yourself. Each
+# dataset should have a short DESCRIPTION, ideally with a date.
+[data]
+NAME         =
+GET_DATA_CMD =
+DESCRIPTION  = 
+
+# The format for INPUT_FILES should be such that `ls ${INPUT_FILES}` lists all
+# input files. CAT_INPUT_FILES should write a concatenation of all input files
+# to stdout. For example, if your input files are gzipped, you can write `zcat
+# ${INPUT_FILES}`. Regarding SETTINGS_JSON, look at the other Qleverfiles for
+# examples. Several batches of size `num-triples-per-batch` are kept in RAM at 
+# the same time; increasing this, increases the memory usage but speeds up the
+# loading process.
+[index]
+INPUT_FILES     = *.ttl
+CAT_INPUT_FILES = cat ${INPUT_FILES}
+SETTINGS_JSON   = { "num-triples-per-batch": 1000000 }
+
+# The server listens on PORT. If you want to send privileged commands to the
+# server, you need to specify an ACCESS_TOKEN, which you then have to set via a
+# URL parameter `access_token`. It should not be easily guessable, unless you
+# don't mind others to get privileged access to your server.
+[server]
+PORT         = 8888
+ACCESS_TOKEN = 
+
+# Use SYSTEM = docker to run QLever inside a docker container; the Docker image
+# will be downloaded automatically. Use SYSTEM = native to use self-compiled
+# binaries `IndexBuilderMain` and `ServerMain` (which should be in you PATH).
+[runtime]
+SYSTEM = docker
+IMAGE  = docker.io/adfreiburg/qlever:latest
+
+# UI_PORT specifies the port of the QLever UI web app, when you run `qlever ui`.
+# The UI_CONFIG must be one of the slugs from http://qlever.cs.uni-freiburg.de
+# (see the dropdown menu on the top right, the slug is the last part of the URL).
+# It determines the example queries and which SPARQL queries are launched to
+# obtain suggestions as you type a query.
+[ui]
+UI_PORT   = 8176
+UI_CONFIG = default

qlever-0.5.25/src/qlever/Qleverfiles/Qleverfile.dnb

@@ -0,0 +1,40 @@
+# Qleverfile for Olympics, use with https://github.com/ad-freiburg/qlever-control
+#
+# qlever get-data  # takes ~ 10 mins to download .nt.gz file of size ~ 8 GB
+# qlever index     # takes ~ 5 min and ~ 5 GB RAM (on an AMD Ryzen 9 5900X)
+# qlever start     # starts the server (instantaneous)
+#
+# IMPORTANT: The current files contain invalid floating point literals. To make
+# QLever ignore them, compile QLever with `invalidLiteralsAreSkipped_ = true`
+# in `src/parser/TurtleParserBase.h:55`.
+#
+# NOTE: https://data.dnb.de/opendata/ is rather confusing becase of the many
+# files. This Qleverfile downloads all the datasets named "Gesamtabzug", except
+# bib_lds.nt.gz, which contains incorrectly formatted IRIs. The file
+# dnb-all_ldsprov.nt.gz contains invalid floating point literals; to ignore
+# them, compile QLever with TurtleParserBase::invalidLiteralsAreSkipped_ = true
+
+[data]
+NAME              = dnb
+BASE_URL          = https://data.dnb.de/opendata
+GET_DATA_CMD      = curl -L -C - --remote-name-all --remote-time ${BASE_URL}/authorities-gnd_lds.nt.gz ${BASE_URL}/dnb-all_lds.nt.gz ${BASE_URL}/dnb-all_ldsprov.nt.gz ${BASE_URL}/zdb_lds.nt.gz 2>&1 | tee ${data:NAME}.getdata-log.txt
+VERSION           = $$(date -r dnb-all_lds.nt.gz +%d.%m.%Y || echo "NO_DATE")
+DESCRIPTION       = DNB data from ${BASE_URL} (authoritities-gnd_lds, dnb_all_lds, dnb-all_ldsprov, zdb_lds), version ${VERSION}
+
+[index]
+INPUT_FILES     = *.nt.gz
+CAT_INPUT_FILES = zcat ${INPUT_FILES} | sed '/"\$$R0"/d;/"0\.03013\$$D"/d'
+SETTINGS_JSON   = { "ascii-prefixes-only": false, "num-triples-per-batch": 1000000 }
+
+[server]
+PORT               = 7035
+ACCESS_TOKEN       = ${data:NAME}
+MEMORY_FOR_QUERIES = 5G
+CACHE_MAX_SIZE     = 2G
+
+[runtime]
+SYSTEM = docker
+IMAGE  = docker.io/adfreiburg/qlever:latest
+
+[ui]
+UI_CONFIG = dnb