From 4862aae2d36dba9dae27fc79f4405d68a7fba10c Mon Sep 17 00:00:00 2001
From: Alice BRENON <alice.brenon@ens-lyon.fr>
Date: Sun, 27 Feb 2022 17:32:52 +0100
Subject: [PATCH] Actually, interp doesn't do the job, will have to fix the
 proposal

---
 ICHLL_Brenon.md | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/ICHLL_Brenon.md b/ICHLL_Brenon.md
index a14a010..bbc904a 100644
--- a/ICHLL_Brenon.md
+++ b/ICHLL_Brenon.md
@@ -383,9 +383,18 @@ points the reader to the correct place in this mind map.
 The situation regarding subject indicators is hardly better outside of the
 module. The `<domain/>` element despite its name belongs exclusively in the
 header of a document and focuses on the social context of the text, not on the
-knowledge area it covers. The `<interp/>` and `<span/>` elements look like good
-candidates in that . This point, although not the most concerning, still remains
-the hardest to address.
+knowledge area it covers. The `<interp/>` despite its name is not so much about
+labeling something as an interpretation to give to a context (which subject
+indicators could be if you consider that, placed at the begining, they are used
+to orient the mind frame of the readers towards a particular subject). However,
+the documentation clearly demonstrates it as a tool for annotators of a
+document, which text content is not part of the original document but some
+additional result of an analysis performed in the context of the encoding, used
+only throughout references in XML attributes.
+
+This point, although not the most concerning, still remains the hardest to
+address but all things considered the `<usg/>` element stands out as the most
+relevant.
 
 ### The notion of meaning
 
-- 
GitLab