1 Redundant

This document contains only the material which needs to be added to the
current chapter 11
of the Guidelines.. You need to read that chapter as well to
follow what's going on here, and the schema generated is not quite
what it will be in the final version.

Note: insert the following material after the 22nd para in
section
11.1

If, as is more often the case, a transcription of the zone
identified in this way is to be included in the encoded TEI document, this
may be done in two ways. If the transcription is regarded as a text in
its own right, organized and structured independently of its physical
realization in the document or documents represented by the facsimile,
then the recommended practice is to use the traditional text
element, provided as a sibling of the facsimile element. This
approach is illustrated in section 1.1.1 Parallel transcription
below. Alternatively, if the transcription is intended to prioritize
representation of the process by which the document came to take its
present form over representation of the final text , it may be
preferable to use a subset of the available elements and to embed them
within the zone element, as further described in section 1.1.2 Embedded transcription below.

1.1 Combining transcription with facsimile

A digitized source document may contain nothing more than page images and a
small amount of metadata. It may also contain an encoded transcription
of the pages represented, which may either be ‘embedded’ within
the facsimile structure, or given in parallel to it.

characterizes the element in some sense, using any convenient
classification scheme or typology.

The elements surface and zone were introduced
above, . The element
patch is useful in cases where some or all of the written
surfaces are composed of physically distinct scraps. In the following
example, taken from the Walt Whitman archive, two pieces of newsprint
have been glued to a piece of blue paper on which a poem is being
drafted:

The two pieces of newsprint might perhaps be regarded as special kinds
of zone, but they are effectively new surfaces, since they might
contain additional written zones themselves (such as the numbers in
this case). The patch element may be used to represent such
‘sub-surfaces’.

Most writing is linear, in the sense that it is composed of
discrete tokens organized physically into groups, typically organized
in a sequence corresponding with the way they are intended to be
read. Depending on the directionality of the writing system used,
this might be any combination of top-down and left to right, or vice
versa. It thus seems convenient to introduce an element line to
hold a complete group of such tokens.
Where, however, the lineation is
not considered significant, any group of tokens may be
indicated using the zone element. The
seg element described in section [ID SASE in TEI Guidelines] may also be used to indicate smaller sequences of tokens
within zone, or line as appropriate.

Using these elements, the Whitman draft above might be encoded as
follows:

<surface><zone><line>Poem</line><line>As in Visions of — at</line><line>night —</line><line>All sorts of fancies running through</line><line>the head</line></zone><patch type="newsprint" binder="glue" flipping="false" height="40cm" width="90cm"><zone>Spring has just set in here, and the weather.... a steamer </zone><metamark function="sequence">2</metamark></patch><patch type="newsprint" binder="glue" flipping="false" height="35cm" width="90cm"><zone>"The shores on either side of the Sound are... The In- </zone><metamark function="sequence">3</metamark></patch></surface>

Note that in this example we have not included any graphic
element corresponding with the zone or surface
elements identified in the transcription. The encoder may choose to
complement a transcription with graphic representations of its source
at whatever level is considered effective, or not at all. Equally, the
encoder may choose to provide only graphics without transcription, or
with a structured (non-embedded) transcription, or any combination of
the three.

1.2 Transcribing the process

Note: Insert the following into the first para of section
11.2
("Scope of Transcriptions"), following the second sentence, before the
word ‘Further’. Some
readjustment of the list in that para will also be needed.

Such elements may also be used for digital
transcriptions in which the object is not to represent a finished
text, but rather to represent the creative process, as evidenced by
different ‘layers’ or ‘traces’ of writing in one or more
documents. Transcriptions of this kind are closely focussed on the physical
appearance of specific documents, needing to distinguish the traces of
different writing activities on them, such as additions,
and deletions but also other indications of how the writing is to be
read, such as indications of transposition, re-affirmation of writing
which has been deleted, and so on. Such distinctions are considered of
particular importance when dealing with authorial manuscripts, but are
also relevant in the case of historical sources such as charters or
other legal documents.

The remainder of this chapter describes a model for encoding such
transcriptions, in which elements such as mod, del,
etc are used to mark writing traces and their functions within the
document. Each such element can be assigned to one or more
editorially-defined modification groups, termed a change,
by means of a global change attribute, which references a
definition for the set of changes concerned, typically provided within the TEI
Header creation element; see further 1.4 Changes. The transcription itself may be embedded within
the elements surface and zone described in section
1 Redundant, or provided in parallel within a text
element. Within a zone, the transcription may be organized
topographically in terms of lines of writing, using the line
element, or in terms of further nested zones, or as a combination of the two; see further 1.1.2 Embedded transcription.

