As noted in the previous section, it is ideal to group your TAN files through subdirectories in a master library. Those collections should contain files that cohere in some way, but this could be for any number of reasons. TAN is designed to encourage cross-linguistic and intertextual research, so what might hold various TAN files together is unpredictable.
In a given project, you are likely to repeat basic information, particularly
<agent>
, <role>
, and <work>
. such as elements with the
the section called “IRI + name Pattern”, consider moving those to a TAN-key file.
It is almost always preferable to develop TAN-keys before resorting to <inclusion>
s. Sorting out lines of
inclusion can be confusing.