#460 Use of geogFeat in transcription?
I'm slightly confused by the description and model of the <geogFeat> element. It is described as an element to tag the term for a geographical feature within a <geogName>. The latter element is often used in transcription, e.g. to tag a river named in the primary text, and its content model is therefore macro.phraseSeq, as such names may be abbreviated, damaged, corrected, regularized, contain words and other names, etc.
It would seem natural--and I have a colleague who would like--to be able to tag the term for the geaographical feature in the transcribed text as well, for example:
<geogName>ἡ τοῦ Σκαμάνδρου <geogFeat>πηγή</geogFeat></geogName>
(i.e. The <geogFeat>source</geogFeat> of the (River) Skamander)
But the content model of <geogFeat> is only macro.xtext (i.e. text and <g>), so if there is any editorial intervention or description inside this word, is cannot be tagged.
Is this a corrigible error (that is, make <geogFeat>'s content match up with <geogName> etc.), or do people think that this element is only for use in the <teiHeader>, and should never be used in transcription? If the latter, then we should make this explicitly clear in the element spec, because currently users have no way to know they should not use this element in a tagged transcription of the primary text.
The reason that
<geogFeat>is macro.xtext rather than macro.phraseSeq is probably that it was expected it would only ever contain a single word or some such; nothing to do with whether it appears in the header or elsewhere -- by definition, as a component of<geogName> it can appear anywhere. But I agree that it would be better to make its content model consistent with other components of<geogName>. How do you feel about<offset>? Presumably the same argument should apply there?Yes, that seems completely right to me. Even more so in the case of
<offset>in fact. At the very least, you might want to tag and lemmatize the words in both of these strings (both of which can contain multiple words, right?).Last edit: BODARD Gabriel 2013-06-19
There seems to be consensus to implement this? Seems reasonable to me. Assigning to me and changing to Green unless Council argues otherwise.
Council approves, and sets a deadline of 20 minutes for JC to implement.
At Oxford 2013-11 face-to-face Council approves and sets a deadline of 'before next teleconference'. (not 20 minutes!)
Closed and fixed. geogFeat was already done but offset wasn't, so implemented that on the same principle. Done in [r12993].
Related
Commit: [r12993]