The DTS Specification is currently a First Public Working Draft.
The Distributed Text Services (DTS) Specification defines a Hypermedia-Driven Web API for working with collections of text as machine-actionable data. It specifies 3 distinct operation endpoints:
The Collections and Navigation endpoints are specified to return LD+JSON adhering to the W3C Hydra standard. The Documents endpoint is specified to return TEI/XML of the requested text or fragment.
Note that DTS is a specification for an API and not in and of itself an implementation of that API. Reference Implementations are available (see below) and individual text publishers are encouraged to implement this API in their own projects where appropriate.
The Distributed Text Services effort has been inspired, informed and influenced by the Canonical Text Services protocol (CTS). CTS has allowed many classical, canonical texts encoded in TEI to be made available in a machine-actionable, linked open data fashion. However, the CTS API is tightly coupled to the CTS URN identifier system which does not support citation systems used by more modern content or other forms of writing, such as papyri or inscriptions. The API also does not adhere to modern community standards for Web APIs.
To address these limitations and enable standardized, machine-actionable operations across a wide variety of texts, a group of interested scholars and technologists have collaborated to develop the Distributed Text Services specification. We hope this will become a community-supported standard for achieving interoperability and shared services and tools for working with digital text collections.
The DTS API provides the following core capabilities to clients:
The DTS API enables its implementors to support:
The DTS API imposes the following requirements on implementors:
The following individuals have contributed to this effort:
Send a request to join https://groups.google.com/forum/#!forum/distributed-text-services