> * Just off the top of my head, the idea of using <respStmt> in <bibl>
> makes a lot of sense, but it seems awfully odd to put it in the
> <head>: was that intentional? (I.e., is the photographer's name in
> the title or heading in the source document, or do you want it
> printed there, Conal?) Seems to me like it would be more sensibly
> placed in a <p> (if it is part of the source or intended for print)
> or <figDesc> (if not).
See 22.3 of the Guidelines.
<head> in <figure> offers the encoder the possibility of not only
recording what has been transcribed but also supplying additional
information as appropriate. And yes it is more of a title than a header,
so <bibl> or <name> elements may not belong here.
<p> in <figure>
Seems to be limited to information transcribed.
<figDesc> in <figure>
Seems to be limited to information supplied. But it may or not be in the
source since the Guidelines at this point reference the possibility of
authoring directly in electonic form.
In documents created in electronic form with the needs of
print-handicapped readers in mind, the <figDesc> element may be provided
by the author rather than a subsequent encoder.
Whether or not the information about the figure, for example the photo
credit, is to be found in the source being transcribed or is supplied by
the author/encoder, it might be appropriate as per the Guidelines to place
such information in a <text> element nested in the <figure> element.
And so our working example:
<!-- elements recording photo credit -->
<!-- could be bibl -->
<head> ... </head>
Although it looks rather verbose, it is probably a more suitable fashion
to capture information relating to the figure -- or parts of the figure
as the discussion of call outs and pointers in 22.3 indicates.
On <bibl> versus other ways of linking names, persons and objects...
For more complex applications, such as onomastics, or wherever a detailed
analysis of the component parts of a name is needed, the specialized
elements described in chapter 20 Names and Dates or the analytical tools
described in chapter 16 Feature Structures should be used.
<cit>TEI Guidelines 6.4 "Names, Numbers, Dates, Abbreviations, and
Francois Lachance, Scholar-at-large
2005 Year of Comparative Connections. DIA: Comparative connections? LOGZ:
Connection, first. Comparison, next. DIA: Check. Comparable ways of
connecting. LOGZ: Selection outcomes, first. Comparative Connections,