Dannet

DanNet is a WordNet for the Danish language. DanNet uses RDF as its native representation at both the database level, in the application space, and as its primary serialisation format.

• Browse the data at wordnet.dk
• Query the data by integrating with AI
• Download datasets from the releases page

Table of Contents

• Dataset Formats
• Companion Datasets
• Standards
• LLM Integration (AI)
• Implementation
• Setup
• Deployment
• Database Release Workflow

Dataset Formats

DanNet is available in multiple formats to maximise compatibility:

Example: Using DanNet with Python

import wn

wn.add("dannet-wn-lmf.xml.gz")

for synset in wn.synsets('kage'): print((synset.lexfile() or "?") + ": " + (synset.definition() or "?"))

Differences Between Formats

While every format includes all synsets/senses/words, the CSV, WN-LMF and DMLex variants do *not* include every data point:

• CSV: Some data is lost when converting from an open graph to fixed tables.
• WN-LMF: Only official GWA relations are included per the standard (proprietary DanNet relations from the DanNet schema are excluded).
• DMLex: Combines DanNet with COR, DDS and COR.SEM in one file. Relations to other datasets are not included. See doc/dmlex/plan.md for the conversion rules.

For the complete dataset, use the RDF format or browse at wordnet.dk.

Companion Datasets

Several companion datasets expand the RDF graph with additional data:

Inferred Data

Additional data is implicitly inferred from the base dataset, companion datasets, and ontological metadata. These inferences can be browsed at wordnet.dk. Releases containing fully inferred graphs are specifically marked as such.

Standards

DanNet is based on the Ontolex-lemon standard combined with relations defined by the Global Wordnet Association as used in the official GWA RDF standard.

URI Prefixes

All DanNet URIs resolve to HTTP resources. Accessing one of these URIs via a GET request returns the data for that resource.

Schemas

DanNet has proprietary relations defined in the DanNet schema in an Ontolex-compatible way. There is also a schema for EuroWordNet concepts. Both schemas follow the RDF conventions listed by Philippe Martin.

LLM Integration

DanNet can be connected to AI tools like Claude via MCP (Model Context Protocol).

• MCP server URL: https://wordnet.dk/mcp
• Registry ID: io.github.kuhumcst/dannet

To connect in e.g. Claude Desktop: go to Settings > Connectors > Browse Connectors, click "add a custom one", enter a name (e.g., "DanNet") and the MCP server URL.

Once connected, you can query DanNet's semantic relations directly through Claude.

Implementation

The database backend is Apache Jena, a mature RDF triplestore with OWL inference support. When represented in Jena, DanNet's relations form a queryable knowledge graph. DanNet is developed in Clojure, using Theophrastus, our fork of Aristotle, to interact with Jena.

See rationale.md for more on the design decisions.

Full Production Setup

The production deployment at wordnet.dk consists of three services managed via Docker Compose:

• DanNet — the Clojure/ClojureScript web application
• MCP server — a Python-based MCP server providing LLM access to DanNet
• Caddy — reverse proxy handling HTTPS and routing

Clojure Support

DanNet can be queried in various ways from Clojure (see queries.md). Apache Jena transactions are built-in and enable persistence via the TDB 2 layer.

Web Application

The frontend is written in ClojureScript using Rum, served by Pedestal. The app works both as a single-page application (with JavaScript) and as a regular HTML website (without). Content negotiation serves different representations (HTML, RDF, Transit+JSON) based on the request.

See doc/web.md for details.

Bootstrap Process

New releases are bootstrapped from the preceding release. The process (in dk.cst.dannet.db.bootstrap):

1. Load and clean the previous version's RDF data
2. Convert to triples using the current schema
3. Import into Apache Jena graphs and apply release changes (only when cutting a release, i.e. when to differs from from)
4. Infer additional triples via OWL/RDFS schemas
5. Export the final RDF dataset (see Database Release Workflow)

Bootstrap data lives under ./bootstrap relative to the execution directory:

the DanNet release assets in ./bootstrap/from/ / (named after the

release being bootstrapped *from*, so several can coexist) and the shared

English datasets in ./bootstrap/other/english/. Missing files are downloaded

automatically, so manual placement is only needed when working offline.

The rest of ./bootstrap/other/ holds files curated by hand, which aren't downloaded. If the COR files (cor*.tsv, *.cordiff and cor.sem.*.tsv) go missing, you can download them again from ordregister.dk.

If a database build fails partway, delete the half-built db/tdb2/ directory before you start again; the build error gives its path. A build only checks that the directory exists, so it would otherwise reuse the incomplete database.

Setup

DanNet requires Java and Clojure's official CLI tools. Dependencies are specified in deps.edn.

Development

1. Start an nREPL on port 7888 with clojure -M:nrepl
2. Start the web service using (restart) in dk.cst.dannet.web.service — available at localhost:3456
3. Run the frontend with shadow-cljs:

   npx shadow-cljs watch app

It serves the app at localhost:7777, in front of the web service.

Most changes can be tried in the REPL without restarting the web service. Run the tests with clojure -X:validate:test, where the :validate alias adds the validators that the DMLex tests need.

Testing a Release Build

Using Docker (requires Docker daemon running):

# From the docker/ directory

docker compose up --build

Or manually:

shadow-cljs --aliases :frontend release app

clojure -T:build org.corfield.build/uber :lib dk.cst/dannet :main dk.cst.dannet.web.service :uber-file "\"dannet.jar\"" java -jar -Xmx4g dannet.jar

Memory Requirements

The system uses ~1.5 GB when idle and ~3 GB when rebuilding the database. A server should have at least 4 GB of available RAM.

Validating RDF (SHACL)

The dn: dataset is validated against SHACL shapes located in resources/schemas/internal/shapes/ (see dk.cst.dannet.db.shapes). This happens in several ways:

• a non-fatal check of the asserted graph runs asynchronously at every boot, logging violations and comparing counts to a known baseline,
• RDF exports of the dn: dataset are gated: a baseline regression aborts the export, and
• fixture-based tests run via clojure -X:validate:test, which is also executed by the GitHub Actions workflow in .github/workflows/test.yml.

Validating WN-LMF

python3 -m venv examples/venv

source examples/venv/bin/activate python3 -m pip install wn python -m wn validate --output-file examples/wn-lmf-validation.json export/wn-lmf/dannet-wn-lmf.xml

Validating DMLex

The validator in dk.cst.dannet.db.export.dmlex-validate checks both serializations of a variant against the official DMLex schemas. It needs the :validate alias:

clojure -M:validate -e "((requiring-resolve 'dk.cst.dannet.db.export.dmlex-validate/validate-dmlex!) \"export/dmlex/\" \"da\")"

Deployment

The production server at wordnet.dk runs as a systemd service delegating to Docker.

Service Setup

cp system/dannet.service /etc/systemd/system/dannet.service

systemctl enable dannet systemctl start dannet

Updating the Web Service

To update the web service software without changing the database:

# From the docker/ directory

docker compose up -d dannet --build

Database Release Workflow

When releasing a new version of the database:

1. Set to in dk.cst.dannet.release to the ne