DTS conformance when not publishing in TEI/XML?

[davidbgk]

From the FAQ:

Can I use DTS if I don’t publish my texts in TEI/XML?

The DTS Collection and Navigations endpoints can be used to provide navigation capabilities across collections of texts and within a textual document regardless of the data format. However, the Document endpoint only supports TEI texts.

(emphase is mine)

And from the specification:

All DTS servers MUST implement all endpoints:

• Entry
• Collection
• Document
• Navigation

All DTS servers MUST implement all valid calls on these endpoints as documented

(again)

I'm wondering how these two entries are compatible? I want to implement the specification for an HTML export of a book (without TEI), what should I do for the Document endpoint?

[hcayless]

Yeah, I think that FAQ is from an older phase of the spec and needs updating. While the Document endpoint should support TEI, the spec explicitly says it can provide other formats. Iirc, the prior thinking was that you could just implement the Collection endpoint and provide a download URL, but we did away with that when we were finalizing the spec.