From dd94928ff954c3ec2de109d7caa577fd91eff932 Mon Sep 17 00:00:00 2001 From: Anne Ferger Date: Tue, 13 Feb 2024 09:13:12 +0100 Subject: [PATCH] annotated 14_2021-23-bleeker --- .../jtei-bleeker-et-al-199-source.xml | 97 ++++++++++--------- taxonomy/software-list.xml | 20 ++++ 2 files changed, 73 insertions(+), 44 deletions(-) diff --git a/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml b/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml index de52cbec..263e951c 100644 --- a/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml +++ b/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml @@ -377,29 +377,30 @@ nonlinear objects, modeled as a GODDAG data structure (Huitfeldt and Sperberg-McQueen 2003). In GODDAG, all children of the markup nodes are typically ordered, but TexMECS provides a - notation to mark certain markup nodes as unordered. The GODDAG processor - ignores the default linear order of these elements’ children, and therefore - TexMECS supports the representation of nonlinear structures. No known working - implementation of TexMECS, however, is currently available. At first glance, - EARMARK (Extremely Annotated RDF Markup) also seems to support the option to - represent nonlinearity: with EARMARK, users can express different linear - structures using RDF statements about text fragments, and in this way it is - possible to describe multiple text orders (Peroni and Vitali 2009, 4.1; Di - Iorio 2009). However, multi-orderedness is not the same as partial - orderedness: if a text is partially ordered, it means that (part of the) text - has no order. Multi-orderedness always implies a certain order. The EARMARK - specification as described in Peroni and - Vitali 2009 does not natively support partially ordered text, in the - sense that EARMARK users cannot mark the branching of the text stream. It is - also important to note that EARMARK is a metamarkup language, which means that - users encode their texts not in EARMARK but in an RDF - serialization.Recognizing the challenge of expressing literary texts - as RDF statements, Barabucci et al. developed the FRETTA approach, which is designed - to express EARMARK annotations in an embedded - syntax such as XML. It is unclear, however, whether this approach - has been further developed or implemented.

+ notation to mark certain markup nodes as unordered. The GODDAG + processor ignores the default linear order of these elements’ children, + and therefore TexMECS supports the representation of nonlinear structures. No + known working implementation of TexMECS, however, is currently available. At + first glance, EARMARK (Extremely Annotated RDF Markup) also seems to support + the option to represent nonlinearity: with EARMARK, users can express different + linear structures using RDF statements about text fragments, and in this way it + is possible to describe multiple text orders (Peroni and Vitali 2009, 4.1; Di Iorio 2009). However, multi-orderedness is not + the same as partial orderedness: if a text is partially ordered, it means that + (part of the) text has no order. Multi-orderedness always implies a certain + order. The EARMARK specification as described in Peroni and Vitali 2009 does not natively support + partially ordered text, in the sense that EARMARK users cannot mark the + branching of the text stream. It is also important to note that EARMARK is a + metamarkup language, which means that users encode their texts not in EARMARK + but in an RDF serialization.Recognizing the challenge of expressing + literary texts as RDF statements, Barabucci et al. developed the FRETTA approach, + which is designed to express EARMARK annotations + in an embedded syntax such as XML. It is unclear, however, + whether this approach has been further developed or implemented.

Discontinuity @@ -543,9 +544,11 @@

TAGML may resemble existing markup languages like XML, TexMECS, or LMNL, but TAGML is more expressive. For instance, in XML all annotation values are of type string, but TAGML offers data-typing of annotations. These data types are - expressed in UTF-8 and interpreted by the TAGML parser as different data types. - Encoders can distinguish between integer, string, or Boolean values ().

+ expressed in UTF-8 and interpreted by the TAGML parser as + different data types. Encoders can distinguish between integer, string, or + Boolean values ().
Example of TAGML, featuring different types of annotation value. @@ -572,11 +575,17 @@ encoding complex textual features, TAGML is designed to make that modeling process as natural as possible. The markup language has the same compactness as XML and is independent of the user environment.TAGML can be edited in any - editor, but the open source text editor Sublime has a TAGML - syntax highlighting package, and the reference - implementation Alexandria can be used to parse and validate TAGML + editor, but the open source text editor Sublime has a TAGML syntax highlighting + package, and the reference + implementation Alexandria can be used to parse and validate TAGML documents and store them as a TAG hypergraph. Following the argument of Sperberg-McQueen and Huitfeldt and Peroni and Vitali, we did not @@ -1048,8 +1057,8 @@ retrieve all quotes together. The first would not pose a problem for TEI XML, but retrieving the disjointed quotations as one (merged) utterance would only be possible with additional, vocabulary-specific coding. Processing the two q elements - as a single q requires a set of XSLT instructions that check + as a single q requires a set of XSLT instructions that check the values of the xml:id and the next and prev attributes in order to know which q elements should be stitched together. In TAGML, both scenarios would be equally straightforward. The hypergraph can be queried @@ -1091,22 +1100,22 @@ TEI transcription of
To process the text of this fragment correctly, one needs to write a rather - complicated set of XSLT instructions. At the very least, these + complicated set of XSLT instructions. At the very least, these instructions need to match the values of the xml:id and prev in order to process the first part of the deletion, look for the second part of the deletion, and then concatenate their textual content. At the same time, one has to prevent the second part from being processed twice (first as the second part of the deletion, and the second time together with the regular del elements). After - some experimenting and consulting several XSLT specialists, we have - come to no less than three different sets of instructions.The authors are - grateful to Peter Boot, Vincent Neyt, and Frederike Neuber for sharing their - expertise and invaluable insights. And considering the ingenuity and - technical expertise of the TEI community, we are quite certain there are even more - ways. In short, it can be a challenging and time-consuming process to write and tweak - vocabulary-specific and schema-aware tools—a daunting task for any TEI XML user who - lacks a certain level of technical expertise.

+ some experimenting and consulting several XSLT specialists, we have come + to no less than three different sets of instructions.The authors are grateful + to Peter Boot, Vincent Neyt, and Frederike Neuber for sharing their expertise and + invaluable insights. And considering the ingenuity and technical expertise + of the TEI community, we are quite certain there are even more ways. In short, it can + be a challenging and time-consuming process to write and tweak vocabulary-specific + and schema-aware tools—a daunting task for any TEI XML user who lacks a certain level + of technical expertise.

Conclusion diff --git a/taxonomy/software-list.xml b/taxonomy/software-list.xml index 0813c6b0..b41a7458 100644 --- a/taxonomy/software-list.xml +++ b/taxonomy/software-list.xml @@ -1690,6 +1690,26 @@ + + GODDAG processor + + + + + TAGML parser + + + + + Sublime Editor + + + + + Sublime Editor TAGML syntax highlighting package + https://huygensing.github.io/tagml-sublime-syntax/ + +