TEI Publisher Implementation

[monotasker]

TEI Publisher developers have part of the work done to implement DTS support. We need to get that completed. This will be an important step in encouraging adoption.

[Bronson-Brown-deVost]

Just to add on to this. I have been using the TEI Publisher support for DTS in the eRabbinica project. If anyone who understands the spec well here has some time, I would love to get some feedback about what I have done incorrectly/or correctly for that matter.

Currently I have the following endpoints:

• https://erabbinica.forschung.digitalbibleonline.org/exist/apps/erabbinica-app/api/dts
• https://erabbinica.forschung.digitalbibleonline.org/exist/apps/erabbinica-app/api/dts/collection
• https://erabbinica.forschung.digitalbibleonline.org/exist/apps/erabbinica-app/api/dts/document
• https://erabbinica.forschung.digitalbibleonline.org/exist/apps/erabbinica-app/api/dts/navigation

and you can see some example data at:

• https://erabbinica.forschung.digitalbibleonline.org/exist/apps/erabbinica-app/api/dts/collection?id=documents&page=1&per-page=30
• https://erabbinica.forschung.digitalbibleonline.org/exist/apps/erabbinica-app/api/dts/navigation?id=S04561.xml
• https://erabbinica.forschung.digitalbibleonline.org/exist/apps/erabbinica-app/api/dts/document?id=S04561.xml&start=4.4.7.3&end=4.4.7.6

I only exposed "canonical" references in the navigation system. Is it possible to expose multiple navigation systems in TEI Publishers DTS implementation—it would be nice if I could enable users to navigate by page/column/line in addition to the "canonical" references currently supported.

I'm happy to share any of my admittedly minimal experience with DTS support in TEI Publisher, if anyone would find it useful.