The <head>
of a class-1 file
is much like that of other formats, with some extra options.
In the key declarations area (see the section called “Key Declarations”), class-1
files may allow <n-alias>
.
See the section called “One Reference System” for context on how to use this
element.
In the section devoted to links to other digital resources (see the section called “Networked Files”), class-1 files allow several extra types of files.
One <model>
is allowed, to
point to another class-1 file that has the model reference system. The model should
be the same work. It may be in a different language, or come from a different
source/scriptum. During verbose validation, any differences between a class-1 file
and its model will be presented as warnings, since small differences are nearly
always inevitable.
Zero or more <redivision>
s are allowed, to point to an alternative
transcription that follows a different reference system. A class-1 file and any
redivisions must have identical text in the <body>
, and draw from the same version of the same
source/scriptum. <redivision>
is an important alternative to the knotty,
longstanding problem that besets texts that admit multiple reference systems. In a
traditional TEI file, one must adopt a primary reference system, and add other
reference systems through milestone-like anchors. This can result in transcriptions
that are difficult to read. TEI anchors do not have the semantic underpinnings needed
to cycle through the milestones from one primary reference system from one to
another. TAN's design principles call for simplicity and disaggregation, hence the
stand-off annotation model. So the ideal TAN approach is to encode same transcription
in multiple files, one per reference system, linked through <redivision>
. This may appear
to contradict another principle, that one should not repeat themselves. But that is
the easier principle to repair. During verbose validation, <redivision>
transcriptions
will be checked against the host, and specific areas that differ will be flagged.
Should users wish, a Schematron Quick Fix will provide an automatic update of a text
to a <redivision>
,
without changing the reference structure.
Zero or more <annotation>
s point to class-2 files that use the file as a
<source>
. This type of
linked resource is helpful for keeping track of key alignments and
annotations.
Zero or more <companion-version>
s point to different versions of the
same work in the same scriptum. This feature is useful for correlating multiple
versions of a work that appear in a single scriptum, e.g., the original text and a
facing translation in a bilingual edition.
The adjustment section of the <head>
(see the section called “Adjustments”) allows zero or
more <normalization>
s
and <replace>
. See the section called “Normalizing Transcriptions”.