User talk:Dmsmith/KJV 2.6 - Revision history

David Haslam: /* Revision History */ 2.10.2

2023-05-04T10:32:03Z

‎Revision History: 2.10.2

David Haslam: /* fine grain operators */ reply

2016-01-25T14:14:44Z

‎fine grain operators: reply

David Haslam: /* fine grain operators */ reduced indents

2016-01-25T14:11:34Z

‎fine grain operators: reduced indents

David Haslam: /* Related discussion */ ==== fine grain operators ====

2016-01-25T14:10:34Z

‎Related discussion: ==== fine grain operators ====

David Haslam: /* catchWord osisRef */ === Related discussion ===

2016-01-25T14:09:34Z

‎catchWord osisRef: === Related discussion ===

Dmsmith: /* Auhoritative reference text for red letter markup */

2016-01-25T13:49:05Z

‎Auhoritative reference text for red letter markup

David Haslam: /* catchWord osisRef */ updated stats after further changes

2016-01-25T12:16:42Z

‎catchWord osisRef: updated stats after further changes

Dmsmith: /* catchWord osisRef */ time for invention?

2016-01-24T18:58:23Z

‎catchWord osisRef: time for invention?

David Haslam: /* catchWord osisRef */ ::The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operat

2016-01-24T17:42:25Z

‎catchWord osisRef: ::The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operat

Dmsmith: /* catchWord osisRef */

2016-01-24T14:48:25Z

‎catchWord osisRef

@@ Line 18: / Line 18: @@
 ! width="10%"|Date
 ! width="85%"|Description
 |-
 | 2.9

