|
48 | 48 | "outputs": [], |
49 | 49 | "source": [ |
50 | 50 | "from tf.app import use\n", |
51 | | - "from tf.core.helpers import project\n", |
52 | 51 | "\n", |
53 | | - "from util import getTfVerses, getShebanqData, compareResults, MQL_RESULTS" |
| 52 | + "from util import getTfVerses, getShebanqData, compareResults, MQL_RESULTS\n" |
54 | 53 | ] |
55 | 54 | }, |
56 | 55 | { |
|
628 | 627 | } |
629 | 628 | ], |
630 | 629 | "source": [ |
631 | | - "VERSION = '2017'\n", |
| 630 | + "VERSION = \"2017\"\n", |
632 | 631 | "# A = use('bhsa', hoist=globals(), version=VERSION)\n", |
633 | | - "A = use('bhsa:clone', checkout=\"clone\", hoist=globals(), version=VERSION)" |
| 632 | + "A = use(\"bhsa:clone\", checkout=\"clone\", hoist=globals(), version=VERSION)" |
634 | 633 | ] |
635 | 634 | }, |
636 | 635 | { |
|
799 | 798 | "\n", |
800 | 799 | "is *not* matched by words 116853 and **116854**, because 116854 is not part of the embedding clause.\n", |
801 | 800 | "\n", |
802 | | - "The Text-Fabric notion of adjacency is more crude. \n", |
| 801 | + "The Text-Fabric notion of adjacency is more crude.\n", |
803 | 802 | "The reason is that in Text-Fabric, the query does not have to be a tree, where each object has a unique\n", |
804 | 803 | "immediate embedder object. There could be several embedder objects in the query, and each of the them may have different\n", |
805 | 804 | "gaps, and if we had the concept of relative adjacency, our query language would need a way to express relative to which object\n", |
|
969 | 968 | "Let's make a mental shift: what *is* the intention of the MQL query?\n", |
970 | 969 | "Here is a bit of query-exegesis, in that the query itself is the object of the exegesis.\n", |
971 | 970 | "\n", |
972 | | - "The MQL query mentions three `[word]` objects, but it puts only the first two of them in `FOCUS`. \n", |
| 971 | + "The MQL query mentions three `[word]` objects, but it puts only the first two of them in `FOCUS`.\n", |
973 | 972 | "\n", |
974 | 973 | "1. it is not interested in the actual value of the third one;\n", |
975 | 974 | "2. the third `[word]` is constrained by a very loose restriction: it can be anything, except two specific values.\n", |
976 | 975 | "\n", |
977 | 976 | "These two things point to the intended meaning of the query, namely:\n", |
978 | 977 | "\n", |
979 | | - "> find a clause with the word `FJM[`, and somewhere after that the word `L`, \n", |
| 978 | + "> find a clause with the word `FJM[`, and somewhere after that the word `L`,\n", |
980 | 979 | "which is not followed by either the word `<JN/` or the word `PNH/`.\n", |
981 | 980 | "\n", |
982 | 981 | "This differs subtly from what the query actually says:\n", |
983 | 982 | "\n", |
984 | | - "> find a clause with the word `FJM[`, and somewhere after that the word `L`, \n", |
| 983 | + "> find a clause with the word `FJM[`, and somewhere after that the word `L`,\n", |
985 | 984 | "which is followed by another word that is not `<JN/` and not `PNH/`.\n", |
986 | 985 | "\n", |
987 | 986 | "The difference is one of *quantification*.\n", |
|
1013 | 1012 | "\n", |
1014 | 1013 | "```\n", |
1015 | 1014 | "\n", |
1016 | | - "See \n", |
| 1015 | + "See\n", |
1017 | 1016 | "[Dirk Roorda: Example 2: not exist](https://shebanq.ancient-data.org/hebrew/query?version=2017&id=4467)" |
1018 | 1017 | ] |
1019 | 1018 | }, |
|
1319 | 1318 | "\n", |
1320 | 1319 | "We tried to improve the MQL query by using `NOTEXIST`, but that did not work out.\n", |
1321 | 1320 | "\n", |
1322 | | - "However, the TF query might include (contrived) cases that the MQL query would rightfully skip. \n", |
| 1321 | + "However, the TF query might include (contrived) cases that the MQL query would rightfully skip.\n", |
1323 | 1322 | "We can verify whether those cases actually exist by running a separate TF query, and it turns out they do not exist.\n", |
1324 | 1323 | "\n", |
1325 | 1324 | "**Lesson**\n", |
1326 | 1325 | "\n", |
1327 | 1326 | "Whenever an exegesis hinges on the results of a query, check and double check.\n", |
1328 | 1327 | "You probably will have to run multiple queries in SHEBANQ and combine the results.\n", |
1329 | 1328 | "This will quickly get very cumbersome.\n", |
1330 | | - "If that happens, it starts to pay off to use Text-Fabric, where you have more complete power over \n", |
| 1329 | + "If that happens, it starts to pay off to use Text-Fabric, where you have more complete power over\n", |
1331 | 1330 | "the computations and their results." |
1332 | 1331 | ] |
1333 | 1332 | } |
|
0 commit comments