1.3 Marking up the writing process

Modifications of various kinds (correction, addition, deletion,
etc.) are frequently found within a single document, and may also
be inferred when different documents are compared, although it may be
an open question as to whether inter-document discrepancies should be regarded in the same way as intra-document
alterations. When two witnesses are collated, we may observe that a
word present in one is missing from the other: this does not necessarily
imply that the word was added to the first witness, nor that it
was deleted from the other.

In this section we discuss a number of elements which may be used to
record traces of the writing process within a document.

1.3.1 Generic modification

mod represents any kind of modification identified within a single document.

rend

(rendition) indicates how the element in question was rendered or presented in the source text.

type

characterizes the element in some sense, using any convenient
classification scheme or typology.

spanTo

indicates the end of a span initiated by the element
bearing this attribute.

Most, if not all, transcriptional elements imply a certain level
of semantic interpretation. For instance, using the add
element to encode a word or phrase that occupies interlinear space
involves a decision that it has been deliberately inserted as an
addition rather than an alternative, and indeed a judgment that it
was written after, rather than before, the other lines. Where it is
felt desirable to keep the recording of ‘what is on the
page’ entirely separate from ‘what is the
editor’s interpretation’, the generic mod
element may be preferred. This element simply indicates any kind of
modification that has been identified in the document, without
prejudice as to its function. Occurrences of the mod
element may be categorised by means of their type
attribute, and visual aspects of their appearance can be described
by means of the rend attribute, but they provide no
further interpretation of the function or intention of the passage
so marked up. The spanTo attribute may be used to indicate the end
of a modified passage if this extends across the boundaries of some
other XML element, for example from the middle of one line tagged
as a line to the middle of another line some
distance further on in the document.

The distinction between an example such as that above and the simple
use of hi to mark the visual salience of the underlining
(apart from the use of the spanTo attribute) is that
hi does not imply that the visual effect being recorded is
understood to represent some kind of modification.

1.3.2 Metamarks

By metamark we mean marks such as numbers, arrows,
crosses, or other symbols introduced by the writer into a document
expressly for the purpose of indicating how the text is to be
read. Such marks thus constitute a kind of markup of the document,
rather than forming part of the text.

metamark contains or describes any kind of graphic or written signal
within a document intended to signal how it should be read but not
forming part of the text itself.

function

describes the function (e.g. add, delete, alternate) of the
mark.

target

indicates the element(s) to which the function of the metamark
refers. Pointers are separated by a white space

spanTo

indicates the end of a span initiated by the element
bearing this attribute.

Unlike marginal notes or other additions to the text, metamarks
are used by the writer to indicate a deliberate alteration of the writing itself,
such as ‘move this passage over there’. An addition or annotation
by contrast would typically concern some property of the passage other
than its intended location or status within the text flow. A metamark
may contain text, or some other graphic which the encoder
wishes to represent, or it may simply consist of arrows, dots, lines
etc. which the encoder simply describes.

The metamark element carries a function
attribute which specifies the function of the metamark, using values
such as reorder, flag, delete,
insert or used. The passage to
which the metamark applies may be indicated in either of two ways: the
target attribute may be used to point to the element or
elements containing the passage concerned, or the spanTo
element may be used to point to a position in the document at which
the passage concerned finishes. In the latter case, the
metamark itself must be supplied at the position in the
document where the passage concerned begins; in the former case it may
be supplied at any convenient point. Both attributes should not be
supplied.

The following example is taken from an
15th century legal book from the city of Göttingen, containing
regulations of everyday life issued by the city council

Figure 2. Kundige bok 2, fol 1v.

In the second paragraph, the word lege ("read") was written in the left hand
margin, next to the sentence beginning ‘Ock en schullen
de bruwere...’. It is thought to
function as a metamark, indicating that this sentence forms part of
the regulations. A further sentence was then added, while at some
later stage the text and also the metamark were deleted. We
might encode this as follows:

The change attribute used here to indicate the sequencing
of these various interventions is discussed below, in section 1.4 Changes. The elements addSpan and
delSpan are discussed in section [ID PHAD in TEI Guidelines].

