(*) The current list of requests that are available for copyright restricted texts is documented here.
Online Tools
Namespace Resolver - Resolve URN namespaces to API endpoints
oTAPIlot - Explore and query registered API endpoints
Openleaf - Read texts in ebook style
Default instances use the generic Text Miner. Custom instances may provide corpus specific features. See the source repository for installation and configuration. Subcorpus setups require a file named "urnlist.txt" as provided in the table.
Need a custom text infrastructure? I provide CTS/DTS, text mining, corpus tools, CTS-aware Search, APIs and data hosting. I also compile specific data sets on request. Contact me for a service contract.
State of Infrastructure
Chronicle
Availability and Software-Versions (versionsoftware.php):
🖌📚
Database Versions (versiondata.php):
🖌📚
tl;dr: This is a decentralized text data service based on Canonical Text Service, Distributed Text Service and additional text APIs.
Is there an API documentation? What requests are available?
Yes. There is a help command that lists functions and parameters for the tm and plain modules and specifications for the cts and dts modules.
Is the implementation feature complete?
CTS: Stable. DTS: Work in Progress. See the Roadmap for planned features.
How do data requests work for texts that are copyright restricted?
Copyright-restricted data can be accessed through temporary, dataset-specific access tokens for authorized users.
Can I host my data on my own server ?
Yes. Data sets are available with database and source via Zenodo and can be deployed on your own server.
Are CTS URNs persistently citable?
CTS URNs are designed for persistent citation. Work-in-progress corpora are explicitly marked. Versioning can be done via edition URNs or the namespace.
How reliable is this service?
The software and copyright-free data sets are openly available and can be independently deployed. A future cloning mechanism will further reduce the dependence on individual servers.
Is it finally "A Library of a Billion Words"?
Academic Mentions
Thibault Clérice, Hugh Cayless, Jonathan Robie, Ian W. Scott (2026) : Distributed Text Services 1.0: An API Standard for Publishing and Extending TEI Document Collections.
⇒
Piotr Ciążyński (2026) : Text Service Infrastructure (GitHub Fork)
⇒
Jacob Langeloh (2024) : Unleash the Apparatus? Towards a shared representation of knowledge about connections between primary sources.
⇒