Person records should use tei:gender rather than tei:sex, and use `@ana` with Syriaca keyword rather than `@value` with string

[wlpotter]

Person records should use tei:gender in place of tei:sex.

Additionally, the value for the gender should be specified using @ana with a Syriaca keyword URI rather than @value with a string, e.g.:

replace <sex source="#bib3183-1" value="M">male</sex> with <gender source="#bib3183-1" ana="http://syriaca.org/keyword/male">male</gender>

[wlpotter]

Proposal for the CSV here:

• CSV column must change from, e.g. sexN to gender.N (can be sourced, etc. with sexN.sourceUri and so forth)
• Field value for this column must be a Syriaca keyword URI that has a skos:broader of http://syriaca.org/keyword/gender (or maybe just a subset?). Current values include:
  • female
  • feminine
  • male
  • masculine
  • sexuality
  • women
• The URI will be added to the @ana attribute and the text node will derive from the keyword URI, e.g. 'male' rather than 'http://syriaca.org/keyword/male'

[wlpotter]

Updated this in the transform. I decided to leave how tei:sex is handled as-is, for backwards compatibility