Complete description of the *dictionaries* module

ICHLL_Brenon.md

@@ -241,7 +241,7 @@ represent features such as
 
 All these are examples and by no means an exhaustive list; the complete set
 provides the encoder with a toolbox to describe all the information related to
-the form the entry is found at and seem general enough to accomodate the
+the form the entry is found at and seems general enough to accomodate the
 structure of any book indexing entries by words.
 
 ### Cross-references
@@ -252,10 +252,29 @@ the reader to the related concept. This is known as cross-references and can
 appear either when the definition of a term is adjacent to another one or to
 catch alternative spellings where some readers might expect the word to appear
 and redirect them to the form chosen as the reference. In XML-TEI, this is done
-with the `<xr/>` element.
+with the `<xr/>` element. It usually contains the whole phrase performing the
+redirection, with an imperative locution like "please see […]".
+
+The "active" part of the cross-reference, that is the very word within the
+`<xr/>` that is considered to be the link or, to make a modern-day HTML
+metaphor, the region that would be clickable, is represented by a `<ref/>`
+element. Though it is not specific to the *dictionaries* module, we include it
+in this description of the toolbox because it is particularly useful in the
+context of dictionaries. This element may have a target attribute which points
+to the other resource to be accessed by the interested reader.
 
 ### Content
 
+The remaining part of entries is also usually the largest and represents the
+content associated to the headword by the entry. In a dictionary, that is its
+meaning.
+
+The `<sense/>` element is a valid child for `<entry/>` and groups together a
+definition of the term with `<def/>`, usage examples with `<usg/>` and other
+high-level information such as translations in other languages. Both `<def/>`
+and `<usg/>` elements may appear directly under the `<entry/>`.
+
+### Remarks about structure
 
 # A new standard ?
 
@@ -265,19 +284,22 @@ are not covered by the *dictionaries* module presented above. We hence conclude
 that this module is not able to encode arbitrary encyclopedic content and
 propose a new encoding scheme.
 
-## Nested structures
+## Idiosynchrasies of encyclopedias
+
+### The notion of meaning
 
-### Example
+### Nested structures
 
 ### Candidates in the *dictionaries* module
 
 - `<sense/>`
 - `<entryFree/>`
 - `<note/>`
+- `<dictScrap/>` / `<floatingText/>`
 
 ## Encoding within the *core* module
 
-The above remark explains why the *dictionary* module by itself is unable to
+The above remarks explain why the *dictionary* module by itself is unable to
 represent encyclopedias, where discourse with nested structures of arbitrary
 depth can occur. Since the *core* module of course accomodates these structures
 by means of the `<div/>`, `<head/>` and `<p/>` elements, we devise an encoding