This is intriguing. I'd never thought of this sort of use-case for
<facsimile> before, but it looks quite convincing to me. If we don't
allow <facsimile> as a child of <teiCorpus>, you'll be reduced to some
strategy such as making the cemetary a sibling <TEI> object with the
gravestones, which clearly misrepresents the relationship between them.
I would vote for allowing it.
On 11-01-23 07:03 AM, Sebastian Rahtz wrote:
> I was slightly surprised to find that we have not allowed<facsimile> as a child of<teiCorpus>,
> and I am wondering whether I am the only person who wants it.
> I have records of gravestones which I manage as a set of<TEI> objects,
> each with a header containing a and<msDesc> and a<listPerson>,
> and a<text> with transcription. All these are combined in a master
> <teiCorpus> with its own header containing taxonomies and so on.
> However, I also have a digitized cemetery plan which I want to
> manage as a<facsimile> under<teiCorpus>
> a) am I doing this wrong, OR
> b) should<facsimile> be allowed inside<teiCorpus>
> Sebastian Rahtz
> Information and Support Group Manager, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
> Sólo le pido a Dios
> que el futuro no me sea indiferente