Difference between revisions of "CapiTainS"

From The Digital Classicist Wiki
Jump to navigation Jump to search
 
Line 25: Line 25:
 
== Bibliography ==
 
== Bibliography ==
  
* Almas & Clérice, Continuous Integration and Unit Testing of Digital Editions, Digital Humanities Quaterly, Volume 11.4, Link
+
* Almas & Clérice, [http://www.digitalhumanities.org/dhq/vol/11/4/000350/000350.html Continuous Integration and Unit Testing of Digital Editions], Digital Humanities Quaterly, Volume 11.4, 2107
 
* Clérice, L[https://journals.openedition.org/medievales/8211 es outils CapiTainS, l’édition numérique et l’exploitation des textes], Médiévales, Volume 73, 2107, pp.115-131  
 
* Clérice, L[https://journals.openedition.org/medievales/8211 es outils CapiTainS, l’édition numérique et l’exploitation des textes], Médiévales, Volume 73, 2107, pp.115-131  
  

Latest revision as of 19:14, 10 November 2020

Available

Authors

  • Bridget Almas
  • Thibault Clérice
  • Matt Munson

Description

CapiTainS is an informal open-source organization which aims at providing a suite of tools and guidelines for Citable Text APIs standards.

It provides XML TEI guidelines for encoding text that can be then consumed or served over different tools :

  • Capitains HookTest, a tool that check compliances of a Corpus with the guidelines for TEI
  • Capitains Nemo, an application that can help quickly put together a website based on Capitains Guidelines
  • Capitains Nautilus, an application that provides different textual APIs (like CTS and DTS) for corpora following Capitains Guidelines
  • Capitains MyCapytain, the shared library used for parsing corpora. It can be used in corpus analysis pipeline to parse local repositories, to consume APIs but it can also be used further for building web application.

Bibliography