Encoding Positions and Items - Revision history

Gerrit bruening: /* Open problem: a position is cleared: “” */

2011-10-22T16:49:17Z

‎Open problem: a position is cleared: “<code><clear/></code>”

2011-08-23T09:11:06Z

‎Starting point

2011-08-23T08:58:21Z

‎Two or more items concur to occupy one position: A simple case (solved)

2011-03-31T16:25:13Z

‎Starting point

2011-03-31T16:23:15Z

‎A combined example

2011-03-31T16:21:47Z

‎An item is questioned

2011-03-31T16:18:35Z

‎Accepted Proposals

2011-03-31T16:18:02Z

‎Proposed Alterations

2011-03-31T16:16:38Z

‎Open problem: a position is cleared: “<code><clear/></code>”

2011-03-31T16:15:09Z

‎Considered alterations

@@ Line 63: / Line 63: @@
 </pre>
-==Open problem: a position is cleared: “<code><clear/></code>”==
+==A position is cleared (solved)==
 In the following example a wording of a verse line is dismissed whereas the position is left intact, because it is part of a stanza pattern:
@@ Line 70: / Line 70: @@
 In other words: The item would have to be substituted, but is not.
-We may be inclined to use <code><del/></code>, because we are rightly used to interprete (and with good reason) a strikeout as a deletion. However:
+We may be inclined to use a mere <code><del/></code>, because we are rightly used to interprete (and with good reason) a strikeout as a deletion. However:
 #<code><del/></code> would be interpreted as a deletion of a position.
 #In fact, as we said above, the position is left intact.
-Therefore, we propose a new '''non-empty''' element, e.g. “<code><clear/></code>” (with an <code><del/></code>-like syntax but a different semantic) that would be applied in the following way: “<code><l><clear>Bl<orig>u</orig>hen <gap/>t das Jar</clear></l></code>”.
+The fact that a wording is dismissed but an unoccupied position remains should be recorded with <code><subst/></code> and <code><add><space/></add></code>.
 ==Open problem: alterations that keep items in suspense==

@@ Line 129: / Line 129: @@
 [[Image:screenshot_sig.jpg|500px]]
-In this way of encoding, <code><alt/></code> is supposed to indicate that both items eventually concur to occupy one and the same position. <code><add/></code> is supposed to record the authorial intervention. Both is expressed by means of '''elements''', not '''attributes'''.
+In this way of encoding, <code><alt/></code> is supposed to indicate that both items eventually compete to occupy one and the same position. <code><add/></code> is supposed to record the authorial intervention. Both is expressed by means of '''elements''', not '''attributes'''.
 We met two problems in this proposal:

@@ Line 12: / Line 12: @@
 The distinction can also be applied to the usage of markup which records alterations of the text. <code><add/></code> and <code><del/></code> record an addition or deletion of an '''item''' (for example a word), and (coming along with that) an addition or deletion of a specific '''position'''. In contrast <code><subst/></code> indicates that one item replaces the other, the position itself remaining unaffected. Whether or not alterations effect the sequence of positions is not explicit in the definitions of the P5 “Guidelines”. However, in the given examples the mere additions and deletions are to be interpreted as accompanied by the emergence or disappearance of the respective position, whereas this does not apply to <code><subst/></code>.
-==Two or more items concur to occupy one position: A simple case (solved)==
+==Two or more items compete to occupy one position: A simple case (solved)==
-Sometimes two or more items concur to occupy one and the same position, as in the present case, where one verse line is followed by seven attempts to the following verse line of which you can see only the first two ones:
+Sometimes two or more items compete to occupy one and the same position, as in the present case, where one verse line is followed by seven attempts to the following verse line of which you can see only the first two ones:
 [[Image:alt.jpg|600px]]

@@ Line 127: / Line 127: @@
 With regard to the considered alterations, a proposal has been made in the “Encoding Model for Genetic Editions” (c. “[http://www.tei-c.org/Activities/Council/Working/tcw19.html#index.xml-body.1_div.3_div.2_div.4 3.2.4 Alternative Readings]”). Applied to the above mentioned example, the textual encoding would look like this:
-[[Datei:screenshot_sig.jpg|500px]]
+[[Image:screenshot_sig.jpg|500px]]
 In this way of encoding, <code><alt/></code> is supposed to indicate that both items eventually concur to occupy one and the same position. <code><add/></code> is supposed to record the authorial intervention. Both is expressed by means of '''elements''', not '''attributes'''.

@@ Line 110: / Line 110: @@
 ===A combined example===
-[[Datei:combined.jpg|500px]]
+[[Image:combined.jpg|500px]]
 In this case the three last phaenomena appear together:

@@ Line 102: / Line 102: @@
 Passages may be marked for the purpose of a prospective deletion or substitution:
-[[Datei:question.jpg|500px]]
+[[Image:question.jpg|500px]]
 In this case, the original “Und” now is inappropriate as a result of the addition of two verse lines in pencil of which the first one begins with “Und”, too.

@@ Line 89: / Line 89: @@
 Another person, e.g. one of the author’s consultants, proposes an alteration:
-[[Datei:391098_0086_painted.jpg|600px]]
+[[Image:391098_0086_painted.jpg|600px]]
 The consultant prefers “Gespenst” (ghost) to the mere repetition of “Gespinst” (figment) in “Gespinst-Gespinnsten”.

@@ Line 66: / Line 66: @@
 In the following example a wording of a verse line is dismissed whereas the position is left intact, because it is part of a stanza pattern:
-[[Datei:clear.jpg|350px]]
+[[Image:clear.jpg|350px]]
 In other words: The item would have to be substituted, but is not.

@@ Line 82: / Line 82: @@
 An alteration is considered by the author, but not carried out:
-[[Datei:391098_0081a.jpg|550px]]
+[[Image:391098_0081a.jpg|550px]]
 Apparently, the author was not decisive about who is speaking: The “Schatzmeister“ (treasurer) or “Marschalk” (constable)?.