Creagh Cole writes:
> This has perhaps been worked through in this forum before now, if so I'm
> sorry . . . I am working on a database of works by many different
> authors and would like to identify gender of authors so that searches
> may be restricted, say, to female poets/novelists etc. I'm not sure how
> to do this with the teilite dtd. ie no particular gender attribute for
> authors. I can think of some fairly arbitrary ways around this at the
> processing stage, but perhaps some more elegant solutions have been
> worked out. Can someone advise me on this?
There's an ANA attribute which I think is for analytic information
(I'm not in the same location as my Green Book right now), and it's
declared as IDREFS which means you can put multiple IDs in there, each
pointing to a different place (presumably in the TEIHEADER) where you
define what the values are for or how they are categorised (not that
you need to explain gender but SGML doesn't know this):
<!DOCTYPE TEI.2 PUBLIC "-//TEI//DTD TEI Lite 1.0//EN">
<AUTHOR ana="femal poet">Bar</AUTHOR>
<tagusage id="female" rend="gender" gi="author">Women</tagusage>
<tagusage id="male" rend="gender" gi="author">Men</tagusage>
<tagusage id="poet" rend="occupation" gi="author">Poets</tagusage>
<tagusage id="playwright" rend="occupation"
<tagusage id="sculptor" rend="occupation"
Where it stumbles is that there's no place to define the namespace,
so genders and occupations are jumbled in together: I've abused REND
in the example to provide a namespace. This way you not only get the
safety of an ID/IDREF check, but processing software can (as you
suggest) take action on the attributes.
The problem is that everyone wants something different. I'd be
inclined to go for the full TEI and use its facilities for modifying
element type name and attribute names to fit it to the task, rather
than use up (abuse up?) attributes which could validly be needed for
other purposes (id=female rend=pink...id=male rend=blue :-)