Skip to end of metadata
Go to start of metadata

5/21/2012 --- Small items that will require pre-processing:

  1. "Gamonyms" (individuals who are identified by virtue of being spouse [primarily husband] of primary role-person; as processing now happens, they get treated as nested within the primary person's id):
    • Akkadian syntax: PN DUMU.MUNUS sza2 FN A LN DAM PN2 DUMU sza2 FN2 A LN2
    • to be read as: PN, daughter of FN, descendant of LN, (who is) wife of PN2, son of FN2, descendant of LN2
    • Examples (searched in TEI of 4-26-2012, not necessarily complete) found in: P296678, P296682 (in witness list?), P296683, P296684, P296686, P296690, P29670, P296719, P296721, P296760, P342212, P342220, P342226, P342228, P342239, P342240, P342241, P342265, P342280, P342282, P342286, P342287, P342297, P342302, P342326, P342339, P342341, P342343, P342344, P342349, P342350, P342352, P342354, P342365, P342375, P342385, P342389, P342391, P342403, P342410, P342420, P342422, P342435, P342442, P342445, P342449, P342460, P342464, P342466, P342467, P342476, P342477, P342478, P342481, P342486, P342496, P342497, P342500, P342505, P382239, P388065, P296678, P296682, P296683, P296684, P296686, P296690, P296704, P296719, P296721, P296760, P342212, P342220,   P342226,
      • clan name optional?: as of 5/20/2012, LEP has not double-checked this
  2. Scribes:
    • the Akkadian reads: PN {lu2}UMBISAG DUMU sza2 FN A LN
      • to be understood as: PN, scribe, son of FN, descendant of LN
        • variants: the FN may be followed by another professional designation (which would be indicated in the lemmatization but which is not currently marked for role in any unique way). If the designation {lu2}UMBISAG following the PN of the scribe is used (singly, or in combination with the @colophon discourse marker, should this be problematic?
      • the text the human looks for is the {lu2}UMBISAG designation, and the appearance of this PN in the last row or two of text prior to the @sealings discourse marker. ATF is currently marked with @colophon discourse marker before the text line containing the scribe's PN
  3. Kings:
    • Royal Names (RN) appear in two places in HBTIN texts:
      • in the date formula, which is in the @colophon section of the text. (there are a couple of instances where the date formula also appears at the very beginning of the text, but I know of no instances where the RN there differs from the one in the date formula)
      • as a descriptor of the staters (monetary measure) in the price of the transaction. This is in the "principals" section of the text. The RN in this section could, in theory, be that of the ruler previous to the one in the date section. In either case, the staters RN, could continue to be identified as a role, but it is a very specific one. (Opportunity to begin to refine role-marking?).
      • List of RNs attested in the corpus: [orthographies can be pulled from the qpn.glo when restored] (need to double-check qpn.glo when Oracc back on line for any RNs forgotten--will only be 1-3 names, at most).
        • Seleucus
        • Antiochus
        • Demetrios
        • Alexander
  4. Witnesses:
    • Discourse marker: @witnesses
      • all names following that have been treated as witnesses, producing 2 kinds of false witnesses (not commenting on the validity of their "testimony")
      • scribes: the @colophon section follows the @witnesses section
      • principals: all PNs on the right edge of the tablet are principals (buyers, sellers, guarantors)
        • the edges are introduced with discourse marker @sealings and then each edge is introduced by @top, @bottom, @left, @right. Each of these should be indicated even if broken.
        • a "special" designation occurs when the mother of a minor child represents him: ina aszabi PN (where PN is the mother's name). This appears in the @witnesses section. The matronym is really an attribute of the minor child.
  5. Neighbors:
    • appear in descriptions of property adjacent to that which is object of transaction
      • are not participating in the transaction itself
      • should be identifiable in the Akkadian property description (item for LEP follow-up to pull enough instances to extract consistent text for mark-up)
  • No labels