If you consider the TEI document to be a new edition of an existing text though, and I think that's how TEI docs normally identify themselves, then adding new appendices should be no big deal. Best practice would be to indicate in the header that these are new in the TEI edition, but I think it's fine to put them in a <back> element. Maybe we can distill some best practice as to when you might do one or the other?
On Aug 16, 2011, at 11:46AM, James Cummings wrote:
> Like Torsten I've always felt nervous about putting these in <back> because they are not actual appendices to the text I'm transcribing (ok, I recognise this distinction may not exist for born digital documents, where they might be considered appendices). So I instead have convinced myself that they are supplementary information I use to describe the source, and thus put them in sourceDesc where they are conveniently allowed. I'm not arguing that is correct, just describing what I've done in the past. I have also, of course, just stored them separately and pointed *to* them as separate files, not feeling any need to suck them all in (virtually or otherwise) into a single file.
> My two pence,
> On 16/08/11 16:13, Martin Holmes wrote:
>> HI Gabby,
>> Typically I keep these in external files. When querying an XML database
>> to get back a single TEI file, though, I'll often import all the
>> <person> or<place> elements which are linked from that particular file,
>> and place them in<back>, so I have a single internally-coherent XML
>> structure for processing with XSLT. I have also put them in the
>> <teiHeader>, though.
>> On 11-08-16 06:42 AM, Gabriel Bodard wrote:
>>> A question for the community about usage:
>>> Where do you (in your own local usage) place, within a TEI document, a
>>> prosopography (listPerson) that is neither a castList nor a participants
>>> description (particDesc), nor a list of scribes in the manuscript etc.;
>>> or a gazetteer (listPlace) that is not a setting description for your
>>> document; or a listNym, listOrg, listEvent? In other words, if the list*
>>> is serving as a vocabulary or external table to your digital corpus,
>>> rather than a manuscript description or catalogue metadata.
>>> My instinct is that such a list doesn't belong in the teiHeader, but
>>> perhaps in the tei:body or tei:back of a text, depending on the
>>> structure of the edition being created.
>>> What have others chosen to do?
> Dr James Cummings, InfoDev,
> Computing Services, University of Oxford