Overview
I developed a viewer for DTS (Distributed Text Services), so this is a memo about it.
You can try it at the following URL.
https://dts-viewer.vercel.app/ja/
Background
The official page for DTS (Distributed Text Services) is below.
https://distributed-text-services.github.io/specifications/
I also covered it in the following article.
This time, I developed a viewer that partially conforms to this DTS specification.
Usage
The following is the top page. Enter a DTS URL in the form. Examples are provided at the bottom of the page. Technically, it uses the Entry point.
This is the collection list page. It uses the Collection Endpoint.
The following API is used as an example.
Following the links navigates to a resource list page like the following.
Pressing the download button displays the TEI/XML. It uses the Document Endpoint.
Pressing the navigation button displays a list of accessible partial texts. It uses the Navigation Endpoint, but currently does not support multiple hierarchy levels.
Clicking a link allows you to download the partial text as shown below.
Design Considerations
The official page states the following.
The DTS Specification is currently in a public comment period following the 1-alpha release
Due to this background, there were variations in how existing DTS implementations described their data. Therefore, the viewer internally converts data to the DTS API (1.0 Draft) format as much as possible, and then visualizes the results.
As the DTS specification matures, such issues should be resolved.
Summary
The DTS specification is described as follows.
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).
I hope this viewer is useful when publishing TEI/XML files.