The metamark element may also be used to encode the
symbols etc. often found in marked-up proofs such as the following,
taken from the Walt Whitman archive:

Figure 3. http://www.whitmanarchive.org/resources/sleepers/

In this example, the whole of what was originally the 14th section
has been marked for deletion, both by horizontal and vertical lines,
and by the metamarks resembling the ‘delta’ deletion symbol to
left and right of the section. The deletion itself might be encoded
by using the normal del or delSpan element.
This is quite a different case from that of the next example, in which the
writer does not intend to suppress the content, but only to mark that
it has been transferred or reused.

This page contains internal deletions, additions, and retracings
but these are semantically quite different from the apparent
‘deletion’ signalled by the largere of the two
single vertical lines, which shows that the written material has been
transferred or re-used, not deleted.

In this example, we class as metamarks both the long vertical line
and the annotation ‘Entered - yes’. Both metamarks are assumed to
indicate that the whole of the written zone with identifier
X2 is marked as having been used.

1.3.3 Fixation and clarification

A writer may sometimes rewrite material a second time without
significant change and in the same place. We consider this a distinct
activity from addition as usually defined because no new textual
material results; instead the status of existing material
is reaffirmed. We may distinguish two variants of this:
fixation where the first version was a tentative draft
which is subsequently reaffirmed, for example by inking it over; and
clarification, where the first version was badly written
and has been rewritten for clarity. The element retrace is
provided for both cases; its cause attribute may be used to
distinguish them.

retrace contains a sequence of text which has been rewritten by the author, for
example by over-inking, to clarify or fix it.

cause

documents the presumed cause of the repeated act of writing.

In this simple example, taken from the papers of Henrik Ibsen, the
writer wrote the word skuldren hastily, and
then returned to it to make the letter l larger
and clearer:

Figure 5. Image from a ms of Peer Gynt, Collin 2869, 4°, I.1.1, the
Royal Library of Copenhagen

We might transcribe this word as follows:

<line>... Sku<retrace cause="unclear">l</retrace>dren </line>

A single rewrite may not be sufficient, and it may be that the
document becomes almost unreadable as a result of repeated
clarification. In the following example, we can distinguish at least
three attempts to write the letters er in the
word bægerklang:

The change attribute used here is discussed further below
(1.4 Changes).

The retrace element is used only for cases where text has
been written multiple times. When metamarks and other markup-like strokes
have been rewritten multiple times, the redo element described in
the next section should be used in preference.

1.3.4 Fixation, cancellation, and reinstatement of modifications

In a draft version of Goethe’s Faust, a passage was struck through
once in pencil during one revision and then again with ink during a
later revision, supposedly to fixate the deletion.

Figure 7. Fixation of a deletion in Goethe’s Faust

A writer may also indicate that an alteration is itself to be altered:
for example, a struck-through passage may be restored via a dotted
underlining, or the underlining of a passage may be deleted by a wavy
line.

The following elements are provided to represent these situations:

redo/ points to one or more marked-up interventions in a
text which have subsequently been
marked for a second time in a different way.

target

points to one or more elements representing
interventions which are to be repeated.

cause

documents the presumed cause of the repeated act of writing.

spanTo

indicates the end of a span initiated by the element
bearing this attribute.

undo/ indicates one or more marked-up interventions in a
text which have subsequently been
marked as to be cancelled or undone.

target

points to one or more elements representing the interventions to be undone.

spanTo

indicates the end of a span initiated by the element
bearing this attribute.

The redo element might be used to encode the Faust example above
as follows:

The element restore ([ID PHCD in TEI Guidelines]) is
provided for the comparatively simple case where a simple deletion is
marked as having been subsequently cancelled. The undo
element discussed here is more widely applicable and may be used for
any kind of cancellation. It points to the element or elements which
are being cancelled. These components need not be contiguous, provided
that the cancellation is clearly a single act; each distinct act of
cancellation requires a distinct undo element, however. Either
of the attributes target or <spanTo> may be used to
indicate the passages concerned.

Consider the following imaginary example :

We hypothesize that the text has gone through three states or changes,
as follows:

using two undo elements, each with a spanTo
attribute, to delimit the two parts of the deletion which were
reverted at change s3. Note that in this case, since target
is not supplied, it is the effect of the parent element (the
del) which is assumed to be undone.

