- ab
- abbr
- acquisition
- add
- additional
- additions
- antiphon
- app
- bibl
- binding
- bindingDesc
- catDesc
- category
- cb
- Certainty
- change
- choice
- cit
- citedRange
- collation
- collection
- colophon
- condition
- country
- creation
- custEvent
- date
- decoDesc
- decoNote
- del
- depth
- desc
- dim
- dimensions
- div
- editor
- ex
- expan
- explicit
- facsimile
- faith
- filiation
- foliation
- foreign
- gap
- geo
- graphic
- keywords
- handDesc
- handNote
- handShift
- height
- hi
- history
- idno
- incipit
- item
- l
- language
- layout
- layoutDesc
- lb
- lem
- list
- listApp
- listBibl
- listPerson
- listRelation
- listWit
- locus
- material
- measure
- msContents
- msDesc
- msIdentifier
- msItem
- msFrag
- msPart
- nationality
- notatedMusic
- note
- objectDesc
- occupation
- orig
- origDate
- origin
- origPlace
- p
- pb
- persName
- person
- personGrp
- physDesc
- place
- placeName
- provenance
- ptr
- q
- quote
- rdg
- ref
- region
- relation
- repository
- roleName
- rubric
- seal
- sealDesc
- seg
- settlement
- signatures
- source
- space
- subst
- summary
- supportDesc
- supplied
- surrogates
- TEI
- term
- textLang
- title
- unclear
- watermark
- width
- witness
- active
- ana
- assertedValue
- atLeast
- atMost
- cRef
- calendar
- cause
- cert
- color
- columns
- contemporary
- corresp
- defective
- dur
- evidence
- facs
- form
- from
- hand
- href
- ident
- key
- n
- name
- new
- notAfter
- notAfter-custom
- notBefore
- notBefore-custom
- part
- passive
- pastedown
- place
- reason
- ref
- rend
- rendition
- resp
- role
- sameAs
- script
- source
- subtype
- target
- to
- type
- unit
- url
- value
- when
- when-custom
- who
- wit
- writtenLines
- xml:base
- xml:id
- xml:lang
- @source
- Additional
- Additions and Varia
- Aligning transliteration and morphological annotations with Alpheios Alignment Tool
- Art Themes
- Attribution of single statements
- Authority files (keywords)
- Bibliographic References
- Binding Description
- Canonicalized TEI
- Catalogue Workflow
- Collation
- Colophons, Titles and Supplications
- Contributing sets of images to the research environment
- Contributing to the research environment
- Corpora
- Create New Entry
- Create a new file, delete existing, deal with doublets
- Critical Apparatus
- Critical Edition Workflow
- Dates
- Decoration Description
- Definition of Works, Textparts and Narrative Units
- Documentary Texts
- Dubious spelling
- Editing the Schema
- Editing these Guidelines
- Editions in Work Records
- Entities ID structure
- Event
- Figures and Links to Images
- General
- General Structure of Work Records
- Groups
- Hands Description
- History
- Identifiers Structure
- Images
- Images of Manuscripts for editions
- Inscriptions
- Keywords
- La Syntaxe du Codex
- Language
- Layout
- Letters
- Linking from Wikidata to the research environment
- Manuscript Contents
- Manuscript Description
- Manuscript Physical Description
- Manuscripts
- Named Entities
- Narrative Units
- Object Description
- Person
- Place or Repository
- Places
- References
- References to a text and its structure
- Referencing parts of the manuscript
- Relations
- Relative Location
- Repositories
- Revisions
- Roles and roleNames
- Scrolls
- Seals Description
- Setup
- Some useful how-to for personal workspace set up
- Spaces
- Stand-off annotations with Hypothes.is
- Standardisation of transcription from Encyclopaedia Aethiopica
- State and Certainty
- Statements about persons
- Structure
- Summary on the Use of @ref and @corresp
- TEI
- Taxonomy
- Team IDs
- Text Encoding
- Training Materials
- Transcriptions with Transkribus
- Transformation
- Transliteration Principles
- Users
- Using Xinclude
- Validation process
- Workflow
- Works
- Works Description
- Zotero Bibliography Guidelines
- titleStmt of Manuscript Records
Roles and roleNames
Mark up of the text
persons with a role
The titles of persons, such as ʾabbā, wayzaro, makʷannǝn etc.,
should be encoded with
<roleName type="title">
↗ at
the place in the texts where they occur. To be reasonably
retrievable, <roleName>
↗ always has to
be encoded within <persName>
↗. However, because <roleName>
↗ can also be used alone, you will have to be careful, the schema cannot help here.
So, when encoding names of persons, which might include the name of a role they have covered,
use of <roleName>
↗ inside <persName>
↗ to encode the role associated with that person in that text.
It is not necessary to mark up <roleName>
↗s in descriptive text added by us: What interests us are the actual attestations of role names in Ethiopic texts.
an office or role as such
There are also names of offices, where no exact person is indicated, as in the Edict of King Galāwdewos:
<ab>ወለተሳየጦሂ፡ እምደቂቀ፡ ዐረብ፡ እንዘ፡ የአምር፡ ከመ፡ ውእቱ፡ ክርስቲያናዊ፡ ይንሥእዎ፡
ኵሎ፡ ንዋዮ። ኵሉ፡ <roleName type="office">አዛዢ።</roleName>
አው፡ <roleName type="office">ፈታሕት፡</roleName> አው፡ <roleName type="office">መኮንን፡</roleName> አው፡
<roleName type="office">ስዩመ፡</roleName> ሀገረ፡ ዘኢይፈትሕ፡ በዘ፡ አዘዝነ፡ ቦቱ፡
ይትቀተል፡ ዘእንበለ፡ ምሕረት፡ ወይትበርበር፡ ኵሉ፡ ንዋዩ፡ ወይኩን፡ ውጉዘ፡ በአፈ፡
አብ፡ ወወልድ፡ ወመንፈስ፡ ቅዱስ፡ ወበአፈ፡ ኵሎሙ፡ አበው፡ ዘተወክፈቶሙ፡ ቤተ ክርስቲያን። </ab>
Example 1
<roleName>
↗ alone to encode the name of the office.
If looking at an unidentified officer named only via his role in a text, also use
a <roleName>
↗ alone. The visualization should pull up a
list of parallel marked-up texts and might help you to identify the
person and consequently mark it up.
You can use <roleName>
↗ also in other places in the encoding,
like in titles or notes or paragraphs, especially if you think that it would be
relevant. For example, in the
following manuscript
description, we know the title of a work about some offices,
of which we have no transcription.
<msItem xml:id="ms_i1.3.1">
<title type="complete">
Two statutes on the
<roleName type="office">bǝḥtwaddad</roleName>
and the
<roleName type="office">blātten getā</roleName>
</title>
<textLang mainLang="gez"></textLang>
</msItem>
Example 2
roleName and role
The
name of the person can be typed in the
<persName>
↗, or, if avoiding typing it
is preferable, the <persName>
↗ element
with the same ID can be repeated immediately after the first
<persName>
↗ which contains
<roleName>
↗. The following examples contain marked-up <roleName>
↗s in descriptive text for illustrative purposes, where it would not be necessary to mark the <roleName>
↗ up.
It lists the books belonging to <persName ref="PRS10796Tasfo"><roleName type="title">ʾabbā</roleName></persName><persName ref="PRS10796Tasfo"></persName>
Example 3
and
It lists the books belonging to <persName ref="PRS10796Tasfo"><roleName type="title">ʾabbā</roleName> Tasfo</persName>
Example 4
will both be visualized as: It lists the books belonging to ʾabbā Tasfo.
Therefore, if only the title encoded should be visualized (without the name of the person it refers to), it should be marked up in the following way:
he was also appointed as <persName ref="PRS5309hesanMo"><roleName type="title">qāla nǝguś</roleName></persName> of King <persName ref="PRS2334BaedaM">Baʾǝda Māryām I</persName>
Example 5
The use of <roleName>
↗ has to be
separated from the use of @role
. The first is used to mark
up a concrete title mentioned in a text, the second specifies the
role the person has regarding the record in which it is
mentioned. This applies for instance to scribes or owners of
manuscripts.
If possible, persNames should take a
@role
where relevant in the description,
and then don't need to be listed again in
<listPers>
↗:
<item xml:id="e1">
<locus target="#60v #143r #144r #152v #167v #171r #173r #189v #192r #234r #255r"></locus>
<desc>The names of the owner <persName role="owner" ref="PRS11297ZenaG"></persName> and his wife <persName ref="PRS11298SeyonM"></persName> are mentioned several times.</desc>
</item>
Example 6
If there is no sensible place within the description, then the
information on the role can also be encoded in
<listPers>
↗ in
<particDesc>
↗.
Use in person records
Here you would encode known roles covered by a person, without further specification. The actual attestations of the person with that or other roles will be picked up in the visualization.
Please see the page about persons under the section "Roles".
This page is referred to in the following pages
Revisions of this page
- Pietro Maria Liuzzo on 2018-04-30: first version of guidelines from Wiki
- Dorothea Reule on 2018-05-18: Split dates