TEIWiki - User contributions [en]

AttsWithoutEgs

2013-11-11T02:28:38Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
| High
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
| High
|-
| 10
| class
| msContents
|
|
|Low
|-
| 11
| cols
| att.tableDecoration
| pfs
|
| Medium
|-
| 12
| confidence
| att.ranging
|
|
| Medium
|-
| 13
| contemporary
| seal
|
|
| Medium
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
| via att.media. Low
|-
| 50
| ident
| att.identified
|
|
| Low
|-
| 51
| inst
| att.interpLike
|
|
| High
|-
| 52
| instant
| att.editLike
|
|
| Low
|-
| 53
| key
| classRef
|
|
| Low
|-
| 54
| key
| macroRef
|
|
| Low
|-
| 55
| level
| sense
|
|
| Medium
|-
| 56
| loc
| app
|
|
| High
|-
| 57
| location
| att.lexicographic
|
|
| Medium
|-
| 58
| lrx
| att.coordinated
|
|
| Low
|-
| 59
| lry
| att.coordinated
|
|
| Low
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:16:02Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Medium
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Medium
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T02:15:10Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
| Low
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
| High
|-
| 61
| max
| att.ranging
|
|
| Low
|-
| 62
| max
| memberOf
|
|
| Low
|-
| 63
| medium
| att.handFeatures
|
|
| Low
|-
| 64
| mergedIn
| att.lexicographic
|
|
| Low
|-
| 65
| met
| att.metrical
|
|
| Medium
|-
| 66
| min
| att.ranging
|
|
| Low
|-
| 67
| min
| memberOf
|
|
| Low
|-
| 68
| module
| att.identified
|
|
| Low. Suggest revising definition from "supplies a name for the module in which this object is to be declared." to "supplies a name for the TEI module in which this object is to be declared."
|-
| 69
| new
| handShift
|
|
| Low; may be renamed in a future release
|-
| 70
| next
| att.global.linking
|
|
| Low
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
| Low
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
| Low
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
| Low
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
| Low
|-
| 75
| notation
| pron
| MH
| 2013-01-30
| Done
|-
| 76
| ns
| attDef
|
|
| Low
|-
| 77
| ns
| att.namespaceable
|
|
| Low
|-
| 78
| nymRef
| att.naming
|
|
| Low
|-
| 79
| opt
| att.lexicographic
|
|
| Low
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Low
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Low
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T01:54:41Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
| Low. Suggest changing definition from "indicates whether or not the value of this feature may be present." to "indicates whether or not the value of this feature may be omitted."
|-
| 81
| ord
| root
|
|
| Low
|-
| 82
| ord
| iNode
|
|
| Low
|-
| 83
| orig
| att.lexicographic
|
|
| Medium
|-
| 84
| parts
| nym
|
|
| Low
|-
| 85
| perf
| tech
|
|
| Low
|-
| 86
| period
| att.datable
|
|
| Low
|-
| 87
| pre
| pc
|
|
| If the definition for the attribute is clarified, this will be a Medium priority for an example. But as it stands, the definition + datatype is confusing. The definition reads: "indicates whether this punctuation mark precedes or follows the unit it delimits." The datatype is data.truthvalue. Does this mean, a value of 1 (true) indicates that the punctuation character precedes, and 0 (false) indicates that it does not precede, and therefore follows? Suggest that the definition be revised to simply read: "indicates whether this punctuation mark precedes the unit it delimits."
|-
| 88
| precision
| att.dimensions
|
|
| Low
|-
| 89
| predeclare
| att.identified
|
|
| Low
|-
| 90
| prefix
| moduleRef
|
|
| High
|-
| 91
| prefix
| elementSpec
|
|
| High
|-
| 92
| prev
| att.global.linking
|
|
| Low
|-
| 93
| quantity
| att.dimensions
| BB
|
| Low
|-
| 94
| real
| att.metrical
|
|
| Low
|-
| 95
| ref
| att.canonical
|
|
| Low
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
| Low
|-
| 97
| resp
| att.responsibility
| BB
|
| Low
|-
| 98
| resp
| space
|
|
| Low
|-
| 99
| rhyme
| att.metrical
|
|
| Low
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T01:22:47Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
| Low
|-
| 101
| role
| org
|
|
| Medium
|-
| 102
| rotate
| zone
|
|
| Low
|-
| 103
| rows
| att.tableDecoration
| pfs
|
| Low
|-
| 104
| sameAs
| att.global.linking
|
|
| Low
|-
| 105
| scale
| graphic
|
|
| Via att.media. Low
|-
| 106
| scale
| binaryObject
|
|
| Via att.media. Low
|-
| 107
| scheme
| catRef
|
|
| Low
|-
| 108
| scheme
| locus
|
|
| Low
|-
| 109
| scheme
| locusGrp
|
|
| Low
|-
| 110
| scribe
| att.handFeatures
|
|
| Low
|-
| 111
| scribeRef
| att.handFeatures
|
|
| Low
|-
| 112
| script
| att.handFeatures
|
|
| Low
|-
| 113
| scriptRef
| att.handFeatures
|
|
| Low
|-
| 114
| select
| att.global.linking
|
|
| Medium
|-
| 115
| seq
| att.transcriptional
|
|
| Low
|-
| 116
| social
| distinct
|
|
| Low--as long as "distatically" is known terminology in the field. Could not find a definition for it that made sense in this context.
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T00:59:58Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
| Low
|-
| 117
| sort
| att.personal
|
|
| Medium
|-
| 118
| source
| att.editLike
|
|
| Low
|-
| 119
| source
| att.readFrom
|
|
| HIgh
|-
| 120
| source
| writing
|
|
| gets @source via att.source. Low.
|-
| 121
| space
| distinct
|
|
| Low
|-
| 122
| spanTo
| att.spanning
| BB
|
| Medium
|-
| 123
| split
| att.lexicographic
|
|
| Medium
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T00:40:08Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
| High
|-
| 125
| start
| att.coordinated
|
|
| High
|-
| 126
| stdDeviation
| precision
|
|
| Low
|-
| 127
| subtype
| att.typed
| pfs
|
| Medium
|-
| 128
| subtype
| abbr
|
|
| title gets @subtype via @att.typed. See No. 127
|-
| 129
| subtype
| title
|
|
| gets @subtype via @att.typed. See No. 127
|-
| 130
| synch
| att.global.linking
|
|
| High
|-
| 131
| targFunc
| att.pointing.group
|
|
| High
|-
| 132
| target
| change
|
|
| Low
|-
| 133
| target
| relatedItem
|
|
| Low
|-
| 134
| targetEnd
| note
|
|
| High for clarity, but low because no longer recommended practice
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T00:13:46Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
|
|-
| 125
| start
| att.coordinated
|
|
|
|-
| 126
| stdDeviation
| precision
|
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|
|-
| 128
| subtype
| abbr
|
|
|
|-
| 129
| subtype
| title
|
|
|
|-
| 130
| synch
| att.global.linking
|
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|
|-
| 132
| target
| change
|
|
|
|-
| 133
| target
| relatedItem
|
|
|
|-
| 134
| targetEnd
| note
|
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
| Low
|-
| 136
| targets
| link
|
|
| Deprecated
|-
| 137
| targets
| join
|
|
| Deprecated
|-
| 138
| targets
| alt
|
|
| Deprecated
|-
| 139
| time
| distinct
|
|
| High
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
| Done
|-
| 141
| to
| app
|
|
| High
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
| Done
|-
| 143
| to-iso
| att.datable.iso
|
|
| Low
|-
| 144
| type
| sound
|
|
| Medium
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-11T00:02:12Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
|
|-
| 125
| start
| att.coordinated
|
|
|
|-
| 126
| stdDeviation
| precision
|
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|
|-
| 128
| subtype
| abbr
|
|
|
|-
| 129
| subtype
| title
|
|
|
|-
| 130
| synch
| att.global.linking
|
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|
|-
| 132
| target
| change
|
|
|
|-
| 133
| target
| relatedItem
|
|
|
|-
| 134
| targetEnd
| note
|
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
|
|-
| 136
| targets
| link
|
|
|
|-
| 137
| targets
| join
|
|
|
|-
| 138
| targets
| alt
|
|
|
|-
| 139
| time
| distinct
|
|
|
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 141
| to
| app
|
|
|
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
|
|-
| 143
| to-iso
| att.datable.iso
|
|
|
|-
| 144
| type
| sound
|
|
|
|-
| 145
| ulx
| att.coordinated
|
|
| Low
|-
| 146
| uly
| att.coordinated
|
|
| Low
|-
| 147
| unit
| pc
|
|
| High
|-
| 148
| url
| moduleRef
|
|
| Low
|-
| 149
| value
| att.lexicographic
|
|
| High
|-
| 150
| value
| node
|
|
| Low
|-
| 151
| value
| root
|
|
| Low
|-
| 152
| value
| iNode
|
|
| Low
|-
| 153
| value
| leaf
|
|
| Low
|-
| 154
| value
| eTree
|
|
| Low
|-
| 155
| value
| triangle
|
|
| Low
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-10T23:44:36Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
|
|-
| 125
| start
| att.coordinated
|
|
|
|-
| 126
| stdDeviation
| precision
|
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|
|-
| 128
| subtype
| abbr
|
|
|
|-
| 129
| subtype
| title
|
|
|
|-
| 130
| synch
| att.global.linking
|
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|
|-
| 132
| target
| change
|
|
|
|-
| 133
| target
| relatedItem
|
|
|
|-
| 134
| targetEnd
| note
|
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
|
|-
| 136
| targets
| link
|
|
|
|-
| 137
| targets
| join
|
|
|
|-
| 138
| targets
| alt
|
|
|
|-
| 139
| time
| distinct
|
|
|
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 141
| to
| app
|
|
|
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
|
|-
| 143
| to-iso
| att.datable.iso
|
|
|
|-
| 144
| type
| sound
|
|
|
|-
| 145
| ulx
| att.coordinated
|
|
|
|-
| 146
| uly
| att.coordinated
|
|
|
|-
| 147
| unit
| pc
|
|
|
|-
| 148
| url
| moduleRef
|
|
|
|-
| 149
| value
| att.lexicographic
|
|
|
|-
| 150
| value
| node
|
|
|
|-
| 151
| value
| root
|
|
|
|-
| 152
| value
| iNode
|
|
|
|-
| 153
| value
| leaf
|
|
|
|-
| 154
| value
| eTree
|
|
|
|-
| 155
| value
| triangle
|
|
| High
|-
| 156
| varSeq
| att.textCritical
|
|
| High
|-
| 157
| version
| unicodeName
|
|
| Medium
|-
| 158
| versionDate
| att.translatable
|
|
| Low
|-
| 159
| when
| docDate
|
|
| Low
|-
| 160
| where
| event
|
|
| Medium
|-
| 161
| width
| graphic actually att.media)
|
|
| Low
|-
| 162
| width
| binaryObject (actually att.media)
|
|
| Low
|-
| 163
| wit
| att.rdgPart
|
|
| Medium
|-
| 164
| wit
| att.witnessed
|
|
| Medium
|}

AttsWithoutEgs

2013-11-10T23:18:36Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
| Low
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
| Medium
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
|
|-
| 125
| start
| att.coordinated
|
|
|
|-
| 126
| stdDeviation
| precision
|
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|
|-
| 128
| subtype
| abbr
|
|
|
|-
| 129
| subtype
| title
|
|
|
|-
| 130
| synch
| att.global.linking
|
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|
|-
| 132
| target
| change
|
|
|
|-
| 133
| target
| relatedItem
|
|
|
|-
| 134
| targetEnd
| note
|
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
|
|-
| 136
| targets
| link
|
|
|
|-
| 137
| targets
| join
|
|
|
|-
| 138
| targets
| alt
|
|
|
|-
| 139
| time
| distinct
|
|
|
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 141
| to
| app
|
|
|
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
|
|-
| 143
| to-iso
| att.datable.iso
|
|
|
|-
| 144
| type
| sound
|
|
|
|-
| 145
| ulx
| att.coordinated
|
|
|
|-
| 146
| uly
| att.coordinated
|
|
|
|-
| 147
| unit
| pc
|
|
|
|-
| 148
| url
| moduleRef
|
|
|
|-
| 149
| value
| att.lexicographic
|
|
|
|-
| 150
| value
| node
|
|
|
|-
| 151
| value
| root
|
|
|
|-
| 152
| value
| iNode
|
|
|
|-
| 153
| value
| leaf
|
|
|
|-
| 154
| value
| eTree
|
|
|
|-
| 155
| value
| triangle
|
|
|
|-
| 156
| varSeq
| att.textCritical
|
|
|
|-
| 157
| version
| unicodeName
|
|
|
|-
| 158
| versionDate
| att.translatable
|
|
|
|-
| 159
| when
| docDate
|
|
|
|-
| 160
| where
| event
|
|
|
|-
| 161
| width
| graphic
|
|
|
|-
| 162
| width
| binaryObject
|
|
|
|-
| 163
| wit
| att.rdgPart
|
|
| low
|-
| 164
| wit
| att.witnessed
|
|
| low
|}

AttsWithoutEgs

2013-11-10T11:52:21Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

Attributes with suggested values are not included.

List generated 2012-12-21T07:56:57.538-08:00

If you have a good example of any of these attributes that you'd like use to include in the guidelines, then 'claim' the attribute here, edit the Guidelines if you have access and mark as completed when it is done. If you don't have access to edit the Guidelines you may email council at tei-c.org or post to the BUG listed above.

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
! Priority (High, Medium, Low)

|-
| 1
| absolute
| when
|
|
|
|-
| 2
| age
| personGrp
| MH
| 2013-01-25
|
|-
| 3
| ana
| att.global.analytic
|
|
|
|-
| 4
| atLeast
| att.ranging
| BB
| 2013-10-16
|
|-
| 5
| atMost
| att.ranging
| BB
| 2013-10-16
|
|-
| 6
| baseTypes
| fsDecl
|
|
|
|-
| 7
| cRef
| att.cReferencing
|
|
|
|-
| 8
| cert
| att.responsibility
| MH
| 2013-01-25
|
|-
| 9
| change
| att.global.change
|
|
|
|-
| 10
| class
| msContents
|
|
|
|-
| 11
| cols
| att.tableDecoration
| pfs
|
|
|-
| 12
| confidence
| att.ranging
|
|
|
|-
| 13
| contemporary
| seal
|
|
|
|-
| 14
| copyOf
| att.global.linking
|
|
|
|-
| 15
| datingMethod
| att.datable.custom
| MH
| 2013-01-25
|
|-
| 16
| datingPoint
| att.datable.custom
|
|
|
|-
| 17
| decls
| att.declaring
|
|
|
|-
| 18
| defective
| att.msExcerpt
|
|
|
|-
| 19
| degree
| att.damaged
|
|
|
|-
| 20
| docLang
| schemaSpec
|
|
|
|-
| 21
| domains
| att.pointing.group
|
|
|
|-
| 22
| dur
| att.duration.w3c
|
|
|
|-
| 23
| dur-iso
| att.duration.iso
|
|
|
|-
| 24
| encoding
| binaryObject
|
|
|
|-
| 25
| end
| att.timed
|
|
|
|-
| 26
| except
| moduleRef
|
|
|
|-
| 27
| exclude
| att.global.linking
|
|
|
|-
| 28
| expand
| att.lexicographic
|
|
|
|-
| 29
| fVal
| f
|
|
|
|-
| 30
| facs
| att.global.facs
|
|
|
|-
| 31
| feats
| fs
|
|
|
|-
| 32
| filter
| equiv
|
|
|
|-
| 33
| flipping
| surface
|
|
|
|-
| 34
| follow
| leaf
|
|
|
|-
| 35
| form
| quotation
|
|
|
|-
| 36
| from
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 37
| from
| app
|
|
|
|-
| 38
| from-custom
| att.datable.custom
| MH
| 2013-01-26
|
|-
| 39
| from-iso
| att.datable.iso
|
|
|
|-
| 40
| function
| att.segLike
|
|
|
|-
| 41
| gradual
| writing
|
|
|
|-
| 42
| group
| att.damaged
|
|
|
|-
| 43
| hand
| att.damaged
|
|
|
|-
| 44
| hand
| att.transcriptional
|
|
|
|-
| 45
| hand
| gap
|
|
|
|-
| 46
| hand
| unclear
|
|
|
|-
| 47
| hand
| att.textCritical
|
|
|
|-
| 48
| height
| graphic
|
|
|
|-
| 49
| height
| binaryObject
|
|
|
|-
| 50
| ident
| att.identified
|
|
|
|-
| 51
| inst
| att.interpLike
|
|
|
|-
| 52
| instant
| att.editLike
|
|
|
|-
| 53
| key
| classRef
|
|
|
|-
| 54
| key
| macroRef
|
|
|
|-
| 55
| level
| sense
|
|
|
|-
| 56
| loc
| app
|
|
|
|-
| 57
| location
| att.lexicographic
|
|
|
|-
| 58
| lrx
| att.coordinated
|
|
|
|-
| 59
| lry
| att.coordinated
|
|
|
|-
| 60
| matchPattern
| att.patternReplacement
|
|
|
|-
| 61
| max
| att.ranging
|
|
|
|-
| 62
| max
| memberOf
|
|
|
|-
| 63
| medium
| att.handFeatures
|
|
|
|-
| 64
| mergedIn
| att.lexicographic
|
|
|
|-
| 65
| met
| att.metrical
|
|
|
|-
| 66
| min
| att.ranging
|
|
|
|-
| 67
| min
| memberOf
|
|
|
|-
| 68
| module
| att.identified
|
|
|
|-
| 69
| new
| handShift
|
|
|
|-
| 70
| next
| att.global.linking
|
|
|
|-
| 71
| notAfter-custom
| att.datable.custom
|
|
|
|-
| 72
| notAfter-iso
| att.datable.iso
|
|
|
|-
| 73
| notBefore-custom
| att.datable.custom
|
|
|
|-
| 74
| notBefore-iso
| att.datable.iso
|
|
|
|-
| 75
| notation
| pron
| MH
| 2013-01-30
|
|-
| 76
| ns
| attDef
|
|
|
|-
| 77
| ns
| att.namespaceable
|
|
|
|-
| 78
| nymRef
| att.naming
|
|
|
|-
| 79
| opt
| att.lexicographic
|
|
|
|-
| 80
| optional
| fDecl
|
|
|
|-
| 81
| ord
| root
|
|
|
|-
| 82
| ord
| iNode
|
|
|
|-
| 83
| orig
| att.lexicographic
|
|
|
|-
| 84
| parts
| nym
|
|
|
|-
| 85
| perf
| tech
|
|
|
|-
| 86
| period
| att.datable
|
|
|
|-
| 87
| pre
| pc
|
|
|
|-
| 88
| precision
| att.dimensions
|
|
|
|-
| 89
| predeclare
| att.identified
|
|
|
|-
| 90
| prefix
| moduleRef
|
|
|
|-
| 91
| prefix
| elementSpec
|
|
|
|-
| 92
| prev
| att.global.linking
|
|
|
|-
| 93
| quantity
| att.dimensions
| BB
|
|
|-
| 94
| real
| att.metrical
|
|
|
|-
| 95
| ref
| att.canonical
|
|
|
|-
| 96
| replacementPattern
| att.patternReplacement
|
|
|
|-
| 97
| resp
| att.responsibility
| BB
|
|
|-
| 98
| resp
| space
|
|
|
|-
| 99
| rhyme
| att.metrical
|
|
|
|-
| 100
| role
| att.naming
|
|
|
|-
| 101
| role
| org
|
|
|
|-
| 102
| rotate
| zone
|
|
|
|-
| 103
| rows
| att.tableDecoration
| pfs
|
|
|-
| 104
| sameAs
| att.global.linking
|
|
|
|-
| 105
| scale
| graphic
|
|
|
|-
| 106
| scale
| binaryObject
|
|
|
|-
| 107
| scheme
| catRef
|
|
|
|-
| 108
| scheme
| locus
|
|
|
|-
| 109
| scheme
| locusGrp
|
|
|
|-
| 110
| scribe
| att.handFeatures
|
|
|
|-
| 111
| scribeRef
| att.handFeatures
|
|
|
|-
| 112
| script
| att.handFeatures
|
|
|
|-
| 113
| scriptRef
| att.handFeatures
|
|
|
|-
| 114
| select
| att.global.linking
|
|
|
|-
| 115
| seq
| att.transcriptional
|
|
|
|-
| 116
| social
| distinct
|
|
|
|-
| 117
| sort
| att.personal
|
|
|
|-
| 118
| source
| att.editLike
|
|
|
|-
| 119
| source
| att.readFrom
|
|
|
|-
| 120
| source
| writing
|
|
|
|-
| 121
| space
| distinct
|
|
|
|-
| 122
| spanTo
| att.spanning
| BB
|
|
|-
| 123
| split
| att.lexicographic
|
|
|
|-
| 124
| start
| att.timed
|
|
|
|-
| 125
| start
| att.coordinated
|
|
|
|-
| 126
| stdDeviation
| precision
|
|
|
|-
| 127
| subtype
| att.typed
| pfs
|
|
|-
| 128
| subtype
| abbr
|
|
|
|-
| 129
| subtype
| title
|
|
|
|-
| 130
| synch
| att.global.linking
|
|
|
|-
| 131
| targFunc
| att.pointing.group
|
|
|
|-
| 132
| target
| change
|
|
|
|-
| 133
| target
| relatedItem
|
|
|
|-
| 134
| targetEnd
| note
|
|
|
|-
| 135
| targetLang
| schemaSpec
|
|
|
|-
| 136
| targets
| link
|
|
|
|-
| 137
| targets
| join
|
|
|
|-
| 138
| targets
| alt
|
|
|
|-
| 139
| time
| distinct
|
|
|
|-
| 140
| to
| att.datable.w3c
| BB
| 2013-10-16
|
|-
| 141
| to
| app
|
|
|
|-
| 142
| to-custom
| att.datable.custom
| MH
| 2013-01-26 (included in example of @from-custom)
|
|-
| 143
| to-iso
| att.datable.iso
|
|
|
|-
| 144
| type
| sound
|
|
|
|-
| 145
| ulx
| att.coordinated
|
|
|
|-
| 146
| uly
| att.coordinated
|
|
|
|-
| 147
| unit
| pc
|
|
|
|-
| 148
| url
| moduleRef
|
|
|
|-
| 149
| value
| att.lexicographic
|
|
|
|-
| 150
| value
| node
|
|
|
|-
| 151
| value
| root
|
|
|
|-
| 152
| value
| iNode
|
|
|
|-
| 153
| value
| leaf
|
|
|
|-
| 154
| value
| eTree
|
|
|
|-
| 155
| value
| triangle
|
|
|
|-
| 156
| varSeq
| att.textCritical
|
|
|
|-
| 157
| version
| unicodeName
|
|
|
|-
| 158
| versionDate
| att.translatable
|
|
|
|-
| 159
| when
| docDate
|
|
|
|-
| 160
| where
| event
|
|
|
|-
| 161
| width
| graphic
|
|
|
|-
| 162
| width
| binaryObject
|
|
|
|-
| 163
| wit
| att.rdgPart
|
|
|
|-
| 164
| wit
| att.witnessed
|
|
|
|}

Council actions 2013-04

2013-06-19T15:20:49Z

RebeccaWelzenbach:

A list of actions, those responsible, and what has been done about them
from Providence, Rhode Island, 2013-04-11 to 2013-04-13 face to face
meeting of TEI Technical Council
{|class="wikitable sortable"
|'''Who'''
|'''What'''
|'''Suggested Deadline'''
|'''Result (What Was Done)'''
|-
|All of Council
|read and comment on the document (even if it's "this bit doesn't make sense to me"). http://goo.gl/AwPs6
|2013-05-17
|
|-
|EM
|to clarify the description on elementSpec on biblScope, citedRange and locus to clarify the use of @from and @to. https://sourceforge.net/p/tei/feature-requests/389/
|2013-06-07
|
|-
|EM and SB
|to take over from KH and get something from the phys bibl group, and/or encourage the generation of cheatsheets for encoding physical bibliography to go on the wiki. [— addendum, 2013-04-14 by Syd: I believe this action was on EM and SB (or perhaps EM, LB, SB); in any case, I have already spoken to Richard Noble who is not only on board but eager. —]
|2013-05-31
|
|-
|GB
|to add examples of schematron constrains on contents of <app> as the (Green) ticket says.
|2013-05-31
|
|-
|GB
|to re-read the section and rephrase/rewrite if necessary. https://sourceforge.net/p/tei/bugs/552/
|2013-05-31
|
|-
|GB
|to close the ticket with explanation, and possibly revise the text to clarify. *DONE* https://sourceforge.net/p/tei/bugs/553/
|2013-04-30
|
|-
|GB
|Close https://sourceforge.net/p/tei/bugs/405/ if fully incorporated into HC's proposal
|2013-04-30
|
|-
|GB
|look at other suggested standards recording s<nowiki/>ex, gender, and gender identity for inclusion in the notes. https://sourceforge.net/p/tei/feature-requests/425/
|2013-04-30
|
|-
|GB
|Implement https://sourceforge.net/p/tei/feature-requests/425/ changing data.s<nowiki/>ex to be datatype data.word, providing changed Guidelines prose and notes to other standards.
|2013-04-30
|
|-
|GB
|to propose a more effective wording incorporating all the nuances. https//sourceforge.net/p/tei/bugs/543/
|2013-05-31
|
|-
|HC
|to change values in @unit to singular, spelled-out forms, add column, and update Guidelines examples and text for consistency with the new values. Leave @type alone because it's deprecated. https://sourceforge.net/p/tei/feature-requests/429/
|2013-05-17
|
|-
|HC
|Nudge NH, SB, and PB for input.
|2013-05-31
|
|-
|HC and SB
|specification and estimated cost for Xpointer resolver
|2013-05-31
|
|-
|HC and SR
|to test the use of @xml:space to solve this specific problem, and to see whether that's the correct solution in the long term. DONE; https://sourceforge.net/p/tei/bugs/544/
|2013-04-30
|DONE
|-
|JC
|to implement https://sourceforge.net/p/tei/feature-requests/449/ add <am> to att.typed.
|2013-04-30
|DONE at revision 12263
|-
|JC
|to close ticket https://sourceforge.net/p/tei/feature-requests/438/ as won't-fix.
|2013-04-30
|DONE
|-
|JC
|to put a copy of the SF XML dump in the Vault.
|2013-04-30
|PENDING
|-
|JC
|to talk to DavidS and ShayneB to find out if we'd be allowed to dump the wiki db, make changes, and re-upload. For the OpenCMS we could do it manually.
|2013-04-30
|DONE (investigating)
|-
|JC
|to email sourceforge and find out if we can turn this off or modify markdown setup and investigate the implications/options.
|2013-04-30
|Investigating options.
|-
|JC
|https://sourceforge.net/p/tei/bugs/504/ implement (already done.) Close Ticket.
|2013-04-30
|DONE (Then revised slightly subsequently)
|-
|JC
|to investigate the Allura system if possible to make the meanings of the (priority) numbers explicit.
|2013-04-30
|DONE
|-
|JC
|to fix this (change "seven" to "four"). https://sourceforge.net/p/tei/bugs/555/
|2013-04-30
|LB Fixed before I had a chance to.
|-
|JC
|get back in touch with SIG conveners to encourage them to become active.
|2013-05-31
|DONE
|-
|JC
|Inform CMC SIG of their acceptance.
|2013-04-30
|DONE
|-
|JC
|Decide on deadlines for actions, but add them to the wiki not official minutes.
|2013-04-22
|DONE!
|-
|JC
|Schedule next teleconference.
|2013-05-17
|PENDING
|-
|JC
|to prod PB on all tickets assigned to him.
|2013-05-31
|PENDING
|-
|JC
|Ensure minutes are tidied up, posted online, summarised and that summary posted to TEI-L.
|2013-04-30
|DONE
|-
|JC and LB
|specification and estimated cost for new web Roma, etc.
|2013-05-31
|PENDING
|-
|JC and SB
|to encourage Piotr to get some people into a room in Rome to discuss this(?). SB will attend to push the more generic viewpoint.
|2013-05-31
|PENDING
|-
|KH
|to email Council to solicit volunteers for TEI Google work, and provide a link to the samples again.
|2013-04-30
|DONE
|-
|KH
|to go through recent soft and hard deprecations and decide whether they're correct (hard) or not, to remove @status and add @validUntil attribute.
|2013-05-31
|[[Practices_no_longer_recommended_or_now_deprecated|Plan of action with questions for others]]
|-
|KH
|to address the original issue at his leisure. https://sourceforge.net/p/tei/bugs/496/
|2013-05-31
|
|-
|KH
|to close ticket wontfix. https://sourceforge.net/p/tei/bugs/493/
|2013-04-30
|DONE
|-
|KH
|to implement the wording changes. https://sourceforge.net/p/tei/bugs/541/
|2013-05-31
|
|-
|KH
|change <idno> to <ref> or <pointer> as appropriate. The criterion to apply is whether the URL in question is an identifier or a link.
|2013-05-31
|
|-
|KH
|to add text to tcw24. Will look at how things are written in the introductory section about terminology. See if it needs adjustment. https://sourceforge.net/p/tei/bugs/548/
|2013-05-31
|
|-
|KH
|look for <note> near <egXML>, see which are just URL, change them to citations. KH will update tcw20. https://sourceforge.net/p/tei/bugs/527/
|2013-05-31
|
|-
|KH
| to complete the ticket and close. https://sourceforge.net/p/tei/bugs/288/
|2013-05-17
|
|-
|LB
|to liaise with Mr Schmidt re audio and video ODD.
|2013-05-31
|Discussion has been active and work is progressing on the google doc : some FRs will be appearing shortly
|-
|LB
|to implement ticket fr 437 https://sourceforge.net/p/tei/feature-requests/437/
|2013-05-31
|done
|-
|LB
|specification and estimated cost for OmegaT
|2013-05-31
|"quick hack" has been done (by Frederic Glorieux) to enable testing but it's not clear how much extra work would be needed to make this usable
|-
|LB
|will request examples of use of @corresp on TEI-L to investigate looser uses
|2013-05-31
|done 2013-06-17
|-
|LB
|look into this and will clarify the note in element spec for publicationStmt to no longer imply that order of publisher, place of publication, etc. is mandatory if you use <p> inside of <publicationStmt>.
|2013-05-31
|Done
|-
|LB
|Draft a message to TEI-L asking people to encode just a few samples by emailing back to TEI-L as a interim measure.
|2013-05-31
|Dunno what this is about. divliminal maybe?
|-
|LB and MH
|Suggest idea of breaking up the chapters, <divs> into files with FlorenceC, report back on desirability or lack thereof. MH: suggests that there would be Canadian contributors to a French translation if that gets off the ground. MH to liaise or introduce them to FlorenceC
|2013-04-30
|FC has no opinion on the subject of breaking chapters but work is in hand; meanwhile I have received rough Fr translations of 4 or 5 other chapters from Henri Hudrisier. Not sure where to go with these.
|-
|LB/PS/KH/MH (Div.liminal working group)
|to build the survey application for community markup method.
|2013-08-31
|
|-
|MH
|to implement https://sourceforge.net/p/tei/feature-requests/446/
|2013-05-31
|Done by rev 11882.
|-
|MH
|to contact JM and resolve the ticket https://sourceforge.net/p/tei/feature-requests/402/ one way or the other.
|2013-05-17
|Done in rev 12023.
|-
|MH
|to implement a draft of a new combined TOC and allow Council to comment https://sourceforge.net/p/tei/feature-requests/421/
|2013-05-31
|In progress. Pilot page created, waiting for feedback from Council.
|-
|MH
|to come up with a very concrete set of use cases for groups of elements and make very specific arguments for their needing @resp. https://sourceforge.net/p/tei/feature-requests/443/
|2013-05-17
|
|-
|MH
|to carry the remaining issues forward with Lou and Laurent to help as needed. https://sourceforge.net/p/tei/bugs/515/
|2013-05-31
|
|-
|MH
|to remove @scheme from <rendition> and replace it with the class; also it will then pick up the new @schemeVersion. https://sourceforge.net/p/tei/bugs/539/
|2013-05-31
|Done by rev 11880.
|-
|MH
|investigate where we say these kinds of things and find a way to implement in XSLT, insert it into the make file so that it generates a <div> in a file, and XInclude that file into the first Guidelines chapter. https://sourceforge.net/p/tei/bugs/512/
|2013-07-31
|Done in various revs by 2013-04-26, and documented in http://www.tei-c.org/Activities/Council/Working/tcw20.xml#body.1_div.3. Ticket closed 2013-05-15.
|-
|MH
|Change our practice in the use of list/@type to @rend in the Guidelines (for values of "simple", "ordered" and "bulleted"). https://sourceforge.net/p/tei/bugs/460/
|2013-04-30
|Done in various revs, including work by SB on Stylesheets.
|-
|MH
|Create a proposal for new recommendations regarding the use of list/@type and list/@rend. https://sourceforge.net/p/tei/bugs/460/
|2013-04-30
|Done 2013-04-23 (on the ticket)
|-
|MH
|Summarize to tei-council mailing list the text-directionality proposals and share the slides.
|2013-04-30
|Done 2013-04-25
|-
|PS
|make new example for the <listOrg> section ND.html#NDORG. Add another example to the element spec for <listOrg> that refers to more typical listorgs. https://sourceforge.net/p/tei/bugs/558/
|2013-05-17
|
|-
|PS
|Select ~6-10 samples for div.liminal which evince the confusions we want help with.
|2013-05-17
|
|-
|RW
|to add proposed wording on <substJoin> to guidelines (and look for photograph of MS). https://sourceforge.net/p/tei/feature-requests/448/ (update to text is already done; remains to be seen whether the image can be found)
|2013-05-17
|DONE
|-
|RW
|Fix https://sourceforge.net/p/tei/bugs/557/
|2013-04-30
|DONE at revision 11890
|-
|RW and BB
|to categorize the table of attributes without examples by adding a column with priorities of high, medium and low.
|2013-05-31
|
|-
|SB
|send KH details about TEI-PB list [done 2013-04-21]
|2013-04-30
|DONE
|-
|SB
|to improve the elementSpec desc and add one or more examples. https://sourceforge.net/p/tei/feature-requests/443/
|2013-05-31
|
|-
|SB
|create @validUntil as a class and write Schematron checks for deprecations.
|2013-05-17
|Mostly done — see post to Council list “new validUntil=” of 2013-05-16 15:27
|-
|SB
|to rename the Specs-Unused directory to Defunct, and move the SH file into it.
|2013-05-17
|done
|-
|SB
|to implement the current wording suggested above (See Minutes), as an interim measure. https://sourceforge.net/p/tei/bugs/543/
|2013-05-31
|
|-
|SB
|make <ptr>, <ref> consistent in component parts of <biblStruct>
|2013-05-31
|
|-
|SB
|remove our own dis-recommended use of <idno> in the bibliography
|2013-05-31
|
|-
|SB
|to implement https://sourceforge.net/p/tei/bugs/527/
|2013-05-31
|
|-
|SB
|add new tickets for the data.enumerated and valItem/@ident needing to be data.word not rng:text and xs:NCname, respectively.
|2013-05-31
|
|-
|SB
|post @rend, @rendition, @style class FR
|2013-04-30
|
|-
|SB and EM
|specification and estimated cost for oxygen front end for ODD.
|2013-05-31
|
|-
|SR
|to continue work on separating the Stylesheets from the guidelines into separate projects and solve problems with the Guidelines build process as a consumer of these. Any separation should be concentrating on making the latter more amenable to community development, reporting on back to Council.
|2013-05-17
|
|-
|SR
|to move the prose re <equiv/> from the core chapter into the tagdocs chapter, and tidy up. https://sourceforge.net/p/tei/bugs/516/
|2013-05-31
|DONE
|-
|SR
|to rewrite the paragraph again, to address other comments on the ticket. https://sourceforge.net/p/tei/bugs/549/
|2013-05-31
|DONE
|-
|SR
|rewrite the paragraph https://sourceforge.net/p/tei/bugs/550/
|2013-05-31
|DONE
|-
|SR
|when he gets the answer, he'll fix it, and definitive response will be sent to Jens. https://sourceforge.net/p/tei/bugs/560/
|2013-04-30
|DONE
|-
|SR
|Circulate ODD-related development papers to Council for comment
|2013-05-31
|DONE
|-
|SR and JC
|to investigate dates for next Council meeting, and set up a Doodle Poll.
|2013-05-31
|
|}
[[Category:Council]]

AnnArbor2012-Actions

2013-04-11T13:31:46Z

RebeccaWelzenbach:

A list of actions, those responsible, and what has been done about them from Ann Arbor 2012 face to face meeting of TEI Technical Council

{|class="wikitable"
|Who
|What
|Result
|-
|KH, LB, PS, and JC
|Get more examples from Ranjith of the current state of the output so that we can calculate some statistics on accuracy, and encourage Google towards making this output format public.
|samples sent to tei-council on 2012-06-28
|-
|SR
|will convert the EEBO-TCP <byline> to <signed> , which solves the issue of the EEBO-TCP import; the broader issue of <figure> will be addressed in the discussion of <floatingDiv> later.
|done
|-
|SR
|Add <trailer> to att.typed
|done
|-
|RW, JC
|http://purl.org/tei/bug/3480609 RW will check TEI documents and outputs to confirm everything licensed CC+BY and BSD2Clause (not CC+BY+SA or otherwise), and will report back about any inconsistencies. JC will close the bug, and a new one will be opened for any issues which emerge.
|done (RW investigating others--in progress, but won't be done before the 6/15 release. rw)
|-
|MH, JC
|http://purl.org/tei/bug/3472477 MH to implement change of IDs in output of guidelines
|Not for June 2012 release. I've had one shot at this and failed. I will try again when I have time, but it's not release-blocking.
|-
|MH, RW
|http://purl.org/tei/bug/3471119 MH will implement the consensus (no spaces around em dashes used parenthetically). RW will create the styleguide document with help from KH who knows the CMS system already. The text style guide will be deleted.
|done
|-
|JC, KH
|http://purl.org/tei/bug/3395448 JC will try to discover whether Virginia is technically still a partner or not. When it’s resolved, KH will implement any changes to the website.
|done
|-
|JC, MH
|http://purl.org/tei/fr/3511134 JC and MH will conspire to implement an html:@id for attributes in HTML Guidelines output in the stylesheets.
|Done in rev 10655.
|-
|KH
|http://purl.org/tei/fr/3437509 KH will review the whole thread and make a recommendation about the form of @ref, and make the soft deprecation changes to the Guidelines; these will be reviewed by LB.
|done
|-
|SR, PB
|http://purl.org/tei/fr/3432520 Finish implementing standard attributes referring to ISOCAT
|done
|-
|PB
|http://purl.org/tei/fr/3046288 PB will contact LR and ask him to provide further examples.
|done
|-
|KH
|http://purl.org/tei/fr/3041605 KH to close ticket
|done
|-
|JC
|http://purl.org/tei/bug/3497369 (JC) Strike the sentence that’s under discussion, because then the paragraph is less confusing. We should also add a new section (12.2.4), which explains that you don’t have to use ids in @from and @to; you can also use any URIs and XPointers with TEI XPointer schemes.
|Done
|-
|MH
|http://purl.org/tei/bug/3497356 MH will ask the submitter (and the TEI-L, pointing to the ticket) for any examples of the use of <div> which suggest that <listApp> might be useful (for instance, organization of <apps> into multiple <div> s with @type).
|The elementSpec for <listApp> has been completed, with an example provided by SOAS, and a brief explanation has been added to the TC chapter as of rev 10719. The ticket is still open pending review by Council of the changes, but it can be closed if everyone is happy.
|-
|LB
|http://purl.org/tei/bug/3496998 LB will add an additional example of how to combine <lacunaEnd> inside a <rdg> . Ticket will be closed.
|done
|-
|KH
|http://purl.org/tei/bug/3475748 KH to implement
|done
|-
|SR to coordinate, KH and GB to assist
|http://purl.org/tei/bug/3440771
*document how to point from a <geo> to the <geoDecl> in order to indicate which coordinate system is being used.
*Remove from the Guidelines the statement that “All uses of geo within a document are required to use the same coordinate system.”
*edit the definition of <location> to say something like “defines the location of a place as *one or more* sets of geographical coordinates...” to indicate that more than one system may be used at once
clarify relationship between <location> and <geo> in the prose of the Guidelines
|done
|-
|LB
|http://purl.org/tei/bug/3458222 LB will add <pc> to pPart.edit and revise the prose accordingly
|done (but see note on ticket -- it's a matter of making <pc> reference pPart.edit, not changing its membership)
|-
|MH
|http://purl.org/tei/bug/3500088 MH to re-visit to determine what's unclear and correct Guidelines.
|Done in rev 10481.
|-
|SR
|http://purl.org/tei/fr/3423686 Sebastian to nag Ontology SIG
|done, tho no resolution
|-
|PB
|http://purl.org/tei/fr/3288293 PB will add a new attribute to att.pointing, called @targetLang.
|done
|-
|JC
|http://purl.org/tei/fr/2724997 and http://purl.org/tei/fr/2507305 linking audio/video; JC will write to TEI-L asking for people who are interested in this area to get in touch. He will run the message by Council first. These people will join a Council working group to come back with a consistent proposal to be discussed later at this meeting.
| (Not release-blocking) -- Postponed until after LB reports on meeting covering this.
|-
|MH, SR, LB
|MH will write a new section for “How to edit the Guidelines” which explains TEI testing framework in more detail; this will then be checked by SR and LB.
|Partially done 2012-09-06. A section on adding a Schematron constraint, along with tests for it, has been inserted into tcw20.xml, but is currently commented out because the CMS can't render it.
|-
|LB, MH
|LB and MH to make sure a new-style inclusion TEI Lite ODD is up to date, regenerate schemas and update prose to match. The result should be packaged and archived as a stable and unchanging resource.
|LB has reworked TEI Lite, using inclusion. Council has not yet decided on how it should be archived and/or maintained; see MH's email to council 2012-08-09 for a summary of options being considered.
|-
|KH, LB, MH
|KH will collaborate with LB and MH to carry out the same process of freezing with Tite.
|
|-
|KH
|KH will make the Best Practices for TEI in Libraries customization available through the TEI website (we will not incorporate it into our build process because it’s too restrictive); the document itself will be mined for good ideas, and turned into a set of recommendations for changes to the Guidelines. KH to submit tickets for items to be added to the main Guidelines, since most of the items are likely to be independent and can be assessed separately.
|added as community customization, [[Incorporating BP into P5|adding tickets is pending]]
|-
|MH
|http://purl.org/tei/bug/3496958 (MH) We leave the content model alone (it’s horrible), but we use this as an example for Council to collaborate on the creation of one or more Schematron constraints which will enforce the presence of at least one <rdg> , to everyone’s edification.
|Schematron constraint added, but wrote to Council to check that's what should have been done given comments on ticket (which is still open).
|-
|JC
|http://purl.org/tei/bug/3496954 No action required; JC to close ticket.
|done
|-
|LB
|http://purl.org/tei/bug/3496951 LB to create att.witnessed for @wit on <rdg> and <lem> and remove @wit from <rdgGrp>
|done at rev 10243
|-
|GB
|http://purl.org/tei/bug/3496949 GB will review the particular example mentioned on the ticket, and revise and expand it: firstly, use a straightforward witness; secondly add an example for the "unattested" case.
|(Needs more discussion--or someone else to implement)
|-
|JC
|http://purl.org/tei/fr/3490054 JC will close ticket with won't fix suggesting it for P6
|done
|-
|JC
|Start wiki page on P6 development ideas http://wiki.tei-c.org/index.php/P6-dev
|done
|-
|SY
|SY will send an email to tei-l to encourage people to add their docs to the samples page to keep open the statistical approach in the long term.
|done
|-
|MH
|MH look at existing pages for attribute classes and see if there are any examples, try adding an example to att.ascribed class spec to see if it works
|Done. Example for @who added to att.ascribed.xml in rev 10491.
|-
|SR
|SR Sebastian will "show all examples" so that at the top it lists examples from the appropriate chapter, and links to that chapter.
|done
|-
|MH
|MH to create a wiki page to coordinate adding examples to attribute classes. Since most attribute classes do not have examples, all of us should generate examples to be added to attribute class pages.
|Done. Page is at [[AttsWithoutEgs]]
|-
|SR
|change build process so that you can't build without examples on attribute classes (once we've actually added examples to [[AttsWithoutEgs|those missing them]])
|
|-
|MH
|http://purl.org/tei/fr/3434990 MH will write a Schematron rule requiring that <lg> contains <l> , <lg> , or <gap>
|Done 2012-06-17, in rev 10522. A Schematron test has been added. Documentation on how to add a Schematron constraint, and tests for it, have been added to tcw20.xml, but it's currently commented out because the CMS XSLT can't handle the use of egXML.
|-
|SR
|http://purl.org/tei/fr/3305016 SR will implement the content model proposed by KH on SF
|done
|-
|GB
|http://purl.org/tei/fr/3416130 GB will survey the guidelines to see what kind of changes <certainty> within milestone elements would involve. He will report back via email, unless there is great disagreement the FR should be approved and implement. If there is disagreement, address at our next teleconference
|Survey done and Council emailed.
|-
|JC
|http://purl.org/tei/fr/3416130 JC will update the ticket in sourceforge to assign to GB and add a note about our decided action
|done
|-
|JC
|macro.paraContent out of place in <gram> etc [cf <u> discussion] link to ticket is broken, so group E did not discuss;
Action: JC to find out what happened to this ticket.
|JC: Found ticket at http://purl.org/tei/bug/3376863 needs more discussion.
|-
|KH
|http://purl.org/tei/fr/3500566 Implement proposal 'a' on SF ticket
|done
|-
|KH (was GB)
|http://purl.org/tei/fr/3497079 GB to write a comment on the ticket giving examples of citations that would be problematic or confusing according to this proposal. Paul can also provide example citations from his U-M CV project. Kevin will discuss with Gabby and incorporate marked-up examples into proposal and revise proposal if appropriate. Leave ticket open for now
|GB commented. Kevin has responded, and after some discussion this ticket has been closed and two new ones created.
|-
|JC
|http://purl.org/tei/fr/3440977 Agreed: Suggest LR to implement. JC will contact him and report back to us if he will not implement.
|Done.
|-
|KH
|http://purl.org/tei/fr/2493417 Agreed and implemented but KH to add more examples/prose
|done
|-
|KH
|http://purl.org/tei/fr/3480057 KH to close
|done
|-
|KH (was MH)
|http://purl.org/tei/bugs/3439587 MH will revise definition of <titleStmt> to no longer imply responsibility for intellectual content only. MH will also investigate adding <distributor> and <publisher> to model.respLike.
|<titleStmt> changes done by MH. Issue of <distributor> and <publisher> remains outstanding and is a bit messy. The ticket has now been assigned by JC to KH. JC and KH have completed it.
|-
|RW
|http://purl.org/tei/fr/3496494 RW will adapt defintion of <span> to take better wording from 17.3
|done on 2012-01-15
|-
|LB
|http://purl.org/tei/fr/3495987 LB will ask Laurent for examples in case we are assuming incorrectly and will look at TEI-L archives.
|
|-
|LB
|http://purl.org/tei/fr/2834511 LB will add proposed Schematron rules but not add any other elements without clear use cases.
|
|-
|SR
|http://purl.org/tei/fr/3291540 SR will take the ticket. We’ll leave it to SR to decide which of the second list of elements should be included as well. Sebastian will send a list to TEI-L so people could comment on any elements where it would be removed.
|Reassigned to GB at following F2F meeting.
|-
|SR
|http://purl.org/tei/fr/3284816 SR to implement.
|did faith. Reassigned to JC at following F2F meeting.
|-
|SR
|http://purl.org/tei/fr/3415801 Allow modification of attributes belonging to a class; SR will implement (in long-term).
|
|-
|LB
|http://purl.org/tei/fr/3118435 LB to close ticket
|done
|-
|SR
|http://purl.org/tei/fr/3426828 SR to close this ticket noting that requestor hasn’t responded.
|done
|-
|MH
|http://purl.org/tei/fr/1650195 MH to implement adding <schemaSpec> to model.encodingDescPart.
|Done in revs 10314-10317. Ticket closed.
|-
|JC
|FloatingText proposal: JC will reply to the message on TEI-L: In light of the current text and examples in the Guidelines on <floatingText> and <spGrp> , we’d like examples of proposed “floating divs” and how they would differ from <floatingText>s.
|Done
|-
|LB, KH, BB, PS
|http://purl.org/tei/bug/3439980 LB to chair an ad hoc council working group on div-liminal to report back on this before next face2face, KH, LB, and PS to be members, others as necessary.
|PS has produced list of samples but nothing done since.
|-
|SR, LB, MH, PB
|Audio/Video Facsimiles -- Working group to be chaired by SR, with LB, MH, and possibly PB; to approach TEI-L and others doing work in this area to get outside expertise; an initial proposal or detailed report of progress at next FTF with status reports at teleconferences.
|Laurent is coordinating a new ISO workgroup in this area "the idea is to have a TEI customization as a self-standing ISO document that will bring together the heterogeneous format we have in ELAN, Esmeralda, Transcriber, ANVIL, etc. For the time being, knowing Thomas [Schmidt]'s paper by heart is a good start since he introduced most of the core concepts." and there will be a meeting in Berlin Nov 22 which LB plans to attend
|-
|MH, GB, SY
|MH will chair this working group on private URI schemes and their documention, bring in GB, SY, and outside people suggested by GB. They will develop concrete proposals for next FTF meeting with status reports at teleconferences.
|Work underway. Description of [[XPointer|current state of XPointer play|XPointer]] and list of [[Stand-off use cases]] done. Use cases circulated to TEI-L for consultation.
|-
|MH
|Private Uri Schemes (split from preceding): the issue of Private Uri Schemes, and a method of documenting their use, is not really part of the TEI Pointers issue at all.
|A proposal is being developed here: http://wiki.tei-c.org/index.php/Private_URI_Schemes (Have Matteo Romanello, Sebastian Heath, etc. been invited to comment on this?)
|-
|JC
|James will prod the critical apparatus working group before next teleconference.
|(Done, but will do again)
|-
|JC
|JC to produce a Council meeting/telco checklist on TEI-C Wiki to ensure we don't forget steps (like asking SIGs if they have technical things they want to report)
|Done
|-
|SY, LB, PB
|UIMA, GATE and other tools. SY will follow up offline w/ LB, PB; PB will put SY in touch with others working in UIMA and interested in converting to TEI;PB and SY report back to Council on progress by next FTF
|
|-
|LB, RW
|http://purl.org/tei/bugs/3454814 LB will write up guidelines for purging comments and distribute to TEI-Council list, including describing first passes to deal with low-hanging fruit and suggested format for how we should comment going forward from there, work of reviewing and purging comments or turning them into notes will be divided among council members. RW will incorporate language from LB’s guidelines into the style guide when appropriate
|Done?
|-
|MH
|http://purl.org/tei/bugs/3454803 MH will compare Chapter CH against the latest version of BCP 47 for inconsistencies
|Done in revs 10650 through 10652 (2012-07-08).
|-
|MH
|Create new Jenkins build script for Ubuntu 12.04 server.
|Done 2012-06-13.
|-
|SR, KH
|http://purl.org/tei/bugs/3432216 SR: double check FM1 to see if list of translators is up to date; KH will add this policy to the “how to edit the guidelines” working paper
|tcw20 now says to leave @version attribute unchanged. Korean translator name added to FM1
|-
|PS, RW
|http://purl.org/tei/bugs/3223636 Expand our explanation of xml:space in the Guidelines:
* in note: expand to acknowledge that many parsers may not handle xml:space properly
* clarify definition of xml:space’s “default” value to match the XML spec (that is, “whatever the processor would normally do)
* remove sentence in prose of guidelines in chapter 22 "the global @xml:space is available to indicate that white space should be preserved within the content of these elements"
|Done
|-
|SR
|http://purl.org/tei/bugs/3393781 SR per LB’s comment on Sourceforge: Agreed to rename @version in att.translatable as @versionDate and give it a date datatype. We don’t want all the possibilities of att.datable.
|done
|-
|JC
|JC to add TEI Sourceforge site to the TEI category so all TEI sourceforge projects can be located at once
|done
|}

[[Category:Council]]

AnnArbor2012-Actions

2012-09-19T08:48:17Z

RebeccaWelzenbach:

A list of actions, those responsible, and what has been done about them from Ann Arbor 2012 face to face meeting of TEI Technical Council

{|class="wikitable"
|Who
|What
|Result
|-
|KH, LB, PS, and JC
|Get more examples from Ranjith of the current state of the output so that we can calculate some statistics on accuracy, and encourage Google towards making this output format public.
|samples sent to tei-council on 2012-06-28
|-
|SR
|will convert the EEBO-TCP <byline> to <signed> , which solves the issue of the EEBO-TCP import; the broader issue of <figure> will be addressed in the discussion of <floatingDiv> later.
|done
|-
|SR
|Add <trailer> to att.typed
|done
|-
|RW, JC
|http://purl.org/tei/bug/3480609 RW will check TEI documents and outputs to confirm everything licensed CC+BY and BSD2Clause (not CC+BY+SA or otherwise), and will report back about any inconsistencies. JC will close the bug, and a new one will be opened for any issues which emerge.
|done (RW investigating others--in progress, but won't be done before the 6/15 release. rw)
|-
|MH, JC
|http://purl.org/tei/bug/3472477 MH to implement change of IDs in output of guidelines
|Not for June 2012 release. I've had one shot at this and failed. I will try again when I have time, but it's not release-blocking.
|-
|MH, RW
|http://purl.org/tei/bug/3471119 MH will implement the consensus (no spaces around em dashes used parenthetically). RW will create the styleguide document with help from KH who knows the CMS system already. The text style guide will be deleted.
|done
|-
|JC, KH
|http://purl.org/tei/bug/3395448 JC will try to discover whether Virginia is technically still a partner or not. When it’s resolved, KH will implement any changes to the website.
|Pending
|-
|JC, MH
|http://purl.org/tei/fr/3511134 JC and MH will conspire to implement an html:@id for attributes in HTML Guidelines output in the stylesheets.
|Done in rev 10655.
|-
|KH
|http://purl.org/tei/fr/3437509 KH will review the whole thread and make a recommendation about the form of @ref, and make the soft deprecation changes to the Guidelines; these will be reviewed by LB.
|done
|-
|SR, PB
|http://purl.org/tei/fr/3432520 Finish implementing standard attributes referring to ISOCAT
|done
|-
|PB
|http://purl.org/tei/fr/3046288 PB will contact LR and ask him to provide further examples.
|done
|-
|KH
|http://purl.org/tei/fr/3041605 KH to close ticket
|done
|-
|JC
|http://purl.org/tei/bug/3497369 (JC) Strike the sentence that’s under discussion, because then the paragraph is less confusing. We should also add a new section (12.2.4), which explains that you don’t have to use ids in @from and @to; you can also use any URIs and XPointers with TEI XPointer schemes.
|Done
|-
|MH
|http://purl.org/tei/bug/3497356 MH will ask the submitter (and the TEI-L, pointing to the ticket) for any examples of the use of <div> which suggest that <listApp> might be useful (for instance, organization of <apps> into multiple <div> s with @type).
|The elementSpec for <listApp> has been completed, with an example provided by SOAS, and a brief explanation has been added to the TC chapter as of rev 10719. The ticket is still open pending review by Council of the changes, but it can be closed if everyone is happy.
|-
|LB
|http://purl.org/tei/bug/3496998 LB will add an additional example of how to combine <lacunaEnd> inside a <rdg> . Ticket will be closed.
|done
|-
|KH
|http://purl.org/tei/bug/3475748 KH to implement
|done
|-
|SR to coordinate, KH and GB to assist
|http://purl.org/tei/bug/3440771
*document how to point from a <geo> to the <geoDecl> in order to indicate which coordinate system is being used.
*Remove from the Guidelines the statement that “All uses of geo within a document are required to use the same coordinate system.”
*edit the definition of <location> to say something like “defines the location of a place as *one or more* sets of geographical coordinates...” to indicate that more than one system may be used at once
clarify relationship between <location> and <geo> in the prose of the Guidelines
|
|-
|LB
|http://purl.org/tei/bug/3458222 LB will add <pc> to pPart.edit and revise the prose accordingly
|done (but see note on ticket -- it's a matter of making <pc> reference pPart.edit, not changing its membership)
|-
|MH
|http://purl.org/tei/bug/3500088 MH to re-visit to determine what's unclear and correct Guidelines.
|Done in rev 10481.
|-
|SR
|http://purl.org/tei/fr/3423686 Sebastian to nag Ontology SIG
|done, tho no resolution
|-
|PB
|http://purl.org/tei/fr/3288293 PB will add a new attribute to att.pointing, called @targetLang.
|done
|-
|JC
|http://purl.org/tei/fr/2724997 and http://purl.org/tei/fr/2507305 linking audio/video; JC will write to TEI-L asking for people who are interested in this area to get in touch. He will run the message by Council first. These people will join a Council working group to come back with a consistent proposal to be discussed later at this meeting.
| (Not release-blocking) -- Postponed until after LB reports on meeting covering this.
|-
|MH, SR, LB
|MH will write a new section for “How to edit the Guidelines” which explains TEI testing framework in more detail; this will then be checked by SR and LB.
|Partially done 2012-09-06. A section on adding a Schematron constraint, along with tests for it, has been inserted into tcw20.xml, but is currently commented out because the CMS can't render it.
|-
|LB, MH
|LB and MH to make sure a new-style inclusion TEI Lite ODD is up to date, regenerate schemas and update prose to match. The result should be packaged and archived as a stable and unchanging resource.
|LB has reworked TEI Lite, using inclusion. Council has not yet decided on how it should be archived and/or maintained; see MH's email to council 2012-08-09 for a summary of options being considered.
|-
|KH, LB, MH
|KH will collaborate with LB and MH to carry out the same process of freezing with Tite.
|
|-
|KH
|KH will make the Best Practices for TEI in Libraries customization available through the TEI website (we will not incorporate it into our build process because it’s too restrictive); the document itself will be mined for good ideas, and turned into a set of recommendations for changes to the Guidelines. KH to submit tickets for items to be added to the main Guidelines, since most of the items are likely to be independent and can be assessed separately.
|added as community customization
|-
|MH
|http://purl.org/tei/bug/3496958 (MH) We leave the content model alone (it’s horrible), but we use this as an example for Council to collaborate on the creation of one or more Schematron constraints which will enforce the presence of at least one <rdg> , to everyone’s edification.
|Schematron constraint added, but wrote to Council to check that's what should have been done given comments on ticket (which is still open).
|-
|JC
|http://purl.org/tei/bug/3496954 No action required; JC to close ticket.
|done
|-
|LB
|http://purl.org/tei/bug/3496951 LB to create att.witnessed for @wit on <rdg> and <lem> and remove @wit from <rdgGrp>
|done at rev 10243
|-
|GB
|http://purl.org/tei/bug/3496949 GB will review the particular example mentioned on the ticket, and revise and expand it: firstly, use a straightforward witness; secondly add an example for the "unattested" case.
|(Needs more discussion--or someone else to implement)
|-
|JC
|http://purl.org/tei/fr/3490054 JC will close ticket with won't fix suggesting it for P6
|done
|-
|JC
|Start wiki page on P6 development ideas http://wiki.tei-c.org/index.php/P6-dev
|done
|-
|SY
|SY will send an email to tei-l to encourage people to add their docs to the samples page to keep open the statistical approach in the long term.
|done
|-
|MH
|MH look at existing pages for attribute classes and see if there are any examples, try adding an example to att.ascribed class spec to see if it works
|Done. Example for @who added to att.ascribed.xml in rev 10491.
|-
|SR
|SR Sebastian will "show all examples" so that at the top it lists examples from the appropriate chapter, and links to that chapter.
|done
|-
|MH
|MH to create a wiki page to coordinate adding examples to attribute classes. Since most attribute classes do not have examples, all of us should generate examples to be added to attribute class pages.
|Done. Page is at [[AttsWithoutEgs#Attributes_without_an_example_in_their_elementSpec_OR_classSpec|AttsWithoutEgs]]
|-
|SR
|change build process so that you can't build without examples on attribute classes (this would have to be implemented later)
|
|-
|MH
|http://purl.org/tei/fr/3434990 MH will write a Schematron rule requiring that <lg> contains <l> , <lg> , or <gap>
|Done 2012-06-17, in rev 10522. A Schematron test has been added. Documentation on how to add a Schematron constraint, and tests for it, have been added to tcw20.xml, but it's currently commented out because the CMS XSLT can't handle the use of egXML.
|-
|SR
|http://purl.org/tei/fr/3305016 SR will implement the content model proposed by KH on SF
|done
|-
|GB
|http://purl.org/tei/fr/3416130 GB will survey the guidelines to see what kind of changes <certainty> within milestone elements would involve. He will report back via email, unless there is great disagreement the FR should be approved and implement. If there is disagreement, address at our next teleconference
|Survey done and Council emailed.
|-
|JC
|http://purl.org/tei/fr/3416130 JC will update the ticket in sourceforge to assign to GB and add a note about our decided action
|done
|-
|JC
|macro.paraContent out of place in <gram> etc [cf <u> discussion] link to ticket is broken, so group E did not discuss;
Action: JC to find out what happened to this ticket.
|JC: Found ticket at http://purl.org/tei/bug/3376863 needs more discussion.
|-
|KH
|http://purl.org/tei/fr/3500566 Implement proposal 'a' on SF ticket
|done
|-
|KH (was GB)
|http://purl.org/tei/fr/3497079 GB to write a comment on the ticket giving examples of citations that would be problematic or confusing according to this proposal. Paul can also provide example citations from his U-M CV project. Kevin will discuss with Gabby and incorporate marked-up examples into proposal and revise proposal if appropriate. Leave ticket open for now
|GB commented. Kevin has responded, and after some discussion this ticket has been closed and two new ones created.
|-
|JC
|http://purl.org/tei/fr/3440977 Agreed: Suggest LR to implement. JC will contact him and report back to us if he will not implement.
|Done.
|-
|KH
|http://purl.org/tei/fr/2493417 Agreed and implemented but KH to add more examples/prose
|done
|-
|KH
|http://purl.org/tei/fr/3480057 KH to close
|done
|-
|KH (was MH)
|http://purl.org/tei/bugs/3439587 MH will revise definition of <titleStmt> to no longer imply responsibility for intellectual content only. MH will also investigate adding <distributor> and <publisher> to model.respLike.
|<titleStmt> changes done by MH. Issue of <distributor> and <publisher> remains outstanding and is a bit messy. The ticket has now been assigned by JC to KH.
|-
|RW
|http://purl.org/tei/fr/3496494 RW will adapt defintion of <span> to take better wording from 17.3
|
|-
|LB
|http://purl.org/tei/fr/3495987 LB will ask Laurent for examples in case we are assuming incorrectly and will look at TEI-L archives.
|
|-
|LB
|http://purl.org/tei/fr/2834511 LB will add proposed Schematron rules but not add any other elements without clear use cases.
|
|-
|SR
|http://purl.org/tei/fr/3291540 SR will take the ticket. We’ll leave it to SR to decide which of the second list of elements should be included as well. Sebastian will send a list to TEI-L so people could comment on any elements where it would be removed.
|
|-
|SR
|http://purl.org/tei/fr/3284816 SR to implement.
|did faith
|-
|SR
|http://purl.org/tei/fr/3415801 Allow modification of attributes belonging to a class; SR will implement (in long-term).
|
|-
|LB
|http://purl.org/tei/fr/3118435 LB to close ticket
|done
|-
|SR
|http://purl.org/tei/fr/3426828 SR to close this ticket noting that requestor hasn’t responded.
|done
|-
|MH
|http://purl.org/tei/fr/1650195 MH to implement adding <schemaSpec> to model.encodingDescPart.
|Done in revs 10314-10317. Ticket closed.
|-
|JC
|FloatingText proposal: JC will reply to the message on TEI-L: In light of the current text and examples in the Guidelines on <floatingText> and <spGrp> , we’d like examples of proposed “floating divs” and how they would differ from <floatingText>s.
|Done
|-
|LB, KH, BB, PS
|http://purl.org/tei/bug/3439980 LB to chair an ad hoc council working group on div-liminal to report back on this before next face2face, KH, LB, and PS to be members, others as necessary.
|PS has produced list of samples but nothing done since.
|-
|SR, LB, MH, PB
|Audio/Video Facsimiles -- Working group to be chaired by SR, with LB, MH, and possibly PB; to approach TEI-L and others doing work in this area to get outside expertise; an initial proposal or detailed report of progress at next FTF with status reports at teleconferences.
|Laurent is coordinating a new ISO workgroup in this area "the idea is to have a TEI customization as a self-standing ISO document that will bring together the heterogeneous format we have in ELAN, Esmeralda, Transcriber, ANVIL, etc. For the time being, knowing Thomas [Schmidt]'s paper by heart is a good start since he introduced most of the core concepts." and there will be a meeting in Berlin Nov 22 which LB plans to attend
|-
|MH, GB, SY
|MH will chair this working group on private URI schemes and their documention, bring in GB, SY, and outside people suggested by GB. They will develop concrete proposals for next FTF meeting with status reports at teleconferences.
|Work underway. Description of [[XPointer|current state of XPointer play|XPointer]] and list of [[Stand-off use cases]] done. Use cases circulated to TEI-L for consultation.
|-
|MH
|Private Uri Schemes (split from preceding): the issue of Private Uri Schemes, and a method of documenting their use, is not really part of the TEI Pointers issue at all.
|A proposal is being developed here: http://wiki.tei-c.org/index.php/Private_URI_Schemes (Have Matteo Romanello, Sebastian Heath, etc. been invited to comment on this?)
|-
|JC
|James will prod the critical apparatus working group before next teleconference.
|(Done, but will do again)
|-
|JC
|JC to produce a Council meeting/telco checklist on TEI-C Wiki to ensure we don't forget steps (like asking SIGs if they have technical things they want to report)
|Done
|-
|SY, LB, PB
|UIMA, GATE and other tools. SY will follow up offline w/ LB, PB; PB will put SY in touch with others working in UIMA and interested in converting to TEI;PB and SY report back to Council on progress by next FTF
|
|-
|LB, RW
|http://purl.org/tei/bugs/3454814 LB will write up guidelines for purging comments and distribute to TEI-Council list, including describing first passes to deal with low-hanging fruit and suggested format for how we should comment going forward from there, work of reviewing and purging comments or turning them into notes will be divided among council members. RW will incorporate language from LB’s guidelines into the style guide when appropriate
|Done?
|-
|MH
|http://purl.org/tei/bugs/3454803 MH will compare Chapter CH against the latest version of BCP 47 for inconsistencies
|Done in revs 10650 through 10652 (2012-07-08).
|-
|MH
|Create new Jenkins build script for Ubuntu 12.04 server.
|Done 2012-06-13.
|-
|SR, KH
|http://purl.org/tei/bugs/3432216 SR: double check FM1 to see if list of translators is up to date; KH will add this policy to the “how to edit the guidelines” working paper
|tcw20 now says to leave @version attribute unchanged. Korean translator name added to FM1
|-
|PS, RW
|http://purl.org/tei/bugs/3223636 Expand our explanation of xml:space in the Guidelines:
* in note: expand to acknowledge that many parsers may not handle xml:space properly
* clarify definition of xml:space’s “default” value to match the XML spec (that is, “whatever the processor would normally do)
* remove sentence in prose of guidelines in chapter 22 "the global @xml:space is available to indicate that white space should be preserved within the content of these elements"
|
|-
|SR
|http://purl.org/tei/bugs/3393781 SR per LB’s comment on Sourceforge: Agreed to rename @version in att.translatable as @versionDate and give it a date datatype. We don’t want all the possibilities of att.datable.
|done
|-
|JC
|JC to add TEI Sourceforge site to the TEI category so all TEI sourceforge projects can be located at once
|done
|}

AttsWithoutEgs

2012-08-17T19:20:43Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

List generated 2012-04-23T08:14:26.517-07:00

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
|-
|| 1 || absolute || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 2 || adj || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 3 || adjFrom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 4 || adjTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 5 || age || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-personGrp.html personGrp] || ||
|-
|| 6 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 7 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || BW ||
|-
|| 8 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 9 || ana || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.analytic.html att.global.analytic] || ||
|-
|| 10 || atLeast || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 11 || atMost || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 12 || attachment || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 13 || autoPrefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-content.html content] || ||
|-
|| 14 || baseTypes || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fsDecl.html fsDecl] || ||
|-
|| 15 || break || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.breaking.html att.breaking] || MDH || 2012-05-20
|-
|| 16 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss] || ||
|-
|| 17 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term] || ||
|-
|| 18 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ptr.html ptr] || ||
|-
|| 19 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ref.html ref] || ||
|-
|| 20 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 21 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 22 || cert || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || ||
|-
|| 23 || change || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.change.html att.global.change] || ||
|-
|| 24 || class || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-msContents.html msContents] || ||
|-
|| 25 || cols || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 26 || confidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 27 || contemporary || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-seal.html seal] || ||
|-
|| 28 || copyOf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 29 || corresp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || MDH || 2012-05-20
|-
|| 30 || datingMethod || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 31 || datingPoint || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 32 || decls || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declaring.html att.declaring] || ||
|-
|| 33 || default || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declarable.html att.declarable] || ||
|-
| 34 || defective || att.ms<nowiki/>Excerpt || ||
|-
|| 35 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 36 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 37 || dim || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || ||
|-
|| 38 || direct || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said] || MDH || 2012-05-21
|-
|| 39 || docLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 40 || domains || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 41 || dur || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.att.duration.w3c.html att.duration.w3c] || ||
|-
|| 42 || dur-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.duration.iso.html att.duration.iso] || ||
|-
|| 43 || encoding || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 44 || end || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 45 || enjamb || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.enjamb.html att.enjamb] || BW ||
|-
|| 46 || evaluate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.html att.pointing] || ||
|-
|| 47 || evidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 48 || except || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 49 || exclude || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 50 || expand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 51 || extent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-orth.html orth] || ||
|-
|| 52 || fVal || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-f.html f] || ||
|-
|| 53 || facs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.facs.html att.global.facs] || ||
|-
|| 54 || feats || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fs.html fs] || ||
|-
|| 55 || filter || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-equiv.html equiv] || ||
|-
|| 56 || flipping || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 57 || follow || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 58 || force || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 59 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || ||
|-
|| 60 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 61 || from-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 62 || from-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 63 || full || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 64 || function || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 65 || generate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classSpec.html classSpec] || ||
|-
|| 66 || gradual || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 67 || group || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 68 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 69 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 70 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || ||
|-
|| 71 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 72 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 73 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 74 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 75 || ident || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 76 || inst || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 77 || instant || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 78 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || SY || 2012-06-06
|-
|| 79 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classRef.html classRef] || ||
|-
|| 80 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-macroRef.html macroRef] || ||
|-
|| 81 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title] || ||
|-
|| 82 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sense.html sense] || ||
|-
|| 83 || loc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 84 || location || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 85 || lrx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 86 || lry || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 87 || material || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-supportDesc.html supportDesc] || ||
|-
|| 88 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 89 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 90 || medium || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 91 || mergedIn || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 92 || met || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 93 || method || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 94 || mimeType || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.internetMedia.html att.internetMedia] || ||
|-
|| 95 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 96 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 97 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classes.html classes] || ||
|-
|| 98 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 99 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.combinable.html att.combinable] || ||
|-
|| 100 || module || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 101 || new || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-handShift.html handShift] || ||
|-
|| 102 || next || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 103 || notAfter-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 104 || notAfter-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 105 || notBefore-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 106 || notBefore-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 107 || notation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pron.html pron] || ||
|-
|| 108 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 109 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 110 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attDef.html attDef] || ||
|-
|| 111 || nymRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 112 || opt || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 113 || optional || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fDecl.html fDecl] || ||
|-
|| 114 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 115 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 116 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 117 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attList.html attList] || ||
|-
|| 118 || orig || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 119 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 120 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 121 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ab.html ab] || ||
|-
|| 122 || parts || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-nym.html nym] || ||
|-
|| 123 || perf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tech.html tech] || ||
|-
|| 124 || period || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.html att.datable] || ||
|-
|| 125 || pre || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 126 || precision || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 127 || predeclare || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 128 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 129 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 130 || prev || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 131 || quantity || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 132 || real || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 133 || ref || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || ||
|-
|| 134 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || ||
|-
|| 135 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || ||
|-
|| 136 || rhyme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 137 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 138 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 139 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-org.html org] || ||
|-
|| 140 || rotate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone] || ||
|-
|| 141 || rows || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 142 || sameAs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 143 || sample || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 144 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 145 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 146 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-catRef.html catRef] || ||
|-
|| 147 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locus.html locus] || ||
|-
|| 148 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locusGrp.html locusGrp] || ||
|-
|| 149 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tag.html tag] || ||
|-
|| 150 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 151 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 152 || scribe || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 153 || scribeRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 154 || script || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 155 || scriptRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 156 || select || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 157 || seq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 158 || social || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 159 || sort || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 160 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 161 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.readFrom.html att.readFrom] || ||
|-
|| 162 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 163 || space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 164 || spanTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.spanning.html att.spanning] || ||
|-
|| 165 || split || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 166 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 167 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 168 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 169 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 170 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 171 || stdDeviation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-precision.html precision] || ||
|-
|| 172 || subtype || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || pfs ||
|-
|| 173 || synch || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 174 || targFunc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 175 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-change.html change] || ||
|-
|| 176 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-relatedItem.html relatedItem] || ||
|-
|| 177 || targetEnd || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-note.html note] || ||
|-
|| 178 || targetLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 179 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-link.html link] || ||
|-
|| 180 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-join.html join] || ||
|-
|| 181 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-alt.html alt] || ||
|-
|| 182 || time || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 183 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || ||
|-
|| 184 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 185 || to-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 186 || to-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 187 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 188 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || SY || 2012-06-06
|-
|| 189 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-q.html q] || ||
|-
|| 190 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-abbr.html abbr] || ||
|-
|| 191 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sound.html sound] || ||
|-
|| 192 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.entryLike.html att.entryLike] || | |
|-
|| 193 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-form.html form] || ||
|-
|| 194 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 195 || ulx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 196 || uly || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 197 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 198 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 199 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 200 || url || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 201 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 202 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || ||
|-
|| 203 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 204 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 205 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 206 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-eTree.html eTree] || ||
|-
|| 207 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-triangle.html triangle] || ||
|-
|| 208 || varSeq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 209 || version || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unicodeName.html unicodeName] || ||
|-
|| 210 || versionDate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.translatable.html att.translatable] || ||
|-
|| 211 || when || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-docDate.html docDate] || ||
|-
|| 212 || where || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html event] || ||
|-
|| 213 || who || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ascribed.html att.ascribed] || ||
|-
|| 214 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 215 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 216 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.rdgPart.html att.rdgPart] || ||
|-
|| 217 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.witnessed.html att.witnessed] || ||
|-
|| 218 || xml:base || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || || Appears to be done already
|-
|| 219 || xml:id || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] ||BW ||
|-
|| 220 || xml:lang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || SY || 2012-06-06
|-
|| 221 || xml:space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] ||BW ||
|}

AttsWithoutEgs

2012-08-17T02:05:55Z

RebeccaWelzenbach: /* Attributes without an example in their elementSpec OR classSpec */

The sourceforge ticket for this is http://purl.org/TEI/BUGS/3520704

== Attributes without an example in their elementSpec OR classSpec ==

List generated 2012-04-23T08:14:26.517-07:00

{| class="sortable" border="1" cellspacing="0" cellpadding="5" align="center"
! #
! Att name
! Defined in
! Assigned to
! Completed
|-
|| 1 || absolute || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 2 || adj || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 3 || adjFrom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 4 || adjTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 5 || age || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-personGrp.html personGrp] || ||
|-
|| 6 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 7 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || ||
|-
|| 8 || agent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 9 || ana || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.analytic.html att.global.analytic] || ||
|-
|| 10 || atLeast || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 11 || atMost || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 12 || attachment || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 13 || autoPrefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-content.html content] || ||
|-
|| 14 || baseTypes || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fsDecl.html fsDecl] || ||
|-
|| 15 || break || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.breaking.html att.breaking] || MDH || 2012-05-20
|-
|| 16 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss] || ||
|-
|| 17 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term] || ||
|-
|| 18 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ptr.html ptr] || ||
|-
|| 19 || cRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ref.html ref] || ||
|-
|| 20 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 21 || cause || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 22 || cert || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || ||
|-
|| 23 || change || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.change.html att.global.change] || ||
|-
|| 24 || class || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-msContents.html msContents] || ||
|-
|| 25 || cols || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 26 || confidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 27 || contemporary || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-seal.html seal] || ||
|-
|| 28 || copyOf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 29 || corresp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || MDH || 2012-05-20
|-
|| 30 || datingMethod || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 31 || datingPoint || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 32 || decls || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declaring.html att.declaring] || ||
|-
|| 33 || default || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.declarable.html att.declarable] || ||
|-
| 34 || defective || att.ms<nowiki/>Excerpt || ||
|-
|| 35 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 36 || degree || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || SY ||
|-
|| 37 || dim || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || ||
|-
|| 38 || direct || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said] || MDH || 2012-05-21
|-
|| 39 || docLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 40 || domains || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 41 || dur || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.att.duration.w3c.html att.duration.w3c] || ||
|-
|| 42 || dur-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.duration.iso.html att.duration.iso] || ||
|-
|| 43 || encoding || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 44 || end || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 45 || enjamb || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.enjamb.html att.enjamb] || ||
|-
|| 46 || evaluate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.html att.pointing] || ||
|-
|| 47 || evidence || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 48 || except || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 49 || exclude || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 50 || expand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 51 || extent || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-orth.html orth] || ||
|-
|| 52 || fVal || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-f.html f] || ||
|-
|| 53 || facs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.facs.html att.global.facs] || ||
|-
|| 54 || feats || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fs.html fs] || ||
|-
|| 55 || filter || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-equiv.html equiv] || ||
|-
|| 56 || flipping || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html surface] || ||
|-
|| 57 || follow || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 58 || force || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 59 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || ||
|-
|| 60 || from || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 61 || from-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 62 || from-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 63 || full || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 64 || function || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 65 || generate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classSpec.html classSpec] || ||
|-
|| 66 || gradual || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 67 || group || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 68 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.damaged.html att.damaged] || ||
|-
|| 69 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 70 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html gap] || ||
|-
|| 71 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html unclear] || ||
|-
|| 72 || hand || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 73 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 74 || height || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 75 || ident || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 76 || inst || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 77 || instant || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 78 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || SY || 2012-06-06
|-
|| 79 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classRef.html classRef] || ||
|-
|| 80 || key || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-macroRef.html macroRef] || ||
|-
|| 81 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title] || ||
|-
|| 82 || level || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sense.html sense] || ||
|-
|| 83 || loc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 84 || location || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 85 || lrx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 86 || lry || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 87 || material || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-supportDesc.html supportDesc] || ||
|-
|| 88 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 89 || max || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 90 || medium || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 91 || mergedIn || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 92 || met || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 93 || method || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 94 || mimeType || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.internetMedia.html att.internetMedia] || ||
|-
|| 95 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ranging.html att.ranging] || ||
|-
|| 96 || min || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 97 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-classes.html classes] || ||
|-
|| 98 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-memberOf.html memberOf] || ||
|-
|| 99 || mode || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.combinable.html att.combinable] || ||
|-
|| 100 || module || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 101 || new || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-handShift.html handShift] || ||
|-
|| 102 || next || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 103 || notAfter-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 104 || notAfter-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 105 || notBefore-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 106 || notBefore-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 107 || notation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pron.html pron] || ||
|-
|| 108 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 109 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 110 || ns || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attDef.html attDef] || ||
|-
|| 111 || nymRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 112 || opt || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 113 || optional || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-fDecl.html fDecl] || ||
|-
|| 114 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 115 || ord || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 116 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 117 || org || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-attList.html attList] || ||
|-
|| 118 || orig || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 119 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 120 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.segLike.html att.segLike] || ||
|-
|| 121 || part || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-ab.html ab] || ||
|-
|| 122 || parts || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-nym.html nym] || ||
|-
|| 123 || perf || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tech.html tech] || ||
|-
|| 124 || period || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.html att.datable] || ||
|-
|| 125 || pre || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 126 || precision || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 127 || predeclare || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 128 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 129 || prefix || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-elementSpec.html elementSpec] || ||
|-
|| 130 || prev || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 131 || quantity || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 132 || real || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 133 || ref || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.canonical.html att.canonical] || ||
|-
|| 134 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.responsibility.html att.responsibility] || ||
|-
|| 135 || resp || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-space.html space] || ||
|-
|| 136 || rhyme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.metrical.html att.metrical] || ||
|-
|| 137 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.naming.html att.naming] || ||
|-
|| 138 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 139 || role || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-org.html org] || ||
|-
|| 140 || rotate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html zone] || ||
|-
|| 141 || rows || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.tableDecoration.html att.tableDecoration] || pfs ||
|-
|| 142 || sameAs || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 143 || sample || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.divLike.html att.divLike] || ||
|-
|| 144 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 145 || scale || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 146 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-catRef.html catRef] || ||
|-
|| 147 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locus.html locus] || ||
|-
|| 148 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-locusGrp.html locusGrp] || ||
|-
|| 149 || scheme || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tag.html tag] || ||
|-
|| 150 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 151 || scope || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 152 || scribe || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 153 || scribeRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 154 || script || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 155 || scriptRef || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.handFeatures.html att.handFeatures] || ||
|-
|| 156 || select || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 157 || seq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 158 || social || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 159 || sort || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html att.personal] || ||
|-
|| 160 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.editLike.html att.editLike] || ||
|-
|| 161 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.readFrom.html att.readFrom] || ||
|-
|| 162 || source || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-writing.html writing] || ||
|-
|| 163 || space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 164 || spanTo || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.spanning.html att.spanning] || ||
|-
|| 165 || split || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 166 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.timed.html att.timed] || ||
|-
|| 167 || start || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 168 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.transcriptional.html att.transcriptional] || ||
|-
|| 169 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-correction.html correction] || ||
|-
|| 170 || status || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.identified.html att.identified] || ||
|-
|| 171 || stdDeviation || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-precision.html precision] || ||
|-
|| 172 || subtype || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || pfs ||
|-
|| 173 || synch || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.linking.html att.global.linking] || ||
|-
|| 174 || targFunc || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.pointing.group.html att.pointing.group] || ||
|-
|| 175 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-change.html change] || ||
|-
|| 176 || target || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-relatedItem.html relatedItem] || ||
|-
|| 177 || targetEnd || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-note.html note] || ||
|-
|| 178 || targetLang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-schemaSpec.html schemaSpec] || ||
|-
|| 179 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-link.html link] || ||
|-
|| 180 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-join.html join] || ||
|-
|| 181 || targets || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-alt.html alt] || ||
|-
|| 182 || time || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-distinct.html distinct] || ||
|-
|| 183 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c] || ||
|-
|| 184 || to || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-app.html app] || ||
|-
|| 185 || to-custom || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.custom.html att.datable.custom] || ||
|-
|| 186 || to-iso || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.iso.html att.datable.iso] || ||
|-
|| 187 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.interpLike.html att.interpLike] || ||
|-
|| 188 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.typed.html att.typed] || SY || 2012-06-06
|-
|| 189 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-q.html q] || ||
|-
|| 190 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-abbr.html abbr] || ||
|-
|| 191 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sound.html sound] || ||
|-
|| 192 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.entryLike.html att.entryLike] || | |
|-
|| 193 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-form.html form] || ||
|-
|| 194 || type || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 195 || ulx || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 196 || uly || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.coordinated.html att.coordinated] || ||
|-
|| 197 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.dimensions.html att.dimensions] || ||
|-
|| 198 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-when.html when] || ||
|-
|| 199 || unit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pc.html pc] || ||
|-
|| 200 || url || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html moduleRef] || ||
|-
|| 201 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.lexicographic.html att.lexicographic] || ||
|-
|| 202 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-node.html node] || ||
|-
|| 203 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-root.html root] || ||
|-
|| 204 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-iNode.html iNode] || ||
|-
|| 205 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-leaf.html leaf] || ||
|-
|| 206 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-eTree.html eTree] || ||
|-
|| 207 || value || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-triangle.html triangle] || ||
|-
|| 208 || varSeq || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.textCritical.html att.textCritical] || ||
|-
|| 209 || version || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unicodeName.html unicodeName] || ||
|-
|| 210 || versionDate || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.translatable.html att.translatable] || ||
|-
|| 211 || when || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-docDate.html docDate] || ||
|-
|| 212 || where || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html event] || ||
|-
|| 213 || who || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.ascribed.html att.ascribed] || ||
|-
|| 214 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-graphic.html graphic] || ||
|-
|| 215 || width || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-binaryObject.html binaryObject] || ||
|-
|| 216 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.rdgPart.html att.rdgPart] || ||
|-
|| 217 || wit || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.witnessed.html att.witnessed] || ||
|-
|| 218 || xml:base || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || || Appears to be done already
|-
|| 219 || xml:id || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || ||
|-
|| 220 || xml:lang || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || SY || 2012-06-06
|-
|| 221 || xml:space || [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.global.html att.global] || ||
|}

AnnArbor2012-Actions

2012-06-14T17:37:32Z

RebeccaWelzenbach:

A list of actions, those responsible, and what has been done about them from Ann Arbor 2012 face to face meeting of TEI Technical Council

{|class="wikitable"
|Who
|What
|Result
|-
|KH, LB, PS, and JC
|Get more examples from Ranjith of the current state of the output so that we can calculate some statistics on accuracy, and encourage Google towards making this output format public.
|done on 2012-04-23, but Kevin thought he'd wait till after the current push of implementing tickets to bring it up on tei-council
|-
|SR
|will convert the EEBO-TCP <byline> to <signed> , which solves the issue of the EEBO-TCP import; the broader issue of <figure> will be addressed in the discussion of <floatingDiv> later.
|done
|-
|SR
|Add <trailer> to att.typed
|done
|-
|RW, JC
|http://purl.org/tei/bug/3480609 RW will check TEI documents and outputs to confirm everything licensed CC+BY and BSD2Clause (not CC+BY+SA or otherwise), and will report back about any inconsistencies. JC will close the bug, and a new one will be opened for any issues which emerge.
|done (RW investigating others--in progress, but won't be done before the 6/15 release. rw)
|-
|MH
|http://purl.org/tei/bug/3472477 MH to implement change of IDs in output of guidelines
|
|-
|MH
|http://purl.org/tei/bug/3471119 MH will implement the consensus (no spaces around em dashes used parenthetically). RW will create the styleguide document with help from KH who knows the CMS system already. The text style guide will be deleted.
|
|-
|JC, KH
|http://purl.org/tei/bug/3395448 JC will try to discover whether Virginia is technically still a partner or not. When it’s resolved, KH will implement any changes to the website.
|Pending
|-
|JC, MH
|http://purl.org/tei/fr/3511134 JC and MH will conspire to implement an html:@id for attributes in HTML Guidelines output in the stylesheets.
|Not for 15 June release
|-
|KH
|http://purl.org/tei/fr/3437509 KH will review the whole thread and make a recommendation about the form of @ref, and make the soft deprecation changes to the Guidelines; these will be reviewed by LB.
|done
|-
|SR, PB
|http://purl.org/tei/fr/3432520 Finish implementing standard attributes referring to ISOCAT
|
|-
|PB
|http://purl.org/tei/fr/3046288 PB will contact LR and ask him to provide further examples.
|
|-
|KH
|http://purl.org/tei/fr/3041605 KH to close ticket
|done
|-
|JC
|http://purl.org/tei/bug/3497369 (JC) Strike the sentence that’s under discussion, because then the paragraph is less confusing. We should also add a new section (12.2.4), which explains that you don’t have to use ids in @from and @to; you can also use any URIs and XPointers with TEI XPointer schemes.
|Pending
|-
|MH
|http://purl.org/tei/bug/3497356 MH will ask the submitter (and the TEI-L, pointing to the ticket) for any examples of the use of <div> which suggest that <listApp> might be useful (for instance, organization of <apps> into multiple <div> s with @type).
|
|-
|LB
|http://purl.org/tei/bug/3496998 LB will add an additional example of how to combine <lacunaEnd> inside a <rdg> . Ticket will be closed.
|done
|-
|KH
|http://purl.org/tei/bug/3475748 KH to implement
|done
|-
|SR to coordinate, KH and GB to assist
|http://purl.org/tei/bug/3440771
*document how to point from a <geo> to the <geoDecl> in order to indicate which coordinate system is being used.
*Remove from the Guidelines the statement that “All uses of geo within a document are required to use the same coordinate system.”
*edit the definition of <location> to say something like “defines the location of a place as *one or more* sets of geographical coordinates...” to indicate that more than one system may be used at once
clarify relationship between <location> and <geo> in the prose of the Guidelines
|
|-
|LB
|http://purl.org/tei/bug/3458222 LB will add <pc> to pPart.edit and revise the prose accordingly
|done (but see note on ticket -- it's a matter of making <pc> reference pPart.edit, not changing its membership)
|-
|MH
|http://purl.org/tei/bug/3500088 MH to re-visit to determine what's unclear and correct Guidelines.
|Done in rev 10481 (assuming it builds OK).
|-
|SR
|http://purl.org/tei/fr/3423686 Sebastian to nag Ontology SIG
|done, tho no resolution
|-
|PB
|http://purl.org/tei/fr/3288293 PB will add a new attribute to att.pointing, called @targetLang.
|
|-
|JC
|http://purl.org/tei/fr/2724997 and http://purl.org/tei/fr/2507305 linking audio/video; JC will write to TEI-L asking for people who are interested in this area to get in touch. He will run the message by Council first. These people will join a Council working group to come back with a consistent proposal to be discussed later at this meeting.
| (Not release-blocking)
|-
|MH, SR, LB
|MH will write a new section for “How to edit the Guidelines” which explains TEI testing framework in more detail; this will then be checked by SR and LB.
|
|-
|LB, MH
|LB and MH to make sure a new-style inclusion TEI Lite ODD is up to date, regenerate schemas and update prose to match. The result should be packaged and archived as a stable and unchanging resource.
|
|-
|KH, LB, MH
|KH will collaborate with LB and MH to carry out the same process of freezing with Tite.
|
|-
|KH
|KH will make the customization available through the TEI website (we will not incorporate it into our build process because it’s too restrictive); the document itself will be mined for good ideas, and turned into a set of recommendations for changes to the Guidelines. KH to submit tickets for items to be added to the main Guidelines, since most of the items are likely to be independent and can be assessed separately.
|added as community customization
|-
|MH
|http://purl.org/tei/bug/3496958 (MH) We leave the content model alone (it’s horrible), but we use this as an example for Council to collaborate on the creation of one or more Schematron constraints which will enforce the presence of at least one <rdg> , to everyone’s edification.
|
|-
|JC
|http://purl.org/tei/bug/3496954 No action required; JC to close ticket.
|done
|-
|LB
|http://purl.org/tei/bug/3496951 LB to create att.witnessed for @wit on <rdg> and <lem> and remove @wit from <rdgGrp>
|done at rev 10243
|-
|GB
|http://purl.org/tei/bug/3496949 GB will review the particular example mentioned on the ticket, and revise and expand it: firstly, use a straightforward witness; secondly add an example for the "unattested" case.
|
|-
|JC
|http://purl.org/tei/fr/3490054 JC will close ticket with won't fix suggesting it for P6
|done
|-
|JC
|Start wiki page on P6 development ideas http://wiki.tei-c.org/index.php/P6-dev
|done
|-
|SY
|SY will send an email to tei-l to encourage people to add their docs to the samples page to keep open the statistical approach in the long term.
|done
|-
|MH
| MH look at existing pages for attribute classes and see if there are any examples, try adding an example to att.ascribed class spec to see if it works
|
|-
|SR
|SR Sebastian will "show all examples" so that at the top it lists examples from the appropriate chapter, and links to that chapter.
|done
|-
|MH
|MH to create a wiki page to coordinate adding examples to attribute classes. Since most attribute classes do not have examples, all of us should generate examples to be added to attribute class pages.
|Done. Page is at [[AttsWithoutEgs#Attributes_without_an_example_in_their_elementSpec_OR_classSpec|AttsWithoutEgs]]
|-
|SR
|change build process so that you can't build without examples on attribute classes (this would have to be implemented later)
|
|-
|MH
|http://purl.org/tei/fr/3434990 MH will write a Schematron rule requiring that <lg> contains <l> , <lg> , or <gap>
|
|-
|SR
|http://purl.org/tei/fr/3305016 SR will implement the content model proposed by KH on SF
|done
|-
|GB
|http://purl.org/tei/fr/3416130 GB will survey the guidelines to see what kind of changes <certainty> within milestone elements would involve. He will report back via email, unless there is great disagreement the FR should be approved and implement. If there is disagreement, address at our next teleconference
|
|-
|JC
|http://purl.org/tei/fr/3416130 JC will update the ticket in sourceforge to assign to GB and add a note about our decided action
|done
|-
|JC
|macro.paraContent out of place in <gram> etc [cf <u> discussion] link to ticket is broken, so group E did not discuss;
Action: JC to find out what happened to this ticket.
|JC: Found ticket at http://purl.org/tei/bug/3376863 needs more discussion.
|-
|KH
|http://purl.org/tei/fr/3500566 Implement proposal 'a' on SF ticket
|done
|-
|GB
|http://purl.org/tei/fr/3497079 GB to write a comment on the ticket giving examples of citations that would be problematic or confusing according to this proposal. Paul can also provide example citations from his U-M CV project. Kevin will discuss with Gabby and incorporate marked-up examples into proposal and revise proposal if appropriate. Leave ticket open for now
|
|-
|JC
|http://purl.org/tei/fr/3440977 Agreed: Suggest LR to implement. JC will contact him and report back to us if he will not implement.
|Emailed, awaiting answer
|-
|KH
|http://purl.org/tei/fr/2493417 Agreed and implemented but KH to add more examples/prose
|done
|-
|KH
|http://purl.org/tei/fr/3480057 KH to close
|done
|-
|MH
|http://purl.org/tei/bugs/3439587 MH will revise definition of <titleStmt> to no longer imply responsibility for intellectual content only. MH will also investigate adding <distributor> and <publisher> to model.respLike.
|
|-
|RW
|http://purl.org/tei/fr/3496494 RW will adapt defintion of <span> to take better wording from 17.3
|
|-
|LB
|http://purl.org/tei/fr/3495987 LB will ask Laurent for examples in case we are assuming incorrectly and will look at TEI-L archives.
|
|-
|LB
|http://purl.org/tei/fr/2834511 LB will add proposed Schematron rules but not add any other elements without clear use cases.
|
|-
|SR
|http://purl.org/tei/fr/3291540 SR will take the ticket. We’ll leave it to SR to decide which of the second list of elements should be included as well. Sebastian will send a list to TEI-L so people could comment on any elements where it would be removed.
|
|-
|SR
|http://purl.org/tei/fr/3284816 SR to implement.
|did faith
|-
|SR
|http://purl.org/tei/fr/3415801 Allow modification of attributes belonging to a class; SR will implement (in long-term).
|
|-
|LB
|http://purl.org/tei/fr/3118435 LB to close ticket
|done
|-
|SR
|http://purl.org/tei/fr/3426828 SR to close this ticket noting that requestor hasn’t responded.
|done
|-
|MH
|http://purl.org/tei/fr/1650195 MH to implement adding <schemaSpec> to model.encodingDescPart.
|Done in revs 10314-10317. Ticket closed.
|-
|JC
|FloatingText proposal: JC will reply to the message on TEI-L: In light of the current text and examples in the Guidelines on <floatingText> and <spGrp> , we’d like examples of proposed “floating divs” and how they would differ from <floatingText>s.
|(Not release-blocking)
|-
|LB, KH, BB, PS
|http://purl.org/tei/bug/3439980 LB to chair an ad hoc council working group on div-liminal to report back on this before next face2face, KH, LB, and PS to be members, others as necessary.
|
|-
|SR, LB, MH, PB
|Audio/Video Facsimiles -- Working group to be chaired by SR, with LB, MH, and possibly PB; to approach TEI-L and others doing work in this area to get outside expertise; an initial proposal or detailed report of progress at next FTF with status reports at teleconferences.
|
|-
|MH, GB, SY
|MH will chair this working group on private URI schemes and their documention, bring in GB, SY, and outside people suggested by GB. They will develop concrete proposals for next FTF meeting with status reports at teleconferences.
|Work underway. Description of [[XPointer|current state of XPointer play|XPointer]] and list of [[Stand-off use cases]] done. Use cases circulated to TEI-L for consultation.
|-
|JC
|James will prod the critical apparatus working group before next teleconference.
|(Done, but will do again)
|-
|JC
|JC to produce a Council meeting/telco checklist on TEI-C Wiki to ensure we don't forget steps (like asking SIGs if they have technical things they want to report)
|(Not release-blocking)
|-
|SY, LB, PB
|UIMA, GATE and other tools. SY will follow up offline w/ LB, PB; PB will put SY in touch with others working in UIMA and interested in converting to TEI;PB and SY report back to Council on progress by next FTF
|
|-
|LB, RW
|http://purl.org/tei/bugs/3454814 LB will write up guidelines for purging comments and distribute to TEI-Council list, including describing first passes to deal with low-hanging fruit and suggested format for how we should comment going forward from there, work of reviewing and purging comments or turning them into notes will be divided among council members. RW will incorporate language from LB’s guidelines into the style guide when appropriate
|
|-
|MH
|http://purl.org/tei/bugs/3454803 MH will compare Chapter CH against the latest version of BCP 47 for inconsistencies
|
|-
|MH
|Create new Jenkins build script for Ubuntu 12.04 server.
|Done 2012-06-13.
|-
|SR, KH
|http://purl.org/tei/bugs/3432216 SR: double check FM1 to see if list of translators is up to date; KH will add this policy to the “how to edit the guidelines” working paper
|tcw20 now says to leave @version attribute unchanged. Korean translator name added to FM1
|-
|PS, RW
|http://purl.org/tei/bugs/3223636 Expand our explanation of xml:space in the Guidelines:
* in note: expand to acknowledge that many parsers may not handle xml:space properly
* clarify definition of xml:space’s “default” value to match the XML spec (that is, “whatever the processor would normally do)
* remove sentence in prose of guidelines in chapter 22 "the global @xml:space is available to indicate that white space should be preserved within the content of these elements"
|
|-
|SR
|http://purl.org/tei/bugs/3393781 SR per LB’s comment on Sourceforge: Agreed to rename @version in att.translatable as @versionDate and give it a date datatype. We don’t want all the possibilities of att.datable.
|done
|-
|JC
|JC to add TEI Sourceforge site to the TEI category so all TEI sourceforge projects can be located at once
|done
|}

Talk:Best Practices for TEI in Libraries

2009-06-18T20:50:54Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Within <code><profileDesc></code>, is <code><keywords scheme=></code> only used if its <code><term></code> children come from a specific controlled vocabulary? Can there be <code><term></code>s without a parent <code><keywords scheme=></code>?

'''''5.1.3 Rationale for Level 1 Encoding'''''

Under the characteristics of projects best-suited for Level 1 encoding, may I suggest the following addition:

-the source documents are printed or nearly all printed

Or something along those lines, since OCR is pretty useless on manuscript materials, and even on complicated typefaces like blackletter/Fraktur.

The other characteristics listed do describe the project workflow, not the physical documents, so perhaps this type of specific characteristic is not appropriate after all. It seems worth noting somewhere in some fashion that certain collections, such as manuscript materials and some types of print, will by their very nature almost certainly require a higher level of encoding. But where or how? Or is this even necessary? Perhaps it is already implied, assumed, or generally understood.

Talk:Best Practices for TEI in Libraries

2009-06-18T20:43:06Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T20:42:25Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T20:41:59Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Within <code><profileDesc></code>, is <code><keywords scheme=></code> only used if its <code><term></code> children come from a specific controlled vocabulary? Can there be <code><term></code>s without a parent <code><keywords scheme=></code>?

'''''5.1.3 Rationale for Level 1 Encoding'''''
Under the characteristics of projects best-suited for Level 1 encoding, may I suggest the following addition:

-the source documents are printed or nearly all printed

Or something along those lines, since OCR is pretty useless on manuscript materials, and even on complicated typefaces like blackletter/Fraktur.

The other characteristics listed do describe the project workflow, not the physical documents, so perhaps this type of specific characteristic is not appropriate after all. It seems worth noting somewhere in some fashion that certain collections, such as manuscript materials and some types of print, will by their very nature almost certainly require a higher level of encoding. But where or how? Or is this even necessary? Perhaps it is already implied, assumed, or generally understood.

'''''5.4.6 General Level 4 Recommendations and Examples'''''
1) Currently reads:
"Section 4.3.1 Grouped Texts states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.” "

Does this refer to Section 4.3.1 of the P5 Guidelines (as opposed to 4.3.1 of these best practices, which does not seem to exist)? Does that need to be specified, as references to the P5 Guidlines are elsewhere in this document?

Talk:Best Practices for TEI in Libraries

2009-06-18T20:29:12Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Within <code><profileDesc></code>, is <code><keywords scheme=></code> only used if its <code><term></code> children come from a specific controlled vocabulary? Can there be <code><term></code>s without a parent <code><keywords scheme=></code>?

'''''5.1.3 Rationale for Level 1 Encoding'''''
Under the characteristics of projects best-suited for Level 1 encoding, may I suggest the following addition:

-the source documents are printed or nearly all printed

Or something along those lines, since OCR is pretty useless on manuscript materials, and even on complicated typefaces like blackletter/Fraktur.

The other characteristics listed do describe the project workflow, not the physical documents, so perhaps this type of specific characteristic is not appropriate after all. It seems worth noting somewhere in some fashion that certain collections, such as manuscript materials and some types of print, will by their very nature almost certainly require a higher level of encoding. But where or how? Or is this even necessary? Perhaps it is already implied, assumed, or generally understood.

Talk:Best Practices for TEI in Libraries

2009-06-18T20:08:59Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Within <code><profileDesc></code>, is <code><keywords scheme=></code> only used if its <code><term></code> children come from a specific controlled vocabulary? Can there be <code><term></code>s without a parent <code><keywords scheme=></code>?

'''''5.1.3 Rationale for Level 1 Encoding'''''
Under the characteristics of projects best-suited for Level 1 encoding, may I suggest the following addition:

-the source documents are printed or nearly all printed

Or something along those lines, since OCR is pretty useless on manuscript materials, and even on complicated typefaces like blackletter/Fraktur.

The other characteristics listed do describe the project workflow, not the physical documents, so perhaps this type of specific characteristic is not appropriate after all. Nevertheless it seems worth noting somewhere that some collections, such as manuscript materials and some types of print, will by their very nature almost certainly require a higher level of encoding.

Talk:Best Practices for TEI in Libraries

2009-06-18T20:08:40Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Within <code><profileDesc></code>, is <code><keywords scheme=></code> only used if its <code><term></code> children come from a specific controlled vocabulary? Can there be <code><term></code>s without a parent <code><keywords scheme=></code>?

'''''5.1.3 Rationale for Level 1 Encoding'''''
Under the characteristics of projects best-suited for Level 1 encoding, may I suggest the following addition:

-the source documents are printed or nearly all printed

Or something along those lines, since OCR is pretty useless on manuscript materials, and even on complicated typefaces like blackletter/Fraktur.

The other characteristics listed do describe the project workflow, not the physical documents, so perhaps this type of specific characteristic is not appropriate after all. Nevertheless it seems worth noting somewhere that some collections, such as manuscript materials and some types of print will by their very nature almost certainly require a higher level of encoding.

Talk:Best Practices for TEI in Libraries

2009-06-18T20:08:13Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Within <code><profileDesc></code>, is <code><keywords scheme=></code> only used if its <code><term></code> children come from a specific controlled vocabulary? Can there be <code><term></code>s without a parent <code><keywords scheme=></code>?

'''''5.1.3 Rationale for Level 1 Encoding'''''
Under the characteristics of projects best-suited for Level 1 encoding, may I suggest the following addition:

-the source documents are printed or nearly all printed

Or something along those lines, since OCR is pretty useless on manuscript materials, and even on complicated typefaces like blackletter/Fraktur.

The other characteristics listed do describe the project workflow, not the physical documents, so perhaps this type of specific characteristic is not appropriate (and indeed will probably change over time as OCR capabilities change). Nevertheless it seems worth noting somewhere that some collections, such as manuscript materials and some types of print will by their very nature almost certainly require a higher level of encoding.

Talk:Best Practices for TEI in Libraries

2009-06-18T20:05:11Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Within <code><profileDesc></code>, is <code><keywords scheme=></code> only used if its <code><term></code> children come from a specific controlled vocabulary? Can there be <code><term></code>s without a parent <code><keywords scheme=></code>?

'''''5.1.3 Rationale for Level 1 Encoding'''''
Under the characteristics of projects best-suited for Level 1 encoding, may I suggest the following addition:

-the source documents are printed or nearly all printed

Or something along those lines, since OCR is pretty useless on manuscript materials, and even on complicated typefaces like blackletter/Fraktur.
Maybe that's assumed, implied, or understood already, but it seems worth noting that collections of manuscript materials and some types of print will almost certainly require a higher level of encoding.

Talk:Best Practices for TEI in Libraries

2009-06-18T19:49:56Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T19:47:36Z

RebeccaWelzenbach:

'''''Introduction'''''

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

'''''2.9 General Guidelines for Attribute Usage'''''

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

'''''4.2 The TEI Header'''''

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

'''''4.4 The TEI Header and Other Metadata Schemas
'''''
1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

'''''4.5 Determining Data Values for the TEI Header'''''

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

'''''4.6 Element Recommendations for the TEI Header'''''

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

2) Under <code><profileDesc></code>, what is the difference between <code><keyword></code> and its child <code><term></code>?

Talk:Best Practices for TEI in Libraries

2009-06-18T19:33:21Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T19:30:43Z

RebeccaWelzenbach: /* 4.6 Element Recommendations for the TEI Header */

==Introduction ==

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

== 2.9 General Guidelines for Attribute Usage ==

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

== 4.2 The TEI Header ==

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

== 4.4 The TEI Header and Other Metadata Schemas ==

1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

== 4.5 Determining Data Values for the TEI Header ==

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

== 4.6 Element Recommendations for the TEI Header ==

1) Under the instructions for the <code>title</code> element that falls within <code><sourceDesc></code>, it currently reads:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated, along with other information, in a list of the possible <code>type</code> attributes that can be used for this element. So, stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

Talk:Best Practices for TEI in Libraries

2009-06-18T19:29:20Z

RebeccaWelzenbach: /* 4.6 Element Recommendations for the TEI Header */

==Introduction ==

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

== 2.9 General Guidelines for Attribute Usage ==

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

== 4.2 The TEI Header ==

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

== 4.4 The TEI Header and Other Metadata Schemas ==

1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

== 4.5 Determining Data Values for the TEI Header ==

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

== 4.6 Element Recommendations for the TEI Header ==

1) Under the <code>title</code> element that falls within the <code><sourceDesc></code>, it currently states:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated below, where there is a list of the possible <code>type</code> attributes that can be used. Stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

Talk:Best Practices for TEI in Libraries

2009-06-18T19:28:52Z

RebeccaWelzenbach:

==Introduction ==

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

== 2.9 General Guidelines for Attribute Usage ==

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

== 4.2 The TEI Header ==

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

== 4.4 The TEI Header and Other Metadata Schemas ==

1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

== 4.5 Determining Data Values for the TEI Header ==

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things? What counts as "evidence" of a source document?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

== 4.6 Element Recommendations for the TEI Header ==

1) Under the <code>title</code> element that falls within the <sourceDesc>, it currently states:

"At least one title element is required for the title of the source document. Give the title according to the national cataloging code. Use a type attribute with a value of marc245c to give the statement of responsibility from a MARC record. "

The information in the second sentence (about marc245c) is immediately reiterated below, where there is a list of the possible <code>type</code> attributes that can be used. Stating it here seems unnecessary and also confusing--without having seen yet that we can also use marc245a and marc245b for the other elements of the title, I don't know why we've skipped right to statements of responsibility in a title element (but I'm not a cataloger)

Best Practices for TEI in Libraries

2009-06-18T19:22:01Z

RebeccaWelzenbach: /* Element Recommendations for the TEI Header */

----
* [[SIG:Libraries|TEI in Libraries: Home]]
----

==Introduction==

These best practices are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, these best practices are meant to be as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing. The encoding levels are not strictly cumulative: while higher levels tend to build upon lower levels by including more elements, higher levels are not supersets because some elements used at lower levels are not used at all at higher levels.

In brief, the encoding levels are:

{| border="1"
|-
| Level 1
| The text is generated through OCR, is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).
|-
| Level 2
| The text is generated through OCR and is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured.
|-
| Level 3
| The text is created by conversion from an electronic source such as HTML or word-processor documents or from a print source, either by way of OCR or keyboarding.
|-
| Level 4
| The text is generated either through corrected OCR or keyboarding and is able to stand alone without page images in order for them to be read by students, scholars, and general readers.
|-
| Level 5
| The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge.
|}

These best practices are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention. Level 3 does not contain as many elements as TEI Tite in order to allow for mass digitization of born-digital source documents or for upgrading of Level 1 or Level 2 texts with only minimal human intervention. For more information, see [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg TEI Tite's Appendix A].

These best practices specify a recommended archival storage format. Local system needs may require transformation of documents in this archival format to another XML format for use by a local indexing or delivery software.

In these guidelines, use of elements and attributes tends toward explicitness for ease of processing even though a human or possibly machine reader might be able to make inferences based on context.

==General Recommendations==

=== Standards and local practice ===

The goal of the TEI is interchange, not interoperability. While seamless interoperability of texts created by different organizations is an unobtainable goal, use of a common markup vocabulary and syntax greatly aids interchange. Nevertheless, keep in mind that others—even within your organization—may use your texts in the future for other uses than you intended in your encoding.

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Hyphenation ===

Encoding end-of-line, end-of-column, and end-of-page hyphenation varies considerably in the TEI community. Some capture all hyphens found on the printed page, while others remove those in the middle of words not normally hyphenated for easier implementation of full-text retrieval. If preserving hyphens, some will capture all hyphens using the same character, while others will distinguish hyphens that must be present in any case (often called "hard hyphens") and those that are only present by virtue of being at the end of a line, column, or page (often called "soft hyphens").

This issue is complicated by the fact that Unicode presribes use of a soft hyphen not for a ''visible hyphen that might have been absent'' but instead for a place where a hyphen ''might occur''. Furthermore, it includes a "non-breaking hyphen", used in cases like "re-creation" (meaning "to create again", as opposed to recreation, meaning "relaxation"), in addition to a regular hyphen, which would normally count as a word boundary. In short, Unicode is oriented toward electronic text that may be processed with a computer in various ways, not toward capturing source documents.

Since OCR software relies on dictionaries to determine the probability not simply of characters but of whole words, it is often able to handle hyphenation in different ways.

At Levels 1 and 2, no attempt should be made to remove hyphens from the source document or disambiguate hard and soft hyphens. Encode all hyphens appearing in the source document using character U+2010.

At Level 3, either encode hyphens as in Levels 1 and 2 or disambiguate soft and hard hyphens. In the latter case, soft hyphens should be encoded using U+00AD and hard hyphens using U+2010.

At Levels 4 or 5, hyphens must be disambiguated using U+00AD for soft hyphens and U+2010 for hard hyphens.

In any case, the hyphenation practice must be recorded in the <tt>editorialDecl</tt>.

Do not confuse hyphen characters with the minus character (U+2212).

=== Filenames ===

A filename scheme that is internally consistent should be established for the project.

If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. Likewise, if you will access files using a version of Apple Filing Protocol (AFP) before 3.0, filenames longer than 31 bytes are likely to be corrupted, so you may wish to limit filenames to 31 single-byte (e.g., ASCII) characters.

Otherwise, consider the following best practices when determining the file name scheme for your project:

* Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
* Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
* Filenames should not include spaces
* Filenames should follow predictable case constructions (e.g., all lowercase, camelCase, etc.)
* The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and XML-based metadata languages
* The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

The choice of numbered or unnumbered divisions must be documented with the <tt>tagUsage</tt> element in the header. See 4.6, Element Recommendations for the TEI Header, below.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at Level 1 (because only one encoded division in the text exists), is optional at Level 2 (because the division-level metadata need not classify these divisions), is recommended at Level 3 (for broad yet useful analysis of text divisions), and required at Levels 4 and 5 (for full analysis of the text structure).

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, with the value of the <tt>n</tt> attribute denoting the number of the page whose text ''follows'' this element. The <tt>pb</tt> element should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are three recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facsimile]</tt> element to define a set of images that corresponds to the text in conjunction with the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== key and ref ====

These attributes are available on the same elements and are used to reference external metadata about the content of the element. The <tt>key</tt> element may contain any string of Unicode characters, whereas the <tt>ref</tt> attribute must contain a URI (including a relative one, as discussed above). While <tt>key</tt> may supply any identifier, there is no mechanism internal to XML for checking that the value of this attribute is valid.

For example,

<code>
<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>
</code>

gives a project-interal key (<tt>lccn-n78-95332</tt>) for this name in the Library of Congress Name Authority File. Values of <tt>key</tt> attributes may be partially explained in a non-machine-readable way through use of a <tt>taxonomy</tt> element:

<code>
<taxonomy xml:id="lccn"><bibl>Library of Congress Control Number</bibl></taxonomy>
</code>

Alternatively, use <tt>ref</tt> with a URI fragment identifier, corresponding to the value of <tt>xml:id</tt> given elsewhere. For example, in the transcription of the text, use

<code>
<placeName ref="#tgn_7012924">Indianapolis</placeName>
</code>

which would be defined in a controlled vocabulary elsewhere:

<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
</listPlace>
</pre>

When validation software encounters <tt>ref="#tgn_7012924"</tt>, it will check that <tt>xml:id="tgn_7012924"</tt> exists elsewhere in the document.

==== rend and rendition ====

The <tt>rend</tt> and <tt>rendition</tt> attributes may be used when it is desirable to record information about how the content object was displayed in the source document.

Never use these attributes on header elements: metadata is transcribed and possibly regularized, as in a catalog record, but its exact appearance is not meant to be captured.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use these attributes; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, one of these attributes should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

For the value of the <tt>rend</tt> attribute, use only valid CSS properties and values. For example:

* <tt><foreign rend="font-style: italic"></tt>
* <tt><title rend="text-decoration: underline; font-size: x-large"></tt>

Alternatively, use the <tt>rendition</tt> '''attribute''' to give an internal scheme:

<tt><foreign rendition="#i"></tt>

documented with the <tt>rendition</tt> '''element''' in the header:

<tt><rendition xml:id="i" scheme="css">font-style: italic</rendition></tt>

Use of the <tt>rendition</tt> attribute and element offers an additional level of indirection, decreasing the total number of keystrokes and possibly reducing the chance of typos being introduced in the encoding.

==== xml:lang ====

Used to indicate the natural language of the content of an element. It is generally not used for children of the <tt>text</tt> element at Level 1 or Level 2 but is common at Level 3 and above. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the data.language datatype in the TEI Guidelines].

==Structure of a TEI Document==

<table border="1">
<tr>
<th colspan="2">Element</th>
<th>Description</th>
</tr>
<tr>
<td colspan="2"><tt><TEI></tt></td>
<td>The root element of a TEI document</td>
</tr>
<tr>
<td>├</td>
<td><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> is required; it indicates the language used for the metadata describing the document.</td>
</tr>
<tr>
<td>├</td>
<td><tt><facsimile></tt></td>
<td>The <tt>facsimile</tt> defines sets of images that correspond with the text. Unlike the <tt>teiHeader</tt> and the <tt>text</tt>, it is an optional element in the TEI document.</td>
</tr>

<tr>
<td>└</td>
<td>The <tt><text xml:lang="___"></tt></td>
<td>The <tt>text</tt> element contains the encoded transcription of the source document. The <tt>xml:lang</tt> attribute is recommended; it indicates the primary language of the source document.</td>
</tr>
</table>

The child elements of the <tt>teiHeader</tt> and <tt>text</tt> elements are described below.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. TEI Lite calls the header "the electronic title page", though it actually more closely resembles a catalog record with additional data not routinely stored in MARC records.

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

In order to allow automatic generation of TEI headers from MARC records and MARC records from TEI headers, some elements (like <tt><author></tt>) contain content not typical for TEI practice but necessary due to a lack of granularity in the MARC format.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element. In the absence of such mechanisms, users of these best practices may use the <tt>idno</tt> element to supply identifiers for outside metadata records and may supply identifiers for certain authority records using the <tt>key</tt> or <tt>ref</tt> attributes, allowed on certain elements.

While elements from non-TEI namespaces may be included in a TEI document, these best practices currently do not attempt to prescribe which and where non-TEI elements may or must be used in the header.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. In an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> attribute is required; it indicates the language used for the metadata describing the document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>├</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains bibliographic metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:

* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document—usually, the author(s) of the source document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>X, Malcolm</author></tt>
* <tt><author>Thomas (Anglo-Normal poet)</author></tt>
* <tt><author>Catherine II, Empress of Russia</author></tt>
* <tt><author>Joannes, Actuarius, 13th/14th cent.</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>
If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that acted as editors of the TEI document—usually, the editor(s) of the source document. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

Unlike in the TEI Guidelines, do not use this element for translators, illustrators, compilers, or other roles not generally considered an editor. Therefore, do not use the <tt>role</tt> attribute.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td><p>Record the names of other persons or organizations, one responsibility or party per <tt><respStmt></tt>, that have responsibility for the intellectual or artistic content of the TEI document—often by transitivity from the source document—not covered by <tt><author></tt> and <tt><editor></tt>. This includes translators, illustrators, compilers, proofreaders, encoders, and those who wrote a preface or introduction. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt>title</tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>type</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD. (This element is used instead of <tt><bibl></tt> to enforce structure, but <tt><biblFull></tt> is not used because it requires more elements than are typically available in library metadata sources.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the intellectual or artistic content of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. Use a <tt>type</tt> attribute with a value of <tt>marc245c</tt> to give the statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>marc245c</tt> (used for the statement of responsibility according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
<p>Statement of responsibility on the source document, according to the national cataloging code. Record
one responsibility or party per <tt><respStmt></tt>. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p>

<p>If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to split the content of the 245c field into <tt>resp</tt> and <tt>name</tt> elements, so it is recommended to use <tt><title type="marc245c"></tt> instead of this element.</p>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a colon) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "S.l." (for no place of publication).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a comma) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "s.n." (for no publisher).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Optionally, use for notes about the source document, according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
Optionally use one or more <tt>idno</tt> elements to give identification numbers for the source document, text, or work, whether assigned by the holding library (such as a call number), the publisher of the original document (such as an ISBN), or a standard bibliography (such as an identifier from the <cite>Short Title Catalogue</cite> or <cite>Books in Maori</cite>). Use the following values for the <tt>type</tt> attribute if applicable, and create other values if appropriate:

* <tt>LC_call_number</tt>
* <tt>isbn-13</tt>
* <tt>isbn-10</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>
Use the <tt>n</tt> attribute to record the encoding level: <tt>1</tt> for Level 1, <tt>2</tt> for Level 2, etc.

Include one or more <tt>p</tt> elements as children with information on:

* editorial decisions made during encoding
* notes about omissions of material found in the original work
* the format of the data in the header: Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?
* automated processes used to generate the markup or content
* external files or databases (such as those containing authority data) referenced in the TEI document

Also include one of the following <tt>p</tt> elements as appropriate:

<tt><p>All hyphens in source document encoded as U+2010.</p></tt>

<tt><p>Soft hyphens encoded as U+00AD; hard hyphens as U+2010.</p></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><tt><rendition xml:id="_" scheme="css"</tt></td>
<td>Include one or more <tt>rendition</tt> elements for each unique value of a <tt>rendition</tt> attribute (not <tt>rend</tt> attribute) used in the body of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>└</p></td>
<td colspan="3"><tt><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td><p>├</p></td>
<td colspan="5"><tt><langUsage></tt></td>
<td>Optionally use this element and child <tt>language</tt> elements to list languages used in the text. This supplements <tt><text xml:lang="___"></tt> in cases where more than one language is used in the text. It is not expected that the <tt>langUsage</tt> element will contain any description of language usage.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="4"><tt><language ident="___"></tt></td>
<td>Use one or more <tt>language</tt> elements to indicate language(s) used in the source document. The <tt>ident</tt> attribute is usually sufficient to indicate the language, so this element should normally have no content. In the unusual case where <tt>ident</tt> is insufficient, provide additional information on the language as content of the element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers may be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change should be recorded using the <tt>when</tt> attribute ((see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]).

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. For example, the document might simply give <tt>who="#Jane_Smith"</tt>, relying on human readers to understand this reference.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="marc245a">Lincoln and Seward.</title>
<title level="m" type="marc245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="marc245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
<p>All hyphens in source document encoded as U+2010.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<langUsage>
<language ident="en"/>
</langUsage>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images). Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added at a later date</li>
</ul>

====Workflow====

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is left uncorrected ("dirty OCR"). Page images are tagged using software that assigns a page-level metadata (page number and possibly tags for page features) to each page image for display in the user interface in a list of pages. Encoding is performed automatically: markup with page-level metadata is inserted at selected points into the dirty OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====Purpose====
To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

====Rationale====
The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Level 2 requires a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are <i>not</i> intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

'''Level 2 is most suitable for projects in which''':

* a large volume of material is to be made available online quickly
* a digital image of each page is desired
* the material is of interest to a large community of users who wish to read texts that allow keyword searching
* rudimentary search and display capabilities based on the large structures of the text are desired
* each text is checked to ensure that divisions and headers are properly identified
* extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

====Workflow====

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’s heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">Unlike in Level 1, in Level 2 one <tt><div1></tt> or <tt><div></tt> is used per section of the text identified with division-level metadata. If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb n="1" facs="[URI of page 1 image]"/>
<head>[heading of section 1]</head>
<ab>[entire contents of section 1 here, with
interspersed <pb> elements pointing to page
images; in this example there are 26 more pages
to section 1]</ab>
</div>
<div type="section">
<pb n="27" facs="[URI of page 27 image]"/>
<div type="subsection">
<head>[heading of section 2 subsection 1]</head>
<ab>[all the paragraphs of subsection one go here
with page breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>

<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING
SHOULD BE ORDERED.</head>
<ab>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Encoding at this level offers provides the foundation for upgrading to higher levels of encoding. Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date</li>
</ul>

====Workflow====

Level 3 texts can be created by conversion from an electronic source such as an HTML file or word-processor document or from a print source, either through OCR or keyboarding. They can be generated trivially by converting from outsourced double-keyboarded texts conforming to TEI Tite, though some granularity of encoding will be lost in the translation.

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2 '''except <tt>ab</tt>''', plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Table of Contents=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT Chapter 4.5, Front Matter]

You may wish not to include front matter content such as table of contents or lists of illustrations, especially if you plan to automatically generate the contents or lists of illustrations. If you do, however, plan to manually encode the table of contents (or lists of illustrations and similar content), use a <tt>div</tt> element with an appropriate <tt>type</tt> attribute (e.g., <tt><div type="contents"></tt>). Within this division, use the <tt>list</tt> element to mark up the table of contents, list of illustrations, etc. Each list item should have a <tt>ptr</tt> or <tt>ref</tt> element with a <tt>target</tt> attribute referencing an <tt>xml:id</tt> attribute on the <tt><pb></tt> or "div" element of the referenced page or section. Use <tt>ref</tt> if you wish to transcribe page numbers in the table of contents; use <tt>ptr</tt> if you do not.

=====Notes=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog
<ref target="#VAA2383_011" rend="text-align: right">3</ref>
</item>
<item>II. Romance
<ref target="#VAA2383_020" rend="text-align: right">12</ref>
</item>
<item>III. The Costume
<ref target="#VAA2383_029" rend="text-align: right">21</ref>
</item>
<item>IV. Desperation
<ref target="#VAA2383_038" rend="text-align: right">30</ref>
</item>
<item>V. The Pageant of the Table Round
<ref target="#VAA2383_046" rend="text-align: right">38</ref>
</item>
</list>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="font-weight: bold">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"<hi rend="font-variant: small-caps">Penrod Schofield</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>
<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern&amp#xAD;
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open&amp#xAD;
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter&amp#xAD;
mination regarding these issues.</p>

<p>FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

<pb n="114" facs="00000002.tif"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>

<p>In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947.

<note place="bottom" anchored="true" n="68">Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re&amp#xAD;
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu&amp#xAD;
ments. CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<pb n="115" facs="00000003.tif"/>
occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per&amp#xAD;
sonal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note reques&amp#xAD;
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

although no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

====Purpose====
<p>To create text that can stand alone as electronic text, identifies
hierarchy and typography, specifies function of textual and structural elements, and describes the
nature of the content and not merely its appearance. This level is not meant to encode or identify all
structural, semantic, or bibliographic features of the text.</p>

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

<p>Finally, functionally accurate encoding in Level 4 texts
allows them to be searched or displayed in sophisticated ways.
For example, a searcher could limit his or her search in a
dramatic text to stage directions or in a verse text to only
first lines. In a political tract published by subscription, a
search could be confined to names that appear in lists, thus
limiting a search to names of people who subscribed to a
particular volume. This ability to limit searches becomes more
significant as textbases become larger, and thus is of great
importance to the library community as it attempts to build into
the initial design and implementation of textbases the features
needed to enhance interoperability.</p>

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

<li>the texts will be used for textual analysis</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added by the scholarly community at a later date</li>
<li>the users of the texts may have limited storage or display capabilities</li>
</ul>

====Workflow====

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup must be added, as discussed in [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg Appendix A of TEI Tite].

====Element Recommendations for Level 4====

<p>Use all elements specified in Levels 1, 2, and 3 '''except <tt>ab</tt>''', plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="font-weight: bold"></tt>). This element may also be used if the more specific elements above are not used.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSnr Chapter 13.1.1, Linking Names and Their Referents]

Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. See the [[#key_and_ref|discussion of <tt>ref</tt> and <tt>key</tt>]] above for how to choose between them.

If using <tt>key</tt>, provide a unique internal identifier, such as in a local database.

If using <tt>ref</tt>, an external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. In such a case the value of the <tt>ref</tt> attribute in the main TEI document (the transcription of the source document) references the value of the <tt>xml:id</tt> attribute in the external file. (In the examples below, the external file is named <tt>context.xml</tt> for “contextual information” and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* Alternatively, instead of using an external file for the authority data, use the <tt>key</tt> attribute to point to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:

<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="font-style: italic">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—&amp; B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
Source: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====

* Within the front matter (<tt><front></tt>) of a performance text, cast lists should be encoded as <tt><castList></tt>s, with each item in that list encoded as <tt><castItem></tt>s. If desired, each <tt><castItem></tt> may be uniquely identified with the <tt>xml:id</tt> attribute.

For example,

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

In either method, use an <tt>xml:id</tt> on the <tt>name</tt> element to uniquely identify the individual participant:

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

<sp who="spk2">
<speaker n="2">WILLIAM LINK:</speaker>
<p>Last time we were talking about Frank Porter Graham. And I have a couple of questions
about Graham, and I wonder if you could clear them up for me. You have mentioned that you
had worked with him as a student at North Carolina State, had you met him before?
</p>
</sp>
<sp who="spk1">
<speaker n="1">WILLIAM C. FRIDAY: </speaker>
<p>No. That budget hearing was the first that I knew of him, of course, but the first time
that I ever encountered him. I was president of class at N.C. State, and that through me into
this kind of public adventure. And so I went merrily on downtown and sat there in the budget
hearing, along with the president of the student body, and some others.
</p>
</sp>
</pre>

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

Use <tt><lg></tt> and <tt><l></tt> as in Level 3. In addition, use the <tt>rend</tt> attribute to indicate lines that are indented.

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="margin-left: 0.5in" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="margin-left: 0.5in" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="margin-left: 0.5in" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="margin-left: 0.5in" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

===== Level 4 Alger Hiss document =====

Note that the soft hyphen character is displayed as an entity reference because it this character will not display in many web browsers.

<pre><TEI xml:id="project_document_identifier"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="./pageImages/AH4_0113.jpg" ed="typed"/>
<pb n="118" ed="subsequent"/>
<head>POINT VIII.</head>
<head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
<lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
<lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
<lb/>family and associates was not known at the time of trial by
<lb/>the defense. Even now, with the release of some of the govern&#xAD;
<lb/>ment documents concerning FBI investigative techniques regarding
<lb/>Hiss, the full extent of surveillance -- wiretapping, mail open&#xAD;
<lb/>ings, mail covers, physical surveillance, and other intrusive
<lb/>techniques -- is still not 'clear. Nevertheless, it is apparent
<lb/>that information gathered through the exploitation of unlawful
<lb/>wiretaps and other illegal surveillance was used at trial and
<lb/>consequently the conviction must be reversed. Alternatively,
<lb/>further discovery and a hearing is essential to a fair deter&#xAD;
<lb/>mination regarding these issues.</p>
<p>FBI surveillance of Hiss began in earnest in 1941 with
<lb/>the institution of a mail cover on his incoming correspondence
<lb/>at his home in connection with an FBI investigation of possible
<lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed
<pb n="114" facs="./pageImages/AH_0114.jpg"/>
<pb n="119" ed="subsequent"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
<lb/>toll call records from the Hiss residence Telephone for the
<lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
<lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>
<p>In late November, 1945, FBI surveillance of the Hiss
<lb/>residence in Washington, D.C., escalated. For the third time,
<lb/>a mail cover was instituted beginning on November 28, 1945,
<lb/>which was continued at least until 1946. CN Ex. 101 at p. 70;
<lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun
<lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
<lb/>surveillance was discontinued on December 14, 1945, physical
<lb/>surveillance was conducted frequently at various times until
<lb/>September, 1947.<note place="foot" anchored="true" n="68">Also
before 1947, a letter from Priscilla Hiss addressed
<lb/>to her son, Timothy Hobson, was intercepted and its contents
<lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947,
<lb/>a letter from a Michael Greenberg addressed to petitioner re&#xAD;
<lb/>garding an application for employment with the United Nations
<lb/>was also intercepted, in a manner not revealed by the docu&#xAD;
<lb/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p>
<p>The most intrusive invasion of petitioner's rights
<pb n="115" facs="./pageImages/AH_0115.jpg"/>
<pb n="120" ed="subsequent"/>
<lb/>occurred from December 13, 1945 until the Hisses moved from
<lb/>Washington, D.C. to New York City on September 13, 1947. A
<soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss
<lb/>telephone at their residence on P Street-in Washington, D.C.
<lb/>The logs of this surveillance constitute twenty-nine volumes
<lb/>of FBI serials and are roughly 2,500 pages in length, in which
<lb/>an enormous amount of information concerning the Hisses' per&#xAD;
<lb/>sonal lives, relationships with friends and associates, and
<lb/>habits is recorded.</p>
<p>The wiretap was installed following FBI Director Hoover's
<lb/>application to the Attorney General for authorization,<note place="bottom" anchored="true" n="69">Hoover's
initial request was answered by a note reques&#xAD;
<lb/>ting information on Hiss. CN Ex. 104<sic> </sic>. Additional information
<lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic> </sic>.</note>
<lb/>although no written authorization appears in the documents released to
<lb/>Hiss. The purpose of the application was to gather information
<lb/>regarding Hiss' alleged contacts with Soviet espionage agents and
<lb/>communists in government service, general allegations which had
<lb/>been made by Elizabeth Bentley and Chambers.</p>
<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI></pre>

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require substantial human intervention by encoders with subject knowledge. These texts might include encodings of semantic, linguistic, prosodic, or other features well beyond the basic structural elements discussed in Levels 1-4 above. They might also include elements for editorial, critical, or analytical additions; manuscript descriptions; translations; or other textual apparatus. It is impossible to make concrete recommendations for encoding at this level since the scholarly analysis required is usually specific to each project; instead, Level 5 offers the full set of P5 elements as needed.

====Reference====
* [http://www.tei-c.org/Guidelines/P5 Complete P5 Guidelines]

====Purpose====
To create deeply analytical encoded texts that might be appropriate for specific research purposes, as part of a scholarly publishing project, or for any other encoding practices in library-based text encoding.

====Rationale====
A significant number of library-based projects engage in high-level analytical text encoding as part of their efforts in digitization, scholarly editing, academic support, or other research. Level 5 is intended to represent that work, which can take advantage of the full richness of the complete TEI Guidelines, while still acknowledging the impact of library-specific practices on encoded text that is created under the auspices of a library.

The specific influences of library practice on a Level-5 encoded text are expressed primarily in adherence to the [[#General_Recommendations|General Recommendations]] and [[#The_TEI_Header|TEI Header]] sections above.

====Element Recommendations and Examples====
Because of the vast range of possibilities for Level-5 encoding, we have chosen to provide neither a list of recommended elements nor any specific examples for this Level.

Please refer to the [[#The_TEI_Header|TEI Header]] section above for examples of <tt><TeiHeader></tt> element usage, and to the [[#General_Recommendations|General Recommendations]] section and the [http://www.tei-c.org/Guidelines/P5 Complete TEI P5 Guidelines] for element recommendations and usage examples within the <tt><text></tt> element.

==Acknowledgments==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Renee McBride, University of North Carolina, Chapel Hill
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to copyediting of this document are:
* Susan Lorand, University of Michigan
* Becky Welzenbach, University of Michigan

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==

This document was formerly known as "TEI Text Encoding in Libraries Guidelines for Best Encoding Practices".

<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (often referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

= Appendix B: Formal Specification =

(This section will be generated automatically once ODDs are created.)

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-06-18T19:05:53Z

RebeccaWelzenbach: /* Determining Data Values for the TEI Header */

----
* [[SIG:Libraries|TEI in Libraries: Home]]
----

==Introduction==

These best practices are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, these best practices are meant to be as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing. The encoding levels are not strictly cumulative: while higher levels tend to build upon lower levels by including more elements, higher levels are not supersets because some elements used at lower levels are not used at all at higher levels.

In brief, the encoding levels are:

{| border="1"
|-
| Level 1
| The text is generated through OCR, is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).
|-
| Level 2
| The text is generated through OCR and is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured.
|-
| Level 3
| The text is created by conversion from an electronic source such as HTML or word-processor documents or from a print source, either by way of OCR or keyboarding.
|-
| Level 4
| The text is generated either through corrected OCR or keyboarding and is able to stand alone without page images in order for them to be read by students, scholars, and general readers.
|-
| Level 5
| The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge.
|}

These best practices are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention. Level 3 does not contain as many elements as TEI Tite in order to allow for mass digitization of born-digital source documents or for upgrading of Level 1 or Level 2 texts with only minimal human intervention. For more information, see [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg TEI Tite's Appendix A].

These best practices specify a recommended archival storage format. Local system needs may require transformation of documents in this archival format to another XML format for use by a local indexing or delivery software.

In these guidelines, use of elements and attributes tends toward explicitness for ease of processing even though a human or possibly machine reader might be able to make inferences based on context.

==General Recommendations==

=== Standards and local practice ===

The goal of the TEI is interchange, not interoperability. While seamless interoperability of texts created by different organizations is an unobtainable goal, use of a common markup vocabulary and syntax greatly aids interchange. Nevertheless, keep in mind that others—even within your organization—may use your texts in the future for other uses than you intended in your encoding.

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Hyphenation ===

Encoding end-of-line, end-of-column, and end-of-page hyphenation varies considerably in the TEI community. Some capture all hyphens found on the printed page, while others remove those in the middle of words not normally hyphenated for easier implementation of full-text retrieval. If preserving hyphens, some will capture all hyphens using the same character, while others will distinguish hyphens that must be present in any case (often called "hard hyphens") and those that are only present by virtue of being at the end of a line, column, or page (often called "soft hyphens").

This issue is complicated by the fact that Unicode presribes use of a soft hyphen not for a ''visible hyphen that might have been absent'' but instead for a place where a hyphen ''might occur''. Furthermore, it includes a "non-breaking hyphen", used in cases like "re-creation" (meaning "to create again", as opposed to recreation, meaning "relaxation"), in addition to a regular hyphen, which would normally count as a word boundary. In short, Unicode is oriented toward electronic text that may be processed with a computer in various ways, not toward capturing source documents.

Since OCR software relies on dictionaries to determine the probability not simply of characters but of whole words, it is often able to handle hyphenation in different ways.

At Levels 1 and 2, no attempt should be made to remove hyphens from the source document or disambiguate hard and soft hyphens. Encode all hyphens appearing in the source document using character U+2010.

At Level 3, either encode hyphens as in Levels 1 and 2 or disambiguate soft and hard hyphens. In the latter case, soft hyphens should be encoded using U+00AD and hard hyphens using U+2010.

At Levels 4 or 5, hyphens must be disambiguated using U+00AD for soft hyphens and U+2010 for hard hyphens.

In any case, the hyphenation practice must be recorded in the <tt>editorialDecl</tt>.

Do not confuse hyphen characters with the minus character (U+2212).

=== Filenames ===

A filename scheme that is internally consistent should be established for the project.

If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. Likewise, if you will access files using a version of Apple Filing Protocol (AFP) before 3.0, filenames longer than 31 bytes are likely to be corrupted, so you may wish to limit filenames to 31 single-byte (e.g., ASCII) characters.

Otherwise, consider the following best practices when determining the file name scheme for your project:

* Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
* Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
* Filenames should not include spaces
* Filenames should follow predictable case constructions (e.g., all lowercase, camelCase, etc.)
* The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and XML-based metadata languages
* The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

The choice of numbered or unnumbered divisions must be documented with the <tt>tagUsage</tt> element in the header. See 4.6, Element Recommendations for the TEI Header, below.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at Level 1 (because only one encoded division in the text exists), is optional at Level 2 (because the division-level metadata need not classify these divisions), is recommended at Level 3 (for broad yet useful analysis of text divisions), and required at Levels 4 and 5 (for full analysis of the text structure).

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, with the value of the <tt>n</tt> attribute denoting the number of the page whose text ''follows'' this element. The <tt>pb</tt> element should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are three recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facsimile]</tt> element to define a set of images that corresponds to the text in conjunction with the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== key and ref ====

These attributes are available on the same elements and are used to reference external metadata about the content of the element. The <tt>key</tt> element may contain any string of Unicode characters, whereas the <tt>ref</tt> attribute must contain a URI (including a relative one, as discussed above). While <tt>key</tt> may supply any identifier, there is no mechanism internal to XML for checking that the value of this attribute is valid.

For example,

<code>
<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>
</code>

gives a project-interal key (<tt>lccn-n78-95332</tt>) for this name in the Library of Congress Name Authority File. Values of <tt>key</tt> attributes may be partially explained in a non-machine-readable way through use of a <tt>taxonomy</tt> element:

<code>
<taxonomy xml:id="lccn"><bibl>Library of Congress Control Number</bibl></taxonomy>
</code>

Alternatively, use <tt>ref</tt> with a URI fragment identifier, corresponding to the value of <tt>xml:id</tt> given elsewhere. For example, in the transcription of the text, use

<code>
<placeName ref="#tgn_7012924">Indianapolis</placeName>
</code>

which would be defined in a controlled vocabulary elsewhere:

<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
</listPlace>
</pre>

When validation software encounters <tt>ref="#tgn_7012924"</tt>, it will check that <tt>xml:id="tgn_7012924"</tt> exists elsewhere in the document.

==== rend and rendition ====

The <tt>rend</tt> and <tt>rendition</tt> attributes may be used when it is desirable to record information about how the content object was displayed in the source document.

Never use these attributes on header elements: metadata is transcribed and possibly regularized, as in a catalog record, but its exact appearance is not meant to be captured.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use these attributes; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, one of these attributes should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

For the value of the <tt>rend</tt> attribute, use only valid CSS properties and values. For example:

* <tt><foreign rend="font-style: italic"></tt>
* <tt><title rend="text-decoration: underline; font-size: x-large"></tt>

Alternatively, use the <tt>rendition</tt> '''attribute''' to give an internal scheme:

<tt><foreign rendition="#i"></tt>

documented with the <tt>rendition</tt> '''element''' in the header:

<tt><rendition xml:id="i" scheme="css">font-style: italic</rendition></tt>

Use of the <tt>rendition</tt> attribute and element offers an additional level of indirection, decreasing the total number of keystrokes and possibly reducing the chance of typos being introduced in the encoding.

==== xml:lang ====

Used to indicate the natural language of the content of an element. It is generally not used for children of the <tt>text</tt> element at Level 1 or Level 2 but is common at Level 3 and above. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the data.language datatype in the TEI Guidelines].

==Structure of a TEI Document==

<table border="1">
<tr>
<th colspan="2">Element</th>
<th>Description</th>
</tr>
<tr>
<td colspan="2"><tt><TEI></tt></td>
<td>The root element of a TEI document</td>
</tr>
<tr>
<td>├</td>
<td><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> is required; it indicates the language used for the metadata describing the document.</td>
</tr>
<tr>
<td>├</td>
<td><tt><facsimile></tt></td>
<td>The <tt>facsimile</tt> defines sets of images that correspond with the text. Unlike the <tt>teiHeader</tt> and the <tt>text</tt>, it is an optional element in the TEI document.</td>
</tr>

<tr>
<td>└</td>
<td>The <tt><text xml:lang="___"></tt></td>
<td>The <tt>text</tt> element contains the encoded transcription of the source document. The <tt>xml:lang</tt> attribute is recommended; it indicates the primary language of the source document.</td>
</tr>
</table>

The child elements of the <tt>teiHeader</tt> and <tt>text</tt> elements are described below.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. TEI Lite calls the header "the electronic title page", though it actually more closely resembles a catalog record with additional data not routinely stored in MARC records.

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

In order to allow automatic generation of TEI headers from MARC records and MARC records from TEI headers, some elements (like <tt><author></tt>) contain content not typical for TEI practice but necessary due to a lack of granularity in the MARC format.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element. In the absence of such mechanisms, users of these best practices may use the <tt>idno</tt> element to supply identifiers for outside metadata records and may supply identifiers for certain authority records using the <tt>key</tt> or <tt>ref</tt> attributes, allowed on certain elements.

While elements from non-TEI namespaces may be included in a TEI document, these best practices currently do not attempt to prescribe which and where non-TEI elements may or must be used in the header.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. In an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> attribute is required; it indicates the language used for the metadata describing the document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>├</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains bibliographic metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:

* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document—usually, the author(s) of the source document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>X, Malcolm</author></tt>
* <tt><author>Thomas (Anglo-Normal poet)</author></tt>
* <tt><author>Catherine II, Empress of Russia</author></tt>
* <tt><author>Joannes, Actuarius, 13th/14th cent.</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>
If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that acted as editors of the TEI document—usually, the editor(s) of the source document. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

Unlike in the TEI Guidelines, do not use this element for translators, illustrators, compilers, or other roles not generally considered an editor. Therefore, do not use the <tt>role</tt> attribute.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td><p>Record the names of other persons or organizations, one responsibility or party per <tt><respStmt></tt>, that have responsibility for the intellectual or artistic content of the TEI document—often by transitivity from the source document—not covered by <tt><author></tt> and <tt><editor></tt>. This includes translators, illustrators, compilers, proofreaders, encoders, and those who wrote a preface or introduction. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt>title</tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>type</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD. (This element is used instead of <tt><bibl></tt> to enforce structure, but <tt>>biblFull<</tt> is not used because it requires more elements than are typically available in library metadata sources.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the intellectual or artistic content of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. Use a <tt>type</tt> attribute with a value of <tt>marc245c</tt> to give the statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>marc245c</tt> (used for the statement of responsibility according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
<p>Statement of responsibility on the source document, according to the national cataloging code. Record
one responsibility or party per <tt><respStmt></tt>. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p>

<p>If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to split the content of the 245c field into <tt>resp</tt> and <tt>name</tt> elements, so it is recommended to use <tt><title type="marc245c"></tt> instead of this element.</p>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a colon) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "S.l." (for no place of publication).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a comma) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "s.n." (for no publisher).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Optionally, use for notes about the source document, according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
Optionally use one or more <tt>idno</tt> elements to give identification numbers for the source document, text, or work, whether assigned by the holding library (such as a call number), the publisher of the original document (such as an ISBN), or a standard bibliography (such as an identifier from the <cite>Short Title Catalogue</cite> or <cite>Books in Maori</cite>). Use the following values for the <tt>type</tt> attribute if applicable, and create other values if appropriate:

* <tt>LC_call_number</tt>
* <tt>isbn-13</tt>
* <tt>isbn-10</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>
Use the <tt>n</tt> attribute to record the encoding level: <tt>1</tt> for Level 1, <tt>2</tt> for Level 2, etc.

Include one or more <tt>p</tt> elements as children with information on:

* editorial decisions made during encoding
* notes about omissions of material found in the original work
* the format of the data in the header: Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?
* automated processes used to generate the markup or content
* external files or databases (such as those containing authority data) referenced in the TEI document

Also include one of the following <tt>p</tt> elements as appropriate:

<tt><p>All hyphens in source document encoded as U+2010.</p></tt>

<tt><p>Soft hyphens encoded as U+00AD; hard hyphens as U+2010.</p></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><tt><rendition xml:id="_" scheme="css"</tt></td>
<td>Include one or more <tt>rendition</tt> elements for each unique value of a <tt>rendition</tt> attribute (not <tt>rend</tt> attribute) used in the body of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>└</p></td>
<td colspan="3"><tt><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td><p>├</p></td>
<td colspan="5"><tt><langUsage></tt></td>
<td>Optionally use this element and child <tt>language</tt> elements to list languages used in the text. This supplements <tt><text xml:lang="___"></tt> in cases where more than one language is used in the text. It is not expected that the <tt>langUsage</tt> element will contain any description of language usage.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="4"><tt><language ident="___"></tt></td>
<td>Use one or more <tt>language</tt> elements to indicate language(s) used in the source document. The <tt>ident</tt> attribute is usually sufficient to indicate the language, so this element should normally have no content. In the unusual case where <tt>ident</tt> is insufficient, provide additional information on the language as content of the element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers may be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change should be recorded using the <tt>when</tt> attribute ((see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]).

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. For example, the document might simply give <tt>who="#Jane_Smith"</tt>, relying on human readers to understand this reference.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="marc245a">Lincoln and Seward.</title>
<title level="m" type="marc245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="marc245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
<p>All hyphens in source document encoded as U+2010.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<langUsage>
<language ident="en"/>
</langUsage>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images). Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added at a later date</li>
</ul>

====Workflow====

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is left uncorrected ("dirty OCR"). Page images are tagged using software that assigns a page-level metadata (page number and possibly tags for page features) to each page image for display in the user interface in a list of pages. Encoding is performed automatically: markup with page-level metadata is inserted at selected points into the dirty OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====Purpose====
To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

====Rationale====
The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Level 2 requires a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are <i>not</i> intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

'''Level 2 is most suitable for projects in which''':

* a large volume of material is to be made available online quickly
* a digital image of each page is desired
* the material is of interest to a large community of users who wish to read texts that allow keyword searching
* rudimentary search and display capabilities based on the large structures of the text are desired
* each text is checked to ensure that divisions and headers are properly identified
* extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

====Workflow====

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’s heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">Unlike in Level 1, in Level 2 one <tt><div1></tt> or <tt><div></tt> is used per section of the text identified with division-level metadata. If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb n="1" facs="[URI of page 1 image]"/>
<head>[heading of section 1]</head>
<ab>[entire contents of section 1 here, with
interspersed <pb> elements pointing to page
images; in this example there are 26 more pages
to section 1]</ab>
</div>
<div type="section">
<pb n="27" facs="[URI of page 27 image]"/>
<div type="subsection">
<head>[heading of section 2 subsection 1]</head>
<ab>[all the paragraphs of subsection one go here
with page breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>

<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING
SHOULD BE ORDERED.</head>
<ab>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Encoding at this level offers provides the foundation for upgrading to higher levels of encoding. Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date</li>
</ul>

====Workflow====

Level 3 texts can be created by conversion from an electronic source such as an HTML file or word-processor document or from a print source, either through OCR or keyboarding. They can be generated trivially by converting from outsourced double-keyboarded texts conforming to TEI Tite, though some granularity of encoding will be lost in the translation.

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2 '''except <tt>ab</tt>''', plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Table of Contents=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT Chapter 4.5, Front Matter]

You may wish not to include front matter content such as table of contents or lists of illustrations, especially if you plan to automatically generate the contents or lists of illustrations. If you do, however, plan to manually encode the table of contents (or lists of illustrations and similar content), use a <tt>div</tt> element with an appropriate <tt>type</tt> attribute (e.g., <tt><div type="contents"></tt>). Within this division, use the <tt>list</tt> element to mark up the table of contents, list of illustrations, etc. Each list item should have a <tt>ptr</tt> or <tt>ref</tt> element with a <tt>target</tt> attribute referencing an <tt>xml:id</tt> attribute on the <tt><pb></tt> or "div" element of the referenced page or section. Use <tt>ref</tt> if you wish to transcribe page numbers in the table of contents; use <tt>ptr</tt> if you do not.

=====Notes=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog
<ref target="#VAA2383_011" rend="text-align: right">3</ref>
</item>
<item>II. Romance
<ref target="#VAA2383_020" rend="text-align: right">12</ref>
</item>
<item>III. The Costume
<ref target="#VAA2383_029" rend="text-align: right">21</ref>
</item>
<item>IV. Desperation
<ref target="#VAA2383_038" rend="text-align: right">30</ref>
</item>
<item>V. The Pageant of the Table Round
<ref target="#VAA2383_046" rend="text-align: right">38</ref>
</item>
</list>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="font-weight: bold">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"<hi rend="font-variant: small-caps">Penrod Schofield</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>
<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern&amp#xAD;
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open&amp#xAD;
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter&amp#xAD;
mination regarding these issues.</p>

<p>FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

<pb n="114" facs="00000002.tif"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>

<p>In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947.

<note place="bottom" anchored="true" n="68">Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re&amp#xAD;
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu&amp#xAD;
ments. CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<pb n="115" facs="00000003.tif"/>
occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per&amp#xAD;
sonal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note reques&amp#xAD;
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

although no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

====Purpose====
<p>To create text that can stand alone as electronic text, identifies
hierarchy and typography, specifies function of textual and structural elements, and describes the
nature of the content and not merely its appearance. This level is not meant to encode or identify all
structural, semantic, or bibliographic features of the text.</p>

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

<p>Finally, functionally accurate encoding in Level 4 texts
allows them to be searched or displayed in sophisticated ways.
For example, a searcher could limit his or her search in a
dramatic text to stage directions or in a verse text to only
first lines. In a political tract published by subscription, a
search could be confined to names that appear in lists, thus
limiting a search to names of people who subscribed to a
particular volume. This ability to limit searches becomes more
significant as textbases become larger, and thus is of great
importance to the library community as it attempts to build into
the initial design and implementation of textbases the features
needed to enhance interoperability.</p>

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

<li>the texts will be used for textual analysis</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added by the scholarly community at a later date</li>
<li>the users of the texts may have limited storage or display capabilities</li>
</ul>

====Workflow====

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup must be added, as discussed in [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg Appendix A of TEI Tite].

====Element Recommendations for Level 4====

<p>Use all elements specified in Levels 1, 2, and 3 '''except <tt>ab</tt>''', plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="font-weight: bold"></tt>). This element may also be used if the more specific elements above are not used.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSnr Chapter 13.1.1, Linking Names and Their Referents]

Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. See the [[#key_and_ref|discussion of <tt>ref</tt> and <tt>key</tt>]] above for how to choose between them.

If using <tt>key</tt>, provide a unique internal identifier, such as in a local database.

If using <tt>ref</tt>, an external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. In such a case the value of the <tt>ref</tt> attribute in the main TEI document (the transcription of the source document) references the value of the <tt>xml:id</tt> attribute in the external file. (In the examples below, the external file is named <tt>context.xml</tt> for “contextual information” and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* Alternatively, instead of using an external file for the authority data, use the <tt>key</tt> attribute to point to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:

<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="font-style: italic">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—&amp; B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
Source: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====

* Within the front matter (<tt><front></tt>) of a performance text, cast lists should be encoded as <tt><castList></tt>s, with each item in that list encoded as <tt><castItem></tt>s. If desired, each <tt><castItem></tt> may be uniquely identified with the <tt>xml:id</tt> attribute.

For example,

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

In either method, use an <tt>xml:id</tt> on the <tt>name</tt> element to uniquely identify the individual participant:

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

<sp who="spk2">
<speaker n="2">WILLIAM LINK:</speaker>
<p>Last time we were talking about Frank Porter Graham. And I have a couple of questions
about Graham, and I wonder if you could clear them up for me. You have mentioned that you
had worked with him as a student at North Carolina State, had you met him before?
</p>
</sp>
<sp who="spk1">
<speaker n="1">WILLIAM C. FRIDAY: </speaker>
<p>No. That budget hearing was the first that I knew of him, of course, but the first time
that I ever encountered him. I was president of class at N.C. State, and that through me into
this kind of public adventure. And so I went merrily on downtown and sat there in the budget
hearing, along with the president of the student body, and some others.
</p>
</sp>
</pre>

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

Use <tt><lg></tt> and <tt><l></tt> as in Level 3. In addition, use the <tt>rend</tt> attribute to indicate lines that are indented.

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="margin-left: 0.5in" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="margin-left: 0.5in" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="margin-left: 0.5in" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="margin-left: 0.5in" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

===== Level 4 Alger Hiss document =====

Note that the soft hyphen character is displayed as an entity reference because it this character will not display in many web browsers.

<pre><TEI xml:id="project_document_identifier"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="./pageImages/AH4_0113.jpg" ed="typed"/>
<pb n="118" ed="subsequent"/>
<head>POINT VIII.</head>
<head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
<lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
<lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
<lb/>family and associates was not known at the time of trial by
<lb/>the defense. Even now, with the release of some of the govern&#xAD;
<lb/>ment documents concerning FBI investigative techniques regarding
<lb/>Hiss, the full extent of surveillance -- wiretapping, mail open&#xAD;
<lb/>ings, mail covers, physical surveillance, and other intrusive
<lb/>techniques -- is still not 'clear. Nevertheless, it is apparent
<lb/>that information gathered through the exploitation of unlawful
<lb/>wiretaps and other illegal surveillance was used at trial and
<lb/>consequently the conviction must be reversed. Alternatively,
<lb/>further discovery and a hearing is essential to a fair deter&#xAD;
<lb/>mination regarding these issues.</p>
<p>FBI surveillance of Hiss began in earnest in 1941 with
<lb/>the institution of a mail cover on his incoming correspondence
<lb/>at his home in connection with an FBI investigation of possible
<lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed
<pb n="114" facs="./pageImages/AH_0114.jpg"/>
<pb n="119" ed="subsequent"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
<lb/>toll call records from the Hiss residence Telephone for the
<lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
<lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>
<p>In late November, 1945, FBI surveillance of the Hiss
<lb/>residence in Washington, D.C., escalated. For the third time,
<lb/>a mail cover was instituted beginning on November 28, 1945,
<lb/>which was continued at least until 1946. CN Ex. 101 at p. 70;
<lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun
<lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
<lb/>surveillance was discontinued on December 14, 1945, physical
<lb/>surveillance was conducted frequently at various times until
<lb/>September, 1947.<note place="foot" anchored="true" n="68">Also
before 1947, a letter from Priscilla Hiss addressed
<lb/>to her son, Timothy Hobson, was intercepted and its contents
<lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947,
<lb/>a letter from a Michael Greenberg addressed to petitioner re&#xAD;
<lb/>garding an application for employment with the United Nations
<lb/>was also intercepted, in a manner not revealed by the docu&#xAD;
<lb/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p>
<p>The most intrusive invasion of petitioner's rights
<pb n="115" facs="./pageImages/AH_0115.jpg"/>
<pb n="120" ed="subsequent"/>
<lb/>occurred from December 13, 1945 until the Hisses moved from
<lb/>Washington, D.C. to New York City on September 13, 1947. A
<soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss
<lb/>telephone at their residence on P Street-in Washington, D.C.
<lb/>The logs of this surveillance constitute twenty-nine volumes
<lb/>of FBI serials and are roughly 2,500 pages in length, in which
<lb/>an enormous amount of information concerning the Hisses' per&#xAD;
<lb/>sonal lives, relationships with friends and associates, and
<lb/>habits is recorded.</p>
<p>The wiretap was installed following FBI Director Hoover's
<lb/>application to the Attorney General for authorization,<note place="bottom" anchored="true" n="69">Hoover's
initial request was answered by a note reques&#xAD;
<lb/>ting information on Hiss. CN Ex. 104<sic> </sic>. Additional information
<lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic> </sic>.</note>
<lb/>although no written authorization appears in the documents released to
<lb/>Hiss. The purpose of the application was to gather information
<lb/>regarding Hiss' alleged contacts with Soviet espionage agents and
<lb/>communists in government service, general allegations which had
<lb/>been made by Elizabeth Bentley and Chambers.</p>
<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI></pre>

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require substantial human intervention by encoders with subject knowledge. These texts might include encodings of semantic, linguistic, prosodic, or other features well beyond the basic structural elements discussed in Levels 1-4 above. They might also include elements for editorial, critical, or analytical additions; manuscript descriptions; translations; or other textual apparatus. It is impossible to make concrete recommendations for encoding at this level since the scholarly analysis required is usually specific to each project; instead, Level 5 offers the full set of P5 elements as needed.

====Reference====
* [http://www.tei-c.org/Guidelines/P5 Complete P5 Guidelines]

====Purpose====
To create deeply analytical encoded texts that might be appropriate for specific research purposes, as part of a scholarly publishing project, or for any other encoding practices in library-based text encoding.

====Rationale====
A significant number of library-based projects engage in high-level analytical text encoding as part of their efforts in digitization, scholarly editing, academic support, or other research. Level 5 is intended to represent that work, which can take advantage of the full richness of the complete TEI Guidelines, while still acknowledging the impact of library-specific practices on encoded text that is created under the auspices of a library.

The specific influences of library practice on a Level-5 encoded text are expressed primarily in adherence to the [[#General_Recommendations|General Recommendations]] and [[#The_TEI_Header|TEI Header]] sections above.

====Element Recommendations and Examples====
Because of the vast range of possibilities for Level-5 encoding, we have chosen to provide neither a list of recommended elements nor any specific examples for this Level.

Please refer to the [[#The_TEI_Header|TEI Header]] section above for examples of <tt><TeiHeader></tt> element usage, and to the [[#General_Recommendations|General Recommendations]] section and the [http://www.tei-c.org/Guidelines/P5 Complete TEI P5 Guidelines] for element recommendations and usage examples within the <tt><text></tt> element.

==Acknowledgments==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Renee McBride, University of North Carolina, Chapel Hill
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to copyediting of this document are:
* Susan Lorand, University of Michigan
* Becky Welzenbach, University of Michigan

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==

This document was formerly known as "TEI Text Encoding in Libraries Guidelines for Best Encoding Practices".

<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (often referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

= Appendix B: Formal Specification =

(This section will be generated automatically once ODDs are created.)

[[Category:SIG:Libraries]]

Talk:Best Practices for TEI in Libraries

2009-06-18T19:05:06Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T19:00:40Z

RebeccaWelzenbach:

==Introduction ==

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

== 2.9 General Guidelines for Attribute Usage ==

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

2) Under "key and ref":

"For example,

<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>

gives a project-interal key (lccn-n78-95332) for this name in the Library of Congress Name Authority File. Values of key attributes may be partially explained in a non-machine-readable way through use of a taxonomy element: "

should "project-interal" be "project-internal?" Or "project-integral?" Or something else?

3) Under "rend and rendition":

"The rend and rendition attributes may be used when it is desirable to record information about how the content object was displayed in the source document. "

Is it meant to read "content object," or just "content," or even just "object?" Having both sounds strange to me, but perhaps it's TEI terminology with which I'm not familiar.

== 4.2 The TEI Header ==

1) Currently reads:
"The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification."

Since there are multiple levels of encoding (does this translate to multiple "specifications?"), should this read either

a) "...encoded according to '''a''' TEI specification"
or
b) "...encoded according to the TEI specification'''s'''" ?

== 4.4 The TEI Header and Other Metadata Schemas ==

1) Currently reads:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element"

To me, the "it" was confusing/ambiguous--I suggest instead:

"Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that '''outside metadata''' should supplement the content of the element"

This feels a little more redundant/wordy, perhaps, but it is clearer.

== 4.5 Determining Data Values for the TEI Header ==

1) Currently reads:

"'''If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation.''' The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used."

Does "source document" refer an analog (physical) source document? Or digitized pages, just lacking a title page? Or OCR or keyboarded text? Or any or all of these things?

Follow up question: If the electronic text already exists, wouldn't title page information be captured in the <code><text></code> element, and so metadata for the header could be gathered from here even without a facsimile of the title page?

Best Practices for TEI in Libraries

2009-06-18T18:47:49Z

RebeccaWelzenbach: /* Determining Data Values for the TEI Header */

----
* [[SIG:Libraries|TEI in Libraries: Home]]
----

==Introduction==

These best practices are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, these best practices are meant to be as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing. The encoding levels are not strictly cumulative: while higher levels tend to build upon lower levels by including more elements, higher levels are not supersets because some elements used at lower levels are not used at all at higher levels.

In brief, the encoding levels are:

{| border="1"
|-
| Level 1
| The text is generated through OCR, is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).
|-
| Level 2
| The text is generated through OCR and is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured.
|-
| Level 3
| The text is created by conversion from an electronic source such as HTML or word-processor documents or from a print source, either by way of OCR or keyboarding.
|-
| Level 4
| The text is generated either through corrected OCR or keyboarding and is able to stand alone without page images in order for them to be read by students, scholars, and general readers.
|-
| Level 5
| The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge.
|}

These best practices are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention. Level 3 does not contain as many elements as TEI Tite in order to allow for mass digitization of born-digital source documents or for upgrading of Level 1 or Level 2 texts with only minimal human intervention. For more information, see [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg TEI Tite's Appendix A].

These best practices specify a recommended archival storage format. Local system needs may require transformation of documents in this archival format to another XML format for use by a local indexing or delivery software.

In these guidelines, use of elements and attributes tends toward explicitness for ease of processing even though a human or possibly machine reader might be able to make inferences based on context.

==General Recommendations==

=== Standards and local practice ===

The goal of the TEI is interchange, not interoperability. While seamless interoperability of texts created by different organizations is an unobtainable goal, use of a common markup vocabulary and syntax greatly aids interchange. Nevertheless, keep in mind that others—even within your organization—may use your texts in the future for other uses than you intended in your encoding.

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Hyphenation ===

Encoding end-of-line, end-of-column, and end-of-page hyphenation varies considerably in the TEI community. Some capture all hyphens found on the printed page, while others remove those in the middle of words not normally hyphenated for easier implementation of full-text retrieval. If preserving hyphens, some will capture all hyphens using the same character, while others will distinguish hyphens that must be present in any case (often called "hard hyphens") and those that are only present by virtue of being at the end of a line, column, or page (often called "soft hyphens").

This issue is complicated by the fact that Unicode presribes use of a soft hyphen not for a ''visible hyphen that might have been absent'' but instead for a place where a hyphen ''might occur''. Furthermore, it includes a "non-breaking hyphen", used in cases like "re-creation" (meaning "to create again", as opposed to recreation, meaning "relaxation"), in addition to a regular hyphen, which would normally count as a word boundary. In short, Unicode is oriented toward electronic text that may be processed with a computer in various ways, not toward capturing source documents.

Since OCR software relies on dictionaries to determine the probability not simply of characters but of whole words, it is often able to handle hyphenation in different ways.

At Levels 1 and 2, no attempt should be made to remove hyphens from the source document or disambiguate hard and soft hyphens. Encode all hyphens appearing in the source document using character U+2010.

At Level 3, either encode hyphens as in Levels 1 and 2 or disambiguate soft and hard hyphens. In the latter case, soft hyphens should be encoded using U+00AD and hard hyphens using U+2010.

At Levels 4 or 5, hyphens must be disambiguated using U+00AD for soft hyphens and U+2010 for hard hyphens.

In any case, the hyphenation practice must be recorded in the <tt>editorialDecl</tt>.

Do not confuse hyphen characters with the minus character (U+2212).

=== Filenames ===

A filename scheme that is internally consistent should be established for the project.

If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. Likewise, if you will access files using a version of Apple Filing Protocol (AFP) before 3.0, filenames longer than 31 bytes are likely to be corrupted, so you may wish to limit filenames to 31 single-byte (e.g., ASCII) characters.

Otherwise, consider the following best practices when determining the file name scheme for your project:

* Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
* Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
* Filenames should not include spaces
* Filenames should follow predictable case constructions (e.g., all lowercase, camelCase, etc.)
* The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and XML-based metadata languages
* The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

The choice of numbered or unnumbered divisions must be documented with the <tt>tagUsage</tt> element in the header. See 4.6, Element Recommendations for the TEI Header, below.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at Level 1 (because only one encoded division in the text exists), is optional at Level 2 (because the division-level metadata need not classify these divisions), is recommended at Level 3 (for broad yet useful analysis of text divisions), and required at Levels 4 and 5 (for full analysis of the text structure).

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, with the value of the <tt>n</tt> attribute denoting the number of the page whose text ''follows'' this element. The <tt>pb</tt> element should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are three recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facsimile]</tt> element to define a set of images that corresponds to the text in conjunction with the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== key and ref ====

These attributes are available on the same elements and are used to reference external metadata about the content of the element. The <tt>key</tt> element may contain any string of Unicode characters, whereas the <tt>ref</tt> attribute must contain a URI (including a relative one, as discussed above). While <tt>key</tt> may supply any identifier, there is no mechanism internal to XML for checking that the value of this attribute is valid.

For example,

<code>
<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>
</code>

gives a project-interal key (<tt>lccn-n78-95332</tt>) for this name in the Library of Congress Name Authority File. Values of <tt>key</tt> attributes may be partially explained in a non-machine-readable way through use of a <tt>taxonomy</tt> element:

<code>
<taxonomy xml:id="lccn"><bibl>Library of Congress Control Number</bibl></taxonomy>
</code>

Alternatively, use <tt>ref</tt> with a URI fragment identifier, corresponding to the value of <tt>xml:id</tt> given elsewhere. For example, in the transcription of the text, use

<code>
<placeName ref="#tgn_7012924">Indianapolis</placeName>
</code>

which would be defined in a controlled vocabulary elsewhere:

<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
</listPlace>
</pre>

When validation software encounters <tt>ref="#tgn_7012924"</tt>, it will check that <tt>xml:id="tgn_7012924"</tt> exists elsewhere in the document.

==== rend and rendition ====

The <tt>rend</tt> and <tt>rendition</tt> attributes may be used when it is desirable to record information about how the content object was displayed in the source document.

Never use these attributes on header elements: metadata is transcribed and possibly regularized, as in a catalog record, but its exact appearance is not meant to be captured.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use these attributes; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, one of these attributes should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

For the value of the <tt>rend</tt> attribute, use only valid CSS properties and values. For example:

* <tt><foreign rend="font-style: italic"></tt>
* <tt><title rend="text-decoration: underline; font-size: x-large"></tt>

Alternatively, use the <tt>rendition</tt> '''attribute''' to give an internal scheme:

<tt><foreign rendition="#i"></tt>

documented with the <tt>rendition</tt> '''element''' in the header:

<tt><rendition xml:id="i" scheme="css">font-style: italic</rendition></tt>

Use of the <tt>rendition</tt> attribute and element offers an additional level of indirection, decreasing the total number of keystrokes and possibly reducing the chance of typos being introduced in the encoding.

==== xml:lang ====

Used to indicate the natural language of the content of an element. It is generally not used for children of the <tt>text</tt> element at Level 1 or Level 2 but is common at Level 3 and above. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the data.language datatype in the TEI Guidelines].

==Structure of a TEI Document==

<table border="1">
<tr>
<th colspan="2">Element</th>
<th>Description</th>
</tr>
<tr>
<td colspan="2"><tt><TEI></tt></td>
<td>The root element of a TEI document</td>
</tr>
<tr>
<td>├</td>
<td><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> is required; it indicates the language used for the metadata describing the document.</td>
</tr>
<tr>
<td>├</td>
<td><tt><facsimile></tt></td>
<td>The <tt>facsimile</tt> defines sets of images that correspond with the text. Unlike the <tt>teiHeader</tt> and the <tt>text</tt>, it is an optional element in the TEI document.</td>
</tr>

<tr>
<td>└</td>
<td>The <tt><text xml:lang="___"></tt></td>
<td>The <tt>text</tt> element contains the encoded transcription of the source document. The <tt>xml:lang</tt> attribute is recommended; it indicates the primary language of the source document.</td>
</tr>
</table>

The child elements of the <tt>teiHeader</tt> and <tt>text</tt> elements are described below.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. TEI Lite calls the header "the electronic title page", though it actually more closely resembles a catalog record with additional data not routinely stored in MARC records.

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

In order to allow automatic generation of TEI headers from MARC records and MARC records from TEI headers, some elements (like <tt><author></tt>) contain content not typical for TEI practice but necessary due to a lack of granularity in the MARC format.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element. In the absence of such mechanisms, users of these best practices may use the <tt>idno</tt> element to supply identifiers for outside metadata records and may supply identifiers for certain authority records using the <tt>key</tt> or <tt>ref</tt> attributes, allowed on certain elements.

While elements from non-TEI namespaces may be included in a TEI document, these best practices currently do not attempt to prescribe which and where non-TEI elements may or must be used in the header.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. In an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> attribute is required; it indicates the language used for the metadata describing the document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>├</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains bibliographic metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:

* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document—usually, the author(s) of the source document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>X, Malcolm</author></tt>
* <tt><author>Thomas (Anglo-Normal poet)</author></tt>
* <tt><author>Catherine II, Empress of Russia</author></tt>
* <tt><author>Joannes, Actuarius, 13th/14th cent.</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>
If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that acted as editors of the TEI document—usually, the editor(s) of the source document. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

Unlike in the TEI Guidelines, do not use this element for translators, illustrators, compilers, or other roles not generally considered an editor. Therefore, do not use the <tt>role</tt> attribute.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td><p>Record the names of other persons or organizations, one responsibility or party per <tt><respStmt></tt>, that have responsibility for the intellectual or artistic content of the TEI document—often by transitivity from the source document—not covered by <tt><author></tt> and <tt><editor></tt>. This includes translators, illustrators, compilers, proofreaders, encoders, and those who wrote a preface or introduction. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt>title</tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>type</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD. (This element is used instead of <tt><bibl></tt> to enforce structure, but <tt>>biblFull<</tt> is not used because it requires more elements than are typically available in library metadata sources.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the intellectual or artistic content of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. Use a <tt>type</tt> attribute with a value of <tt>marc245c</tt> to give the statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>marc245c</tt> (used for the statement of responsibility according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
<p>Statement of responsibility on the source document, according to the national cataloging code. Record
one responsibility or party per <tt><respStmt></tt>. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p>

<p>If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to split the content of the 245c field into <tt>resp</tt> and <tt>name</tt> elements, so it is recommended to use <tt><title type="marc245c"></tt> instead of this element.</p>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a colon) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "S.l." (for no place of publication).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a comma) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "s.n." (for no publisher).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Optionally, use for notes about the source document, according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
Optionally use one or more <tt>idno</tt> elements to give identification numbers for the source document, text, or work, whether assigned by the holding library (such as a call number), the publisher of the original document (such as an ISBN), or a standard bibliography (such as an identifier from the <cite>Short Title Catalogue</cite> or <cite>Books in Maori</cite>). Use the following values for the <tt>type</tt> attribute if applicable, and create other values if appropriate:

* <tt>LC_call_number</tt>
* <tt>isbn-13</tt>
* <tt>isbn-10</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>
Use the <tt>n</tt> attribute to record the encoding level: <tt>1</tt> for Level 1, <tt>2</tt> for Level 2, etc.

Include one or more <tt>p</tt> elements as children with information on:

* editorial decisions made during encoding
* notes about omissions of material found in the original work
* the format of the data in the header: Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?
* automated processes used to generate the markup or content
* external files or databases (such as those containing authority data) referenced in the TEI document

Also include one of the following <tt>p</tt> elements as appropriate:

<tt><p>All hyphens in source document encoded as U+2010.</p></tt>

<tt><p>Soft hyphens encoded as U+00AD; hard hyphens as U+2010.</p></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><tt><rendition xml:id="_" scheme="css"</tt></td>
<td>Include one or more <tt>rendition</tt> elements for each unique value of a <tt>rendition</tt> attribute (not <tt>rend</tt> attribute) used in the body of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>└</p></td>
<td colspan="3"><tt><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td><p>├</p></td>
<td colspan="5"><tt><langUsage></tt></td>
<td>Optionally use this element and child <tt>language</tt> elements to list languages used in the text. This supplements <tt><text xml:lang="___"></tt> in cases where more than one language is used in the text. It is not expected that the <tt>langUsage</tt> element will contain any description of language usage.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="4"><tt><language ident="___"></tt></td>
<td>Use one or more <tt>language</tt> elements to indicate language(s) used in the source document. The <tt>ident</tt> attribute is usually sufficient to indicate the language, so this element should normally have no content. In the unusual case where <tt>ident</tt> is insufficient, provide additional information on the language as content of the element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers may be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change should be recorded using the <tt>when</tt> attribute ((see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]).

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. For example, the document might simply give <tt>who="#Jane_Smith"</tt>, relying on human readers to understand this reference.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="marc245a">Lincoln and Seward.</title>
<title level="m" type="marc245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="marc245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
<p>All hyphens in source document encoded as U+2010.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<langUsage>
<language ident="en"/>
</langUsage>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images). Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added at a later date</li>
</ul>

====Workflow====

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is left uncorrected ("dirty OCR"). Page images are tagged using software that assigns a page-level metadata (page number and possibly tags for page features) to each page image for display in the user interface in a list of pages. Encoding is performed automatically: markup with page-level metadata is inserted at selected points into the dirty OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====Purpose====
To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

====Rationale====
The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Level 2 requires a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are <i>not</i> intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

'''Level 2 is most suitable for projects in which''':

* a large volume of material is to be made available online quickly
* a digital image of each page is desired
* the material is of interest to a large community of users who wish to read texts that allow keyword searching
* rudimentary search and display capabilities based on the large structures of the text are desired
* each text is checked to ensure that divisions and headers are properly identified
* extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

====Workflow====

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’s heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">Unlike in Level 1, in Level 2 one <tt><div1></tt> or <tt><div></tt> is used per section of the text identified with division-level metadata. If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb n="1" facs="[URI of page 1 image]"/>
<head>[heading of section 1]</head>
<ab>[entire contents of section 1 here, with
interspersed <pb> elements pointing to page
images; in this example there are 26 more pages
to section 1]</ab>
</div>
<div type="section">
<pb n="27" facs="[URI of page 27 image]"/>
<div type="subsection">
<head>[heading of section 2 subsection 1]</head>
<ab>[all the paragraphs of subsection one go here
with page breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>

<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING
SHOULD BE ORDERED.</head>
<ab>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Encoding at this level offers provides the foundation for upgrading to higher levels of encoding. Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date</li>
</ul>

====Workflow====

Level 3 texts can be created by conversion from an electronic source such as an HTML file or word-processor document or from a print source, either through OCR or keyboarding. They can be generated trivially by converting from outsourced double-keyboarded texts conforming to TEI Tite, though some granularity of encoding will be lost in the translation.

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2 '''except <tt>ab</tt>''', plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Table of Contents=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT Chapter 4.5, Front Matter]

You may wish not to include front matter content such as table of contents or lists of illustrations, especially if you plan to automatically generate the contents or lists of illustrations. If you do, however, plan to manually encode the table of contents (or lists of illustrations and similar content), use a <tt>div</tt> element with an appropriate <tt>type</tt> attribute (e.g., <tt><div type="contents"></tt>). Within this division, use the <tt>list</tt> element to mark up the table of contents, list of illustrations, etc. Each list item should have a <tt>ptr</tt> or <tt>ref</tt> element with a <tt>target</tt> attribute referencing an <tt>xml:id</tt> attribute on the <tt><pb></tt> or "div" element of the referenced page or section. Use <tt>ref</tt> if you wish to transcribe page numbers in the table of contents; use <tt>ptr</tt> if you do not.

=====Notes=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog
<ref target="#VAA2383_011" rend="text-align: right">3</ref>
</item>
<item>II. Romance
<ref target="#VAA2383_020" rend="text-align: right">12</ref>
</item>
<item>III. The Costume
<ref target="#VAA2383_029" rend="text-align: right">21</ref>
</item>
<item>IV. Desperation
<ref target="#VAA2383_038" rend="text-align: right">30</ref>
</item>
<item>V. The Pageant of the Table Round
<ref target="#VAA2383_046" rend="text-align: right">38</ref>
</item>
</list>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="font-weight: bold">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"<hi rend="font-variant: small-caps">Penrod Schofield</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>
<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern&amp#xAD;
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open&amp#xAD;
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter&amp#xAD;
mination regarding these issues.</p>

<p>FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

<pb n="114" facs="00000002.tif"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>

<p>In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947.

<note place="bottom" anchored="true" n="68">Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re&amp#xAD;
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu&amp#xAD;
ments. CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<pb n="115" facs="00000003.tif"/>
occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per&amp#xAD;
sonal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note reques&amp#xAD;
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

although no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

====Purpose====
<p>To create text that can stand alone as electronic text, identifies
hierarchy and typography, specifies function of textual and structural elements, and describes the
nature of the content and not merely its appearance. This level is not meant to encode or identify all
structural, semantic, or bibliographic features of the text.</p>

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

<p>Finally, functionally accurate encoding in Level 4 texts
allows them to be searched or displayed in sophisticated ways.
For example, a searcher could limit his or her search in a
dramatic text to stage directions or in a verse text to only
first lines. In a political tract published by subscription, a
search could be confined to names that appear in lists, thus
limiting a search to names of people who subscribed to a
particular volume. This ability to limit searches becomes more
significant as textbases become larger, and thus is of great
importance to the library community as it attempts to build into
the initial design and implementation of textbases the features
needed to enhance interoperability.</p>

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

<li>the texts will be used for textual analysis</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added by the scholarly community at a later date</li>
<li>the users of the texts may have limited storage or display capabilities</li>
</ul>

====Workflow====

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup must be added, as discussed in [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg Appendix A of TEI Tite].

====Element Recommendations for Level 4====

<p>Use all elements specified in Levels 1, 2, and 3 '''except <tt>ab</tt>''', plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="font-weight: bold"></tt>). This element may also be used if the more specific elements above are not used.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSnr Chapter 13.1.1, Linking Names and Their Referents]

Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. See the [[#key_and_ref|discussion of <tt>ref</tt> and <tt>key</tt>]] above for how to choose between them.

If using <tt>key</tt>, provide a unique internal identifier, such as in a local database.

If using <tt>ref</tt>, an external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. In such a case the value of the <tt>ref</tt> attribute in the main TEI document (the transcription of the source document) references the value of the <tt>xml:id</tt> attribute in the external file. (In the examples below, the external file is named <tt>context.xml</tt> for “contextual information” and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* Alternatively, instead of using an external file for the authority data, use the <tt>key</tt> attribute to point to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:

<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="font-style: italic">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—&amp; B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
Source: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====

* Within the front matter (<tt><front></tt>) of a performance text, cast lists should be encoded as <tt><castList></tt>s, with each item in that list encoded as <tt><castItem></tt>s. If desired, each <tt><castItem></tt> may be uniquely identified with the <tt>xml:id</tt> attribute.

For example,

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

In either method, use an <tt>xml:id</tt> on the <tt>name</tt> element to uniquely identify the individual participant:

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

<sp who="spk2">
<speaker n="2">WILLIAM LINK:</speaker>
<p>Last time we were talking about Frank Porter Graham. And I have a couple of questions
about Graham, and I wonder if you could clear them up for me. You have mentioned that you
had worked with him as a student at North Carolina State, had you met him before?
</p>
</sp>
<sp who="spk1">
<speaker n="1">WILLIAM C. FRIDAY: </speaker>
<p>No. That budget hearing was the first that I knew of him, of course, but the first time
that I ever encountered him. I was president of class at N.C. State, and that through me into
this kind of public adventure. And so I went merrily on downtown and sat there in the budget
hearing, along with the president of the student body, and some others.
</p>
</sp>
</pre>

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

Use <tt><lg></tt> and <tt><l></tt> as in Level 3. In addition, use the <tt>rend</tt> attribute to indicate lines that are indented.

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="margin-left: 0.5in" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="margin-left: 0.5in" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="margin-left: 0.5in" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="margin-left: 0.5in" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

===== Level 4 Alger Hiss document =====

Note that the soft hyphen character is displayed as an entity reference because it this character will not display in many web browsers.

<pre><TEI xml:id="project_document_identifier"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="./pageImages/AH4_0113.jpg" ed="typed"/>
<pb n="118" ed="subsequent"/>
<head>POINT VIII.</head>
<head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
<lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
<lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
<lb/>family and associates was not known at the time of trial by
<lb/>the defense. Even now, with the release of some of the govern&#xAD;
<lb/>ment documents concerning FBI investigative techniques regarding
<lb/>Hiss, the full extent of surveillance -- wiretapping, mail open&#xAD;
<lb/>ings, mail covers, physical surveillance, and other intrusive
<lb/>techniques -- is still not 'clear. Nevertheless, it is apparent
<lb/>that information gathered through the exploitation of unlawful
<lb/>wiretaps and other illegal surveillance was used at trial and
<lb/>consequently the conviction must be reversed. Alternatively,
<lb/>further discovery and a hearing is essential to a fair deter&#xAD;
<lb/>mination regarding these issues.</p>
<p>FBI surveillance of Hiss began in earnest in 1941 with
<lb/>the institution of a mail cover on his incoming correspondence
<lb/>at his home in connection with an FBI investigation of possible
<lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed
<pb n="114" facs="./pageImages/AH_0114.jpg"/>
<pb n="119" ed="subsequent"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
<lb/>toll call records from the Hiss residence Telephone for the
<lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
<lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>
<p>In late November, 1945, FBI surveillance of the Hiss
<lb/>residence in Washington, D.C., escalated. For the third time,
<lb/>a mail cover was instituted beginning on November 28, 1945,
<lb/>which was continued at least until 1946. CN Ex. 101 at p. 70;
<lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun
<lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
<lb/>surveillance was discontinued on December 14, 1945, physical
<lb/>surveillance was conducted frequently at various times until
<lb/>September, 1947.<note place="foot" anchored="true" n="68">Also
before 1947, a letter from Priscilla Hiss addressed
<lb/>to her son, Timothy Hobson, was intercepted and its contents
<lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947,
<lb/>a letter from a Michael Greenberg addressed to petitioner re&#xAD;
<lb/>garding an application for employment with the United Nations
<lb/>was also intercepted, in a manner not revealed by the docu&#xAD;
<lb/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p>
<p>The most intrusive invasion of petitioner's rights
<pb n="115" facs="./pageImages/AH_0115.jpg"/>
<pb n="120" ed="subsequent"/>
<lb/>occurred from December 13, 1945 until the Hisses moved from
<lb/>Washington, D.C. to New York City on September 13, 1947. A
<soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss
<lb/>telephone at their residence on P Street-in Washington, D.C.
<lb/>The logs of this surveillance constitute twenty-nine volumes
<lb/>of FBI serials and are roughly 2,500 pages in length, in which
<lb/>an enormous amount of information concerning the Hisses' per&#xAD;
<lb/>sonal lives, relationships with friends and associates, and
<lb/>habits is recorded.</p>
<p>The wiretap was installed following FBI Director Hoover's
<lb/>application to the Attorney General for authorization,<note place="bottom" anchored="true" n="69">Hoover's
initial request was answered by a note reques&#xAD;
<lb/>ting information on Hiss. CN Ex. 104<sic> </sic>. Additional information
<lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic> </sic>.</note>
<lb/>although no written authorization appears in the documents released to
<lb/>Hiss. The purpose of the application was to gather information
<lb/>regarding Hiss' alleged contacts with Soviet espionage agents and
<lb/>communists in government service, general allegations which had
<lb/>been made by Elizabeth Bentley and Chambers.</p>
<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI></pre>

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require substantial human intervention by encoders with subject knowledge. These texts might include encodings of semantic, linguistic, prosodic, or other features well beyond the basic structural elements discussed in Levels 1-4 above. They might also include elements for editorial, critical, or analytical additions; manuscript descriptions; translations; or other textual apparatus. It is impossible to make concrete recommendations for encoding at this level since the scholarly analysis required is usually specific to each project; instead, Level 5 offers the full set of P5 elements as needed.

====Reference====
* [http://www.tei-c.org/Guidelines/P5 Complete P5 Guidelines]

====Purpose====
To create deeply analytical encoded texts that might be appropriate for specific research purposes, as part of a scholarly publishing project, or for any other encoding practices in library-based text encoding.

====Rationale====
A significant number of library-based projects engage in high-level analytical text encoding as part of their efforts in digitization, scholarly editing, academic support, or other research. Level 5 is intended to represent that work, which can take advantage of the full richness of the complete TEI Guidelines, while still acknowledging the impact of library-specific practices on encoded text that is created under the auspices of a library.

The specific influences of library practice on a Level-5 encoded text are expressed primarily in adherence to the [[#General_Recommendations|General Recommendations]] and [[#The_TEI_Header|TEI Header]] sections above.

====Element Recommendations and Examples====
Because of the vast range of possibilities for Level-5 encoding, we have chosen to provide neither a list of recommended elements nor any specific examples for this Level.

Please refer to the [[#The_TEI_Header|TEI Header]] section above for examples of <tt><TeiHeader></tt> element usage, and to the [[#General_Recommendations|General Recommendations]] section and the [http://www.tei-c.org/Guidelines/P5 Complete TEI P5 Guidelines] for element recommendations and usage examples within the <tt><text></tt> element.

==Acknowledgments==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Renee McBride, University of North Carolina, Chapel Hill
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to copyediting of this document are:
* Susan Lorand, University of Michigan
* Becky Welzenbach, University of Michigan

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==

This document was formerly known as "TEI Text Encoding in Libraries Guidelines for Best Encoding Practices".

<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (often referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

= Appendix B: Formal Specification =

(This section will be generated automatically once ODDs are created.)

[[Category:SIG:Libraries]]

Talk:Best Practices for TEI in Libraries

2009-06-18T18:38:44Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T18:30:36Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T18:19:12Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T18:09:55Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T18:06:57Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T18:06:38Z

RebeccaWelzenbach: /* '''Introduction:''' */

== '''Introduction:''' ==

1) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)

2) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

== 2.9 General Guidelines for Attribute Usage ==

1) Since this isn't a comprehensive list of attributes (I don't think), why bother including the "xml:id" and "target" attributes if specific details about how libraries should use these is not actually included in this document? Is the documentation for these elements considered important to these guidelines, but too extensive to replicate? How does this differ from the specific best practices given for other attributes listed here, like "n" or "rend"?

Best Practices for TEI in Libraries

2009-06-18T17:53:07Z

RebeccaWelzenbach: /* Text divisions */

----
* [[SIG:Libraries|TEI in Libraries: Home]]
----

==Introduction==

These best practices are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, these best practices are meant to be as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing. The encoding levels are not strictly cumulative: while higher levels tend to build upon lower levels by including more elements, higher levels are not supersets because some elements used at lower levels are not used at all at higher levels.

In brief, the encoding levels are:

{| border="1"
|-
| Level 1
| The text is generated through OCR, is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).
|-
| Level 2
| The text is generated through OCR and is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured.
|-
| Level 3
| The text is created by conversion from an electronic source such as HTML or word-processor documents or from a print source, either by way of OCR or keyboarding.
|-
| Level 4
| The text is generated either through corrected OCR or keyboarding and is able to stand alone without page images in order for them to be read by students, scholars, and general readers.
|-
| Level 5
| The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge.
|}

These best practices are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention. Level 3 does not contain as many elements as TEI Tite in order to allow for mass digitization of born-digital source documents or for upgrading of Level 1 or Level 2 texts with only minimal human intervention. For more information, see [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg TEI Tite's Appendix A].

These best practices specify a recommended archival storage format. Local system needs may require transformation of documents in this archival format to another XML format for use by a local indexing or delivery software.

In these guidelines, use of elements and attributes tends toward explicitness for ease of processing even though a human or possibly machine reader might be able to make inferences based on context.

==General Recommendations==

=== Standards and local practice ===

The goal of the TEI is interchange, not interoperability. While seamless interoperability of texts created by different organizations is an unobtainable goal, use of a common markup vocabulary and syntax greatly aids interchange. Nevertheless, keep in mind that others—even within your organization—may use your texts in the future for other uses than you intended in your encoding.

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Hyphenation ===

Encoding end-of-line, end-of-column, and end-of-page hyphenation varies considerably in the TEI community. Some capture all hyphens found on the printed page, while others remove those in the middle of words not normally hyphenated for easier implementation of full-text retrieval. If preserving hyphens, some will capture all hyphens using the same character, while others will distinguish hyphens that must be present in any case (often called "hard hyphens") and those that are only present by virtue of being at the end of a line, column, or page (often called "soft hyphens").

This issue is complicated by the fact that Unicode presribes use of a soft hyphen not for a ''visible hyphen that might have been absent'' but instead for a place where a hyphen ''might occur''. Furthermore, it includes a "non-breaking hyphen", used in cases like "re-creation" (meaning "to create again", as opposed to recreation, meaning "relaxation"), in addition to a regular hyphen, which would normally count as a word boundary. In short, Unicode is oriented toward electronic text that may be processed with a computer in various ways, not toward capturing source documents.

Since OCR software relies on dictionaries to determine the probability not simply of characters but of whole words, it is often able to handle hyphenation in different ways.

At Levels 1 and 2, no attempt should be made to remove hyphens from the source document or disambiguate hard and soft hyphens. Encode all hyphens appearing in the source document using character U+2010.

At Level 3, either encode hyphens as in Levels 1 and 2 or disambiguate soft and hard hyphens. In the latter case, soft hyphens should be encoded using U+00AD and hard hyphens using U+2010.

At Levels 4 or 5, hyphens must be disambiguated using U+00AD for soft hyphens and U+2010 for hard hyphens.

In any case, the hyphenation practice must be recorded in the <tt>editorialDecl</tt>.

Do not confuse hyphen characters with the minus character (U+2212).

=== Filenames ===

A filename scheme that is internally consistent should be established for the project.

If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. Likewise, if you will access files using a version of Apple Filing Protocol (AFP) before 3.0, filenames longer than 31 bytes are likely to be corrupted, so you may wish to limit filenames to 31 single-byte (e.g., ASCII) characters.

Otherwise, consider the following best practices when determining the file name scheme for your project:

* Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
* Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
* Filenames should not include spaces
* Filenames should follow predictable case constructions (e.g., all lowercase, camelCase, etc.)
* The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and XML-based metadata languages
* The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

The choice of numbered or unnumbered divisions must be documented with the <tt>tagUsage</tt> element in the header. See 4.6, Element Recommendations for the TEI Header, below.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at Level 1 (because only one encoded division in the text exists), is optional at Level 2 (because the division-level metadata need not classify these divisions), is recommended at Level 3 (for broad yet useful analysis of text divisions), and required at Levels 4 and 5 (for full analysis of the text structure).

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, with the value of the <tt>n</tt> attribute denoting the number of the page whose text ''follows'' this element. The <tt>pb</tt> element should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are three recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facsimile]</tt> element to define a set of images that corresponds to the text in conjunction with the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== key and ref ====

These attributes are available on the same elements and are used to reference external metadata about the content of the element. The <tt>key</tt> element may contain any string of Unicode characters, whereas the <tt>ref</tt> attribute must contain a URI (including a relative one, as discussed above). While <tt>key</tt> may supply any identifier, there is no mechanism internal to XML for checking that the value of this attribute is valid.

For example,

<code>
<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>
</code>

gives a project-interal key (<tt>lccn-n78-95332</tt>) for this name in the Library of Congress Name Authority File. Values of <tt>key</tt> attributes may be partially explained in a non-machine-readable way through use of a <tt>taxonomy</tt> element:

<code>
<taxonomy xml:id="lccn"><bibl>Library of Congress Control Number</bibl></taxonomy>
</code>

Alternatively, use <tt>ref</tt> with a URI fragment identifier, corresponding to the value of <tt>xml:id</tt> given elsewhere. For example, in the transcription of the text, use

<code>
<placeName ref="#tgn_7012924">Indianapolis</placeName>
</code>

which would be defined in a controlled vocabulary elsewhere:

<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
</listPlace>
</pre>

When validation software encounters <tt>ref="#tgn_7012924"</tt>, it will check that <tt>xml:id="tgn_7012924"</tt> exists elsewhere in the document.

==== rend and rendition ====

The <tt>rend</tt> and <tt>rendition</tt> attributes may be used when it is desirable to record information about how the content object was displayed in the source document.

Never use these attributes on header elements: metadata is transcribed and possibly regularized, as in a catalog record, but its exact appearance is not meant to be captured.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use these attributes; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, one of these attributes should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

For the value of the <tt>rend</tt> attribute, use only valid CSS properties and values. For example:

* <tt><foreign rend="font-style: italic"></tt>
* <tt><title rend="text-decoration: underline; font-size: x-large"></tt>

Alternatively, use the <tt>rendition</tt> '''attribute''' to give an internal scheme:

<tt><foreign rendition="#i"></tt>

documented with the <tt>rendition</tt> '''element''' in the header:

<tt><rendition xml:id="i" scheme="css">font-style: italic</rendition></tt>

Use of the <tt>rendition</tt> attribute and element offers an additional level of indirection, decreasing the total number of keystrokes and possibly reducing the chance of typos being introduced in the encoding.

==== xml:lang ====

Used to indicate the natural language of the content of an element. It is generally not used for children of the <tt>text</tt> element at Level 1 or Level 2 but is common at Level 3 and above. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the data.language datatype in the TEI Guidelines].

==Structure of a TEI Document==

<table border="1">
<tr>
<th colspan="2">Element</th>
<th>Description</th>
</tr>
<tr>
<td colspan="2"><tt><TEI></tt></td>
<td>The root element of a TEI document</td>
</tr>
<tr>
<td>├</td>
<td><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> is required; it indicates the language used for the metadata describing the document.</td>
</tr>
<tr>
<td>├</td>
<td><tt><facsimile></tt></td>
<td>The <tt>facsimile</tt> defines sets of images that correspond with the text. Unlike the <tt>teiHeader</tt> and the <tt>text</tt>, it is an optional element in the TEI document.</td>
</tr>

<tr>
<td>└</td>
<td>The <tt><text xml:lang="___"></tt></td>
<td>The <tt>text</tt> element contains the encoded transcription of the source document. The <tt>xml:lang</tt> attribute is recommended; it indicates the primary language of the source document.</td>
</tr>
</table>

The child elements of the <tt>teiHeader</tt> and <tt>text</tt> elements are described below.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. TEI Lite calls the header "the electronic title page", though it actually more closely resembles a catalog record with additional data not routinely stored in MARC records.

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

In order to allow automatic generation of TEI headers from MARC records and MARC records from TEI headers, some elements (like <tt><author></tt>) contain content not typical for TEI practice but necessary due to a lack of granularity in the MARC format.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element. In the absence of such mechanisms, users of these best practices may use the <tt>idno</tt> element to supply identifiers for outside metadata records and may supply identifiers for certain authority records using the <tt>key</tt> or <tt>ref</tt> attributes, allowed on certain elements.

While elements from non-TEI namespaces may be included in a TEI document, these best practices currently do not attempt to prescribe which and where non-TEI elements may or must be used in the header.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> attribute is required; it indicates the language used for the metadata describing the document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>├</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains bibliographic metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:

* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document—usually, the author(s) of the source document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>X, Malcolm</author></tt>
* <tt><author>Thomas (Anglo-Normal poet)</author></tt>
* <tt><author>Catherine II, Empress of Russia</author></tt>
* <tt><author>Joannes, Actuarius, 13th/14th cent.</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>
If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that acted as editors of the TEI document—usually, the editor(s) of the source document. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

Unlike in the TEI Guidelines, do not use this element for translators, illustrators, compilers, or other roles not generally considered an editor. Therefore, do not use the <tt>role</tt> attribute.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td><p>Record the names of other persons or organizations, one responsibility or party per <tt><respStmt></tt>, that have responsibility for the intellectual or artistic content of the TEI document—often by transitivity from the source document—not covered by <tt><author></tt> and <tt><editor></tt>. This includes translators, illustrators, compilers, proofreaders, encoders, and those who wrote a preface or introduction. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt>title</tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>type</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD. (This element is used instead of <tt><bibl></tt> to enforce structure, but <tt>>biblFull<</tt> is not used because it requires more elements than are typically available in library metadata sources.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the intellectual or artistic content of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. Use a <tt>type</tt> attribute with a value of <tt>marc245c</tt> to give the statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>marc245c</tt> (used for the statement of responsibility according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
<p>Statement of responsibility on the source document, according to the national cataloging code. Record
one responsibility or party per <tt><respStmt></tt>. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p>

<p>If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to split the content of the 245c field into <tt>resp</tt> and <tt>name</tt> elements, so it is recommended to use <tt><title type="marc245c"></tt> instead of this element.</p>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a colon) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "S.l." (for no place of publication).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a comma) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "s.n." (for no publisher).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Optionally, use for notes about the source document, according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
Optionally use one or more <tt>idno</tt> elements to give identification numbers for the source document, text, or work, whether assigned by the holding library (such as a call number), the publisher of the original document (such as an ISBN), or a standard bibliography (such as an identifier from the <cite>Short Title Catalogue</cite> or <cite>Books in Maori</cite>). Use the following values for the <tt>type</tt> attribute if applicable, and create other values if appropriate:

* <tt>LC_call_number</tt>
* <tt>isbn-13</tt>
* <tt>isbn-10</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>
Use the <tt>n</tt> attribute to record the encoding level: <tt>1</tt> for Level 1, <tt>2</tt> for Level 2, etc.

Include one or more <tt>p</tt> elements as children with information on:

* editorial decisions made during encoding
* notes about omissions of material found in the original work
* the format of the data in the header: Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?
* automated processes used to generate the markup or content
* external files or databases (such as those containing authority data) referenced in the TEI document

Also include one of the following <tt>p</tt> elements as appropriate:

<tt><p>All hyphens in source document encoded as U+2010.</p></tt>

<tt><p>Soft hyphens encoded as U+00AD; hard hyphens as U+2010.</p></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><tt><rendition xml:id="_" scheme="css"</tt></td>
<td>Include one or more <tt>rendition</tt> elements for each unique value of a <tt>rendition</tt> attribute (not <tt>rend</tt> attribute) used in the body of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>└</p></td>
<td colspan="3"><tt><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td><p>├</p></td>
<td colspan="5"><tt><langUsage></tt></td>
<td>Optionally use this element and child <tt>language</tt> elements to list languages used in the text. This supplements <tt><text xml:lang="___"></tt> in cases where more than one language is used in the text. It is not expected that the <tt>langUsage</tt> element will contain any description of language usage.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="4"><tt><language ident="___"></tt></td>
<td>Use one or more <tt>language</tt> elements to indicate language(s) used in the source document. The <tt>ident</tt> attribute is usually sufficient to indicate the language, so this element should normally have no content. In the unusual case where <tt>ident</tt> is insufficient, provide additional information on the language as content of the element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers may be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change should be recorded using the <tt>when</tt> attribute ((see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]).

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. For example, the document might simply give <tt>who="#Jane_Smith"</tt>, relying on human readers to understand this reference.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="marc245a">Lincoln and Seward.</title>
<title level="m" type="marc245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="marc245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
<p>All hyphens in source document encoded as U+2010.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<langUsage>
<language ident="en"/>
</langUsage>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images). Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added at a later date</li>
</ul>

====Workflow====

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is left uncorrected ("dirty OCR"). Page images are tagged using software that assigns a page-level metadata (page number and possibly tags for page features) to each page image for display in the user interface in a list of pages. Encoding is performed automatically: markup with page-level metadata is inserted at selected points into the dirty OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====Purpose====
To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

====Rationale====
The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Level 2 requires a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are <i>not</i> intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

'''Level 2 is most suitable for projects in which''':

* a large volume of material is to be made available online quickly
* a digital image of each page is desired
* the material is of interest to a large community of users who wish to read texts that allow keyword searching
* rudimentary search and display capabilities based on the large structures of the text are desired
* each text is checked to ensure that divisions and headers are properly identified
* extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

====Workflow====

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’s heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">Unlike in Level 1, in Level 2 one <tt><div1></tt> or <tt><div></tt> is used per section of the text identified with division-level metadata. If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb n="1" facs="[URI of page 1 image]"/>
<head>[heading of section 1]</head>
<ab>[entire contents of section 1 here, with
interspersed <pb> elements pointing to page
images; in this example there are 26 more pages
to section 1]</ab>
</div>
<div type="section">
<pb n="27" facs="[URI of page 27 image]"/>
<div type="subsection">
<head>[heading of section 2 subsection 1]</head>
<ab>[all the paragraphs of subsection one go here
with page breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>

<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING
SHOULD BE ORDERED.</head>
<ab>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Encoding at this level offers provides the foundation for upgrading to higher levels of encoding. Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date</li>
</ul>

====Workflow====

Level 3 texts can be created by conversion from an electronic source such as an HTML file or word-processor document or from a print source, either through OCR or keyboarding. They can be generated trivially by converting from outsourced double-keyboarded texts conforming to TEI Tite, though some granularity of encoding will be lost in the translation.

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2 '''except <tt>ab</tt>''', plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Table of Contents=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT Chapter 4.5, Front Matter]

You may wish not to include front matter content such as table of contents or lists of illustrations, especially if you plan to automatically generate the contents or lists of illustrations. If you do, however, plan to manually encode the table of contents (or lists of illustrations and similar content), use a <tt>div</tt> element with an appropriate <tt>type</tt> attribute (e.g., <tt><div type="contents"></tt>). Within this division, use the <tt>list</tt> element to mark up the table of contents, list of illustrations, etc. Each list item should have a <tt>ptr</tt> or <tt>ref</tt> element with a <tt>target</tt> attribute referencing an <tt>xml:id</tt> attribute on the <tt><pb></tt> or "div" element of the referenced page or section. Use <tt>ref</tt> if you wish to transcribe page numbers in the table of contents; use <tt>ptr</tt> if you do not.

=====Notes=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog
<ref target="#VAA2383_011" rend="text-align: right">3</ref>
</item>
<item>II. Romance
<ref target="#VAA2383_020" rend="text-align: right">12</ref>
</item>
<item>III. The Costume
<ref target="#VAA2383_029" rend="text-align: right">21</ref>
</item>
<item>IV. Desperation
<ref target="#VAA2383_038" rend="text-align: right">30</ref>
</item>
<item>V. The Pageant of the Table Round
<ref target="#VAA2383_046" rend="text-align: right">38</ref>
</item>
</list>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="font-weight: bold">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"<hi rend="font-variant: small-caps">Penrod Schofield</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>
<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern&amp#xAD;
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open&amp#xAD;
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter&amp#xAD;
mination regarding these issues.</p>

<p>FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

<pb n="114" facs="00000002.tif"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>

<p>In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947.

<note place="bottom" anchored="true" n="68">Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re&amp#xAD;
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu&amp#xAD;
ments. CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<pb n="115" facs="00000003.tif"/>
occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per&amp#xAD;
sonal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note reques&amp#xAD;
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

although no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

====Purpose====
<p>To create text that can stand alone as electronic text, identifies
hierarchy and typography, specifies function of textual and structural elements, and describes the
nature of the content and not merely its appearance. This level is not meant to encode or identify all
structural, semantic, or bibliographic features of the text.</p>

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

<p>Finally, functionally accurate encoding in Level 4 texts
allows them to be searched or displayed in sophisticated ways.
For example, a searcher could limit his or her search in a
dramatic text to stage directions or in a verse text to only
first lines. In a political tract published by subscription, a
search could be confined to names that appear in lists, thus
limiting a search to names of people who subscribed to a
particular volume. This ability to limit searches becomes more
significant as textbases become larger, and thus is of great
importance to the library community as it attempts to build into
the initial design and implementation of textbases the features
needed to enhance interoperability.</p>

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

<li>the texts will be used for textual analysis</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added by the scholarly community at a later date</li>
<li>the users of the texts may have limited storage or display capabilities</li>
</ul>

====Workflow====

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup must be added, as discussed in [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg Appendix A of TEI Tite].

====Element Recommendations for Level 4====

<p>Use all elements specified in Levels 1, 2, and 3 '''except <tt>ab</tt>''', plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="font-weight: bold"></tt>). This element may also be used if the more specific elements above are not used.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSnr Chapter 13.1.1, Linking Names and Their Referents]

Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. See the [[#key_and_ref|discussion of <tt>ref</tt> and <tt>key</tt>]] above for how to choose between them.

If using <tt>key</tt>, provide a unique internal identifier, such as in a local database.

If using <tt>ref</tt>, an external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. In such a case the value of the <tt>ref</tt> attribute in the main TEI document (the transcription of the source document) references the value of the <tt>xml:id</tt> attribute in the external file. (In the examples below, the external file is named <tt>context.xml</tt> for “contextual information” and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* Alternatively, instead of using an external file for the authority data, use the <tt>key</tt> attribute to point to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:

<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="font-style: italic">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—&amp; B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
Source: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====

* Within the front matter (<tt><front></tt>) of a performance text, cast lists should be encoded as <tt><castList></tt>s, with each item in that list encoded as <tt><castItem></tt>s. If desired, each <tt><castItem></tt> may be uniquely identified with the <tt>xml:id</tt> attribute.

For example,

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

In either method, use an <tt>xml:id</tt> on the <tt>name</tt> element to uniquely identify the individual participant:

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

<sp who="spk2">
<speaker n="2">WILLIAM LINK:</speaker>
<p>Last time we were talking about Frank Porter Graham. And I have a couple of questions
about Graham, and I wonder if you could clear them up for me. You have mentioned that you
had worked with him as a student at North Carolina State, had you met him before?
</p>
</sp>
<sp who="spk1">
<speaker n="1">WILLIAM C. FRIDAY: </speaker>
<p>No. That budget hearing was the first that I knew of him, of course, but the first time
that I ever encountered him. I was president of class at N.C. State, and that through me into
this kind of public adventure. And so I went merrily on downtown and sat there in the budget
hearing, along with the president of the student body, and some others.
</p>
</sp>
</pre>

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

Use <tt><lg></tt> and <tt><l></tt> as in Level 3. In addition, use the <tt>rend</tt> attribute to indicate lines that are indented.

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="margin-left: 0.5in" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="margin-left: 0.5in" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="margin-left: 0.5in" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="margin-left: 0.5in" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

===== Level 4 Alger Hiss document =====

Note that the soft hyphen character is displayed as an entity reference because it this character will not display in many web browsers.

<pre><TEI xml:id="project_document_identifier"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="./pageImages/AH4_0113.jpg" ed="typed"/>
<pb n="118" ed="subsequent"/>
<head>POINT VIII.</head>
<head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
<lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
<lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
<lb/>family and associates was not known at the time of trial by
<lb/>the defense. Even now, with the release of some of the govern&#xAD;
<lb/>ment documents concerning FBI investigative techniques regarding
<lb/>Hiss, the full extent of surveillance -- wiretapping, mail open&#xAD;
<lb/>ings, mail covers, physical surveillance, and other intrusive
<lb/>techniques -- is still not 'clear. Nevertheless, it is apparent
<lb/>that information gathered through the exploitation of unlawful
<lb/>wiretaps and other illegal surveillance was used at trial and
<lb/>consequently the conviction must be reversed. Alternatively,
<lb/>further discovery and a hearing is essential to a fair deter&#xAD;
<lb/>mination regarding these issues.</p>
<p>FBI surveillance of Hiss began in earnest in 1941 with
<lb/>the institution of a mail cover on his incoming correspondence
<lb/>at his home in connection with an FBI investigation of possible
<lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed
<pb n="114" facs="./pageImages/AH_0114.jpg"/>
<pb n="119" ed="subsequent"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
<lb/>toll call records from the Hiss residence Telephone for the
<lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
<lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>
<p>In late November, 1945, FBI surveillance of the Hiss
<lb/>residence in Washington, D.C., escalated. For the third time,
<lb/>a mail cover was instituted beginning on November 28, 1945,
<lb/>which was continued at least until 1946. CN Ex. 101 at p. 70;
<lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun
<lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
<lb/>surveillance was discontinued on December 14, 1945, physical
<lb/>surveillance was conducted frequently at various times until
<lb/>September, 1947.<note place="foot" anchored="true" n="68">Also
before 1947, a letter from Priscilla Hiss addressed
<lb/>to her son, Timothy Hobson, was intercepted and its contents
<lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947,
<lb/>a letter from a Michael Greenberg addressed to petitioner re&#xAD;
<lb/>garding an application for employment with the United Nations
<lb/>was also intercepted, in a manner not revealed by the docu&#xAD;
<lb/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p>
<p>The most intrusive invasion of petitioner's rights
<pb n="115" facs="./pageImages/AH_0115.jpg"/>
<pb n="120" ed="subsequent"/>
<lb/>occurred from December 13, 1945 until the Hisses moved from
<lb/>Washington, D.C. to New York City on September 13, 1947. A
<soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss
<lb/>telephone at their residence on P Street-in Washington, D.C.
<lb/>The logs of this surveillance constitute twenty-nine volumes
<lb/>of FBI serials and are roughly 2,500 pages in length, in which
<lb/>an enormous amount of information concerning the Hisses' per&#xAD;
<lb/>sonal lives, relationships with friends and associates, and
<lb/>habits is recorded.</p>
<p>The wiretap was installed following FBI Director Hoover's
<lb/>application to the Attorney General for authorization,<note place="bottom" anchored="true" n="69">Hoover's
initial request was answered by a note reques&#xAD;
<lb/>ting information on Hiss. CN Ex. 104<sic> </sic>. Additional information
<lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic> </sic>.</note>
<lb/>although no written authorization appears in the documents released to
<lb/>Hiss. The purpose of the application was to gather information
<lb/>regarding Hiss' alleged contacts with Soviet espionage agents and
<lb/>communists in government service, general allegations which had
<lb/>been made by Elizabeth Bentley and Chambers.</p>
<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI></pre>

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require substantial human intervention by encoders with subject knowledge. These texts might include encodings of semantic, linguistic, prosodic, or other features well beyond the basic structural elements discussed in Levels 1-4 above. They might also include elements for editorial, critical, or analytical additions; manuscript descriptions; translations; or other textual apparatus. It is impossible to make concrete recommendations for encoding at this level since the scholarly analysis required is usually specific to each project; instead, Level 5 offers the full set of P5 elements as needed.

====Reference====
* [http://www.tei-c.org/Guidelines/P5 Complete P5 Guidelines]

====Purpose====
To create deeply analytical encoded texts that might be appropriate for specific research purposes, as part of a scholarly publishing project, or for any other encoding practices in library-based text encoding.

====Rationale====
A significant number of library-based projects engage in high-level analytical text encoding as part of their efforts in digitization, scholarly editing, academic support, or other research. Level 5 is intended to represent that work, which can take advantage of the full richness of the complete TEI Guidelines, while still acknowledging the impact of library-specific practices on encoded text that is created under the auspices of a library.

The specific influences of library practice on a Level-5 encoded text are expressed primarily in adherence to the [[#General_Recommendations|General Recommendations]] and [[#The_TEI_Header|TEI Header]] sections above.

====Element Recommendations and Examples====
Because of the vast range of possibilities for Level-5 encoding, we have chosen to provide neither a list of recommended elements nor any specific examples for this Level.

Please refer to the [[#The_TEI_Header|TEI Header]] section above for examples of <tt><TeiHeader></tt> element usage, and to the [[#General_Recommendations|General Recommendations]] section and the [http://www.tei-c.org/Guidelines/P5 Complete TEI P5 Guidelines] for element recommendations and usage examples within the <tt><text></tt> element.

==Acknowledgments==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Renee McBride, University of North Carolina, Chapel Hill
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to copyediting of this document are:
* Susan Lorand, University of Michigan
* Becky Welzenbach, University of Michigan

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==

This document was formerly known as "TEI Text Encoding in Libraries Guidelines for Best Encoding Practices".

<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (often referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

= Appendix B: Formal Specification =

(This section will be generated automatically once ODDs are created.)

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-06-18T17:51:13Z

RebeccaWelzenbach: /* Text divisions */

----
* [[SIG:Libraries|TEI in Libraries: Home]]
----

==Introduction==

These best practices are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, these best practices are meant to be as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing. The encoding levels are not strictly cumulative: while higher levels tend to build upon lower levels by including more elements, higher levels are not supersets because some elements used at lower levels are not used at all at higher levels.

In brief, the encoding levels are:

{| border="1"
|-
| Level 1
| The text is generated through OCR, is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).
|-
| Level 2
| The text is generated through OCR and is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured.
|-
| Level 3
| The text is created by conversion from an electronic source such as HTML or word-processor documents or from a print source, either by way of OCR or keyboarding.
|-
| Level 4
| The text is generated either through corrected OCR or keyboarding and is able to stand alone without page images in order for them to be read by students, scholars, and general readers.
|-
| Level 5
| The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge.
|}

These best practices are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention. Level 3 does not contain as many elements as TEI Tite in order to allow for mass digitization of born-digital source documents or for upgrading of Level 1 or Level 2 texts with only minimal human intervention. For more information, see [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg TEI Tite's Appendix A].

These best practices specify a recommended archival storage format. Local system needs may require transformation of documents in this archival format to another XML format for use by a local indexing or delivery software.

In these guidelines, use of elements and attributes tends toward explicitness for ease of processing even though a human or possibly machine reader might be able to make inferences based on context.

==General Recommendations==

=== Standards and local practice ===

The goal of the TEI is interchange, not interoperability. While seamless interoperability of texts created by different organizations is an unobtainable goal, use of a common markup vocabulary and syntax greatly aids interchange. Nevertheless, keep in mind that others—even within your organization—may use your texts in the future for other uses than you intended in your encoding.

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Hyphenation ===

Encoding end-of-line, end-of-column, and end-of-page hyphenation varies considerably in the TEI community. Some capture all hyphens found on the printed page, while others remove those in the middle of words not normally hyphenated for easier implementation of full-text retrieval. If preserving hyphens, some will capture all hyphens using the same character, while others will distinguish hyphens that must be present in any case (often called "hard hyphens") and those that are only present by virtue of being at the end of a line, column, or page (often called "soft hyphens").

This issue is complicated by the fact that Unicode presribes use of a soft hyphen not for a ''visible hyphen that might have been absent'' but instead for a place where a hyphen ''might occur''. Furthermore, it includes a "non-breaking hyphen", used in cases like "re-creation" (meaning "to create again", as opposed to recreation, meaning "relaxation"), in addition to a regular hyphen, which would normally count as a word boundary. In short, Unicode is oriented toward electronic text that may be processed with a computer in various ways, not toward capturing source documents.

Since OCR software relies on dictionaries to determine the probability not simply of characters but of whole words, it is often able to handle hyphenation in different ways.

At Levels 1 and 2, no attempt should be made to remove hyphens from the source document or disambiguate hard and soft hyphens. Encode all hyphens appearing in the source document using character U+2010.

At Level 3, either encode hyphens as in Levels 1 and 2 or disambiguate soft and hard hyphens. In the latter case, soft hyphens should be encoded using U+00AD and hard hyphens using U+2010.

At Levels 4 or 5, hyphens must be disambiguated using U+00AD for soft hyphens and U+2010 for hard hyphens.

In any case, the hyphenation practice must be recorded in the <tt>editorialDecl</tt>.

Do not confuse hyphen characters with the minus character (U+2212).

=== Filenames ===

A filename scheme that is internally consistent should be established for the project.

If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. Likewise, if you will access files using a version of Apple Filing Protocol (AFP) before 3.0, filenames longer than 31 bytes are likely to be corrupted, so you may wish to limit filenames to 31 single-byte (e.g., ASCII) characters.

Otherwise, consider the following best practices when determining the file name scheme for your project:

* Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
* Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
* Filenames should not include spaces
* Filenames should follow predictable case constructions (e.g., all lowercase, camelCase, etc.)
* The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and XML-based metadata languages
* The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

The choice of numbered or unnumbered divisions must be documented with the <tt>tagUsage</tt> element in the header. See 4.6, Element Recommendations for the TEI Header, below.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at Level 1 (because only one encoded division in the text), is optional at Level 2 (because the division-level metadata need not classify these divisions), is recommended at Level 3 (for broad yet useful analysis of text divisions), and required at Levels 4 and 5 (for full analysis of the text structure).

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, with the value of the <tt>n</tt> attribute denoting the number of the page whose text ''follows'' this element. The <tt>pb</tt> element should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are three recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facsimile]</tt> element to define a set of images that corresponds to the text in conjunction with the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== key and ref ====

These attributes are available on the same elements and are used to reference external metadata about the content of the element. The <tt>key</tt> element may contain any string of Unicode characters, whereas the <tt>ref</tt> attribute must contain a URI (including a relative one, as discussed above). While <tt>key</tt> may supply any identifier, there is no mechanism internal to XML for checking that the value of this attribute is valid.

For example,

<code>
<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>
</code>

gives a project-interal key (<tt>lccn-n78-95332</tt>) for this name in the Library of Congress Name Authority File. Values of <tt>key</tt> attributes may be partially explained in a non-machine-readable way through use of a <tt>taxonomy</tt> element:

<code>
<taxonomy xml:id="lccn"><bibl>Library of Congress Control Number</bibl></taxonomy>
</code>

Alternatively, use <tt>ref</tt> with a URI fragment identifier, corresponding to the value of <tt>xml:id</tt> given elsewhere. For example, in the transcription of the text, use

<code>
<placeName ref="#tgn_7012924">Indianapolis</placeName>
</code>

which would be defined in a controlled vocabulary elsewhere:

<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
</listPlace>
</pre>

When validation software encounters <tt>ref="#tgn_7012924"</tt>, it will check that <tt>xml:id="tgn_7012924"</tt> exists elsewhere in the document.

==== rend and rendition ====

The <tt>rend</tt> and <tt>rendition</tt> attributes may be used when it is desirable to record information about how the content object was displayed in the source document.

Never use these attributes on header elements: metadata is transcribed and possibly regularized, as in a catalog record, but its exact appearance is not meant to be captured.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use these attributes; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, one of these attributes should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

For the value of the <tt>rend</tt> attribute, use only valid CSS properties and values. For example:

* <tt><foreign rend="font-style: italic"></tt>
* <tt><title rend="text-decoration: underline; font-size: x-large"></tt>

Alternatively, use the <tt>rendition</tt> '''attribute''' to give an internal scheme:

<tt><foreign rendition="#i"></tt>

documented with the <tt>rendition</tt> '''element''' in the header:

<tt><rendition xml:id="i" scheme="css">font-style: italic</rendition></tt>

Use of the <tt>rendition</tt> attribute and element offers an additional level of indirection, decreasing the total number of keystrokes and possibly reducing the chance of typos being introduced in the encoding.

==== xml:lang ====

Used to indicate the natural language of the content of an element. It is generally not used for children of the <tt>text</tt> element at Level 1 or Level 2 but is common at Level 3 and above. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the data.language datatype in the TEI Guidelines].

==Structure of a TEI Document==

<table border="1">
<tr>
<th colspan="2">Element</th>
<th>Description</th>
</tr>
<tr>
<td colspan="2"><tt><TEI></tt></td>
<td>The root element of a TEI document</td>
</tr>
<tr>
<td>├</td>
<td><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> is required; it indicates the language used for the metadata describing the document.</td>
</tr>
<tr>
<td>├</td>
<td><tt><facsimile></tt></td>
<td>The <tt>facsimile</tt> defines sets of images that correspond with the text. Unlike the <tt>teiHeader</tt> and the <tt>text</tt>, it is an optional element in the TEI document.</td>
</tr>

<tr>
<td>└</td>
<td>The <tt><text xml:lang="___"></tt></td>
<td>The <tt>text</tt> element contains the encoded transcription of the source document. The <tt>xml:lang</tt> attribute is recommended; it indicates the primary language of the source document.</td>
</tr>
</table>

The child elements of the <tt>teiHeader</tt> and <tt>text</tt> elements are described below.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. TEI Lite calls the header "the electronic title page", though it actually more closely resembles a catalog record with additional data not routinely stored in MARC records.

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

In order to allow automatic generation of TEI headers from MARC records and MARC records from TEI headers, some elements (like <tt><author></tt>) contain content not typical for TEI practice but necessary due to a lack of granularity in the MARC format.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element. In the absence of such mechanisms, users of these best practices may use the <tt>idno</tt> element to supply identifiers for outside metadata records and may supply identifiers for certain authority records using the <tt>key</tt> or <tt>ref</tt> attributes, allowed on certain elements.

While elements from non-TEI namespaces may be included in a TEI document, these best practices currently do not attempt to prescribe which and where non-TEI elements may or must be used in the header.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> attribute is required; it indicates the language used for the metadata describing the document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>├</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains bibliographic metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:

* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document—usually, the author(s) of the source document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>X, Malcolm</author></tt>
* <tt><author>Thomas (Anglo-Normal poet)</author></tt>
* <tt><author>Catherine II, Empress of Russia</author></tt>
* <tt><author>Joannes, Actuarius, 13th/14th cent.</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>
If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that acted as editors of the TEI document—usually, the editor(s) of the source document. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

Unlike in the TEI Guidelines, do not use this element for translators, illustrators, compilers, or other roles not generally considered an editor. Therefore, do not use the <tt>role</tt> attribute.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td><p>Record the names of other persons or organizations, one responsibility or party per <tt><respStmt></tt>, that have responsibility for the intellectual or artistic content of the TEI document—often by transitivity from the source document—not covered by <tt><author></tt> and <tt><editor></tt>. This includes translators, illustrators, compilers, proofreaders, encoders, and those who wrote a preface or introduction. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt>title</tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>type</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD. (This element is used instead of <tt><bibl></tt> to enforce structure, but <tt>>biblFull<</tt> is not used because it requires more elements than are typically available in library metadata sources.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the intellectual or artistic content of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. Use a <tt>type</tt> attribute with a value of <tt>marc245c</tt> to give the statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>marc245c</tt> (used for the statement of responsibility according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
<p>Statement of responsibility on the source document, according to the national cataloging code. Record
one responsibility or party per <tt><respStmt></tt>. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p>

<p>If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to split the content of the 245c field into <tt>resp</tt> and <tt>name</tt> elements, so it is recommended to use <tt><title type="marc245c"></tt> instead of this element.</p>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a colon) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "S.l." (for no place of publication).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a comma) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "s.n." (for no publisher).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Optionally, use for notes about the source document, according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
Optionally use one or more <tt>idno</tt> elements to give identification numbers for the source document, text, or work, whether assigned by the holding library (such as a call number), the publisher of the original document (such as an ISBN), or a standard bibliography (such as an identifier from the <cite>Short Title Catalogue</cite> or <cite>Books in Maori</cite>). Use the following values for the <tt>type</tt> attribute if applicable, and create other values if appropriate:

* <tt>LC_call_number</tt>
* <tt>isbn-13</tt>
* <tt>isbn-10</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>
Use the <tt>n</tt> attribute to record the encoding level: <tt>1</tt> for Level 1, <tt>2</tt> for Level 2, etc.

Include one or more <tt>p</tt> elements as children with information on:

* editorial decisions made during encoding
* notes about omissions of material found in the original work
* the format of the data in the header: Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?
* automated processes used to generate the markup or content
* external files or databases (such as those containing authority data) referenced in the TEI document

Also include one of the following <tt>p</tt> elements as appropriate:

<tt><p>All hyphens in source document encoded as U+2010.</p></tt>

<tt><p>Soft hyphens encoded as U+00AD; hard hyphens as U+2010.</p></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><tt><rendition xml:id="_" scheme="css"</tt></td>
<td>Include one or more <tt>rendition</tt> elements for each unique value of a <tt>rendition</tt> attribute (not <tt>rend</tt> attribute) used in the body of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>└</p></td>
<td colspan="3"><tt><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td><p>├</p></td>
<td colspan="5"><tt><langUsage></tt></td>
<td>Optionally use this element and child <tt>language</tt> elements to list languages used in the text. This supplements <tt><text xml:lang="___"></tt> in cases where more than one language is used in the text. It is not expected that the <tt>langUsage</tt> element will contain any description of language usage.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="4"><tt><language ident="___"></tt></td>
<td>Use one or more <tt>language</tt> elements to indicate language(s) used in the source document. The <tt>ident</tt> attribute is usually sufficient to indicate the language, so this element should normally have no content. In the unusual case where <tt>ident</tt> is insufficient, provide additional information on the language as content of the element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers may be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change should be recorded using the <tt>when</tt> attribute ((see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]).

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. For example, the document might simply give <tt>who="#Jane_Smith"</tt>, relying on human readers to understand this reference.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="marc245a">Lincoln and Seward.</title>
<title level="m" type="marc245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="marc245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
<p>All hyphens in source document encoded as U+2010.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<langUsage>
<language ident="en"/>
</langUsage>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images). Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added at a later date</li>
</ul>

====Workflow====

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is left uncorrected ("dirty OCR"). Page images are tagged using software that assigns a page-level metadata (page number and possibly tags for page features) to each page image for display in the user interface in a list of pages. Encoding is performed automatically: markup with page-level metadata is inserted at selected points into the dirty OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====Purpose====
To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

====Rationale====
The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Level 2 requires a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are <i>not</i> intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

'''Level 2 is most suitable for projects in which''':

* a large volume of material is to be made available online quickly
* a digital image of each page is desired
* the material is of interest to a large community of users who wish to read texts that allow keyword searching
* rudimentary search and display capabilities based on the large structures of the text are desired
* each text is checked to ensure that divisions and headers are properly identified
* extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

====Workflow====

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’s heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">Unlike in Level 1, in Level 2 one <tt><div1></tt> or <tt><div></tt> is used per section of the text identified with division-level metadata. If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb n="1" facs="[URI of page 1 image]"/>
<head>[heading of section 1]</head>
<ab>[entire contents of section 1 here, with
interspersed <pb> elements pointing to page
images; in this example there are 26 more pages
to section 1]</ab>
</div>
<div type="section">
<pb n="27" facs="[URI of page 27 image]"/>
<div type="subsection">
<head>[heading of section 2 subsection 1]</head>
<ab>[all the paragraphs of subsection one go here
with page breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>

<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING
SHOULD BE ORDERED.</head>
<ab>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Encoding at this level offers provides the foundation for upgrading to higher levels of encoding. Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date</li>
</ul>

====Workflow====

Level 3 texts can be created by conversion from an electronic source such as an HTML file or word-processor document or from a print source, either through OCR or keyboarding. They can be generated trivially by converting from outsourced double-keyboarded texts conforming to TEI Tite, though some granularity of encoding will be lost in the translation.

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2 '''except <tt>ab</tt>''', plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Table of Contents=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT Chapter 4.5, Front Matter]

You may wish not to include front matter content such as table of contents or lists of illustrations, especially if you plan to automatically generate the contents or lists of illustrations. If you do, however, plan to manually encode the table of contents (or lists of illustrations and similar content), use a <tt>div</tt> element with an appropriate <tt>type</tt> attribute (e.g., <tt><div type="contents"></tt>). Within this division, use the <tt>list</tt> element to mark up the table of contents, list of illustrations, etc. Each list item should have a <tt>ptr</tt> or <tt>ref</tt> element with a <tt>target</tt> attribute referencing an <tt>xml:id</tt> attribute on the <tt><pb></tt> or "div" element of the referenced page or section. Use <tt>ref</tt> if you wish to transcribe page numbers in the table of contents; use <tt>ptr</tt> if you do not.

=====Notes=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog
<ref target="#VAA2383_011" rend="text-align: right">3</ref>
</item>
<item>II. Romance
<ref target="#VAA2383_020" rend="text-align: right">12</ref>
</item>
<item>III. The Costume
<ref target="#VAA2383_029" rend="text-align: right">21</ref>
</item>
<item>IV. Desperation
<ref target="#VAA2383_038" rend="text-align: right">30</ref>
</item>
<item>V. The Pageant of the Table Round
<ref target="#VAA2383_046" rend="text-align: right">38</ref>
</item>
</list>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="font-weight: bold">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"<hi rend="font-variant: small-caps">Penrod Schofield</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>
<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern&amp#xAD;
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open&amp#xAD;
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter&amp#xAD;
mination regarding these issues.</p>

<p>FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

<pb n="114" facs="00000002.tif"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>

<p>In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947.

<note place="bottom" anchored="true" n="68">Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re&amp#xAD;
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu&amp#xAD;
ments. CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<pb n="115" facs="00000003.tif"/>
occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per&amp#xAD;
sonal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note reques&amp#xAD;
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

although no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

====Purpose====
<p>To create text that can stand alone as electronic text, identifies
hierarchy and typography, specifies function of textual and structural elements, and describes the
nature of the content and not merely its appearance. This level is not meant to encode or identify all
structural, semantic, or bibliographic features of the text.</p>

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

<p>Finally, functionally accurate encoding in Level 4 texts
allows them to be searched or displayed in sophisticated ways.
For example, a searcher could limit his or her search in a
dramatic text to stage directions or in a verse text to only
first lines. In a political tract published by subscription, a
search could be confined to names that appear in lists, thus
limiting a search to names of people who subscribed to a
particular volume. This ability to limit searches becomes more
significant as textbases become larger, and thus is of great
importance to the library community as it attempts to build into
the initial design and implementation of textbases the features
needed to enhance interoperability.</p>

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

<li>the texts will be used for textual analysis</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added by the scholarly community at a later date</li>
<li>the users of the texts may have limited storage or display capabilities</li>
</ul>

====Workflow====

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup must be added, as discussed in [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg Appendix A of TEI Tite].

====Element Recommendations for Level 4====

<p>Use all elements specified in Levels 1, 2, and 3 '''except <tt>ab</tt>''', plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="font-weight: bold"></tt>). This element may also be used if the more specific elements above are not used.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSnr Chapter 13.1.1, Linking Names and Their Referents]

Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. See the [[#key_and_ref|discussion of <tt>ref</tt> and <tt>key</tt>]] above for how to choose between them.

If using <tt>key</tt>, provide a unique internal identifier, such as in a local database.

If using <tt>ref</tt>, an external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. In such a case the value of the <tt>ref</tt> attribute in the main TEI document (the transcription of the source document) references the value of the <tt>xml:id</tt> attribute in the external file. (In the examples below, the external file is named <tt>context.xml</tt> for “contextual information” and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* Alternatively, instead of using an external file for the authority data, use the <tt>key</tt> attribute to point to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:

<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="font-style: italic">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—&amp; B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
Source: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====

* Within the front matter (<tt><front></tt>) of a performance text, cast lists should be encoded as <tt><castList></tt>s, with each item in that list encoded as <tt><castItem></tt>s. If desired, each <tt><castItem></tt> may be uniquely identified with the <tt>xml:id</tt> attribute.

For example,

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

In either method, use an <tt>xml:id</tt> on the <tt>name</tt> element to uniquely identify the individual participant:

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

<sp who="spk2">
<speaker n="2">WILLIAM LINK:</speaker>
<p>Last time we were talking about Frank Porter Graham. And I have a couple of questions
about Graham, and I wonder if you could clear them up for me. You have mentioned that you
had worked with him as a student at North Carolina State, had you met him before?
</p>
</sp>
<sp who="spk1">
<speaker n="1">WILLIAM C. FRIDAY: </speaker>
<p>No. That budget hearing was the first that I knew of him, of course, but the first time
that I ever encountered him. I was president of class at N.C. State, and that through me into
this kind of public adventure. And so I went merrily on downtown and sat there in the budget
hearing, along with the president of the student body, and some others.
</p>
</sp>
</pre>

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

Use <tt><lg></tt> and <tt><l></tt> as in Level 3. In addition, use the <tt>rend</tt> attribute to indicate lines that are indented.

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="margin-left: 0.5in" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="margin-left: 0.5in" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="margin-left: 0.5in" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="margin-left: 0.5in" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

===== Level 4 Alger Hiss document =====

Note that the soft hyphen character is displayed as an entity reference because it this character will not display in many web browsers.

<pre><TEI xml:id="project_document_identifier"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="./pageImages/AH4_0113.jpg" ed="typed"/>
<pb n="118" ed="subsequent"/>
<head>POINT VIII.</head>
<head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
<lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
<lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
<lb/>family and associates was not known at the time of trial by
<lb/>the defense. Even now, with the release of some of the govern&#xAD;
<lb/>ment documents concerning FBI investigative techniques regarding
<lb/>Hiss, the full extent of surveillance -- wiretapping, mail open&#xAD;
<lb/>ings, mail covers, physical surveillance, and other intrusive
<lb/>techniques -- is still not 'clear. Nevertheless, it is apparent
<lb/>that information gathered through the exploitation of unlawful
<lb/>wiretaps and other illegal surveillance was used at trial and
<lb/>consequently the conviction must be reversed. Alternatively,
<lb/>further discovery and a hearing is essential to a fair deter&#xAD;
<lb/>mination regarding these issues.</p>
<p>FBI surveillance of Hiss began in earnest in 1941 with
<lb/>the institution of a mail cover on his incoming correspondence
<lb/>at his home in connection with an FBI investigation of possible
<lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed
<pb n="114" facs="./pageImages/AH_0114.jpg"/>
<pb n="119" ed="subsequent"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
<lb/>toll call records from the Hiss residence Telephone for the
<lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
<lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>
<p>In late November, 1945, FBI surveillance of the Hiss
<lb/>residence in Washington, D.C., escalated. For the third time,
<lb/>a mail cover was instituted beginning on November 28, 1945,
<lb/>which was continued at least until 1946. CN Ex. 101 at p. 70;
<lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun
<lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
<lb/>surveillance was discontinued on December 14, 1945, physical
<lb/>surveillance was conducted frequently at various times until
<lb/>September, 1947.<note place="foot" anchored="true" n="68">Also
before 1947, a letter from Priscilla Hiss addressed
<lb/>to her son, Timothy Hobson, was intercepted and its contents
<lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947,
<lb/>a letter from a Michael Greenberg addressed to petitioner re&#xAD;
<lb/>garding an application for employment with the United Nations
<lb/>was also intercepted, in a manner not revealed by the docu&#xAD;
<lb/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p>
<p>The most intrusive invasion of petitioner's rights
<pb n="115" facs="./pageImages/AH_0115.jpg"/>
<pb n="120" ed="subsequent"/>
<lb/>occurred from December 13, 1945 until the Hisses moved from
<lb/>Washington, D.C. to New York City on September 13, 1947. A
<soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss
<lb/>telephone at their residence on P Street-in Washington, D.C.
<lb/>The logs of this surveillance constitute twenty-nine volumes
<lb/>of FBI serials and are roughly 2,500 pages in length, in which
<lb/>an enormous amount of information concerning the Hisses' per&#xAD;
<lb/>sonal lives, relationships with friends and associates, and
<lb/>habits is recorded.</p>
<p>The wiretap was installed following FBI Director Hoover's
<lb/>application to the Attorney General for authorization,<note place="bottom" anchored="true" n="69">Hoover's
initial request was answered by a note reques&#xAD;
<lb/>ting information on Hiss. CN Ex. 104<sic> </sic>. Additional information
<lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic> </sic>.</note>
<lb/>although no written authorization appears in the documents released to
<lb/>Hiss. The purpose of the application was to gather information
<lb/>regarding Hiss' alleged contacts with Soviet espionage agents and
<lb/>communists in government service, general allegations which had
<lb/>been made by Elizabeth Bentley and Chambers.</p>
<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI></pre>

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require substantial human intervention by encoders with subject knowledge. These texts might include encodings of semantic, linguistic, prosodic, or other features well beyond the basic structural elements discussed in Levels 1-4 above. They might also include elements for editorial, critical, or analytical additions; manuscript descriptions; translations; or other textual apparatus. It is impossible to make concrete recommendations for encoding at this level since the scholarly analysis required is usually specific to each project; instead, Level 5 offers the full set of P5 elements as needed.

====Reference====
* [http://www.tei-c.org/Guidelines/P5 Complete P5 Guidelines]

====Purpose====
To create deeply analytical encoded texts that might be appropriate for specific research purposes, as part of a scholarly publishing project, or for any other encoding practices in library-based text encoding.

====Rationale====
A significant number of library-based projects engage in high-level analytical text encoding as part of their efforts in digitization, scholarly editing, academic support, or other research. Level 5 is intended to represent that work, which can take advantage of the full richness of the complete TEI Guidelines, while still acknowledging the impact of library-specific practices on encoded text that is created under the auspices of a library.

The specific influences of library practice on a Level-5 encoded text are expressed primarily in adherence to the [[#General_Recommendations|General Recommendations]] and [[#The_TEI_Header|TEI Header]] sections above.

====Element Recommendations and Examples====
Because of the vast range of possibilities for Level-5 encoding, we have chosen to provide neither a list of recommended elements nor any specific examples for this Level.

Please refer to the [[#The_TEI_Header|TEI Header]] section above for examples of <tt><TeiHeader></tt> element usage, and to the [[#General_Recommendations|General Recommendations]] section and the [http://www.tei-c.org/Guidelines/P5 Complete TEI P5 Guidelines] for element recommendations and usage examples within the <tt><text></tt> element.

==Acknowledgments==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Renee McBride, University of North Carolina, Chapel Hill
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to copyediting of this document are:
* Susan Lorand, University of Michigan
* Becky Welzenbach, University of Michigan

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==

This document was formerly known as "TEI Text Encoding in Libraries Guidelines for Best Encoding Practices".

<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (often referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

= Appendix B: Formal Specification =

(This section will be generated automatically once ODDs are created.)

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-06-18T17:47:27Z

RebeccaWelzenbach: /* Filenames */

----
* [[SIG:Libraries|TEI in Libraries: Home]]
----

==Introduction==

These best practices are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, these best practices are meant to be as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing. The encoding levels are not strictly cumulative: while higher levels tend to build upon lower levels by including more elements, higher levels are not supersets because some elements used at lower levels are not used at all at higher levels.

In brief, the encoding levels are:

{| border="1"
|-
| Level 1
| The text is generated through OCR, is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).
|-
| Level 2
| The text is generated through OCR and is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured.
|-
| Level 3
| The text is created by conversion from an electronic source such as HTML or word-processor documents or from a print source, either by way of OCR or keyboarding.
|-
| Level 4
| The text is generated either through corrected OCR or keyboarding and is able to stand alone without page images in order for them to be read by students, scholars, and general readers.
|-
| Level 5
| The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge.
|}

These best practices are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention. Level 3 does not contain as many elements as TEI Tite in order to allow for mass digitization of born-digital source documents or for upgrading of Level 1 or Level 2 texts with only minimal human intervention. For more information, see [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg TEI Tite's Appendix A].

These best practices specify a recommended archival storage format. Local system needs may require transformation of documents in this archival format to another XML format for use by a local indexing or delivery software.

In these guidelines, use of elements and attributes tends toward explicitness for ease of processing even though a human or possibly machine reader might be able to make inferences based on context.

==General Recommendations==

=== Standards and local practice ===

The goal of the TEI is interchange, not interoperability. While seamless interoperability of texts created by different organizations is an unobtainable goal, use of a common markup vocabulary and syntax greatly aids interchange. Nevertheless, keep in mind that others—even within your organization—may use your texts in the future for other uses than you intended in your encoding.

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Hyphenation ===

Encoding end-of-line, end-of-column, and end-of-page hyphenation varies considerably in the TEI community. Some capture all hyphens found on the printed page, while others remove those in the middle of words not normally hyphenated for easier implementation of full-text retrieval. If preserving hyphens, some will capture all hyphens using the same character, while others will distinguish hyphens that must be present in any case (often called "hard hyphens") and those that are only present by virtue of being at the end of a line, column, or page (often called "soft hyphens").

This issue is complicated by the fact that Unicode presribes use of a soft hyphen not for a ''visible hyphen that might have been absent'' but instead for a place where a hyphen ''might occur''. Furthermore, it includes a "non-breaking hyphen", used in cases like "re-creation" (meaning "to create again", as opposed to recreation, meaning "relaxation"), in addition to a regular hyphen, which would normally count as a word boundary. In short, Unicode is oriented toward electronic text that may be processed with a computer in various ways, not toward capturing source documents.

Since OCR software relies on dictionaries to determine the probability not simply of characters but of whole words, it is often able to handle hyphenation in different ways.

At Levels 1 and 2, no attempt should be made to remove hyphens from the source document or disambiguate hard and soft hyphens. Encode all hyphens appearing in the source document using character U+2010.

At Level 3, either encode hyphens as in Levels 1 and 2 or disambiguate soft and hard hyphens. In the latter case, soft hyphens should be encoded using U+00AD and hard hyphens using U+2010.

At Levels 4 or 5, hyphens must be disambiguated using U+00AD for soft hyphens and U+2010 for hard hyphens.

In any case, the hyphenation practice must be recorded in the <tt>editorialDecl</tt>.

Do not confuse hyphen characters with the minus character (U+2212).

=== Filenames ===

A filename scheme that is internally consistent should be established for the project.

If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. Likewise, if you will access files using a version of Apple Filing Protocol (AFP) before 3.0, filenames longer than 31 bytes are likely to be corrupted, so you may wish to limit filenames to 31 single-byte (e.g., ASCII) characters.

Otherwise, consider the following best practices when determining the file name scheme for your project:

* Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
* Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
* Filenames should not include spaces
* Filenames should follow predictable case constructions (e.g., all lowercase, camelCase, etc.)
* The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and XML-based metadata languages
* The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

The choice of numbered or unnumbered divisions must be documented with the <tt>tagUsage</tt> element in the header. See the Element Recommendations for the TEI Header below.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at Level 1 (because only one encoded division in the text), is optional at Level 2 (because the division-level metadata need not classify these divisions), is recommended at Level 3 (for broad yet useful analysis of text divisions), and required at Levels 4 and 5 (for full analysis of the text structure).

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, with the value of the <tt>n</tt> attribute denoting the number of the page whose text ''follows'' this element. The <tt>pb</tt> element should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are three recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facsimile]</tt> element to define a set of images that corresponds to the text in conjunction with the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== key and ref ====

These attributes are available on the same elements and are used to reference external metadata about the content of the element. The <tt>key</tt> element may contain any string of Unicode characters, whereas the <tt>ref</tt> attribute must contain a URI (including a relative one, as discussed above). While <tt>key</tt> may supply any identifier, there is no mechanism internal to XML for checking that the value of this attribute is valid.

For example,

<code>
<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>
</code>

gives a project-interal key (<tt>lccn-n78-95332</tt>) for this name in the Library of Congress Name Authority File. Values of <tt>key</tt> attributes may be partially explained in a non-machine-readable way through use of a <tt>taxonomy</tt> element:

<code>
<taxonomy xml:id="lccn"><bibl>Library of Congress Control Number</bibl></taxonomy>
</code>

Alternatively, use <tt>ref</tt> with a URI fragment identifier, corresponding to the value of <tt>xml:id</tt> given elsewhere. For example, in the transcription of the text, use

<code>
<placeName ref="#tgn_7012924">Indianapolis</placeName>
</code>

which would be defined in a controlled vocabulary elsewhere:

<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
</listPlace>
</pre>

When validation software encounters <tt>ref="#tgn_7012924"</tt>, it will check that <tt>xml:id="tgn_7012924"</tt> exists elsewhere in the document.

==== rend and rendition ====

The <tt>rend</tt> and <tt>rendition</tt> attributes may be used when it is desirable to record information about how the content object was displayed in the source document.

Never use these attributes on header elements: metadata is transcribed and possibly regularized, as in a catalog record, but its exact appearance is not meant to be captured.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use these attributes; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, one of these attributes should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

For the value of the <tt>rend</tt> attribute, use only valid CSS properties and values. For example:

* <tt><foreign rend="font-style: italic"></tt>
* <tt><title rend="text-decoration: underline; font-size: x-large"></tt>

Alternatively, use the <tt>rendition</tt> '''attribute''' to give an internal scheme:

<tt><foreign rendition="#i"></tt>

documented with the <tt>rendition</tt> '''element''' in the header:

<tt><rendition xml:id="i" scheme="css">font-style: italic</rendition></tt>

Use of the <tt>rendition</tt> attribute and element offers an additional level of indirection, decreasing the total number of keystrokes and possibly reducing the chance of typos being introduced in the encoding.

==== xml:lang ====

Used to indicate the natural language of the content of an element. It is generally not used for children of the <tt>text</tt> element at Level 1 or Level 2 but is common at Level 3 and above. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the data.language datatype in the TEI Guidelines].

==Structure of a TEI Document==

<table border="1">
<tr>
<th colspan="2">Element</th>
<th>Description</th>
</tr>
<tr>
<td colspan="2"><tt><TEI></tt></td>
<td>The root element of a TEI document</td>
</tr>
<tr>
<td>├</td>
<td><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> is required; it indicates the language used for the metadata describing the document.</td>
</tr>
<tr>
<td>├</td>
<td><tt><facsimile></tt></td>
<td>The <tt>facsimile</tt> defines sets of images that correspond with the text. Unlike the <tt>teiHeader</tt> and the <tt>text</tt>, it is an optional element in the TEI document.</td>
</tr>

<tr>
<td>└</td>
<td>The <tt><text xml:lang="___"></tt></td>
<td>The <tt>text</tt> element contains the encoded transcription of the source document. The <tt>xml:lang</tt> attribute is recommended; it indicates the primary language of the source document.</td>
</tr>
</table>

The child elements of the <tt>teiHeader</tt> and <tt>text</tt> elements are described below.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. TEI Lite calls the header "the electronic title page", though it actually more closely resembles a catalog record with additional data not routinely stored in MARC records.

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

In order to allow automatic generation of TEI headers from MARC records and MARC records from TEI headers, some elements (like <tt><author></tt>) contain content not typical for TEI practice but necessary due to a lack of granularity in the MARC format.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element. In the absence of such mechanisms, users of these best practices may use the <tt>idno</tt> element to supply identifiers for outside metadata records and may supply identifiers for certain authority records using the <tt>key</tt> or <tt>ref</tt> attributes, allowed on certain elements.

While elements from non-TEI namespaces may be included in a TEI document, these best practices currently do not attempt to prescribe which and where non-TEI elements may or must be used in the header.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> attribute is required; it indicates the language used for the metadata describing the document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>├</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains bibliographic metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:

* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document—usually, the author(s) of the source document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>X, Malcolm</author></tt>
* <tt><author>Thomas (Anglo-Normal poet)</author></tt>
* <tt><author>Catherine II, Empress of Russia</author></tt>
* <tt><author>Joannes, Actuarius, 13th/14th cent.</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>
If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that acted as editors of the TEI document—usually, the editor(s) of the source document. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

Unlike in the TEI Guidelines, do not use this element for translators, illustrators, compilers, or other roles not generally considered an editor. Therefore, do not use the <tt>role</tt> attribute.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td><p>Record the names of other persons or organizations, one responsibility or party per <tt><respStmt></tt>, that have responsibility for the intellectual or artistic content of the TEI document—often by transitivity from the source document—not covered by <tt><author></tt> and <tt><editor></tt>. This includes translators, illustrators, compilers, proofreaders, encoders, and those who wrote a preface or introduction. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt>title</tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>type</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD. (This element is used instead of <tt><bibl></tt> to enforce structure, but <tt>>biblFull<</tt> is not used because it requires more elements than are typically available in library metadata sources.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the intellectual or artistic content of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. Use a <tt>type</tt> attribute with a value of <tt>marc245c</tt> to give the statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>marc245c</tt> (used for the statement of responsibility according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
<p>Statement of responsibility on the source document, according to the national cataloging code. Record
one responsibility or party per <tt><respStmt></tt>. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p>

<p>If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to split the content of the 245c field into <tt>resp</tt> and <tt>name</tt> elements, so it is recommended to use <tt><title type="marc245c"></tt> instead of this element.</p>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a colon) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "S.l." (for no place of publication).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a comma) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "s.n." (for no publisher).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Optionally, use for notes about the source document, according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
Optionally use one or more <tt>idno</tt> elements to give identification numbers for the source document, text, or work, whether assigned by the holding library (such as a call number), the publisher of the original document (such as an ISBN), or a standard bibliography (such as an identifier from the <cite>Short Title Catalogue</cite> or <cite>Books in Maori</cite>). Use the following values for the <tt>type</tt> attribute if applicable, and create other values if appropriate:

* <tt>LC_call_number</tt>
* <tt>isbn-13</tt>
* <tt>isbn-10</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>
Use the <tt>n</tt> attribute to record the encoding level: <tt>1</tt> for Level 1, <tt>2</tt> for Level 2, etc.

Include one or more <tt>p</tt> elements as children with information on:

* editorial decisions made during encoding
* notes about omissions of material found in the original work
* the format of the data in the header: Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?
* automated processes used to generate the markup or content
* external files or databases (such as those containing authority data) referenced in the TEI document

Also include one of the following <tt>p</tt> elements as appropriate:

<tt><p>All hyphens in source document encoded as U+2010.</p></tt>

<tt><p>Soft hyphens encoded as U+00AD; hard hyphens as U+2010.</p></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><tt><rendition xml:id="_" scheme="css"</tt></td>
<td>Include one or more <tt>rendition</tt> elements for each unique value of a <tt>rendition</tt> attribute (not <tt>rend</tt> attribute) used in the body of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>└</p></td>
<td colspan="3"><tt><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td><p>├</p></td>
<td colspan="5"><tt><langUsage></tt></td>
<td>Optionally use this element and child <tt>language</tt> elements to list languages used in the text. This supplements <tt><text xml:lang="___"></tt> in cases where more than one language is used in the text. It is not expected that the <tt>langUsage</tt> element will contain any description of language usage.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="4"><tt><language ident="___"></tt></td>
<td>Use one or more <tt>language</tt> elements to indicate language(s) used in the source document. The <tt>ident</tt> attribute is usually sufficient to indicate the language, so this element should normally have no content. In the unusual case where <tt>ident</tt> is insufficient, provide additional information on the language as content of the element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers may be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change should be recorded using the <tt>when</tt> attribute ((see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]).

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. For example, the document might simply give <tt>who="#Jane_Smith"</tt>, relying on human readers to understand this reference.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="marc245a">Lincoln and Seward.</title>
<title level="m" type="marc245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="marc245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
<p>All hyphens in source document encoded as U+2010.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<langUsage>
<language ident="en"/>
</langUsage>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images). Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added at a later date</li>
</ul>

====Workflow====

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is left uncorrected ("dirty OCR"). Page images are tagged using software that assigns a page-level metadata (page number and possibly tags for page features) to each page image for display in the user interface in a list of pages. Encoding is performed automatically: markup with page-level metadata is inserted at selected points into the dirty OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====Purpose====
To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

====Rationale====
The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Level 2 requires a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are <i>not</i> intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

'''Level 2 is most suitable for projects in which''':

* a large volume of material is to be made available online quickly
* a digital image of each page is desired
* the material is of interest to a large community of users who wish to read texts that allow keyword searching
* rudimentary search and display capabilities based on the large structures of the text are desired
* each text is checked to ensure that divisions and headers are properly identified
* extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

====Workflow====

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’s heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">Unlike in Level 1, in Level 2 one <tt><div1></tt> or <tt><div></tt> is used per section of the text identified with division-level metadata. If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb n="1" facs="[URI of page 1 image]"/>
<head>[heading of section 1]</head>
<ab>[entire contents of section 1 here, with
interspersed <pb> elements pointing to page
images; in this example there are 26 more pages
to section 1]</ab>
</div>
<div type="section">
<pb n="27" facs="[URI of page 27 image]"/>
<div type="subsection">
<head>[heading of section 2 subsection 1]</head>
<ab>[all the paragraphs of subsection one go here
with page breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>

<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING
SHOULD BE ORDERED.</head>
<ab>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Encoding at this level offers provides the foundation for upgrading to higher levels of encoding. Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date</li>
</ul>

====Workflow====

Level 3 texts can be created by conversion from an electronic source such as an HTML file or word-processor document or from a print source, either through OCR or keyboarding. They can be generated trivially by converting from outsourced double-keyboarded texts conforming to TEI Tite, though some granularity of encoding will be lost in the translation.

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2 '''except <tt>ab</tt>''', plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Table of Contents=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT Chapter 4.5, Front Matter]

You may wish not to include front matter content such as table of contents or lists of illustrations, especially if you plan to automatically generate the contents or lists of illustrations. If you do, however, plan to manually encode the table of contents (or lists of illustrations and similar content), use a <tt>div</tt> element with an appropriate <tt>type</tt> attribute (e.g., <tt><div type="contents"></tt>). Within this division, use the <tt>list</tt> element to mark up the table of contents, list of illustrations, etc. Each list item should have a <tt>ptr</tt> or <tt>ref</tt> element with a <tt>target</tt> attribute referencing an <tt>xml:id</tt> attribute on the <tt><pb></tt> or "div" element of the referenced page or section. Use <tt>ref</tt> if you wish to transcribe page numbers in the table of contents; use <tt>ptr</tt> if you do not.

=====Notes=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog
<ref target="#VAA2383_011" rend="text-align: right">3</ref>
</item>
<item>II. Romance
<ref target="#VAA2383_020" rend="text-align: right">12</ref>
</item>
<item>III. The Costume
<ref target="#VAA2383_029" rend="text-align: right">21</ref>
</item>
<item>IV. Desperation
<ref target="#VAA2383_038" rend="text-align: right">30</ref>
</item>
<item>V. The Pageant of the Table Round
<ref target="#VAA2383_046" rend="text-align: right">38</ref>
</item>
</list>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="font-weight: bold">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"<hi rend="font-variant: small-caps">Penrod Schofield</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>
<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern&amp#xAD;
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open&amp#xAD;
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter&amp#xAD;
mination regarding these issues.</p>

<p>FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

<pb n="114" facs="00000002.tif"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>

<p>In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947.

<note place="bottom" anchored="true" n="68">Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re&amp#xAD;
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu&amp#xAD;
ments. CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<pb n="115" facs="00000003.tif"/>
occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per&amp#xAD;
sonal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note reques&amp#xAD;
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

although no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

====Purpose====
<p>To create text that can stand alone as electronic text, identifies
hierarchy and typography, specifies function of textual and structural elements, and describes the
nature of the content and not merely its appearance. This level is not meant to encode or identify all
structural, semantic, or bibliographic features of the text.</p>

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

<p>Finally, functionally accurate encoding in Level 4 texts
allows them to be searched or displayed in sophisticated ways.
For example, a searcher could limit his or her search in a
dramatic text to stage directions or in a verse text to only
first lines. In a political tract published by subscription, a
search could be confined to names that appear in lists, thus
limiting a search to names of people who subscribed to a
particular volume. This ability to limit searches becomes more
significant as textbases become larger, and thus is of great
importance to the library community as it attempts to build into
the initial design and implementation of textbases the features
needed to enhance interoperability.</p>

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

<li>the texts will be used for textual analysis</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added by the scholarly community at a later date</li>
<li>the users of the texts may have limited storage or display capabilities</li>
</ul>

====Workflow====

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup must be added, as discussed in [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg Appendix A of TEI Tite].

====Element Recommendations for Level 4====

<p>Use all elements specified in Levels 1, 2, and 3 '''except <tt>ab</tt>''', plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="font-weight: bold"></tt>). This element may also be used if the more specific elements above are not used.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSnr Chapter 13.1.1, Linking Names and Their Referents]

Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. See the [[#key_and_ref|discussion of <tt>ref</tt> and <tt>key</tt>]] above for how to choose between them.

If using <tt>key</tt>, provide a unique internal identifier, such as in a local database.

If using <tt>ref</tt>, an external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. In such a case the value of the <tt>ref</tt> attribute in the main TEI document (the transcription of the source document) references the value of the <tt>xml:id</tt> attribute in the external file. (In the examples below, the external file is named <tt>context.xml</tt> for “contextual information” and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* Alternatively, instead of using an external file for the authority data, use the <tt>key</tt> attribute to point to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:

<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="font-style: italic">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—&amp; B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
Source: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====

* Within the front matter (<tt><front></tt>) of a performance text, cast lists should be encoded as <tt><castList></tt>s, with each item in that list encoded as <tt><castItem></tt>s. If desired, each <tt><castItem></tt> may be uniquely identified with the <tt>xml:id</tt> attribute.

For example,

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

In either method, use an <tt>xml:id</tt> on the <tt>name</tt> element to uniquely identify the individual participant:

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

<sp who="spk2">
<speaker n="2">WILLIAM LINK:</speaker>
<p>Last time we were talking about Frank Porter Graham. And I have a couple of questions
about Graham, and I wonder if you could clear them up for me. You have mentioned that you
had worked with him as a student at North Carolina State, had you met him before?
</p>
</sp>
<sp who="spk1">
<speaker n="1">WILLIAM C. FRIDAY: </speaker>
<p>No. That budget hearing was the first that I knew of him, of course, but the first time
that I ever encountered him. I was president of class at N.C. State, and that through me into
this kind of public adventure. And so I went merrily on downtown and sat there in the budget
hearing, along with the president of the student body, and some others.
</p>
</sp>
</pre>

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

Use <tt><lg></tt> and <tt><l></tt> as in Level 3. In addition, use the <tt>rend</tt> attribute to indicate lines that are indented.

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="margin-left: 0.5in" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="margin-left: 0.5in" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="margin-left: 0.5in" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="margin-left: 0.5in" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

===== Level 4 Alger Hiss document =====

Note that the soft hyphen character is displayed as an entity reference because it this character will not display in many web browsers.

<pre><TEI xml:id="project_document_identifier"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="./pageImages/AH4_0113.jpg" ed="typed"/>
<pb n="118" ed="subsequent"/>
<head>POINT VIII.</head>
<head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
<lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
<lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
<lb/>family and associates was not known at the time of trial by
<lb/>the defense. Even now, with the release of some of the govern&#xAD;
<lb/>ment documents concerning FBI investigative techniques regarding
<lb/>Hiss, the full extent of surveillance -- wiretapping, mail open&#xAD;
<lb/>ings, mail covers, physical surveillance, and other intrusive
<lb/>techniques -- is still not 'clear. Nevertheless, it is apparent
<lb/>that information gathered through the exploitation of unlawful
<lb/>wiretaps and other illegal surveillance was used at trial and
<lb/>consequently the conviction must be reversed. Alternatively,
<lb/>further discovery and a hearing is essential to a fair deter&#xAD;
<lb/>mination regarding these issues.</p>
<p>FBI surveillance of Hiss began in earnest in 1941 with
<lb/>the institution of a mail cover on his incoming correspondence
<lb/>at his home in connection with an FBI investigation of possible
<lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed
<pb n="114" facs="./pageImages/AH_0114.jpg"/>
<pb n="119" ed="subsequent"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
<lb/>toll call records from the Hiss residence Telephone for the
<lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
<lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>
<p>In late November, 1945, FBI surveillance of the Hiss
<lb/>residence in Washington, D.C., escalated. For the third time,
<lb/>a mail cover was instituted beginning on November 28, 1945,
<lb/>which was continued at least until 1946. CN Ex. 101 at p. 70;
<lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun
<lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
<lb/>surveillance was discontinued on December 14, 1945, physical
<lb/>surveillance was conducted frequently at various times until
<lb/>September, 1947.<note place="foot" anchored="true" n="68">Also
before 1947, a letter from Priscilla Hiss addressed
<lb/>to her son, Timothy Hobson, was intercepted and its contents
<lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947,
<lb/>a letter from a Michael Greenberg addressed to petitioner re&#xAD;
<lb/>garding an application for employment with the United Nations
<lb/>was also intercepted, in a manner not revealed by the docu&#xAD;
<lb/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p>
<p>The most intrusive invasion of petitioner's rights
<pb n="115" facs="./pageImages/AH_0115.jpg"/>
<pb n="120" ed="subsequent"/>
<lb/>occurred from December 13, 1945 until the Hisses moved from
<lb/>Washington, D.C. to New York City on September 13, 1947. A
<soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss
<lb/>telephone at their residence on P Street-in Washington, D.C.
<lb/>The logs of this surveillance constitute twenty-nine volumes
<lb/>of FBI serials and are roughly 2,500 pages in length, in which
<lb/>an enormous amount of information concerning the Hisses' per&#xAD;
<lb/>sonal lives, relationships with friends and associates, and
<lb/>habits is recorded.</p>
<p>The wiretap was installed following FBI Director Hoover's
<lb/>application to the Attorney General for authorization,<note place="bottom" anchored="true" n="69">Hoover's
initial request was answered by a note reques&#xAD;
<lb/>ting information on Hiss. CN Ex. 104<sic> </sic>. Additional information
<lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic> </sic>.</note>
<lb/>although no written authorization appears in the documents released to
<lb/>Hiss. The purpose of the application was to gather information
<lb/>regarding Hiss' alleged contacts with Soviet espionage agents and
<lb/>communists in government service, general allegations which had
<lb/>been made by Elizabeth Bentley and Chambers.</p>
<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI></pre>

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require substantial human intervention by encoders with subject knowledge. These texts might include encodings of semantic, linguistic, prosodic, or other features well beyond the basic structural elements discussed in Levels 1-4 above. They might also include elements for editorial, critical, or analytical additions; manuscript descriptions; translations; or other textual apparatus. It is impossible to make concrete recommendations for encoding at this level since the scholarly analysis required is usually specific to each project; instead, Level 5 offers the full set of P5 elements as needed.

====Reference====
* [http://www.tei-c.org/Guidelines/P5 Complete P5 Guidelines]

====Purpose====
To create deeply analytical encoded texts that might be appropriate for specific research purposes, as part of a scholarly publishing project, or for any other encoding practices in library-based text encoding.

====Rationale====
A significant number of library-based projects engage in high-level analytical text encoding as part of their efforts in digitization, scholarly editing, academic support, or other research. Level 5 is intended to represent that work, which can take advantage of the full richness of the complete TEI Guidelines, while still acknowledging the impact of library-specific practices on encoded text that is created under the auspices of a library.

The specific influences of library practice on a Level-5 encoded text are expressed primarily in adherence to the [[#General_Recommendations|General Recommendations]] and [[#The_TEI_Header|TEI Header]] sections above.

====Element Recommendations and Examples====
Because of the vast range of possibilities for Level-5 encoding, we have chosen to provide neither a list of recommended elements nor any specific examples for this Level.

Please refer to the [[#The_TEI_Header|TEI Header]] section above for examples of <tt><TeiHeader></tt> element usage, and to the [[#General_Recommendations|General Recommendations]] section and the [http://www.tei-c.org/Guidelines/P5 Complete TEI P5 Guidelines] for element recommendations and usage examples within the <tt><text></tt> element.

==Acknowledgments==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Renee McBride, University of North Carolina, Chapel Hill
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to copyediting of this document are:
* Susan Lorand, University of Michigan
* Becky Welzenbach, University of Michigan

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==

This document was formerly known as "TEI Text Encoding in Libraries Guidelines for Best Encoding Practices".

<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (often referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

= Appendix B: Formal Specification =

(This section will be generated automatically once ODDs are created.)

[[Category:SIG:Libraries]]

Best Practices for TEI in Libraries

2009-06-18T17:47:08Z

RebeccaWelzenbach: /* Filenames */

----
* [[SIG:Libraries|TEI in Libraries: Home]]
----

==Introduction==

These best practices are for libraries using the [http://www.tei-c.org/ Text Encoding Initiative]’s [http://www.tei-c.org/Guidelines/P5/ Guidelines for Text Encoding and Interchange (P5)]. They are intended for use in large, library-based digitization projects, but may be useful in other scenarios as well. Consult the full TEI Guidelines for guidance beyond what is described below.

There are many different library text digitization projects, for different purposes. With this in mind, these best practices are meant to be as inclusive as possible by specifying a series of encoding levels. These levels are meant to allow for a range of practice, from wholly automated text creation and encoding, to encoding that requires expert content knowledge, analysis, and editing. The encoding levels are not strictly cumulative: while higher levels tend to build upon lower levels by including more elements, higher levels are not supersets because some elements used at lower levels are not used at all at higher levels.

In brief, the encoding levels are:

{| border="1"
|-
| Level 1
| The text is generated through OCR, is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images).
|-
| Level 2
| The text is generated through OCR and is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured.
|-
| Level 3
| The text is created by conversion from an electronic source such as HTML or word-processor documents or from a print source, either by way of OCR or keyboarding.
|-
| Level 4
| The text is generated either through corrected OCR or keyboarding and is able to stand alone without page images in order for them to be read by students, scholars, and general readers.
|-
| Level 5
| The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge.
|}

These best practices are meant to complement the TEI Tite customization of the TEI Guidelines. Whereas TEI Tite is meant for vendors who need exact specifications for encoding without room for interpretation or local practice, these guidelines document how a library or other large-scale encoding project might create TEI documents that conform as closely as possible both to common TEI practice and to library standards. If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention. Level 3 does not contain as many elements as TEI Tite in order to allow for mass digitization of born-digital source documents or for upgrading of Level 1 or Level 2 texts with only minimal human intervention. For more information, see [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg TEI Tite's Appendix A].

These best practices specify a recommended archival storage format. Local system needs may require transformation of documents in this archival format to another XML format for use by a local indexing or delivery software.

In these guidelines, use of elements and attributes tends toward explicitness for ease of processing even though a human or possibly machine reader might be able to make inferences based on context.

==General Recommendations==

=== Standards and local practice ===

The goal of the TEI is interchange, not interoperability. While seamless interoperability of texts created by different organizations is an unobtainable goal, use of a common markup vocabulary and syntax greatly aids interchange. Nevertheless, keep in mind that others—even within your organization—may use your texts in the future for other uses than you intended in your encoding.

An encoding project should strive for internal consistency and for use of standards so that the data can be modified or enhanced in the future with ease. In cases where local practice deviates from standards, there should at least be internal consistency in the local practice.

=== Transcription ===

When reformatting to digital media using any level of encoding, the electronic text should begin with the transcription of the first word on the first leaf of the original work. It may be impractical or undesirable to transcribe and encode certain features of the text, such as publisher’s advertisements or indexes, but if at all possible, they should be included as links to page images. Any omissions of material found in the original work should be noted in the <tt><editorialDecl></tt> in the TEI header.

=== Hyphenation ===

Encoding end-of-line, end-of-column, and end-of-page hyphenation varies considerably in the TEI community. Some capture all hyphens found on the printed page, while others remove those in the middle of words not normally hyphenated for easier implementation of full-text retrieval. If preserving hyphens, some will capture all hyphens using the same character, while others will distinguish hyphens that must be present in any case (often called "hard hyphens") and those that are only present by virtue of being at the end of a line, column, or page (often called "soft hyphens").

This issue is complicated by the fact that Unicode presribes use of a soft hyphen not for a ''visible hyphen that might have been absent'' but instead for a place where a hyphen ''might occur''. Furthermore, it includes a "non-breaking hyphen", used in cases like "re-creation" (meaning "to create again", as opposed to recreation, meaning "relaxation"), in addition to a regular hyphen, which would normally count as a word boundary. In short, Unicode is oriented toward electronic text that may be processed with a computer in various ways, not toward capturing source documents.

Since OCR software relies on dictionaries to determine the probability not simply of characters but of whole words, it is often able to handle hyphenation in different ways.

At Levels 1 and 2, no attempt should be made to remove hyphens from the source document or disambiguate hard and soft hyphens. Encode all hyphens appearing in the source document using character U+2010.

At Level 3, either encode hyphens as in Levels 1 and 2 or disambiguate soft and hard hyphens. In the latter case, soft hyphens should be encoded using U+00AD and hard hyphens using U+2010.

At Levels 4 or 5, hyphens must be disambiguated using U+00AD for soft hyphens and U+2010 for hard hyphens.

In any case, the hyphenation practice must be recorded in the <tt>editorialDecl</tt>.

Do not confuse hyphen characters with the minus character (U+2212).

=== Filenames ===

A filename scheme that is internally consistent should be established for the project.

If it is likely that the files will need to be used on more primitive devices (MS-DOS computers or unextended ISO 9660 CDs) it may be useful to limit names to 8 characters (limited to the 26 lower case letters of ASCII, digits, hyphens, and underscore), a dot, and an extension of 3 alphanumeric characters. Likewise, if you will access files using a version of Apple Filing Protocol (AFP) before 3.0, filenames longer than 31 bytes are likely to be corrupted, so you may wish to limit filenames to 31 single-byte (e.g., ASCII) characters.

Otherwise, consider the following best practices when determining the file name scheme for your project:

* Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
* Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
* Filenames should not include spaces
* Filenames should follow a predictable case constructions (e.g., all lowercase, camelCase, etc.)
* The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and XML-based metadata languages
* The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).

=== URIs ===

A number of attributes take a [http://tools.ietf.org/html/rfc3986 URI] (Uniform Resource Identifier) as their value. Note that in addition to the full form of reference defined by URI syntax, these attributes can take a relative reference (e.g., <tt>filename.ext</tt>) or a fragment identifier (e.g., <tt>#foo</tt>).

=== Text divisions ===

An encoding project should use only numbered divisions (i.e., <tt><div1></tt>, <tt><div2></tt>, etc.) or unnumbered divisions (i.e., <tt><div></tt>) but not both. This applies both within a TEI document (i.e., within <tt><front></tt>, <tt><body></tt>, <tt><back></tt>, even if nested within <tt><group></tt> or <tt><floatingText></tt>) and across TEI documents in any given collection. Keep in mind that numbering of <tt><div></tt>s starts over (at <tt><div1></tt>) within <tt><floatingText></tt>, so any software that expects to process nested numbered divisions within a document will need to account for this.

The choice of numbered or unnumbered divisions must be documented with the <tt>tagUsage</tt> element in the header. See the Element Recommendations for the TEI Header below.

Whether numbered or unnumbered divisions are used, the <tt>type</tt> attribute of the division element is not recommended at Level 1 (because only one encoded division in the text), is optional at Level 2 (because the division-level metadata need not classify these divisions), is recommended at Level 3 (for broad yet useful analysis of text divisions), and required at Levels 4 and 5 (for full analysis of the text structure).

=== Page breaks ===

Page breaks should be encoded using the <tt>pb</tt> element, with the value of the <tt>n</tt> attribute denoting the number of the page whose text ''follows'' this element. The <tt>pb</tt> element should always be contained within a text division for ease of retrieval with indexing software. For example, a page break that occurs between chapters 2 and 3 should be encoded soon after the <tt><div></tt> that opens chapter 3 (rather than before the <tt></div></tt> that ends chapter 2).

=== Linking between encoded text and images of source documents ===

There are three recommended mechanisms for linking between the encoded text and facsimile page images of source documents. Projects may either:

<ol style="list-style-type: upper-alpha;">
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.</li>
<li>Use the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facsimile]</tt> element to define a set of images that corresponds to the text in conjunction with the <tt>[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX facs]</tt> attribute on each <tt>pb</tt> element to point to the corresponding page image using a URI.
<li>Use the <tt>xml:id</tt> attribute on each <tt>pb</tt> element and a METS document to provide correspondence between <tt>pb</tt> elements and one or more facsimile page images (e.g., master, web derivatives, etc.).</li>
</ol>

For those projects relying on the [http://www.loc.gov/standards/mets/ Metadata Encoding and Transmission Standard] (METS), the <tt>xml:id</tt> attribute is used as a conceptual identifier for content as opposed to an explicit pointer (i.e., <tt>facs</tt> attribute) to a specific representation of that content. These identifiers are then used to generate a METS document that bundles the various content types (e.g., master image files, derivative image files for Web delivery, PDFs, etc.), explicitly lists all versions of the content, and defines the relationships between the constituent parts. This is achieved through the use of the <tt><mets:fileSec></tt> and <tt><mets:structMap></tt> sections of the METS document (see [http://fedora.dlib.indiana.edu:8080/fedora/get/iudl:269584/METSNAV sample METS document] for a TEI project).

=== General Guidelines for Attribute Usage ===

Some general advice on the use of particular attributes follows. (All of these attributes are commonly used on various elements, but not every element requires or even allows these attributes.)

==== type ====

Constructing a list of acceptable attribute values for the <tt>type</tt> attribute for each element, on which everyone could agree, is impossible. Instead, it is recommended that projects describe the <tt>type</tt> attribute values used in their texts in the project [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#IM ODD] file and that this list be made available to people using the texts. It is worth noting that, at present, [http://www.tei-c.org/Roma/ Roma], the web front-end editor for ODD files, does not have a mechanism for providing this documentation — it should be added to the ODD file directly. For a list of standard names and definitions of bibliographic features of printed books, see <i>ABC for Book Collectors</i> by John Carter (8th edition, New Castle, Del. and London: Oak Knoll Books and the British Library, 2004, available online at http://www.ilab.org/images/abcforbookcollectors.pdf).

==== n ====

This element is sometimes used to number elements for machine processing, but it often includes data represented in the source document, such as page numbers or footnote numbers.
Example: <tt><pb n="456"/></tt>

==== xml:id ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA .

==== target ====

See the full TEI guidelines for how to use this attribute: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html#STGA.

==== key and ref ====

These attributes are available on the same elements and are used to reference external metadata about the content of the element. The <tt>key</tt> element may contain any string of Unicode characters, whereas the <tt>ref</tt> attribute must contain a URI (including a relative one, as discussed above). While <tt>key</tt> may supply any identifier, there is no mechanism internal to XML for checking that the value of this attribute is valid.

For example,

<code>
<author><persName type="marc100" key="lccn-n78-95332">Shakespeare, William, 1564-1616</persName></author>
</code>

gives a project-interal key (<tt>lccn-n78-95332</tt>) for this name in the Library of Congress Name Authority File. Values of <tt>key</tt> attributes may be partially explained in a non-machine-readable way through use of a <tt>taxonomy</tt> element:

<code>
<taxonomy xml:id="lccn"><bibl>Library of Congress Control Number</bibl></taxonomy>
</code>

Alternatively, use <tt>ref</tt> with a URI fragment identifier, corresponding to the value of <tt>xml:id</tt> given elsewhere. For example, in the transcription of the text, use

<code>
<placeName ref="#tgn_7012924">Indianapolis</placeName>
</code>

which would be defined in a controlled vocabulary elsewhere:

<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
</listPlace>
</pre>

When validation software encounters <tt>ref="#tgn_7012924"</tt>, it will check that <tt>xml:id="tgn_7012924"</tt> exists elsewhere in the document.

==== rend and rendition ====

The <tt>rend</tt> and <tt>rendition</tt> attributes may be used when it is desirable to record information about how the content object was displayed in the source document.

Never use these attributes on header elements: metadata is transcribed and possibly regularized, as in a catalog record, but its exact appearance is not meant to be captured.

If a project is normalizing the rendering of text objects (for example, such that all titles should be italicized, regardless of how they appeared in the source document), there is no need to use these attributes; instead, a stylesheet will determine that all titles are displayed in italics.

However, if a project is faithfully recording the rendering in the source document, one of these attributes should be used to indicate this rendering, either on all elements to be rendered differently from the surrounding text or on all elements whose rendering does not follow the default stylesheet.

For the value of the <tt>rend</tt> attribute, use only valid CSS properties and values. For example:

* <tt><foreign rend="font-style: italic"></tt>
* <tt><title rend="text-decoration: underline; font-size: x-large"></tt>

Alternatively, use the <tt>rendition</tt> '''attribute''' to give an internal scheme:

<tt><foreign rendition="#i"></tt>

documented with the <tt>rendition</tt> '''element''' in the header:

<tt><rendition xml:id="i" scheme="css">font-style: italic</rendition></tt>

Use of the <tt>rendition</tt> attribute and element offers an additional level of indirection, decreasing the total number of keystrokes and possibly reducing the chance of typos being introduced in the encoding.

==== xml:lang ====

Used to indicate the natural language of the content of an element. It is generally not used for children of the <tt>text</tt> element at Level 1 or Level 2 but is common at Level 3 and above. See [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-data.language.html the data.language datatype in the TEI Guidelines].

==Structure of a TEI Document==

<table border="1">
<tr>
<th colspan="2">Element</th>
<th>Description</th>
</tr>
<tr>
<td colspan="2"><tt><TEI></tt></td>
<td>The root element of a TEI document</td>
</tr>
<tr>
<td>├</td>
<td><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> is required; it indicates the language used for the metadata describing the document.</td>
</tr>
<tr>
<td>├</td>
<td><tt><facsimile></tt></td>
<td>The <tt>facsimile</tt> defines sets of images that correspond with the text. Unlike the <tt>teiHeader</tt> and the <tt>text</tt>, it is an optional element in the TEI document.</td>
</tr>

<tr>
<td>└</td>
<td>The <tt><text xml:lang="___"></tt></td>
<td>The <tt>text</tt> element contains the encoded transcription of the source document. The <tt>xml:lang</tt> attribute is recommended; it indicates the primary language of the source document.</td>
</tr>
</table>

The child elements of the <tt>teiHeader</tt> and <tt>text</tt> elements are described below.

==The TEI Header==

===Reference===
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html Chapter 2, TEI Header, P5 Guidelines]

===The TEI Header===

The TEI header is a metadata record that describes an electronic text encoded according to the TEI specification. The purpose of the TEI header is to declare the bibliographic information related to the electronic document and, if appropriate, the bibliographic data for the original analog source document from which the electronic edition was created. The TEI header often includes a description of the encoding decisions or practices used to create the electronic document. TEI Lite calls the header "the electronic title page", though it actually more closely resembles a catalog record with additional data not routinely stored in MARC records.

As with any descriptive metadata, the metadata in the TEI header can serve multiple audiences. In the local context, a TEI header provides metadata about the TEI document, its source, and its provenance. The TEI header may be used for metadata exchange, to automatically create indexes (author lists, title lists) for a collection of TEI documents, and to aid in browsing heterogeneous TEI documents. TEI headers may also be used as a basis for other metadata records (such as MARC or Dublin Core), though generation of other formats may require human intervention because they often are more granular, or have different granularity, than TEI headers.

===The TEI Header and MARC===

While a TEI header is often perceived as similar to or at least related to a MARC record, a TEI header does not typically have a one-to-one correspondence with a MARC record. One TEI header may be described by multiple MARC analytic records, or one MARC record may be used to describe a collection of TEI documents with individual headers. Furthermore, while a MARC record captures metadata about a bibliographic entity in a library’s collection, a TEI header records information both about an encoded text and about the source document for that encoded text.

Each institution and even each project may have a different approach to the way electronic texts are created in TEI and then represented in a larger public catalog through MARC. At one institution, the same unit (e.g., a cataloging department) may be responsible for creating both TEI Headers and MARC records, while at other institutions the work may be distributed among different units. Within the library domain, metadata or cataloging experts are usually required for at least review and standardization of both the TEI header and the MARC record.

In order to allow automatic generation of TEI headers from MARC records and MARC records from TEI headers, some elements (like <tt><author></tt>) contain content not typical for TEI practice but necessary due to a lack of granularity in the MARC format.

===The TEI Header and Other Metadata Schemas===

Several other descriptive metadata schemas are prevalent within the library domain, including Dublin Core (DC), Dublin Core Qualified (DCQ), and the Metadata Object Description Schema (MODS). Each of these schemas contains elements that capture the same data as many of the elements in the TEI header. As with MARC, a variety of automated or manual workflows can be implemented to crosswalk metadata from one standard to another and provide for increased sharing of metadata about electronic texts in larger contexts. In particular, DC and MODS are common schemas used by the Open Archives Initiative (OAI) and may be particularly valuable for sharing metadata across institutions.

Unfortunately, there is currently no mechanism for specifying that the content of an element should be drawn from an outside metadata source or that it should supplement the content of the element. In the absence of such mechanisms, users of these best practices may use the <tt>idno</tt> element to supply identifiers for outside metadata records and may supply identifiers for certain authority records using the <tt>key</tt> or <tt>ref</tt> attributes, allowed on certain elements.

While elements from non-TEI namespaces may be included in a TEI document, these best practices currently do not attempt to prescribe which and where non-TEI elements may or must be used in the header.

===Determining Data Values for the TEI Header===

Within the library domain, there are several authoritative publications on how to create bibliographic and descriptive metadata for objects. These are usually called “content standards”; two prominent examples are the <cite>Anglo-American Cataloging Rules Second Edition</cite> (AACR2) and the <cite>International Standard Bibliographic Description for Electronic Resources</cite> (ISBD(ER)). These standards are extensive and outline a set of rules that enforce consistency across a voluminous amount of metadata.

Perhaps the primary purpose of these content standards is to give rules for what sources of information may be used in transcribing or generating metadata about a bibliographic entity. Within an electronic context, the analog object may not be available, so the TEI header creator will need access to digitized images or other verifiable information to create accurate metadata.

The following sources of information are recommended in creating the TEI header:

<ol>
<li> For an electronic document with a digitized title page and title page verso:<ol style="list-style: lower-alpha;">
<li> Chief source of information is the information coded as title page.</li>
<li> Use added information from an originating paper document if absolutely certain it is the source.</li></ol></li>

<li>If there is no digitized title page but the header creator has satisfactory evidence of the source document, the header creator should refer to the source document for metadata creation. The lack of a title page may be for one of many reasons: for example, the original document is a manuscript item, or the electronic edition is a portion of the original object (a poem or short story that was published in a collection or an article from a serial). In all cases, it is recommended that important bibliographic evidence, such as a digitized image of the title page and title page verso for a collection, be provided to the header creator, even if just a piece of the collection is used.</li>

<li>If no title page is present and there is no evidence from a source document, the header creator may assign a title and author, if appropriate, enclosing the information in square brackets (using the standard English-language convention for editorial interjections).</li></ol>

===Element Recommendations for the TEI Header===

<table border="1">
<tr>
<th colspan="7">Element</th>
<th>Description</th>
<th>Equivalent in MARC when cataloging the TEI document</th>
<th>Equivalent in MARC for the source document</th>
</tr>

<tr>
<td colspan="7"><tt><teiHeader xml:lang="___"></tt></td>
<td>The <tt>teiHeader</tt> contains metadata about the TEI document. The <tt>xml:lang</tt> attribute is required; it indicates the language used for the metadata describing the document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>├</td>
<td colspan="6"><tt><fileDesc></tt></td>
<td>The <tt>fileDesc</tt> contains bibliographic metadata about the TEI document. One of its child elements, <tt>sourceDesc</tt>, describes the source document from which the TEI document was created.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><titleStmt></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><title></tt></td>
<td>
One or more <tt>title</tt> elements are used to give the title of the TEI document being created. It is suggested that titles be constructed based on the source document according to a national cataloging code.

Use of the <tt>level</tt> attribute is not recommended since it does not apply to a TEI document in a collection.

The <tt>type</tt> attribute may have any of the following values:

* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><author></tt></td>
<td>
One or more <tt>author</tt> elements (one name per element) are used to encode the names of entities primarily responsible for the content of the TEI document—usually, the author(s) of the source document. Use <tt>persName</tt> or <tt>orgName</tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file. Examples:

* <tt><author><persName>Shakespeare, William, 1564-1616</persName></author></tt>
* <tt><author><orgName>National Organization for Women</orgName></author></tt>
* <tt><author>X, Malcolm</author></tt>
* <tt><author>Thomas (Anglo-Normal poet)</author></tt>
* <tt><author>Catherine II, Empress of Russia</author></tt>
* <tt><author>Joannes, Actuarius, 13th/14th cent.</author></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><editor></tt></td>
<td>
If applicable, use one or more <tt>editor</tt> elements (one name per element) to encode the names of entities besides those in <tt>author</tt> elements that acted as editors of the TEI document—usually, the editor(s) of the source document. If considered appropriate by the encoding project, the editor of the TEI document should be entered here. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.

Unlike in the TEI Guidelines, do not use this element for translators, illustrators, compilers, or other roles not generally considered an editor. Therefore, do not use the <tt>role</tt> attribute.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><respStmt></tt></td>
<td><p>Record the names of other persons or organizations, one responsibility or party per <tt><respStmt></tt>, that have responsibility for the intellectual or artistic content of the TEI document—often by transitivity from the source document—not covered by <tt><author></tt> and <tt><editor></tt>. This includes translators, illustrators, compilers, proofreaders, encoders, and those who wrote a preface or introduction. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><editionStmt></tt></td>
<td>This element contains information about the edition of the TEI document produced, not the source document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><publicationStmt></tt></td>
<td>Use the child elements below (rather than <tt><p></tt>) for a prose description.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><publisher></tt></td>
<td>The publisher is the party responsible for making the file (the TEI document, not the source document) public.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><distributor></tt></td>
<td>The distributor is the party from whom copies of the file (the TEI document, not the source document) can be obtained. Often the same as <tt><publisher></tt>, in which case no <tt><distributor></tt> element should be specified.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><authority></tt></td>
<td>Only used for a text (the TEI document, not the source document) that is not formally published, but is nevertheless made available for circulation, in which case the party who makes it available should be recorded here.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><idno></tt></td>
<td>Any unique identification number for the TEI document determined by the publisher of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="4"><tt><availability><p></tt></td>
<td>Provide a prose rights statement for the TEI document. Provide a standard license, such as one from Creative Commons, if possible. Provide information on all applicable rights: rights in the original work, rights in page images of the source document, and rights in the encoded text.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><date when="____"/></tt></td>
<td>Refers to the date of the first publication of the TEI document. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing. This element has no content.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="5"><tt><seriesStmt></tt></td>
<td>This element contains information about the electronic series being created. It has one required element (<tt>title</tt>) and other optional elements.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td><p>│</p></td>
<td>└</td>
<td colspan="4"><tt><title level="s" type="_"></tt></td>
<td>Whenever possible, establish or use the form of the name from a national name authority file for the electronic series being created. The value of the <tt>type</tt> attribute is [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html drawn from the full TEI Guidelines].
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><notesStmt></tt></td>
<td>Optional.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><sourceDesc></tt></td>
<td>Use one <tt><sourceDesc></tt> per source document. Metadata for the source document may be automatically generated from a MARC record.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><biblStruct></tt></td>
<td>Use <tt><biblStruct></tt> with child elements arranged in the order below for ease of display according to ISBD. (This element is used instead of <tt><bibl></tt> to enforce structure, but <tt>>biblFull<</tt> is not used because it requires more elements than are typically available in library metadata sources.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>├</td>
<td colspan="3"><tt><monogr></tt></td>
<td>Use this element to group together the elements describing the whole source document. The TEI definition of this element specifies that it is used even for works that might not otherwise be considered “monographs.”</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><author></tt></td>
<td>One or more <tt>author</tt> elements (one name per element) are used to encode the name for the personal author or corporate body responsible for the creation of the intellectual or artistic content of the source document, even if this creator is not the main entry in the catalog record. Use <tt><persName></tt> or <tt><orgName></tt> when applicable. Whenever possible, establish or use the form of the name from a national name authority file.
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><title level="_" type="_"></tt></td>
<td>
At least one <tt>title</tt> element is required for the title of the source document. Give the title according to the national cataloging code. Use a <tt>type</tt> attribute with a value of <tt>marc245c</tt> to give the statement of responsibility from a MARC record.

The <tt>level</tt> attribute is used [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as in the main TEI Guidelines].

Use of the <tt>type</tt> attribute is required. It may have any of the following values:
* <tt>main</tt>
* <tt>sub</tt>
* <tt>alt</tt>
* <tt>short</tt>
* <tt>desc</tt>
* <tt>translated</tt>
* <tt>marc245a</tt> (used for the title proper and alternative title according to the national cataloging code)
* <tt>marc245b</tt> (used for the the remainder of the title information -- parallel titles, titles subsequent to the first, and other title information -- according to the national cataloging code)
* <tt>marc245c</tt> (used for the statement of responsibility according to the national cataloging code)
* <tt>uniform</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><respStmt></tt></td>
<td>
<p>Statement of responsibility on the source document, according to the national cataloging code. Record
one responsibility or party per <tt><respStmt></tt>. Each <tt><respStmt></tt> must contain either:</p>
<ul>
<li>one <tt><resp></tt> element followed by one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements</li>
<li>one or more <tt><name></tt> (or <tt><persName></tt> or <tt><orgName></tt>) elements followed by one <tt><resp></tt> element</li>
</ul>
<p>Whenever possible, establish or use the form of the name from a national name authority file.</p>

<p>If generating the <tt><sourceDesc></tt> from a MARC record, it will be difficult to split the content of the 245c field into <tt>resp</tt> and <tt>name</tt> elements, so it is recommended to use <tt><title type="marc245c"></tt> instead of this element.</p>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><edition></tt></td>
<td>Edition statement (if present).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>├</p></td>
<td colspan="2"><tt><imprint></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><pubPlace></tt></td>
<td>Place of publication from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a colon) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "S.l." (for no place of publication).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>├</p></td>
<td colspan="1"><tt><publisher></tt></td>
<td>Name of publisher, distributor, etc. from the original source (if present). It is recommended but not required to remove ISBD punctuation for separating areas of the bibliographic description (such as a comma) when deriving from a MARC record. However, leave brackets that indicate supplied information or an abbreviation like "s.n." (for no publisher).</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="1"><tt><date when="____"></tt></td>
<td>Date of publication, distribution, etc. from the original source (if present). The content of the element is the statement of this data according to the national cataloging code. Use the <tt>when</tt> attribute (see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]) to aid machine processing.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>│</td>
<td><p>└</p></td>
<td colspan="2"><tt><extent></tt></td>
<td>Use of this element to describe the extent of the source document is recommended. If the data is generated by hand, it should include a comprehensible statement of the size of the item, such as the number of pages or leaves. If generated from a catalog record, there should be two elements: one for the extent of the item and other physical details, and a second one for the dimension. Both should be recorded according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><series></tt></td>
<td>Name of the series to which the source document belongs. If generating this data from a catalog record, it is likely that you will have only one child element: a <tt>title</tt>.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td><p>├</p></td>
<td colspan="3"><tt><note></tt></td>
<td>Optionally, use for notes about the source document, according to a national cataloging code.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><idno></tt></td>
<td>
Optionally use one or more <tt>idno</tt> elements to give identification numbers for the source document, text, or work, whether assigned by the holding library (such as a call number), the publisher of the original document (such as an ISBN), or a standard bibliography (such as an identifier from the <cite>Short Title Catalogue</cite> or <cite>Books in Maori</cite>). Use the following values for the <tt>type</tt> attribute if applicable, and create other values if appropriate:

* <tt>LC_call_number</tt>
* <tt>isbn-13</tt>
* <tt>isbn-10</tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><encodingDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td>└</td>
<td colspan="5"><tt><projectDesc><p></tt></td>
<td>Enter a description of the purpose for which the electronic file was encoded.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><editorialDecl n="_"></tt></td>
<td>
Use the <tt>n</tt> attribute to record the encoding level: <tt>1</tt> for Level 1, <tt>2</tt> for Level 2, etc.

Include one or more <tt>p</tt> elements as children with information on:

* editorial decisions made during encoding
* notes about omissions of material found in the original work
* the format of the data in the header: Does the data in the <tt><sourceDesc></tt> follow AACR rules? How about in the <tt><fileDesc></tt>? Is ISBD punctuation included?
* automated processes used to generate the markup or content
* external files or databases (such as those containing authority data) referenced in the TEI document

Also include one of the following <tt>p</tt> elements as appropriate:

<tt><p>All hyphens in source document encoded as U+2010.</p></tt>

<tt><p>Soft hyphens encoded as U+00AD; hard hyphens as U+2010.</p></tt>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><tagsDecl></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>├</p></td>
<td colspan="3"><tt><rendition xml:id="_" scheme="css"</tt></td>
<td>Include one or more <tt>rendition</tt> elements for each unique value of a <tt>rendition</tt> attribute (not <tt>rend</tt> attribute) used in the body of the TEI document.</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>│</p></td>
<td><p>└</p></td>
<td colspan="3"><tt><namespace name="http://www.tei-c.org/ns/1.0"><tagUsage></tt></td>
<td>
<tt><tagUsage></tt> must be one of the following:
* <code><tagUsage gi="div1">Numbered divs used.</tagUsage></code>
* <code><tagUsage gi="div">Unnumbered divs used.</tagUsage></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><classDecl><taxonomy xml:id="____"><bibl></tt></td>
<td>
Use to document classification schemes used in the header or body of the TEI document. For example:
* <code><taxonomy xml:id="LCC"><bibl>Library of Congress Classification</bibl></taxonomy></code>
* <code><taxonomy xml:id="LCSH"><bibl>Library of Congress Subject Headings</bibl></taxonomy></code>
* <code><taxonomy xml:id="AAT"><bibl>Art &amp; Architecture Theasaurus</bibl></taxonomy></code>
</td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>├</p></td>
<td colspan="6"><tt><profileDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td><p>├</p></td>
<td colspan="5"><tt><langUsage></tt></td>
<td>Optionally use this element and child <tt>language</tt> elements to list languages used in the text. This supplements <tt><text xml:lang="___"></tt> in cases where more than one language is used in the text. It is not expected that the <tt>langUsage</tt> element will contain any description of language usage.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>│</td>
<td><p>└</p></td>
<td colspan="4"><tt><language ident="___"></tt></td>
<td>Use one or more <tt>language</tt> elements to indicate language(s) used in the source document. The <tt>ident</tt> attribute is usually sufficient to indicate the language, so this element should normally have no content. In the unusual case where <tt>ident</tt> is insufficient, provide additional information on the language as content of the element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>│</td>
<td>└</td>
<td colspan="5"><tt><textClass></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td><p>├</p></td>
<td colspan="4"><tt><classCode scheme="___"></tt></td>
<td>True classification numbers as opposed to call numbers may be entered here. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCC"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td>└</td>
<td colspan="4"><tt><keywords scheme="____"></tt></td>
<td>Repeat this element as many times as there are keyword schemes. If the child <tt>term</tt> elements contain terms from a controlled vocabulary, indicate that controlled vocabulary through the scheme attribute. The value of the scheme attribute corresponds to a classification scheme defined previously in <tt><classDecl></tt>.
Example: <code>scheme="#LCSH"</code></td>
<td></td>
<td></td>
</tr>

<tr>
<td><p>│</p></td>
<td></td>
<td></td>
<td>└</td>
<td colspan="3"><tt><term></tt></td>
<td>Use for terms from controlled or uncontrolled vocabularies, as indicated in the parent <tt>keywords</tt> element.</td>
<td></td>
<td></td>
</tr>

<tr>
<td>└</td>
<td colspan="6"><tt><revisionDesc></tt></td>
<td></td>
<td></td>
<td></td>
</tr>

<tr>
<td></td>
<td>└</td>
<td colspan="5"><tt><change when="''YYYY-MM-DD''" who="''URI''"></tt></td>
<td>
Create a <tt>change</tt> element to record each significant change to the TEI document, in reverse chronological order (i.e., most recent first). A prose description of the change is recorded as the content of each <tt>change</tt> element. This prose may contain lists for organization, and phrase-level markup (like <tt><gi></tt>, <tt><ptr></tt>, or <tt><date></tt>), but not paragraphs.

The date of the change should be recorded using the <tt>when</tt> attribute ((see [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.datable.w3c.html att.datable.w3c class]).

The person who is responsible for making the change is indicated by the <tt>who</tt> attribute of <tt><change></tt>. Its value is a URI that points to a <tt><respStmt></tt> or <tt><person></tt> element that encodes information about the responsible party. Note that this reference is a URI reference and not an ID/IDREF reference, and thus is not checked by validation software. Small projects sometimes take advantage of this by putting information into the URI itself, and not having a <tt>respStmt</tt> or <tt>person</tt> element. For example, the document might simply give <tt>who="#Jane_Smith"</tt>, relying on human readers to understand this reference.
</td>
<td></td>
<td></td>
</tr>
</table>

===Sample TEI Header===
<blockquote><pre>
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<title type="main">Lincoln and Seward.</title>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
</titleStmt>
<publicationStmt>
<publisher>University of Michigan, Digital Library Initiatives</publisher>
<availability>
<p>These pages may be freely searched and displayed. Permission must be received for
subsequent distribution in print or electronically. Please go to
http://www.umdl.umich.edu/ for more information.</p>
</availability>
<date when="1996"/>
</publicationStmt>
<seriesStmt>
<title level="s" type="main">Making of America</title>
</seriesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<author>
<persName>Welles, Gideon, 1802-1878.</persName>
</author>
<title level="m" type="marc245a">Lincoln and Seward.</title>
<title level="m" type="marc245b">Remarks upon the memorial address of Chas. Francis
Adams, on the late William H. Seward, with incidents and comments illustrative of the
measures and policy of the administration of Abraham Lincoln. And views as to the
relative positions of the late President and secretary of state.</title>
<title type="marc245c">By Gideon Welles</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Sheldon &amp; company</publisher>
<date when="1874">1874</date>
</imprint>
<extent>viii, [7]-215 p</extent>
<extent>20 cm.</extent>
</monogr>
<note>First published in condensed form in the Galaxy, v. 16, 1873, p. [518]-530,
[687]-700, [793]-804.</note>
<idno type="isbn-10">1-4255-1817-6</idno>
<idno type="LC_call_number">E456 .W44</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>XML created for the Making of America collection.</p>
</projectDesc>
<editorialDecl n="1">
<p>Data in the <gi>sourceDesc</gi> of the header comes from a pre-AACR2 record. Other data
follows AACR2 when applicable.</p>
<p><gi>sourceDesc</gi> created by exporting from catalog on 2008-06-15.</p>
<p>This electronic text file was created by optical character recognition (OCR). No
corrections have been made to the OCR-ed text and no editing has been done to the content
of the original document. Encoding has been done using the recommendations for Level 1 of
the TEI in Libraries Guidelines.</p>
<p>All hyphens in source document encoded as U+2010.</p>
</editorialDecl>
<tagsDecl>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="div">Unnumbered divs used.</tagUsage>
</namespace>
</tagsDecl>
<classDecl>
<taxonomy xml:id="LCC">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<langUsage>
<language ident="en"/>
</langUsage>
<textClass>
<classCode scheme="#LCC">E456</classCode>
<keywords scheme="#LCSH">
<term>Lincoln, Abraham, 1809-1865.</term>
<term>Seward, William Henry, 1801-1872.</term>
<term>Adams, Charles Francis, 1807-1886. Address of Charles Francis Adams ... on the life
... of William H. Seward.</term>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change who="#CKP" when="2005-05-25">Header generated from export of MARC record</change>
</revisionDesc>
</teiHeader>
</pre></blockquote>

==Encoding Levels==

===LEVEL 1: Fully Automated Conversion and Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]

====Purpose====

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

====Rationale====

The text is subordinate to the page image, and is not intended to stand alone as an electronic text (without page images). Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. Though their encoding is minimal, Level 1 texts are fully valid XML texts. In addition to taking advantage of the TEI header, these texts, while lightly encoded, can be easily combined with more richly encoded texts (that also follow these guidelines) for searching. Further encoding based on document structures or content analysis can be added to a Level 1 text at any time.

<p>'''Level 1 is most suitable for projects with the following characteristics''':</p>
<ul>
<li>a large volume of material is to be made available online quickly</li>
<li>a digital image of each page is desired</li>
<li>no manual intervention will be performed in the text creation process</li>
<li>the material is of interest to a large community of users who wish to read texts that allow keyword searching</li>
<li>sophisticated search and display capabilities based on the structure of the text are not necessary</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added at a later date</li>
</ul>

====Workflow====

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is left uncorrected ("dirty OCR"). Page images are tagged using software that assigns a page-level metadata (page number and possibly tags for page features) to each page image for display in the user interface in a list of pages. Encoding is performed automatically: markup with page-level metadata is inserted at selected points into the dirty OCR text, generating a valid XML document. This encoding is both minimal and reliable, and does not typically require extensive review of each page of each text.

====Element Recommendations for Level 1====

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><div></tt> or <tt><div1></tt></td>
<td colspan="1">There should be only one child of <tt><body></tt>: a single <tt><div></tt> (or <tt><div1></tt>).</td>
</tr>

<tr>
<td colspan="1"><tt><ab></tt></td>
<td colspan="1">There should be only one child of the <tt><div></tt> (or <tt><div1></tt>): a single <tt><ab></tt> wrapping all of the OCR text. If the text is ever “upgraded” to Level 3 or higher, the <tt>ab</tt> element will be replaced by structural elements like <tt><p></tt> and <tt><table></tt>.</td>
</tr>
<tr>

<td colspan="1"><tt><pb></tt></td>
<td colspan="1">Required in Level 1. See the explanation above for [http://wiki.tei-c.org/index.php/TEI_in_Libraries:_Guidelines_for_Best_Practices#Linking_between_encoded_text_and_images_of_source_documents how to link between the encoded text and images of source documents].</td>
</tr>
</table>

==== Level 1 Example: Alger Hiss document ====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<ab>
<pb n="113" facs="00000001.tif"/>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 2: Minimal Encoding===

====Reference====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html Chapter 3, Elements Available in All TEI Documents]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure]

====Purpose====
To create electronic text for full-text searching, linking to page images, and identifying simple structural hierarchy to improve navigation. (For example, you can create a table of contents from such encoding.)

====Rationale====
The text is mainly subordinate to the page image, though navigational markers (textual divisions, headings) are captured. However, the text could stand alone as electronic text (without page images) if the accuracy of its contents is suitable to its intended use and it is not necessary to display low-level typographic or structural information. Level 2 requires a set of elements more granular than those of Level 1, including bibliographic or structural information below the monographic or volume level. One of the motivations for using Level 2 is to avoid expensive analysis of textual elements and/or the expense of accurate text conversion, e.g., double-keying or detailed proofreading of automatic OCR.

For the most part, Level 2 texts are <i>not</i> intended to be displayed separately from their page images. Level 2 encoding of sections and headings provides greater navigational possibilities than Level 1 encoding, and enables searching to be restricted within particular textual divisions (for example, searching for two phrases within the same chapter).

'''Level 2 is most suitable for projects in which''':

* a large volume of material is to be made available online quickly
* a digital image of each page is desired
* the material is of interest to a large community of users who wish to read texts that allow keyword searching
* rudimentary search and display capabilities based on the large structures of the text are desired
* each text is checked to ensure that divisions and headers are properly identified
* extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date

====Workflow====

Level 2 generally can be created and encoded by automated means. Pagination is identified as in Level 1, and metadata for the <tt><div></tt> structure is created, likely based on the page images. The <tt><div></tt> structure metadata might contain the page number on which the division begins and a transcription of that <tt><div></tt>’s heading. This metadata is inserted into the raw OCR at the appropriate points, forming a valid XML document. Level 2 texts do not require any special knowledge or manual intervention below the section level.

====Element Recommendations for Level 2====

Use all elements specified in Level 1 plus the following:

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>
<td colspan="1">Optional.</td>
</tr>
<tr>
<td colspan="1"><tt><div1></tt> or <tt><div></tt></td>
<td colspan="1">Unlike in Level 1, in Level 2 one <tt><div1></tt> or <tt><div></tt> is used per section of the text identified with division-level metadata. If no <tt>type</tt> attribute is specified, a <tt>type</tt> value of <tt>"section"</tt> should be presumed. </td>
</tr>
<tr>
<td colspan="1"><tt><head></tt></td>
<td colspan="1">Required if headings are present.</td>
</tr>
</table>

====Level 2 Examples====
=====Level 2 Basic Structure=====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
[title page information, table of contents, prefaces, etc.]
[optional]
</front>
<body>
<div type="section">
<pb n="1" facs="[URI of page 1 image]"/>
<head>[heading of section 1]</head>
<ab>[entire contents of section 1 here, with
interspersed <pb> elements pointing to page
images; in this example there are 26 more pages
to section 1]</ab>
</div>
<div type="section">
<pb n="27" facs="[URI of page 27 image]"/>
<div type="subsection">
<head>[heading of section 2 subsection 1]</head>
<ab>[all the paragraphs of subsection one go here
with page breaks inserted]</ab>
</div>
</div>
</body>
<back> [optional] </back>
</text>
</TEI>
</pre>

===== Level 2 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>

<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING
SHOULD BE ORDERED.</head>
<ab>

POINT VIII.
BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
DISCOVERY AND A HEARING SHOULD BE ORDERED.
The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern‐
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open‐
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter‐
mination regarding these issues.
FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

-113 -


<pb n="114" facs="00000002.tif"/>

on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.
In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947. CN Ex. 102; CN Ex. 103.
The most intrusive invasion of petitioner's rights
68/ Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re‐
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu‐
ments. CN Ex. 100B

-114 -


<pb n="115" facs="00000003.tif"/>

occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per‐
sonal lives, relationships with friends and associates, and
habits is recorded.
The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization, although
no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.
As one would expect, the interception of every telephone
h9/ Hoover's initial request was answered by a note reques‐
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.

-115 -


</ab>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 3: Simple Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines] (for handling notes)

====Purpose====

<p>
To create a stand-alone electronic text and identify
hierarchy (logical structure) and typography without content analysis being of primary importance.</p>

====Rationale====

<p>
Encoding at this level offers provides the foundation for upgrading to higher levels of encoding. Level 3 generally requires some human editing, but the features to be encoded are determined by the logical structure and appearance of the text and not specialized content analysis.</p>

<p>Level 3 texts identify front and back matter, divisions within the text, and all paragraph breaks. Floating texts, or sub-texts like a poem or letter embedded in the greater text, are supported in this level. The finer granularity of encoding these features, as well as figures, notes, and all changes of typography, allows a range of options for display, delivery, and searching. For example, one has the option of identifying, and therefore specifying, the display characteristics of different typographic styles, and regularizing the display and placement of note text.</p>

<p>Level 3 texts can stand alone as text without page images, and therefore can be uploaded, downloaded, and delivered quickly, and require less storage space than digital collections with page images. However, the simple level of structural analysis and absence of specialized content analysis reflected in Level 3 encoding may make it desirable for some, depending on project priorities, to include page images in order to provide users with a fuller set of resources.</p>

<p>
'''Level 3 is most suitable for projects with the following characteristics:'''
</p>

<ul>
<li>the material is of interest to a large community of users who wish to read texts that allow for keyword searching</li>
<li>some sophistication of display, delivery, and searching based on structure of the text is desired</li>
<li>each text will undergo quality control to ensure that encoding decisions have been made appropriately</li>
<li>the users of the texts may have limited storage or display capabilities</li>
<li>the creator of the texts has limited or no ability to provide content expertise to analyze, tag, or review texts</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of encoding to be added at a later date</li>
</ul>

====Workflow====

Level 3 texts can be created by conversion from an electronic source such as an HTML file or word-processor document or from a print source, either through OCR or keyboarding. They can be generated trivially by converting from outsourced double-keyboarded texts conforming to TEI Tite, though some granularity of encoding will be lost in the translation.

====Element Recommendations for Level 3====

<p>Use all elements specified in Levels 1 and 2 '''except <tt>ab</tt>''', plus the following:</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><front></tt>, <tt><back></tt></td>

<td colspan="1">Required if present.</td>
</tr>
<tr>
<td colspan="1"><tt><div></tt></td>

<td colspan="1">Required if present; <tt>type</tt> attribute is recommended.</td>
</tr>
<tr>
<td colspan="1"><tt><floatingText></tt></td>

<td colspan="1">Recommended if present.</td>
</tr>

<tr>
<td colspan="1"><tt><p></tt></td>
<td colspan="1">Required for paragraph breaks in prose.</td>
</tr>

<tr>
<td colspan="1"><tt><lg></tt> and <tt><l></tt></td>
<td colspan="1">Required for identifying groups of lines and lines, respectively.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">May be used in this level to indicate ordered and unordered list structures.</td>
</tr>
<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>

<td colspan="1">May be used to indicate table structures.</td>
</tr>
<tr>
<td colspan="1"><tt><figure></tt></td>
<td colspan="1">Required to indicate figures other than page images.</td>
</tr>
<tr>

<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate changes in typeface; <tt>rend</tt> attribute is optional.</td>
</tr>
<tr>
<td colspan="1"><tt><note></tt></td>
<td colspan="1">All notes must be encoded. It is also recommended that notes that extend beyond one page be combined into one <tt><note></tt> element. Marginal notes, without reference, should occur at the beginning of the paragraph to which they refer, with the value of the <tt>place</tt> attribute as <tt>"margin"</tt>.</td>

</tr>
<tr>
<td colspan="1"><tt><lb/></tt></td>
<td colspan="1">May be used to indicate line breaks.</td>
</tr>
</table>

====General Level 3 Recommendations====

=====Forme Work=====

Running heads, catch words, page numbers, signatures, and other artifacts derived from printing should not be included in Level 3, with the exception of page numbers, which are recorded using <tt><pb></tt>. If upgrading a text from Level 1 or Level 2 that was generated using OCR, discard the forme work information.

=====Table of Contents=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT Chapter 4.5, Front Matter]

You may wish not to include front matter content such as table of contents or lists of illustrations, especially if you plan to automatically generate the contents or lists of illustrations. If you do, however, plan to manually encode the table of contents (or lists of illustrations and similar content), use a <tt>div</tt> element with an appropriate <tt>type</tt> attribute (e.g., <tt><div type="contents"></tt>). Within this division, use the <tt>list</tt> element to mark up the table of contents, list of illustrations, etc. Each list item should have a <tt>ptr</tt> or <tt>ref</tt> element with a <tt>target</tt> attribute referencing an <tt>xml:id</tt> attribute on the <tt><pb></tt> or "div" element of the referenced page or section. Use <tt>ref</tt> if you wish to transcribe page numbers in the table of contents; use <tt>ptr</tt> if you do not.

=====Notes=====

<p>'''<tt><note></tt>''': It may be desirable to move footnotes from their original location in the text. If left at the bottom of a page, a note may become included in another paragraph or section of the encoded text, and thus separated from its reference. There are two options for placement of footnotes if they are moved:</p>

<ul>
<li>Inline. The note itself is inserted at the point of reference. (See Alger Hiss example below.)</li>
<li>End-of-Division. All notes in a division are group together at the end of the division for ease of conversion from OCR, with a <tt>ref</tt> element inserted at each point of reference. For example: <pre><ref target="#foo">68</ref></pre> at the point of the footnote reference, pointing to <pre><note place="bottom" anchored="true" xml:id="foo" n="68">Also before 1947, [. . .]</note></pre>
</li>
</ul>

====Level 3 Examples====

=====Level 3 Basic Structure: Prose =====

<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<div type="frontispiece">[figure]</div>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
</div>
</body>
<back>
<div type="appendix">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
</pre>

=====Level 3 Basic Structure: Verse =====
<pre>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="VAA2383">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<front>
<titlePage>[text]</titlePage>
<div type="dedication">[text]</div1>
<div type="contents">[text]</div1>
</front>
<body>
<div type="book">
<head>[book title]</head>
<div type="part">
<head>[section title]</head>
<div type="poem">
<head>THE DAYS GONE BY.</head>
<lg>
<l>O the days gone by! O the days gone by!</l>
<l>The apples in the orchard, and the pathway through the rye;</l>
<l>The chirrup of the robin, and the whistle of the quail</l>
<l>As he piped across the meadows sweet as any nightingale;</l>
<l>When the bloom was on the clover, and the blue was in the sky,</l>
<l>And my happy heart brimmed overin the happy days gone by.</l>
</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
<lg>[lines of poetry]</lg>
</div>
</div>
</div>
</body>
</text>
</TEI>
</pre>

=====Level 3 Table of Contents=====
<pre>

<div type="contents">
<head>CONTENTS</head>
<list type="simple">
<item>I. A Boy and His Dog
<ref target="#VAA2383_011" rend="text-align: right">3</ref>
</item>
<item>II. Romance
<ref target="#VAA2383_020" rend="text-align: right">12</ref>
</item>
<item>III. The Costume
<ref target="#VAA2383_029" rend="text-align: right">21</ref>
</item>
<item>IV. Desperation
<ref target="#VAA2383_038" rend="text-align: right">30</ref>
</item>
<item>V. The Pageant of the Table Round
<ref target="#VAA2383_046" rend="text-align: right">38</ref>
</item>
</list>
</div>
</pre>

=====Level 3 Chapter with Letter=====
<pre>
<div type="chapter">
<pb xml:id="VAA2383_126" n="118"/>
<head type="main">CHAPTER XIV</head>
<head type="subtitle">MAURICE LEVY'S CONSTITUTION</head>
<p><hi rend="font-weight: bold">L</hi>O, SAM!" said Maurice cautiously. "What you doin'?"</p>
<p>Penrod at that instant had a singular experiencean intellectual shock like a flash of fire in the
brain. Sitting in darkness, a great light flooded him with wild brilliance. He gasped!</p>

<p>"What you doin'?" asked Maurice for the third time, Sam Williams not having decided upon a reply.</p>
<pb xml:id="VAA2383_127" n="119"/>
<p>It was Penrod who answered.</p>
<p>"Drinkin' lickrish water," he said simply, and wiped his mouth with such delicious enjoyment that
Sam's jaded thirst was instantly stimulated. He took the bottle eagerly from Penrod.</p>
<p>"A-a-h!" exclaimed Penrod, smacking his lips. "That was a good un!"</p>

<p>Penrod uttered some muffled words and then waved both armseither in response or as an expression
of his condition of mind; it may have been a gesture of despair. How much intention there was in
this actobviously so rash, considering the position he occupiedit is impossible to say.
Undeniably there must remain a suspicion of deliberate purpose.</p>

<pb xml:id="VAA2383_138" n="130"/>
<p>The damsel curtsied again and handed him the following communication, addressed to herself: </p>
<floatingText>
<body>
<div type="letter">
<p>"Dear madam Please excuse me from dancing the cotilo with you
this afternoon as I have fell off the barn</p>
<p>"Sincerly yours<lb/>
"<hi rend="font-variant: small-caps">Penrod Schofield</hi>."
</p>
</div>
</body>
</floatingText>
</div>
</pre>

===== Level 3 Alger Hiss document =====

<pre>
<TEI xml:id="someid" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="00000001.tif"/>
<head>POINT VIII. BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S CONVICTION SHOULD BE VACATED; ALTERNATIVELY, DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
family and associates was not known at the time of trial by
the defense. Even now, with the release of some of the govern&amp#xAD;
ment documents concerning FBI investigative techniques regarding
Hiss, the full extent of surveillance -- wiretapping, mail open&amp#xAD;
ings, mail covers, physical surveillance, and other intrusive
techniques -- is still not 'clear. Nevertheless, it is apparent
that information gathered through the exploitation of unlawful
wiretaps and other illegal surveillance was used at trial and
consequently the conviction must be reversed. Alternatively,
further discovery and a hearing is essential to a fair deter&amp#xAD;
mination regarding these issues.</p>

<p>FBI surveillance of Hiss began in earnest in 1941 with
the institution of a mail cover on his incoming correspondence
at his home in connection with an FBI investigation of possible
Hatch Act violations. CN Ex. 98A. Another mail cover was placed

<pb n="114" facs="00000002.tif"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
toll call records from the Hiss residence Telephone for the
years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>

<p>In late November, 1945, FBI surveillance of the Hiss
residence in Washington, D.C., escalated. For the third time,
a mail cover was instituted beginning on November 28, 1945,
which was continued at least until 1946. CN Ex. 101 at p. 70;
CN Ex. 102. Continuous physical surveillance of Hiss was begun
as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
surveillance was discontinued on December 14, 1945, physical
surveillance was conducted frequently at various times until
September, 1947.

<note place="bottom" anchored="true" n="68">Also before 1947, a letter from Priscilla Hiss addressed
to her son, Timothy Hobson, was intercepted and its contents
read. CN Ex. 100A at p. 167. In approximately March, 1947,
a letter from a Michael Greenberg addressed to petitioner re&amp#xAD;
garding an application for employment with the United Nations
was also intercepted, in a manner not revealed by the docu&amp#xAD;
ments. CN Ex. 100B</note>

CN Ex. 102; CN Ex. 103.</p>

<p>The most intrusive invasion of petitioner's rights

<pb n="115" facs="00000003.tif"/>
occurred from December 13, 1945 until the Hisses moved from
Washington, D.C. to New York City on September 13, 1947. A
"technical surveillance," -- a wiretap -- was placed on the Hiss
telephone at their residence on P Street-in Washington, D.C.
The logs of this surveillance constitute twenty-nine volumes
of FBI serials and are roughly 2,500 pages in length, in which
an enormous amount of information concerning the Hisses' per&amp#xAD;
sonal lives, relationships with friends and associates, and
habits is recorded.</p>

<p>The wiretap was installed following FBI Director Hoover's
application to the Attorney General for authorization,

<note place="bottom" anchored="true" n="69">Hoover's initial request was answered by a note reques&amp#xAD;
ting information on Hiss. CN Ex. 104. Additional information
was furnished by letter dated November 30, 1945. CN Ex. 105.</note>

although no written authorization appears in the documents released to
Hiss. The purpose of the application was to gather information
regarding Hiss' alleged contacts with Soviet espionage agents and
communists in government service, general allegations which had
been made by Elizabeth Bentley and Chambers.</p>

<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI>
</pre>

===LEVEL 4: Basic Content Analysis===

====Reference====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQ Chapter 3.3 Highlighting and Quotation, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COED Chapter 3.4 Simple Editorial Changes, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONA Chapter 3.5 Names, Numbers, Dates, Abbreviations, and Addresses, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COVE Chapter 3.12.1 Core Tags for Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CODR Chapter 3.12.2 Core Tags for Drama, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html Chapter 4, Default Text Structure, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html Chapter 6, Verse, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRCAST Chapter 7.1.4 Performance Texts: castLists and castItems, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRDIV Chapter 7.2.1 Performance Texts: Major Structural Divisions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSP Chapter 7.2.2 Performance Texts: Speeches and Speakers, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DR.html#DRSTA Chapter 7.2.3 Performance Texts: Stage Directions, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html Chapter 13, Names, Dates, People, and Places, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FT.html Chapter 14, Tables, Formulæ, and Graphics, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#FTGRA Chapter 14.3 Specific Elements for Graphic Images, P5 Guidelines]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html Chapter 16, Linking, Segmentation, and Alignment, P5 Guidelines]

====Purpose====
<p>To create text that can stand alone as electronic text, identifies
hierarchy and typography, specifies function of textual and structural elements, and describes the
nature of the content and not merely its appearance. This level is not meant to encode or identify all
structural, semantic, or bibliographic features of the text.</p>

====Rationale====
<p>Greater description of function and content allows for:</p>

<ul>
<li>flexibility of display and delivery</li>
<li>sophisticated searching within specified textual and structural elements</li>
<li>combining the broadest range of uses and audiences</li>

</ul>

<p>Texts encoded at Level 4 are able to stand alone without page images in order for them to be read by students, scholars, and general readers. This level of TEI
encoding allows them to be displayed or printed in a variety of ways suitable for classroom or scholarly
use.</p>

<p>Level 4 texts contain elements and attributes that describe content. Features of the text that may contribute to meaning, such as indentation of verse lines and typographic change, are preserved. These are textual features that are not encoded at lower levels and that allow the text to be used and understood fully independent of images. The ability to stand alone as text means that Level 4 texts are more nimble and robust for exercises such as format repurposing and textual analysis.</p>

<p>Finally, functionally accurate encoding in Level 4 texts
allows them to be searched or displayed in sophisticated ways.
For example, a searcher could limit his or her search in a
dramatic text to stage directions or in a verse text to only
first lines. In a political tract published by subscription, a
search could be confined to names that appear in lists, thus
limiting a search to names of people who subscribed to a
particular volume. This ability to limit searches becomes more
significant as textbases become larger, and thus is of great
importance to the library community as it attempts to build into
the initial design and implementation of textbases the features
needed to enhance interoperability.</p>

<p>
'''Level 4 is most suitable for projects with the following characteristics''':
</p>

<ul>
<li>sophisticated search and retrieval capabilities are desired</li>

<li>the texts will be used for textual analysis</li>
<li>extensibility is desired; that is, one desires to keep open the option for a higher level of
encoding to be added by the scholarly community at a later date</li>
<li>the users of the texts may have limited storage or display capabilities</li>
</ul>

====Workflow====

Text is generated by keyboarding (likely outsourced double keyboarding from page images using TEI Tite) or possibly by correcting OCR text using software that identifies spelling mistakes and consults a log from the OCR software to find regions of uncertainty in the OCR text. If converting from TEI Tite, minimal additional markup must be added, as discussed in [http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg Appendix A of TEI Tite].

====Element Recommendations for Level 4====

<p>Use all elements specified in Levels 1, 2, and 3 '''except <tt>ab</tt>''', plus elements in the following table. Note that some of these elements are defined in Level 3 as well, but their use in Level 4 is more strict.</p>

<table border="1" width="80%">
<tr>
<td colspan="1"><tt><titlePage></tt> and appropriate child elements</td>
<td colspan="1">Required.</td>
</tr>

<tr>
<td colspan="1"><tt><group></tt></td>
<td colspan="1">Required to encode a collection of independent texts that are regarded as a single group for processing or other purposes.</td>
</tr>

<tr>
<td colspan="1"><tt><list></tt> and <tt><item></tt></td>
<td colspan="1">Required to indicate ordered and unordered list structures.</td>
</tr>

<tr>
<td colspan="1"><tt><table></tt>, <tt><row></tt>, and <tt><cell></tt></td>
<td colspan="1">Required to indicate table structures.</td>
</tr>

<tr>
<td colspan="1"><tt><hi></tt></td>
<td colspan="1">Required to indicate change in rendition when a more specific element is not being used; <tt>rend</tt> attribute is optional.</td>
</tr>

<tr>
<td colspan="1"><tt><emph></tt>, <tt><foreign></tt>, <tt><gloss></tt>, or <tt><term></tt></td>
<td colspan="1">Recommended to identify typographically distinct text.</td>
</tr>

<tr>
<td colspan="1"><tt><title></tt></td>
<td colspan="1">Recommended to identify typographically distinct text. For <tt>title</tt> elements within the body of a document, use the <tt>type</tt> attribute with a value [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html as given in the full TEI guidelines] except for main titles. (The <tt>main</tt> attribute should be used, when appropriate, for <tt><title></tt>s within a TEI Header, but is not needed for <tt><title></tt>s elsewhere in a document.)</td>
</tr>

<tr>
<td colspan="1"><tt><epigraph></tt>, <tt><quote></tt>, <tt><said></tt>, <tt><mentioned></tt>, or <tt><soCalled></tt></td>
<td colspan="1">Recommended to represent speech, thought, quotation, etc.</td>
</tr>

<tr>
<td colspan="1"><tt><sic></tt>, <tt><corr></tt>, or <tt><choice></tt></td>
<td colspan="1">Recommended to encode errors or typos.</td>
</tr>

<tr>
<td colspan="1"><tt><opener></tt>, <tt><dateline></tt>, <tt><salute></tt> <tt><closer></tt>, <tt><signed></tt>, <tt><postscript></tt></td>
<td colspan="1">Required to indicate specific parts of letters.</td>
</tr>

<tr>
<td colspan="1"><tt><argument></tt></td>
<td colspan="1">Recommended to encode a “list of topics sometimes found at the start of a chapter or other division.”</td>
</tr>

<tr>
<td colspan="1"><tt><trailer></tt></td>
<td colspan="1">Recommended to encode a “closing title or footer” at the end of a division.</td>
</tr>

<tr>
<td colspan="1"><tt><add></tt>, <tt><del></tt>, <tt><gap></tt>, and <tt><unclear></tt></td>
<td colspan="1">Recommended to encode material that is omitted, added, marked for deletion, or is illegible, invisible, or inaudible. </td>
</tr>

<tr>
<td colspan="1"><tt><figure></tt>, <tt><head></tt>, <tt><figDesc></tt>, and <tt><graphic></tt></td>
<td colspan="1">Used to refer to illustrative images and descriptive information about those images.</td>
</tr>

<tr>
<td colspan="1"><tt><castList></tt>, <tt><castItem></tt>, <tt><sp></tt>, <tt><speaker></tt>, and <tt><stage></tt></td>
<td colspan="1">Required to encode different structures in performance texts (i.e. drama).</td>
</tr>

<tr>
<td colspan="1"><tt><sp></tt> and <tt><speaker></tt></td>
<td colspan="1">Required to encode oral history interviews.</td>
</tr>

<tr>
<td colspan="1"><tt><persName></tt>, <tt><placeName></tt>, <tt><geogName></tt>, and <tt><orgName></tt> </td>
<td colspan="1">Recommended to encode personal, place, and organizational names used in a text.</td>
</tr>

<tr>
<td colspan="1"><tt><listName></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt> </td>
<td colspan="1">Recommended in support of personal, place, and organizational names normalization and to capture
additional information about the names. Should be captured in an external TEI file or database for easier maintenance of names.</td>
</tr>
</table>

====General Level 4 Recommendations and Examples====

* The use of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-group.html <group>] is required when you need to encode a body of distinct texts that are grouped together and are regarded as a unit. Most typical examples of such composite texts would be anthologies, collected works of an author, etc. Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSGRP 4.3.1 Grouped Texts] states, “The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded in this way.”

* Typographically distinct text may be encoded using the following elements:
**to represent speech, thought, quotation, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-epigraph.html epigraph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quote.html quote]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html said]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-mentioned.html mentioned]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-soCalled.html soCalled]
**to represent foreign words or phrases, linguistically emphatic or stressed words or phrases, words regarded as technical terms, etc.:
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-emph.html emph]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-foreign.html foreign] (e.g. <tt><foreign xml:lang="fr"></tt>)
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gloss.html gloss]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-term.html term]
***[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-title.html title]

* Any ambiguous typographically distinct text should be encoded as [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-hi.html hi] (e.g. <tt><hi rend="font-weight: bold"></tt>). This element may also be used if the more specific elements above are not used.

* Any of the following three methods may be used to encode errors or typos in original texts:
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-sic.html sic] element used alone is recommended to indicate errors without correcting them
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-corr.html corr] element used alone is recommended to provide corrections without indicating the initial error
** the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-choice.html choice] element allows both the apparent error and its editorial correction to be recorded, as in the following examples:

<pre>
<p>He has no Scruple about Fish; but won't touch a bit of Pork, it being
<choice>
<sic>expresly</sic>
<corr>expressly<corr>
</choice> forbidden by their Law.</p>
</pre>
Source: Thomas Bluett. ''Some Memoirs of the Life of Job, the Son of Solomon,
the High Priest of Boonda in Africa; Who was a Slave About Two Years in Maryland; and Afterwards Being Brought to England, was Set Free, and Sent to His Native Land in the Year 1734.'' London: Printed for R. Ford, 1734.

or

<pre>
<p>4. The art of writing she obtained by her own industry and curiosity, and in so
short a time that in the year 1765, when she was not more than twelve years of
<choice>
<sic>age,she</sic>
<corr>age, she</corr>
</choice>
was capable of writing letters to her friends <pb xml:id="p11" n="11"/> on various
subjects. She also wrote to several persons in high stations.</p>
</pre>
Source: Abigail Mott, 1766-1851. ''Biographical Sketches and Interesting Anecdotes of Persons of Colour. To Which is Added, a Selection of Pieces in Poetry.'' New-York: M. Day, 1826.

* Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-argument.html <tt><argument></tt>] to encode a prefatory list or prose description of the topics usually discovered at the beginning of a chapter. The content within the <tt>argument</tt> element can be presented as a list or as a paragraph:

<pre>
<div type="chapter" n="1">
<pb xml:id="albert14" n="14"/>
<head>CHAPTER I.<lb/>CHARLOTTE BROOKS.</head>
<argument>
<p>Causes of immorality among colored people - Charlotte Brooks - She is sold South -
Sunday work.</p>
</argument>
<p> ... </p>
</div>
</pre>
Source: Octavia V. Rogers Albert. ''The House of Bondage, or, Charlotte Brooks and Other Slaves, Original and Life Like, As They Appeared in Their Old Plantation and City Slave Life; Together with Pen-Pictures of the Peculiar Institution, with Sights and Insights into Their New Relations as Freedmen, Freemen, and Citizens.'' New York: Hunt & Eaton, 1890.

* The [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-trailer.html <tt>trailer</tt>] element is recommended to encode a heading- or title-like content at the end of a division (i.e. chapter, book, etc.):
<pre>
<body>
<head>[book title]</head>
<div type="chapter" n="1">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 1.</trailer>
</div>
<div type="chapter" n="2">
<head>[chapter title]</head>
<p>[text]</p>
<trailer>Here ends the Chapter 2.</trailer>
</div>
<trailer>FINIS.</trailer>
</body>
</pre>

* The elements [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html <tt>add</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-del.html <tt>del</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-unclear.html <tt>unclear</tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-gap.html <tt>gap</tt>] may be used to indicate instances when a text (i.e. word or part of it, phrase or part of it) has been added, marked for deletion, or to indicate cases where transcription is difficult (<tt><unclear></tt>) or impossible (<tt><gap></tt>) because the material is illegible, invisible, or inaudible (i.e. while transcribing oral history interviews):

<pre>
<p>But it is well authenticated by the observation of every one, that <del
rend="text-decoration: line-through" hand="#JHL">their manner</del> <add rend="vertical-align: super" hand="#JHL">this way—i.e.
the above</add> of writing influences the style of compos. of those who practise it
considerably, when they grow up to years of manhood; for their productions, <del
hand="#JHL" rend="text-decoration: line-through">instead</del> far from being terse, argumentative,
convincing, are without head or tail &amp; are generally an incongruous mass mixed up in the
most disgusting manner, without divisions or heads &amp; in short without a subject (so to
speak).</p>
</pre>
Source: Class Composition of J. Horace Lacy, [January 1851] 1. Lacy, James Horace, 1834-1852
<pre>
<p>But I still hope for &amp; trust in God and I believe he will animate our brave
defenders with a superhuman power and we will yet drive from our soil the hated invaders
whose tread <gap reason="ink blot"/> profanation, but this is an hour to try
men's souls—Fort Donelson has been taken by the enemy. Frank was there and covered
himself with honor but his bravery cost him a wound; he was wounded in the leg slightly—a
flesh wound only, you must not be uneasy.</p>
</pre>
Source: Kimberly Family Personal Correspondence, 1862-1864. Transcript of the manuscript, UNC-Chapel Hill, Southern Historical Collection.

=====Level 4 Front and Back Matter=====

* The use of the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt>titlePage</tt>] element with appropriate child elements describing the major features of most title pages is required. The child elements are listed in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSTITL Section 4.6 "Title Pages"].

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-titlePage.html <tt><titlePage></tt>] should include the verso if present, divided by <tt><pb n="verso"/></tt>.

* Frontispieces should be encoded as a <tt><figure></tt>, within a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project) and <tt><p></tt>.

* Tables of contents, errata, subscription lists, “other titles by the same author” should be included in a separate division (numbered or unnumbered, depending on the general editorial decision for a specific encoding project), as a [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt><list></tt>] with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s.

*It is recommended that all prefaces, tables of contents, afterwords, appendices, endnotes, and apparatus be encoded with phrase-level elements.

*For publishers’ advertisements, indexes, and glossaries, or other front or back matter that are not considered of primary importance to the text, there are three options:
**Fully transcribe and encode. For an index, use <tt>type="index"</tt> on the <tt><div></tt>, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX <tt><list></tt>s] to mark up index entries. Use <tt><ref target="____"></tt> to mark up page numbers given in the index, with the value of <tt>target</tt> referring to the <tt>xml:id</tt> attribute of the <tt><pb></tt> of the referenced page.
**Link to page images (may omit encoded transcription)
**Fully omit and note the omission in [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-samplingDecl.html <tt><samplingDecl></tt>]

=====Level 4 Name Tagging=====

* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSnr Chapter 13.1.1, Linking Names and Their Referents]

Names should be encoded using <tt>persName</tt>, <tt>placeName</tt>, <tt>geogName</tt>, and <tt>orgName</tt> elements with the <tt>ref</tt> or <tt>key</tt> attribute providing a reference to a <tt>person</tt>, <tt>place</tt>, or <tt>org</tt> element in an external file or database for managing name normalization and compilation of additional information such as biographical or geospatial information. See the [[#key_and_ref|discussion of <tt>ref</tt> and <tt>key</tt>]] above for how to choose between them.

If using <tt>key</tt>, provide a unique internal identifier, such as in a local database.

If using <tt>ref</tt>, an external TEI file may contain an entry for each name, grouped accordingly under <tt><listPerson></tt>, <tt><listPlace></tt>, and <tt><listOrg></tt>, which is uniquely identified with an <tt>xml:id</tt> attribute. In such a case the value of the <tt>ref</tt> attribute in the main TEI document (the transcription of the source document) references the value of the <tt>xml:id</tt> attribute in the external file. (In the examples below, the external file is named <tt>context.xml</tt> for “contextual information” and is in the same directory as the source file, but it may be named anything and placed anywhere that can be referenced by a URI.)

When referencing external files or databases, it is strongly recommended to provide an explanation in the <tt><editorialDecl></tt> section of the TEI header. References to controlled vocabularies and national or local authority files may be signified by a prefix in the <tt>xml:id</tt> attribute (e.g., <tt>tgn_0000000</tt> for the ''Getty Thesaurus of Geographic Names''). When referencing a controlled vocabulary be sure to specify this information in the <tt><classDecl></tt> section of the TEI header.

* Place-name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>The first Jews arrived in <placeName ref="context.xml#tgn_7012924">Indianapolis</placeName> in
the middle of the 19th century. Primarily immigrants from <placeName ref="context.xml#tgn_7000084"
> Germany</placeName> and other points in central Europe (though many had lived elsewhere in the
<placeName ref="context.xml#tgn_7012149">United States</placeName> before they arrived in the
city), they were drawn from throughout the Midwest by the growth of commerce and rail lines in
<placeName ref="context.xml#tgn_7012924">Indianapolis</placeName>. </p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining place name normalization and additional information:
<pre>
<listPlace>
<place xml:id="tgn_7012924">
<placeName>
<settlement type="city">Indianapolis</settlement>
<region type="state">Indiana</region>
</placeName>
</place>
<place xml:id="tgn_7000084">
<placeName>
<country xml:lang="de">Deutschland</country>
</placeName>
</place>
<place xml:id="tgn_7012149">
<placeName>
<country>United States</country>
</placeName>
</place>
</listPlace>
</pre>

* Personal and organizational name tagging example in main TEI document (the transcription of the source document):
<pre>
<p>PRIZE LIBRARY GIFT-Indiana University President <persName ref="context.xml#lcnaf_82134365"
>Elvis J. Stahr</persName> (right), a former law dean and practicing attorney, reminisces with
Professor of Law <persName ref="context.xml#lcnaf_00113347">W. Howard Mann</persName> as the two
inspect some of the nearly 3,000 volumes of <orgName ref="context.xml#lcnaf_79006848">U.S.
Supreme Court</orgName> records recently transferred to I.U. from the <orgName
ref="context.xml#lcnaf_79109178">Indiana Supreme Court Library</orgName>. The collection,
dating back to 1925, is one of the oldest and most complete sets in existence.</p>
</pre>

* In the external file <tt>context.xml</tt>, for maintaining personal and organization name normalization and additional information:
<pre>
<listPerson>
<person xml:id="lcnaf_82134365">
<persName>
<surname>Stahr</surname>
<forename type="first">Elvis</forename>
<forename type="middle">J.</forename>
</persName>
<birth when="1916"/>
</person>
<person xml:id="lcnaf_00113347">
<persName>
<surname>Mann</surname>
<forename type="first">W.</forename>
<forename type="middle">Howard</forename>
</persName>
</person>
</listPerson>

<listOrg>
<org xml:id="lcnaf_79006848">
<orgName>United States. Supreme Court</orgName>
</org>
<org xml:id="lcnaf_79109178">
<orgName>Indiana. Supreme Court</orgName>
</org>
</listOrg>
</pre>

* Alternatively, instead of using an external file for the authority data, use the <tt>key</tt> attribute to point to a unique key in a MySQL table that stores information like county name, FIPS county code, and latitude/longitude values:

<pre>
<p>When Harry Byrd "retired" to his orchards and Rosemont, his new house outside
<placeName key="1498453">Berryville</placeName> in 1930, he was still an energetic
young man with a long political career ahead of him.</p>
</pre>

=====Level 4 Figures=====

<tt><figure></tt> groups elements representing or containing graphic information such as an illustration or figure; in this context <tt><figure></tt> typically contains the following elements:

* <tt><head></tt>, containing a literal transcription of a caption on a figurative image.

* <tt><figDesc></tt>, containing a free text description of the image used, potentially, for searching the images themselves.

* <tt><graphic></tt>, pointing to the URI of the image itself using a <tt>url</tt> attribute and containing other presentation instructions such as dimension at which the graphic should be displayed, etc.

An example of frontispiece encoding:
<pre>

<front>
<div type="frontispiece">
<figure>
<head>Sojourner Truth.</head>
<figDesc>Woodcut of Sojourner Truth.</figDesc>
<graphic url="http://docsouth.unc.edu/neh/truth50/frontis.html" scale="0.5"/>
</figure>
</div>
[Etc ...]
</front>
</pre>

Source: ''Narrative of Sojourner Truth, a Northern Slave, Emancipated from Bodily Servitude by the State of New York, in 1828''.

=====Level 4 Embedded Texts =====

At Level 4, texts embedded within other texts must be marked as such.

In the case of a quotation from another text, use <tt><quote></tt>, and do not include quotation marks in the content of this element or just outside the opening and closing tags. If the rendering of this quotation needs to be recorded, use the <tt>rend</tt> attribute to describe how this quotation is set off from the rest of the text.

If the embedded text is more than a short quotation, use <tt><floatingText></tt> even if only an excerpt of the embedded texts is provided. If your project uses <tt><quote></tt> to identify quotations, surround instances of floating texts which are quotations with <tt>quote</tt> tags.

Personal letters are a common example of an embedded text. While a collection of letters would use a <tt>div</tt> element for each letter, if a letter is quoted as part of a larger text, use <tt><floatingText></tt> <tt><body></tt> <tt><div1 type="letter"></tt> with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-opener.html <tt><opener></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-dateline.html <tt><dateline></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-salute.html <tt><salute></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-signed.html <tt><signed></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-closer.html <tt><closer></tt>], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-postscript.html <tt><postscript></tt>] included as appropriate. For example:

<pre>
<p>She opened and read as follows:</p>
<floatingText>
<body>
<div1 type="letter">
<opener>
<dateline>AUGUSTA, March 4th, 18—</dateline>
<salute>
<hi rend="font-style: italic">Mrs. A. Mitten:</hi>
</salute>
</opener>
<p>"Having recently understood that you have procured a private teacher, we have
ventured to stop your advertisement, <hi rend="font-style: italic">though ordered to continue it
until forbid,</hi> under the impression that you have probably forgotten to have it
stopped. If, however, we have been misinformed, we will promptly resume the
publication of it. You will find our account below; which as we are much in want of
funds, you will oblige us by settling as soon as convenient. Hoping your teacher is
all that you could desire in one,</p>
<closer>
<salute>"We remain, your ob't. serv'ts,</salute>
<signed>"H—&amp; B—”</signed>
</closer>
</div1>
</body>
</floatingText>
</pre>
Source: Augustus Baldwin Longstreet, 1790-1870. ''Master William Mitten: or, A Youth of Brilliant Talents, Who Was Ruined by Bad Luck.'' Macon, Ga.: Burke, Boykin, 1864.

=====Level 4 Drama=====

* Within the front matter (<tt><front></tt>) of a performance text, cast lists should be encoded as <tt><castList></tt>s, with each item in that list encoded as <tt><castItem></tt>s. If desired, each <tt><castItem></tt> may be uniquely identified with the <tt>xml:id</tt> attribute.

For example,

<pre>
<front>
<castList><head>Dramatis Personae</head>
<castItem xml:id="kllear">LEAR king of Britain</castItem>
<castItem xml:id="klfrance">KING OF FRANCE</castItem>
<castItem xml:id="klburgundy">DUKE OF BURGUNDY</castItem>
<castItem xml:id="klcornwall">DUKE OF CORNWALL</castItem>
<castItem xml:id="klalbany">DUKE OF ALBANY</castItem>
<castItem xml:id="klkent">EARL OF KENT</castItem>
<castItem xml:id="klgloucester">EARL OF GLOUCESTER</castItem>
<castItem xml:id="kledgar">EDGAR son to Gloucester.</castItem>
<castItem xml:id="kledmund">EDMUND bastard son to Gloucester.</castItem>
[. . .]
</castList>
</front>
</pre>

Source: Shakespeare’s ''King Lear''

*Within the body of performative texts, speeches are encoded as <tt><sp></tt> and speakers identified by the <tt>speaker</tt> element, which is a child of <tt><sp></tt>.
*Stage directions are encoded as <tt><stage></tt> and enclose content describing scenery, stage directions, etc.
*When encoding the actual speech content itself, utilize elements and attributes that correspond to the type of dramatic speech presented (e.g. <tt><p></tt> for prose speech with <tt><lb></tt> to designate a new line in a particular edition of the text or <tt><lg></tt> and <tt><l></tt> to describe dramatic verse structures).
*If referencing the <tt>xml:id</tt> defined in the <tt><castList></tt> is desired, use the <tt>who</tt> attribute for the IDREF datatype.

<pre>
<div type="act" n="1">
<head>Act 1</head>
<div type="scene" n="1">
<head>Scene 1</head>
<stage>King Lear's palace.</stage>
<stage>Enter KENT, GLOUCESTER, and EDMUND</stage>

<sp n="1">
<speaker who="klkent">KENT</speaker>
<p>I thought the king had more affected the Duke of<lb/>
Albany than Cornwall.</p>
</sp>
<sp n="2">
<speaker who="klgloucester">GLOUCESTER</speaker>
<p>It did always seem so to us: but now, in the<lb/>
division of the kingdom, it appears not which of<lb/>
the dukes he values most; for equalities are so<lb/>
weighed, that curiosity in neither can make choice<lb/>
of either's moiety.</p>
</sp>
<sp n="3">
<speaker who="klkent">KENT</speaker>
<p>Is not this your son, my lord?</p>
</sp>
[. . .]
</div>
</div>
</pre>

Source: Shakespeare’s ''King Lear''

=====Level 4 Oral History=====

Speakers in oral history interviews, i.e. interviewee(s) and interviewer(s), may be identified in the <tt><teiHeader></tt> in several ways:

* In the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-profileDesc.html <tt><profileDesc></tt>], in the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-particDesc.html <tt><particDesc></tt>], using the [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-list.html <tt>list</tt>] element, with [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html <tt><name></tt>] inside of [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-item.html <tt><item></tt>]s
* As a list of author <tt><name></tt>s within [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD2 <tt><fileDesc></tt>] / [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21 <tt><titleStmt></tt>]

In either method, use an <tt>xml:id</tt> on the <tt>name</tt> element to uniquely identify the individual participant:

* The list of an interview’s participants can be also listed within the body of the interview (see example below).
* Questions and answers from interviewees and interviewers are encoded as <tt><sp></tt>, with speakers identified within <tt>speaker</tt> elements with a <tt>who</tt> attribute the value of which corresponds to the <tt>xml:id</tt> in the list of interview participants.

<pre>
<list type="simple">
<head>Interview Participants</head>
<item>
<name xml:id="spk1" key="wf" reg="Friday, William C." type="interviewee">WILLIAM C. FRIDAY
</name>, interviewee
</item>
<item>
<name xml:id="spk2" key="wl" reg="Link, William" type="interviewer">WILLIAM LINK</name>, interviewer
</item>
</list>

[. . . ]

<sp who="spk2">
<speaker n="2">WILLIAM LINK:</speaker>
<p>Last time we were talking about Frank Porter Graham. And I have a couple of questions
about Graham, and I wonder if you could clear them up for me. You have mentioned that you
had worked with him as a student at North Carolina State, had you met him before?
</p>
</sp>
<sp who="spk1">
<speaker n="1">WILLIAM C. FRIDAY: </speaker>
<p>No. That budget hearing was the first that I knew of him, of course, but the first time
that I ever encountered him. I was president of class at N.C. State, and that through me into
this kind of public adventure. And so I went merrily on downtown and sat there in the budget
hearing, along with the president of the student body, and some others.
</p>
</sp>
</pre>

One possible way to synchronize audio and transcript has been introduced in [http://docsouth.unc.edu/sohp/ Oral Histories of the American South], using [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-milestone.html <tt><milestone></tt>] with a timestamp attribute:
<pre>
<milestone n="7248" unit="empty" type="stop" timestamp="00:08:54"/>
</pre>

=====Level 4 Verse=====

Use <tt><lg></tt> and <tt><l></tt> as in Level 3. In addition, use the <tt>rend</tt> attribute to indicate lines that are indented.

For example,
<pre>
<div type="fit" n="1">
<head>Fit the First: THE LANDING</head>

<lg type="stanza" n="1">
<l n="1.1">"Just the place for a Snark!" the Bellman cried,</l>
<l rend="margin-left: 0.5in" n="1.2">As he landed his crew with care;</l>
<l n="1.3">Supporting each man on the top of the tide</l>
<l rend="margin-left: 0.5in" n="1.4">By a finger entwined in his hair.</l>
</lg>

<lg type="stanza" n="2">
<l n="2.1">"Just the place for a Snark! I have said it twice:</l>
<l rend="margin-left: 0.5in" n="2.2">That alone should encourage the crew.</l>
<l n="2.3">Just the place for a Snark! I have said it thrice:</l>
<l rend="margin-left: 0.5in" n="2.4">What I tell you three times is true."</l>
</lg>

[ETC....]

</div>
</pre>
Source: Lewis Carroll’s ''The Hunting of the Snark''

===== Level 4 Milestones =====

Instead of using the <tt>milestone</tt> element available in TEI, use <tt><ab type="typography"></tt>. The content of this element is the character(s) or device used to mark the milestone in the source document. For example:

<pre>
<ab type="typography">*****</ab>
</pre>

===== Level 4 Alger Hiss document =====

Note that the soft hyphen character is displayed as an entity reference because it this character will not display in many web browsers.

<pre><TEI xml:id="project_document_identifier"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xml:lang="en">

</teiHeader>
<text xml:lang="en">
<body>
<div1>
<pb n="113" facs="./pageImages/AH4_0113.jpg" ed="typed"/>
<pb n="118" ed="subsequent"/>
<head>POINT VIII.</head>
<head>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S
<lb/>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,
<lb/>DISCOVERY AND A HEARING SHOULD BE ORDERED.</head>
<p>The nature and extent of surveillance of Hiss, his
<lb/>family and associates was not known at the time of trial by
<lb/>the defense. Even now, with the release of some of the govern&#xAD;
<lb/>ment documents concerning FBI investigative techniques regarding
<lb/>Hiss, the full extent of surveillance -- wiretapping, mail open&#xAD;
<lb/>ings, mail covers, physical surveillance, and other intrusive
<lb/>techniques -- is still not 'clear. Nevertheless, it is apparent
<lb/>that information gathered through the exploitation of unlawful
<lb/>wiretaps and other illegal surveillance was used at trial and
<lb/>consequently the conviction must be reversed. Alternatively,
<lb/>further discovery and a hearing is essential to a fair deter&#xAD;
<lb/>mination regarding these issues.</p>
<p>FBI surveillance of Hiss began in earnest in 1941 with
<lb/>the institution of a mail cover on his incoming correspondence
<lb/>at his home in connection with an FBI investigation of possible
<lb/>Hatch Act violations. CN Ex. 98A. Another mail cover was placed
<pb n="114" facs="./pageImages/AH_0114.jpg"/>
<pb n="119" ed="subsequent"/>
on the Hiss mail in 1945, and at the same time the FBI obtained
<lb/>toll call records from the Hiss residence Telephone for the
<lb/>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,
<lb/>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</p>
<p>In late November, 1945, FBI surveillance of the Hiss
<lb/>residence in Washington, D.C., escalated. For the third time,
<lb/>a mail cover was instituted beginning on November 28, 1945,
<lb/>which was continued at least until 1946. CN Ex. 101 at p. 70;
<lb/>CN Ex. 102. Continuous physical surveillance of Hiss was begun
<lb/>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour
<lb/>surveillance was discontinued on December 14, 1945, physical
<lb/>surveillance was conducted frequently at various times until
<lb/>September, 1947.<note place="foot" anchored="true" n="68">Also
before 1947, a letter from Priscilla Hiss addressed
<lb/>to her son, Timothy Hobson, was intercepted and its contents
<lb/>read. CN Ex. 100A at p. 167. In approximately March, 1947,
<lb/>a letter from a Michael Greenberg addressed to petitioner re&#xAD;
<lb/>garding an application for employment with the United Nations
<lb/>was also intercepted, in a manner not revealed by the docu&#xAD;
<lb/>ments. CN Ex. 100B</note> CN Ex. 102; CN Ex. 103.</p>
<p>The most intrusive invasion of petitioner's rights
<pb n="115" facs="./pageImages/AH_0115.jpg"/>
<pb n="120" ed="subsequent"/>
<lb/>occurred from December 13, 1945 until the Hisses moved from
<lb/>Washington, D.C. to New York City on September 13, 1947. A
<soCalled>technical surveillance</soCalled>, -- a wiretap -- was placed on the Hiss
<lb/>telephone at their residence on P Street-in Washington, D.C.
<lb/>The logs of this surveillance constitute twenty-nine volumes
<lb/>of FBI serials and are roughly 2,500 pages in length, in which
<lb/>an enormous amount of information concerning the Hisses' per&#xAD;
<lb/>sonal lives, relationships with friends and associates, and
<lb/>habits is recorded.</p>
<p>The wiretap was installed following FBI Director Hoover's
<lb/>application to the Attorney General for authorization,<note place="bottom" anchored="true" n="69">Hoover's
initial request was answered by a note reques&#xAD;
<lb/>ting information on Hiss. CN Ex. 104<sic> </sic>. Additional information
<lb/>was furnished by letter dated November 30, 1945. CN Ex. 105<sic> </sic>.</note>
<lb/>although no written authorization appears in the documents released to
<lb/>Hiss. The purpose of the application was to gather information
<lb/>regarding Hiss' alleged contacts with Soviet espionage agents and
<lb/>communists in government service, general allegations which had
<lb/>been made by Elizabeth Bentley and Chambers.</p>
<p>As one would expect, the interception of every telephone</p>
</div1>
</body>
</text>
</TEI></pre>

===LEVEL 5: Scholarly Encoding Projects===

Level 5 texts are those that require substantial human intervention by encoders with subject knowledge. These texts might include encodings of semantic, linguistic, prosodic, or other features well beyond the basic structural elements discussed in Levels 1-4 above. They might also include elements for editorial, critical, or analytical additions; manuscript descriptions; translations; or other textual apparatus. It is impossible to make concrete recommendations for encoding at this level since the scholarly analysis required is usually specific to each project; instead, Level 5 offers the full set of P5 elements as needed.

====Reference====
* [http://www.tei-c.org/Guidelines/P5 Complete P5 Guidelines]

====Purpose====
To create deeply analytical encoded texts that might be appropriate for specific research purposes, as part of a scholarly publishing project, or for any other encoding practices in library-based text encoding.

====Rationale====
A significant number of library-based projects engage in high-level analytical text encoding as part of their efforts in digitization, scholarly editing, academic support, or other research. Level 5 is intended to represent that work, which can take advantage of the full richness of the complete TEI Guidelines, while still acknowledging the impact of library-specific practices on encoded text that is created under the auspices of a library.

The specific influences of library practice on a Level-5 encoded text are expressed primarily in adherence to the [[#General_Recommendations|General Recommendations]] and [[#The_TEI_Header|TEI Header]] sections above.

====Element Recommendations and Examples====
Because of the vast range of possibilities for Level-5 encoding, we have chosen to provide neither a list of recommended elements nor any specific examples for this Level.

Please refer to the [[#The_TEI_Header|TEI Header]] section above for examples of <tt><TeiHeader></tt> element usage, and to the [[#General_Recommendations|General Recommendations]] section and the [http://www.tei-c.org/Guidelines/P5 Complete TEI P5 Guidelines] for element recommendations and usage examples within the <tt><text></tt> element.

==Acknowledgments==
This document is the result of a group of individuals with a range of experience with TEI text encoding, which formed together under the TEI Special Interest Group on Libraries and Digital Library Federation umbrellas. We would like to thank and acknowledge all of those who have given their time and expertise to develop these best practices.

The individuals who have contributed to the writing of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Renee McBride, University of North Carolina, Chapel Hill
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to the planning of this document are:

* Syd Bauman, Brown University
* Michelle Dalmau, Indiana University
* Matthew Gibson, University of Virginia
* Kevin Hawkins, University of Michigan
* Lisa McAulay, University of California, Los Angeles
* Chris Powell, University of Michigan
* Andrew Rouner, Washington University in St. Louis
* Melanie Schlosser, Ohio State University
* Natasha Smith, University of North Carolina, Chapel Hill
* Perry Willett, California Digital Library
* Richard Wisneski, Case Western University
* Glen Worthey, Stanford University

The individuals who have contributed to copyediting of this document are:
* Susan Lorand, University of Michigan
* Becky Welzenbach, University of Michigan

Lastly, we would like to thank the Digital Library Federation (DLF) for sponsoring two in-person meetings as part of the Spring 2008 Forum in Minneapolis, Minnesota, and the Spring 2009 Forum in Raleigh, North Carolina, in support of our revision work. The DLF also provided teleconferencing support for our regularly scheduled meetings.

==Appendix A: History of This Document==

This document was formerly known as "TEI Text Encoding in Libraries Guidelines for Best Encoding Practices".

<p>The Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (referred to as
the <i>TEI Guidelines</i>) were first published in 1994 and represent a tremendous
achievement in electronic text standards by providing a highly sophisticated structure for encoding
electronic text. Digital librarians have benefited greatly from the standardization provided by these
guidelines, and the potential for interoperability and long-term preservation of digital collections
facilitated by their wide adoption.</p>

<p>In 1998, the Digital Library Federation (DLF) sponsored the [http://www.lib.umich.edu/lit/dlps/history/teidlf/index.html TEI and XML in Digital Libraries Workshop] at the
Library of Congress to discuss the use of the <i>TEI Guidelines</i> in libraries for electronic text,
and to create a set of best practices for librarians implementing them. From this workshop, three working
groups were formed, the members of which represented some of the largest and most mature digital library
programs in the U.S.</p>

<p>Group 1 was charged to recommend some best practices for TEI header content and to review the relationship between the Text Encoding Initiative header and MARC. To this end, representatives of the University of Virginia Library and the University of Michigan Library gathered in Ann Arbor in early October 1998 to develop a recommended practice guide. This work was assisted by similar efforts that had taken place in the United Kingdom under the auspices of the Oxford Text Archive the previous year. The section on the header is based on a draft of those recommended practices. It was submitted to various constituencies for
comment. In 2008 and 2009, it was heavily revised by Melanie Schlosser, Kevin Hawkins, and other members of the TEI SIG on Libraries.</p>

<p>Group 2 was charged with developing a set of recommendations for libraries using the
TEI Guidelines in electronic text encoding. This group included the following representatives from six libraries:
</p>
<ul>
<li>LeeEllen Friedland, Library of Congress</li>
<li>Nancy Kushigian, University of California, Davis</li>
<li>Chris Powell, University of Michigan</li>
<li>David Seaman, University of Virginia</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>At the ALA Midwinter Meeting (January 1999), the DLF task force revised a draft set of best practices, called
TEI Text Encoding in Libraries: Guidelines for Best Practices (often referred to as <i>TEI in Libraries
Guidelines</i>). The revised recommendations were circulated to the conference working group in May
1999 and presented at the joint annual meeting of the Association of Computers and the Humanities and
Association of Literary and Linguistic Computing in June 1999. [http://www.diglib.org/standards/tei-old.htm Version 1.0] was circulated for comments in
August 1999. These guidelines were endorsed by the DLF, and have been used by many digital libraries,
including those of the task force members, as a model for their own local best practices. Libraries,
museums, and end-users have benefitted from a set of best practices for electronic text in a number of
ways, including better interoperability between electronic text collections, better documented practices
among digital libraries, and a starting point for discussion of best practices with commercial publishers
regarding electronic text creation.</p>

<p>Written in 1998, this first iteration of <i>TEI in Libraries Guidelines</i> made no mention of XML,
XSLT, or any of the other powerful tools that have now become common parlance and practice in creating
digital documents and collections. Based on these important changes in markup technology, it came to the
attention of the DLF and members of the original Task Force that the <i>TEI in Libraries Guidelines</i>
required substantial revision. In 2002, the TEI Consortium published a new edition of the complete
<i>TEI Guidelines</i> that conformed to XML specifications. In order to remain useful, the <i>TEI in
Libraries Guidelines</i> had to be updated to reflect these developments.</p>

<p>Furthermore, librarians need more guidance than the original <i>TEI in Libraries Guidelines</i>
provided. There are many library-specific encoding issues which need to be addressed and documented to
ensure consistency. The intention of this document is to provide recommended paths of encoding for these
issues.</p>

<p>In addition, these library guidelines have the potential to be much more useful if they can serve as a
training document from which librarians can learn about text encoding and addressing particular encoding
challenges. To fulfill this role, the guidelines require more examples and detailed explanations,
giving documentation of the use of TEI in a library context. Librarians also need a set of standards
and best practices for vendors and publishers who create electronic text for digital libraries, so that
these collections adhere to the same archival standards as locally-created electronic text collections.
With detailed guidelines that could serve as an encoding specification, librarians might encourage
vendors to follow the principles in these standards, to facilitate the long-term preservation of
commercially published electronic text collections, and more readily allow for cross-collection
searching.</p>

<p>In order to facilitate the evolution of this document, another DLF-sponsored Task Force—some
of the representatives of which were on the original Task Force—met on October 24-25, 2003 at
the Cosmos Club in Washington, D.C.: </p>
<ul>
<li>Richard Gartner, Oxford University Library</li>
<li>Matthew Gibson, University of Virginia Library</li>
<li>Kirk Hastings, California Digital Library</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, Indiana University (chair)</li>
</ul>
<p>These representatives met to revise the original <i>TEI in Libraries Guidelines</i> in order
that they: </p>
<ul>
<li>reflect changes occuring within the text encoding world generally and within the TEI
community specifically</li>
<li>further illuminate the different levels of encoding by offering clearer and more robust
examples.</li>
</ul>
<p>After producing [http://www.diglib.org/standards/tei2/tei20.htm Version 2.0] of the Guidelines, this group (with some changes in membership) met again
at the Cosmos Club on February 13-14, 2006. Those in attendance were: </p>
<ul>
<li>Syd Bauman, The TEI Consortium</li>
<li>Richard Gartner, Oxford University Library (by phone)</li>
<li>Matthew Gibson, University of Virginia (chair)</li>
<li>Chris Powell, University of Michigan</li>
<li>Merrilee Proffitt, RLG</li>
<li>David Seaman, Digital Library Federation</li>
<li>Natasha Smith, University of North Carolina, Chapel Hill</li>
<li>Perry Willett, University of Michigan</li>
</ul>

= Appendix B: Formal Specification =

(This section will be generated automatically once ODDs are created.)

[[Category:SIG:Libraries]]

Talk:Best Practices for TEI in Libraries

2009-06-18T17:40:28Z

RebeccaWelzenbach:

Talk:Best Practices for TEI in Libraries

2009-06-18T17:38:30Z

RebeccaWelzenbach:

== '''Introduction:''' ==

1) "If a library uses TEI Tite to outsource its encoding, it should find conversion of TEI Tite files to be trivial: to Level 3 with some loss of granularity and to Level 4 with the addition of some markup, which amounts to minimal human intervention."

Should the colon after "trivial" be there?

2) Definition of level 5 encoding currently reads:

"The text is generated either through corrected OCR or keyboarding, but the tagging requires substantial human intervention by encoders with subject knowledge. "

I suggest instead:

"The text is generated either through corrected OCR or keyboarding, '''and''' the tagging requires substantial human intervention by encoders with subject knowledge, "

because corrected OCR, keyboarding, and expert tagging ALL require substantial human intervention (though the first two, of course, don't require subject knowledge, and perhaps that is the point of the original phrasing)