KONI: An Openly Licensed Linked Open Data Cross-Reference of the Thesaurus Linguae Graecae Canon

KONI — Linked Open Data Cross-Reference of the Thesaurus Linguae Graecae Canon Dataset README (Zenodo deposit) Authors / creators: Tamás Kovács (University of Graz - Department of Digital Humanities; https://orcid.org/0000-0002-3913-2946)Version: 1.0DOI: 10.5281/zenodo.21068684Related software: FLAME (text-reuse engine), https://doi.org/10.5281/zenodo.15805449Related publication: --- 1. Description This dataset is the openly licensed authority and cross-reference layer of the KONI (Koiné Online Nexus of Integration) project. It reconstructs the identifier structure of the Thesaurus Linguae Graecae (TLG) canon — the numbering that assigns every ancient and Byzantine Greek author a four-digit ID (Homer = `tlg0012`) and every work a three-digit ID (Iliad = `tlg0012.tlg001`) — and links those identifiers to the wider Linked Open Data cloud. It is not a text corpus: it carries no running Greek text. It is a graph of entities and links — authors, works, their stable URIs, their equivalences in public authority systems (Wikidata, VIAF), their canonical text references (CTS URNs / the Scaife Viewer), and the source-edition citation for each work that has an openly licensed digital text. The dataset covers 3,274 authors and 8,815 works. Of these, 1,924 authors carry a link to an external authority record and 1,622 works are bound to an openly licensed digital edition. Records without such a link are not omitted — they are published with an explicit `proposed` flag, so the dataset is at once a resolved cross-reference and a structured worklist of the identifiers that are still missing from the open graph. What is deliberately not included To respect the copyright of the TLG canon, the project's full local serialisation — which carries TLG-derived author names, epithets, and work titles — is not part of this deposit. The published files contain only identifiers, links to public resources, and openly licensed or self-curated edition citations. A provenance-tier firewall in the build pipeline excludes any source marked as restricted, and an automated self-test verifies that no restricted content reaches these files.