evaluate Distributed Text Services (DTS) and possibly implement it

[peterstadler]

What is DTS?

The Distributed Text Services (DTS) Specification defines an API for working with collections of text as machine-actionable data.

Publishers of digital text collections can use the DTS API to help them make their textual data Findable, Accessible, Interoperable and Reusable (FAIR).

DTS enables machine-consumption of digital text collections, and can be used by consumers of these collections in a variety of ways, such as for data analysis and the development of user-interfaces, tools and services.

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.

Source: https://distributed-text-services.github.io/specifications/

Why I think this is relevant for the WeGA

The WeGA already features an API, yet a non-standardized one. Adhering to the DTS standard will make the API and the data more interoperable and more FAIR.

[peterstadler]

I was looking for an Openapi swagger.json file for facilitating adoption, but only found that there was such a file but it got removed in distributed-text-services/specifications@2d8dd21. The commit message doesn't tell anything about the motivation though.