Welcome to the Perseus Digital Library's CapiTainS environment.
+Perseus is bringing its primary source texts into + CTS and + EpiDoc TEI compliance + in the context of the efforts on the Perseids Project, + which is funded by the Andrew W. Mellon Foundation. +
+Why CTS? + "Canonical Text Services (“CTS”) is a component of the pioneering CITE architecture developed by the + Homer Multitext Project. CTS offers several advantages. In brief, CTS URNs allow us to produce a + semantically meaningful identifier which represents the position of a text in the hierarchy in which it is + traditionally cited. This same identifier scheme can also be used to cite into the text at the passage + level, within a specific version or instance of that text, or within the notional work the text represents. + This permits more precise, refined citation of textual sources and provides a basis for better text + alignment, text retrieval, and citation. +
+CapiTainS is a suite of tools and guidelines for the CTS standards. + The user interface provided here is an extension of the + Nemo Flask application and + the texts are served by the Nautilus + CTS provider. Texts are updated directly from the PerseusDL canonical github repositories as they pass tests + in the Hook Continuous Integration environment. +
+How does this work relate to the current version of Perseus? Tufts University and the Perseus team are + committed to maintaining Perseus 4.0 as is. + The CapiTainS environment, developed through the support of the Humboldt Chair of Digital Humanities at the University of Leipzig, offers a + means of demonstrating the on-going text conversion efforts as we move towards a contributor-based model of + publication. It is our hope that this environment will provide the basis for further collaboration within + the digital classics and digital humanities communities. +
+For further information, suggestions for improvement, or error reports, please create a GitHub issue or + contact Perseus via email. +
+