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 provides a model for the reference system that has
been adopted. 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. Each one points to an alternative
transcription that restructures the same transcription in according to a different
reference system. A class-1 file and any redivisions must have identical text in the
<body>
. <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. TEI anchors
do not have the semantic underpinnings needed to cycle through the milestones from
one primary reference system from one to another. The TAN alternative 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, a file's text
will be checked against every <redivision>
, and specific areas that differ will be
flagged. Should users wish, a Schematron Quick Fix will allow a user to synchronize a
local file against a redivided version.
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”.