Alternatively, we might more economically use the generic seg element within
the line to delimit the two sequences whose
deletion is being reverted, and then use the <target> attribute
on a single undo element:

1.3.5 Transpositions

A transposition occurs when metamarks are found in a
document indicating that passages should be moved to a different
position. Typically this may be done using
arrows, asterisks or numbers, or other means. By definition the result
of a transposition is not present in the document, and should not
therefore be encoded, if the intention is to record its actual
state. Instead, the following elements may be used to indicate the
intended reordering:

transposeGrp supplies a list of transpositions indicated at some point in the text,
typically by means of metamarks.

transpose describes a single textual transposition as an ordered list of at least two
pointers specifying the order in which the elements indicated should be
re-combined.

Consider for example, the
following extract from an Ibsen manuscript

Figure 8. Extracted from
http://www.emunch.no/tei-mm-2008/ms.html

The underlined numbers 1 and 2 here indicate that, although the word
bör precedes the word
hör in the text, the order of the two words
should be reversed. We may encode this as follows:

Note the use of the generic seg element to identify the
sections of text being transposed. When (as in the following example)
the whole of a line is to be transposed, there is no need to delimit the
sections concerned:

When transposition is made, the whole element indicated is understood
to be moved, not just its contents. In the above example, the
metamarks are thus understood to be moved along with the lines to
which they apply.

One or more transposeGrp elements may be supplied either
embedded within the text or in the profileDesc of the header,
depending on local preference. Each transposeGrp can contain
one or more transpose elements, each of which defines a
single transposition.

1.3.6 Alternative Readings

Figure 10. Lalla Rookh 3

In this example two alternative readings are provided, but no
preference is indicated. While the author apparently
first composed the line ‘Alone before his native river -’, at some
later point, he entertained the possibility of using the word beside
instead of before. The manuscript supplies no
indication of which word Moore favours at this point, although in
fact, in the first printed
edition of Lalla Rookh the word
beside was chosen.

The element alt provided by the linking module gives a simple way of
encoding the state of this manuscript, as follows:

The alt element is further discussed in section [ID SA-whatever in TEI Guidelines].

1.3.7 Instant corrections

The use of elements such as del and add
necessarily implies that the modifications they indicate were made at
some time after the original writing. An exception to this is where a
false start or ‘instant’ correction has been
identified: the author starts to write, and then immediately corrects
what has been written.

The instant attribute defined by this module may be
used on any element which is a member of the att.editLike class to modify this default assumption.
When the value of instant is set to true,
the addition or deletion is considered to belong to the same change as
its parent element, while false means some change
later than that of its parent.

1.4 Changes

