- Additions and Varia
- Art Themes
- Authority files (keywords)
- Bibliographic References
- Binding Description
- Create New Entry
- Critical Apparatus
- Decoration Description
- Definition of Works, Textparts and Narrative Units
- Dubious spelling
- Editing the Schema
- Editing these Guidelines
- Editions in Work Records
- Entities ID structure
- General Structure of Work Records
- Hands Description
- Identifiers Structure
- Manuscript Contents
- Manuscript Description
- Manuscript Physical Description
- Named Entities
- Narrative Units
- Object Description
- Place or Repository
- Relative Location
- Roles and roleNames
- Seals Description
- Some useful how-to for personal workspace set up
- Stand-off annotations with Hypothes.is
- Standardisation of transcription from Encyclopaedia Aethiopica
- State and Certainty
- Statements about persons
- Summary on the Use of @ref and @corresp
- Team IDs
- Text Encoding
- Transliteration Principles
- Validation process
- Works Description
- Zotero Bibliography Guidelines
- titleStmt of Manuscript Records
The title(s) of the work are encoded in
@typewith value main to signal the title which is to be used for labels, pointers and headers.
The title which will be printed on the website will therefore be, in order of priority
<title[@type = 'main'][@corresp = '#t1']>↗
<title[@corresp = '#t1'][@xml:lang = 'am']>↗
<title[@corresp = '#t1'][@xml:lang = 'gez']>↗
<title[@corresp = '#t1'][@xml:lang = 'en']>↗
<title[@corresp = '#t1']>↗
Titles of the same work in another tradition will be reported
following the same rule and attributing an arbitrary t+digit
and the appropriate
You can also use
<title type='short'>↗ for shortened
titles like citation forms:
If a subpart of a work, which does not circulate independently in the Ethiopic
tradition, does circulate independently in other
traditions, the relevant titles and references will be added in the appropriate
<div type='textpart'>↗, not in
Please Note that we will encode AUTHORSHIP as a relation in the work record, to be more specific and explicit about the sort of authorship.
<relation name='dcterms:creator' active='LIT1608hoheta' passive='PRS4709Giyorgis'>↗
This means that the work has this author.
If a work is traditionally attributed to an author whose authorship is not currently considered to be historical, this can be expressed verbally with bibliographic references in the description of the relation, for example LIT1608hoheta:
<relation name='saws:isAttributedToAuthor' active='LIT1608hoheta' passive="PRS4709Giyorgis'>↗
<relation name='saws:isAttributedToAuthor' active='LIT1608hoheta' passive='PRS3709eleni'>↗
you can use many of this and also have different types for one work. If you come across records which use the author element, please correct them.
You might need to express concept which need more than one relation. For example if Person A is author of a translation B of a work C in arabic, you will need a relation of authorship between A and B (A isAuthorOf B) and the relation stating the fact that B is a translation of C (B isLooseTranslationOf C). If a digital edition of the translated work exists, please use that as a value in the relation. If no such edition exist you might point to the ID of the title in the language of the original.
<witness>↗ for those manuscripts
which are actually used for the
edition we are going to provide in the
<div type='edition'>↗. All
manuscript records containing the work are displayed in the app anyway.
<listWit>↗s can be nested if needed for example
to group them in families. Each
have to take a
@corresp pointing to the
@xml:id. If the manuscript is in
beta mesaheft catalogue that is enough. If the manuscript is into an
external catalogue, than use @type='external' as in
listBibl[type='mss'] in the manuscript entity. You can use
@cert to specify a degree of certainty
regarding the manuscript you are listing. Please, note that each
witness element can take a fully marked up description in relation to
As information provided by the catalogues we are working with
should not be lost, whenever a catalogue description contains
references to other manuscripts containing the same work, mini ms
records containing the work ID should be created for those
manuscripts. This assures that all the manuscripts containing the same
work can be retrieved by the app while reserving
<listWit>↗ in the work records mainly for the
manuscripts used for the edition.
Each relationship should be listed separately in a
<relation>↗, even if the same relationship exists
between this and more than one other entity.
@name contains the name of the relation.
Allowed values for relations among works and authors are those in the
Ontology and those used by syriaca.org you can filter them out
in oXygen typing syriaca: or saws: in the value list.
@active should contain the xml:id of the
@passive should contain the IDs
of the related works, people, places, separated by a space
The relationship between a work and its subject is expressed in the person record:
Edition statement, Source statement, and encoding description
These elements should be provided in the header for texts that we provide edition for. The Edition statement should specify the origin of the text. The encoding description specifies the principles used when encoding, when known (e.g. transcription, specific tag sets, etc.)
Digital text based on
Text prepared within the framework of the TraCES project.
The following errors
in Marrassini edition have been corrected:
Original spelling and typography is retained.
Extent should be specified for the works wherever possible; obligatory for works with digital text provided, after the edition statement:
Digital text based on
If you have multiple recensions/version of a text, these can be
linked with a relation with
<name='saws:isVersionOf'>↗ this will be used to
pick up these in the text view. The same parallel content in the
different versions should have the same @corresp to a NAR unit and
there should always be a @resp in the div[@type='edition'] containing
this text part with multiple versions with either the initials of the
editor or the pointer to the xml:id of the bibl element which has a
pointer to the edition.
any other date relevant to the work elaboration or life could be added in a date element, possibly pointing to one of the placeNames in the file with a proper ID as in the example below.
It is important that the ID of the referred place starts with P because there are cases where corresp is already used to point to another ID, e.g. a work in another tradition title. Look at this fictitious example, where I have entered a placeName with Q item id from wikidata (Ethiopia) and assigned the second corresp and the id with P
this sounds like a dirty hack to get it working... and it is!
Short Summary of Contents
A theological treatise believed to be a responce of king
Summaries given in catalogues can be copied here and edited.
Revisions of this page
- Dorothea Reule on 2018-04-26: editing of the Work section of the guidelines
- Pietro Maria Liuzzo on 2018-04-30: first version of guidelines from Wiki