| Popis: |
The granular representation and cross-referencing of online digital textual resources across editions in various languages in a machine-readable format is a complex problem, even more so when considering resources available in non-Latin scripts due to the large number of potential multilingual editions of the same text. Various solutions to this issue have been proposed over the years: one of the most notable initiatives is the Canonical Text Services protocol [1] (hereinafter referred to as CTS). A more recent ongoing project, the Distributed Text Services protocol [2], aims to propose a standard which addresses some of the limitations and issues encountered in the development and real-world use of CTS. The main difficulties of designing such a protocol could be summarized as follows: First, what could be considered as a ‘discrete’ textual resource can be composed of numerous, hierarchical sub-parts which can potentially be written in different languages, down to the level of a single word. Furthermore, each of these sub-parts might have a been translated in various different languages, and therefore available in a multitude of different online editions. To facilitate the consumption of these textual resources by digital research tools, it is therefore crucial to have a robust yet flexible way to represent and reference these different editions. Over the last two years, Department III of the Max Planck Institute for the History of Science has been working on a protocol called SHINE [3] which aims to tackle this issue by proposing a new approach to the representation of textual resources and their associated metadata. By combining a relatively rigid way of modelling textual resources with a highly flexible and hierarchical metadata scheme, we believe that we can propose a protocol that is both straightforward to implement and powerful enough to allow the representation and cross-referencing of any type of multilingual online textual resources. [1]https://wiki.digitalclassicist.org/Canonical_Text_Services, accessed 27/03/2019 [2]https://github.com/distributed-text-services/specifications, accessed 27/03/2019 [3]https://rise.mpiwg-berlin.mpg.de/pages/doc_for_developers, accessed 27/03/2019 |