Note: Add this as a new section before
section
11.8 ("Other
Primary Source Features not Covered")

A major purpose of genetic editing is the identification of
‘revision campaigns’ or, more generally,
changes. An editor may wish to assign a set of alterations
(deletions, additions, substitutions, transpositions, etc.) or any
other act of writing to a particular change, to indicate both that one
or more of such phenomena preceded or followed another and also to
indicate that they are related in some way, for example that one is a
consequence of the other. To document this we need:

a system to assign phenomena to a particular change

a way to characterize a change, in itself and in relation to
other changes.

The existing element creation (within the TEI Header
profile description) is defined as the appropriate location for all
information relating to the genesis or production of a text. We modify
it slightly to permit a new listChange element which contains
a number of change elements, one for each identified change:

In the following example taken from the genetic edition of Goethe’s
Faust, the editor has identified four distinct changes:

<profileDesc><creation><listChange ordered="true"><change xml:id="ST-1">First stage, written in ink by a writer</change><change xml:id="ST-2">Second stage, written in Goethe's hand using pencil</change><change xml:id="ST-3">Fixation of the revised passages and further revisions by Goethe using ink</change><change xml:id="ST-4">Addition of another stanza in a different hand, probably at a later stage</change></listChange></creation></profileDesc>

The listChange element carries an attribute ordered, which can take the
values true or false (the default). The attribute specifies
whether the order of child elements signifies a temporal order for the revision campaigns
which they document. In the Faust example above, the editor has asserted that the four
stages distinguished are ordered chronologically according to the order of the
change elements. Note that asserting a specific order early on, though probably
one of the hardest tasks in a genetic analysis, can considerably reduce the encoding effort
in assigning textual alterations to stages during the transcription, as we will see below.
For instance deletions can only be assigned to a stage that follows the one in which the
passage being deleted was written down. Hence, having a certain order of stages put in
place before transcription begins, will allow the encoder to reduce verbose tagging, where
default assumptions based on the natural order of actions can be made.

If necessary, listChange elements can be nested hierarchically. This may be helpful
in two cases. Firstly one can build up hypotheses about related revisions step-by-step,
starting with stages of smaller coverage, whose members are certainly related, and then in
a subsequent pass grouping these stages in turn, thereby extending their reach.

A nested listChange elements is also useful to indicate a
partial ordering of revision campaigns.

<listChange ordered="true"><change xml:id="ST1">The first stage</change><listChange> .<change xml:id="ST-rev1">A revision of the first stage</change><change xml:id="ST-rev2">Another revision of the first stage</change></listChange><change xml:id="STX">The last stage</change></listChange>

In addition to the possibility of ordering text stages in relation to each other,
change elements may carry a number of attributes from the
att.datable class (period, when,
notBefore, notAfter, from, and to) which
allow each stage to be dated as exactly or inexactly as necessary, in the same way as is
currently possible for the TEI date element.

<profileDesc><creation><date notAfter="1816-07-18"/><listChange ordered="true"><change xml:id="mod1" when="1816-07-16">The first draft of<title>Persuasion</title> is completed by the <date>July 16 1816</date> written after the word <q>Finis</q> at <ref target="#pers-30">page 30</ref>.</change><change xml:id="mod2" notBefore="1816-07-16">After the <date>16th of July</date> Austen starts revision of the two final chapters, by rewriting the end and adding a new zone (<ref target="#transp-1">pages 32-35</ref>) to be inserted at <ref target="#insertion-p1">page 19</ref>. This stage is documented by the deletion of the date (<date>July 16 1816</date>) at <ref target="#pers-30">page 30</ref>, and the addition of more text and of a new date (<date>July 18. 1816</date>) at <ref target="#pers-31">page 31</ref></change><change notBefore="1816-07-18">Before publication, after <date>July 18th, 1816</date> chapters 10-11 were broken into three chapters, 10, 11, 12, as witnessed by the print.</change></listChange></creation></profileDesc>

Each change element, apart from declaring a distinct change in the creation of the
document, may also contain references to other annotations contained within the
teiHeader or in the document (as shown in the previous example). Such
references, along with the textual content are purely documentary and do not affect the
textual stage associated with any element thus referred to. The association of a textual
component with a change is always made explicitly, either by pointing from the
change attribute target to one or more elements, or (preferably)
by pointing from the element concerned to the change element by means of its
change attribute:

<line change="#firstStage">This is a <subst change="#secondStage"><del>house</del><add>mouse</add></subst>.</line>

This simple example shows the latter of the two options: The relevant changes are declared
in the header; then textual alterations and acts of writing
are associated with them. The above
markup indicates that the whole sentence was realized in the first stage, while the
substitution of “house” with “mouse” happened at the second stage.

Note first, that a change, once assigned to an element, is inherited by all descendants of
that element unless overridden by a subsequent assignment. So in the example above the
three verses are assigned to the first stage initially. The writing of
Nun (as part of the substitution in the first verse) takes place
in the second stage and is repeated or fixated in the third. Also the substitution in the
second verse is done repeatedly: initially it takes place in the second stage, but is
fixated as a whole in the third.

The interpretation of change assignments for a particular text passage is based on a number
of implicit assumptions and constraints which have the effect of minimizing the amount of
tagging necessary. The system is also flexible enough to support an explicit distinction
between acts of writing and textual alterations, since either of these can be associated
with changes described in the encoding. The following example shows an encoding in which the
same passage is transcribed twice, once from a documentary perspective, and once from a
textual one :

The documentary transcription stresses the writing process, while the textual transcription
emphasizes textual alterations. In either case, the change of writing activity associated
with a particular feature in the transcript is explicitly indicated. From the documentary
perspective, the stage assignments describe the writing process, in that they specify,
which segment has been written when and how often. From the textual perspective, the markup
concentrates on the order of textual alterations and makes no assumptions about the order
of writing. In this example, the association is made by pointing from the change
element to all the passages and alterations in question in either perspective, which has
the merit of not confusing the presentation of the interventions concerned with writing
sequence information, at the price of requiring a distinct identifier on each intervention.

2 Formal specifications

Schema testgenetic: changed components

att.editLike

att.editLike provides attributes describing the nature of a encoded scholarly intervention or
interpretation of any kind.

The value must conform to BCP 47. If the value is a private use code (i.e., starts
with x- or contains -x-) it should, and if not it may, match the
value of an ident attribute of a language element supplied in the TEI
Header of the current document.

Note

If no value is specified for xml:lang, the xml:lang value for the
immediately enclosing element is inherited; for this reason, a value should always be
specified on the outermost element (TEI).

rend

(rendition) indicates how the element in question was rendered or presented in the source text.

These Guidelines make no binding recommendations for the values of the rend
attribute; the characteristics of visual presentation vary too much from text to text and
the decision to record or ignore individual characteristics varies too much from project
to project. Some potentially useful conventions are noted from time to time at appropriate
points in the Guidelines.

rendition

points to a description of the rendering or presentation used for this element in the
source text.

The rendition attribute is used in a very similar way to the class
attribute defined for XHTML but with the important distinction that its function is to
describe the appearance of the source text, not necessarily to determine how that text
should be presented on screen or paper.

Where both rendition and rend are supplied, the latter is
understood to override or complement the former.

Each URI provided should indicate a rendition element defining the intended
rendition in terms of some appropriate style language, as indicated by the
scheme attribute.

points to one or more change elements which contain a
description of a text-change to which the editors think the alteration/
text passage marked by the element bearing this attribute (and its
children) belongs.

The who attribute may be used to point to any other element, but will typically
specify a respStmt or <person> element elsewhere in the header, identifying
the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent
first. The status attribute may be used to indicate the
status of a document following the change documented.

The creation element may be used to record details of a text's creation, e.g. the
date and place it was composed, if these are of interest; it should not be confused with the
publicationStmt element, which records date and place of publication.

<l>When wolde the cat dwelle in his ynne</l><handShift medium="greenish-ink"/><l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>

Note

The handShift element may be used either to
denote a shift in the document hand (as from one scribe to another,
on one writing style to another). Or, it may indicate a shift within
a document hand, as a change of writing style, character or ink. Like
other milestone elements, it should appear at the point of
transition from some other state to the state which it describes.

<line>

<line> contains the transcription of a topographic line in the source
document

Multiple rewritings are indicated by nesting one retrace within
another. In principle, a rewriting differs from a substitution in that
second and subsequent rewrites do not materially alter the content of an
element. Where there are minor changes made during the rewriting however
these may be marked up using del, add, etc. with an
appropriate value for the change attribute.

<sourceDoc>

<sourceDoc> contains a transcription or other representation of a single source document
potentially forming part of a dossier genetique.

<sourceDoc><graphic url="page1.png"/><zone>Text on page 1</zone><surface><graphic url="page2-highRes.png"/><graphic url="page2-lowRes.png"/><zone><line>A line of text </line><line>Another line of text</line></zone></surface></sourceDoc>

<surface>

<surface> defines a written surface in terms of a rectangular
coordinate space, optionally grouping one or more graphic representations of
that space, and rectangular zones of interest
within it.

The surface element represents a rectangular area of
any physical surface forming part of the source material. This may be a sheet of
paper, one face of a monument, a billboard, a papyrus scroll, or
indeed any 2-dimensional surface.

The coordinate space defined by this element may be thought of as
a grid lrx - ulx units wide and uly - lry units high. This
grid is superimposed on the whole of any image directly contained by
the surface element. The coordinate values used by every
zone element contained by this surface are to be understood
with reference to the same grid.

<transpose>

<transpose> describes a single textual transposition as an ordered list of at least two
pointers specifying the order in which the elements indicated should be
re-combined.

indicates the amount by which this zone has been rotated clockwise,
with respect to the normal orientation of the parent surface
element as implied by the dimensions given in the msDesc element
or by the coordinates of the surface itself. The orientation is
expressed in arc degrees.

The position of every zone for a given surface is always
defined by reference to the coordinate system defined for that
surface. Any graphic element contained by a zone represents the whole
of the zone.

accMat:
(accompanying material) contains details of any significant additional
material which may be closely associated with the manuscript being
described, such as non-contemporaneous documents or fragments bound in
with the manuscript at some earlier historical period. «#msadac»

acquisition:
contains any descriptive or other information
concerning the process by which a manuscript or manuscript part entered the holding
institution. «#mshy»

binding:
contains a description of one binding, i.e. type of covering, boards,
etc. applied to a manuscript. «#msphbi»

bindingDesc:
(binding description) describes the present and former bindings of a manuscript, either
as a series of paragraphs or as a series of distinct binding elements,
one for each binding of the manuscript. «#msphbi»

data.point:
defines the data type used to express a point in cartesian space.

data.pointer:
defines the range of attribute values used to provide a single
URI pointer to any other
resource, either within the current document or elsewhere.

data.probability:
defines the range of attribute values expressing a probability.

data.temporal.iso:
defines the range of attribute values expressing a temporal expression such as a date, a
time, or a combination of them, that conform to the international standard Data elements
and interchange formats – Information interchange – Representation of dates and times.

data.temporal.w3c:
defines the range of attribute values expressing a temporal
expression such as a date, a time, or a combination of them, that
conform to the W3C XML Schema Part 2: Datatypes
specification.

data.truthValue:
defines the range of attribute values used to express a truth
value.

data.version:
defines the range of attribute values which may be used to
specify a TEI version number.

data.word:
defines the range of attribute values expressed as a single
word or token.

data.xTruthValue:
(extended truth value) defines the range of attribute values used to express a truth value which may be unknown.

filiation:
contains information concerning the manuscript's filiation, i.e. its relationship to other surviving manuscripts of the same text, its protographs, antigraphs and apographs. «#mscoit»

finalRubric:
contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. «#mscoit»

incipit:
contains the incipit of a manuscript item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipts were, in fomer times, frequently used a means of reference to a work, in place of a title. «#mscoit»

localName:
(locally-defined property name) contains a locally defined name for some property.

locus:
defines a location within a manuscript or manuscript part, usually as a
(possibly discontinuous) sequence of folio references. «#msloc»

locusGrp:
groups a number of locations which together form a
distinct but discontinuous item within a manuscript or manuscript
part, according to a specific foliation.
«#msloc»

macro.anyXML:
defines a content model within which any XML elements are
permitted

macro.limitedContent:
(paragraph content) defines the content of prose elements that are not used for transcription of extant materials.

macro.paraContent:
(paragraph content) defines the content of paragraphs and similar elements.

macro.phraseSeq:
(phrase sequence) defines a sequence of character data and phrase-level elements.

macro.phraseSeq.limited:
(limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically
used for transcribing extant documents.

macro.specialPara:
('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a
series of component-level elements or else have the same structure as a paragraph, containing a
series of phrase-level and inter-level elements.

macro.xtext:
(extended text) defines a sequence of character data and gaiji elements.

mapping:
(character mapping) contains one or more
characters which are related to the parent character or glyph
in some respect, as specified by the type
attribute.

material:
contains a word or phrase describing the
material of which the object being described is composed.
«#msmat»

physDesc:
(physical description) contains a full physical description of a
manuscript or manuscript part, optionally subdivided using more
specialised elements from the model.physDescPart class. «#msph»

provenance:
contains any descriptive or other information
concerning a single identifiable episode during the history of a manuscript
or manuscript part, after its creation but before its acquisition. «#mshy»

q:
(separated from the surrounding text with quotation marks) contains material which is marked as (ostensibly) being somehow different than the
surrounding text, for any one of a variety of reasons including, but not limited to: direct
speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and
passages that are mentioned but not used. http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ

rubric:
contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which a
manuscript signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, usually in red ink, or by use of different size or type of script, or some other such visual device. «#mscoit»

scriptDesc:
contains a description of the scripts used in a manuscript or similar source. «#msphwr»

scriptNote:
describes a particular script distinguished within
the description of a manuscript or similar resource. «#msph2»

seal:
contains a description of one seal or similar
attachment applied to a manuscript. «#msphse»

sealDesc:
(seal description) describes the seals or other external items attached to a manuscript, either
as a series of paragraphs or as a series of distinct seal elements,
possibly with additional decoNotes. «#msphse»

secFol:
(second folio) The word or words taken from a fixed point
in a codex (typically the beginning of the
second leaf) in order
to provide a unique identifier for it.
«#msmisc»

subst:
(substitution) groups one or more deletions with one or more additions when
the combination is to be regarded as a single intervention in the text.

summary:
contains an overview of the available
information concerning some aspect of an item (for example, its
intellectual content, history, layout, typography etc.) as a
complement or alternative to the more detailed information carried by
more specific elements.