From 19f342f07c24cd0a62d3f5e9a65fc3e326bccd66 Mon Sep 17 00:00:00 2001 From: Alice BRENON <alice.brenon@ens-lyon.fr> Date: Fri, 25 Feb 2022 10:09:48 +0100 Subject: [PATCH] Hopefully dotting the Is and crossing the Ts of the structural remarks --- ICHLL_Brenon.md | 37 ++++++++++++++++++++++++------------- 1 file changed, 24 insertions(+), 13 deletions(-) diff --git a/ICHLL_Brenon.md b/ICHLL_Brenon.md index c57bbbf..cc0bb88 100644 --- a/ICHLL_Brenon.md +++ b/ICHLL_Brenon.md @@ -298,13 +298,24 @@ contain only one word, like `<pos>adj</pos>` in the example given in the official documentation. Secondly, although we have seen examples of connections from this module to the -rest of the XML-TEI, especially the *core* module (see the case of the `<ref/>` -element above), the *dictionaries* appears somewhat isolated from important -structural elements like `<head/>` or `<div/>`. Indeed, computing all the paths -from either `<entry/>` or `<sense/>` elements to the latter of length shorter or -equal to 5 by a systematic traversal of the graph yields exclusively paths -(respectively 9042 and 39093 of them) containing either a `<floatingText/>` or -an `<app/>` element. The first one is used to encode +rest of the XML-TEI, especially to the *core* module (see the case of the +`<ref/>` element above), the *dictionaries* module appears somewhat isolated +from important structural elements like `<head/>` or `<div/>`. Indeed, computing +all the paths from either `<entry/>` or `<sense/>` elements to the latter of +length shorter or equal to 5 by a systematic traversal of the graph yields +exclusively paths (respectively 9042 and 39093 of them) containing either a +`<floatingText/>` or an `<app/>` element. The first one, as its name aptly +suggests, is used to encode text that doesn't quite fit the regular flow of the +document, as for example in the context of an embedded narrative. Both examples +displayed in the online documentation feature a `<body/>` as direct child of +`<floatingText/>`, neatly separating its content as independent. The purpose of +the second one, although its name — short for apparatus — is less clear, is to +wrap together several versions of the same excerpts, for instance when there are +several possible readings of an unclear group of words in a manuscript, or when +the encoder is trying to compile a single version of a piece of work from +several sources which disagree over some passage. In both case, it appears +obvious that it is not something that is expected to occur naturally in the +course of an article in the general case. Thus, despite a rather dense internal connectivity, the *dictionaries* module fails to provide encoders with a device to represent recursively nesting @@ -381,12 +392,12 @@ attribute. In addition, each line within the article must start with a `<lb/>` to mark its begining including before the `<head/>` element, which, although a surprising setup, underlines the fact that in the dense layout of encyclopedias, the -carriage return separating two articles is meaningful. Stating each new line -explicitly also keeps enough information to reconstruct a faithful facsimile but -it also has the advantage of highlighting the fact than even though the -definition is cut from the headword by being in a separate XML element, they -still occur on the same line, which is a typographic choice usually made both in -encyclopedias and dictionaries where space is at a premium. +carriage return separating two articles is meaningful. Stating each new line +explicitly keeps enough information to reconstruct a faithful facsimile but it +also has the advantage of highlighting the fact than even though the definition +is cut from the headword by being in a separate XML element, they still occur on +the same line, which is a typographic choice usually made both in encyclopedias +and dictionaries where space is at a premium. Finally, the various sections and sub-sections occurring within the article body may be nested as usual with `<div/>` and sub-`<div/>`s, filled with `<p/>` for -- GitLab