← Older revision		Revision as of 14:14, 25 January 2016
Line 163:		Line 163:
	:The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam\|David Haslam]] 10:42, 24 January 2016 (MST)		:The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam\|David Haslam]] 10:42, 24 January 2016 (MST)
	:: I think it should be easy to understand that a range is anchored at the start and follows to the end. I'd argue that the @s[a]-@s[b] implies that a and b do not reoccur in the range. Maybe it is lacking a secondary subscript as in @s[a] means the first occurrence, also @s[a][1] means the first occurrence, but @s[a][3] means the third occurrence. Since OSIS is targeted to commentaries as well as Bibles, it should be expected that text referenced by an osisID is large. OSIS has another operator that gives the counted position of the match. I think it counts code points though. IIRC: cp(n). It'd be better to have one that counted words, e.g. wc(n). The further complication is that @s[asdf] might be a substring match rather than a whole word match. --[[User:Dmsmith\|Dmsmith]] 11:58, 24 January 2016 (MST)		:: I think it should be easy to understand that a range is anchored at the start and follows to the end. I'd argue that the @s[a]-@s[b] implies that a and b do not reoccur in the range. Maybe it is lacking a secondary subscript as in @s[a] means the first occurrence, also @s[a][1] means the first occurrence, but @s[a][3] means the third occurrence. Since OSIS is targeted to commentaries as well as Bibles, it should be expected that text referenced by an osisID is large. OSIS has another operator that gives the counted position of the match. I think it counts code points though. IIRC: cp(n). It'd be better to have one that counted words, e.g. wc(n). The further complication is that @s[asdf] might be a substring match rather than a whole word match. --[[User:Dmsmith\|Dmsmith]] 11:58, 24 January 2016 (MST)
		+	:::That's a good point about substrings. We need to develop a tighter specification for the '''@s[text]''' operator, but one that gives much more flexibility of use, while retaining precision for word locations. [[User:David Haslam\|David Haslam]] 07:14, 25 January 2016 (MST)

@@ Line 160: / Line 160: @@
 === Related discussion ===
 ==== fine grain operators ====
-::The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith|Dmsmith]] 07:48, 24 January 2016 (MST)
+The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith|Dmsmith]] 07:48, 24 January 2016 (MST)
-::The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam|David Haslam]] 10:42, 24 January 2016 (MST)
+:The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam|David Haslam]] 10:42, 24 January 2016 (MST)
 :: I think it should be easy to understand that a range is anchored at the start and follows to the end. I'd argue that the @s[a]-@s[b] implies that a and b do not reoccur in the range. Maybe it is lacking a secondary subscript as in @s[a] means the first occurrence, also @s[a][1] means the first occurrence, but @s[a][3] means the third occurrence. Since OSIS is targeted to commentaries as well as Bibles, it should be expected that text referenced by an osisID is large. OSIS has another operator that gives the counted position of the match. I think it counts code points though. IIRC: cp(n). It'd be better to have one that counted words, e.g. wc(n). The further complication is that @s[asdf] might be a substring match rather than a whole word match. --[[User:Dmsmith|Dmsmith]] 11:58, 24 January 2016 (MST)

@@ Line 159: / Line 159: @@
 [[User:David Haslam|David Haslam]] 05:16, 25 January 2016 (MST)
 === Related discussion ===
 ::The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith|Dmsmith]] 07:48, 24 January 2016 (MST)
 ::The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam|David Haslam]] 10:42, 24 January 2016 (MST)
 :: I think it should be easy to understand that a range is anchored at the start and follows to the end. I'd argue that the @s[a]-@s[b] implies that a and b do not reoccur in the range. Maybe it is lacking a secondary subscript as in @s[a] means the first occurrence, also @s[a][1] means the first occurrence, but @s[a][3] means the third occurrence. Since OSIS is targeted to commentaries as well as Bibles, it should be expected that text referenced by an osisID is large. OSIS has another operator that gives the counted position of the match. I think it counts code points though. IIRC: cp(n). It'd be better to have one that counted words, e.g. wc(n). The further complication is that @s[asdf] might be a substring match rather than a whole word match. --[[User:Dmsmith|Dmsmith]] 11:58, 24 January 2016 (MST)

@@ Line 158: / Line 158: @@
 [[User:David Haslam|David Haslam]] 05:16, 25 January 2016 (MST)
+=== Related discussion ===
 ::The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith|Dmsmith]] 07:48, 24 January 2016 (MST)
 ::The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam|David Haslam]] 10:42, 24 January 2016 (MST)
 :: I think it should be easy to understand that a range is anchored at the start and follows to the end. I'd argue that the @s[a]-@s[b] implies that a and b do not reoccur in the range. Maybe it is lacking a secondary subscript as in @s[a] means the first occurrence, also @s[a][1] means the first occurrence, but @s[a][3] means the third occurrence. Since OSIS is targeted to commentaries as well as Bibles, it should be expected that text referenced by an osisID is large. OSIS has another operator that gives the counted position of the match. I think it counts code points though. IIRC: cp(n). It'd be better to have one that counted words, e.g. wc(n). The further complication is that @s[asdf] might be a substring match rather than a whole word match. --[[User:Dmsmith|Dmsmith]] 11:58, 24 January 2016 (MST)

@@ Line 12: / Line 12: @@
 # words tagged as the divine name
 # extracts which include the tagged divine name
 == Revision History ==

@@ Line 153: / Line 153: @@
 * 6958 = total, of which
 * 5242 = do not contain a space
-* 5866 = now have osisRef (1 of which requires reverting)<ref><code><catchWord osisRef="Num.26.39@s[Shupham…Hupham]">Shupham…Hupham</catchWord></code></ref>
+* 5958 = now have osisRef (1 of which requires reverting)<ref><code><catchWord osisRef="Num.26.39@s[Shupham…Hupham]">Shupham…Hupham</catchWord></code></ref>
-* 1092 = are still without osisRef, of which
+* 1000 = are still without osisRef, of which
-* 0079 = are single keywords in verse 1 for Psalms with titles<ref>Currently excluded because the XML line does not start with a verse sID milestone.</ref>
+* 0000 = are keywords in verse 1 for Psalms with titles<ref>These are now included because I fixed the XML file such that these lines now start with a verse sID milestone.</ref>
 '''Notes:'''
@@ Line 164: / Line 164: @@
 ::<code><catchWord osisRef="Num.26.39@s[Shupham]-Num.26.39@s[Hupham]">Shupham…Hupham</catchWord></code>
-[[User:David Haslam|David Haslam]] 03:11, 24 January 2016 (MST)
+[[User:David Haslam|David Haslam]] 05:16, 25 January 2016 (MST)
 ::The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith|Dmsmith]] 07:48, 24 January 2016 (MST)
 ::The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam|David Haslam]] 10:42, 24 January 2016 (MST)
 :: I think it should be easy to understand that a range is anchored at the start and follows to the end. I'd argue that the @s[a]-@s[b] implies that a and b do not reoccur in the range. Maybe it is lacking a secondary subscript as in @s[a] means the first occurrence, also @s[a][1] means the first occurrence, but @s[a][3] means the third occurrence. Since OSIS is targeted to commentaries as well as Bibles, it should be expected that text referenced by an osisID is large. OSIS has another operator that gives the counted position of the match. I think it counts code points though. IIRC: cp(n). It'd be better to have one that counted words, e.g. wc(n). The further complication is that @s[asdf] might be a substring match rather than a whole word match. --[[User:Dmsmith|Dmsmith]] 11:58, 24 January 2016 (MST)

← Older revision		Revision as of 17:42, 24 January 2016
Line 167:		Line 167:

	:::The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith\|Dmsmith]] 07:48, 24 January 2016 (MST)		:::The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith\|Dmsmith]] 07:48, 24 January 2016 (MST)
		+	::The range concept could work in a lot of places, but what when the range end word is also found earlier in the verse text than the range begin word? The '''@s[word]''' operator finds only the first occurrence of the word in question. I expect there are many such examples. [[User:David Haslam\|David Haslam]] 10:42, 24 January 2016 (MST)

← Older revision		Revision as of 14:48, 24 January 2016
Line 165:		Line 165:

	[[User:David Haslam\|David Haslam]] 03:11, 24 January 2016 (MST)		[[User:David Haslam\|David Haslam]] 03:11, 24 January 2016 (MST)
		+
		+	:::The … was probably an artifact of typesetting margin notes. Limited space, resulting in truncation. I like the idea of a range. Regarding Psalm titles, you can double check the reference by dumping with mod2imp. --[[User:Dmsmith\|Dmsmith]] 07:48, 24 January 2016 (MST)