I'd echo what Syd has said and add that these specialised list-like
components are equally at home in a textual context as a metadata one.
The reason is that you might find a list of these in a text and want to
encode them as you find them.
For example, the bibliography at the end of a work and transcribe it as
back matter with listBibl. Similarly you might be transcribing a
gazetteer of places, or a copy of who's who, or a chronicle of events.
Where it goes in the document depends entirely on whether it is
additional textual material for the digital edition (perhaps as back
material as Syd suggests), the primary text being transcribed, or
metadata about the text.
On 15/08/10 22:50, Syd Bauman wrote:
> Doug --
> <listEvent> is a member of model.listLike, which in turn is a
> member of model.inter. Thus<listEvent> can appear anywhere other
> inter-level elements can, e.g. inside<p> or between two<p>s in a
> Personally, I tend put my contextual lists like<listBibl>,
> <listEvent>,<listPerson>, and<listPlace> inside a<div
> type="editorial"> in the<back>.
>> James Cummings recently pointed out via Twitter the listEvent tag
>> which seems appropriate for some work I am doing for the Library of
>> Congress which requires a set of events with dates and descriptions
>> which then point to a set of METS files. The examples in the P5
>> docs seems isomorphic to what I need, but as far as I can tell,
>> listEvent can only appear in the teiHeader. Is this a correct
>> assumption? If it is, then does it seem strange to have a teiHeader
>> with no text at all? Should I even be using TEI at that point?