README Oracc Home SEARCH DOCUMENTATION

Creative Commons License

ORACC Home


Introduction


ATF in CDLI and Oracc


Oracc Documentation


C-ATF Main Points


Examples in C-ATF

Example 1

Example 2


Resources

CDLI ATF Primer

Steve Tinney
Version of 2014-07-14

Introduction

If you are preparing texts for insertion directly into the CDLI repository you should read this document first.

ATF in CDLI and Oracc

Before learning any ATF it is useful to know a little about the history and current state of ATF. ATF was developed for use in CDLI, and was first defined as a relatively small specification which used only ASCII characters. Over time, two things have happened. Firstly, the range of texts encoded in ATF has grown, and ATF has grown with it. Secondly, ATF has been extended to allow Assyriologists to process legacy data more quickly and to type new texts in a format that is very close to the way things look on screen.

Because of the archival nature of the CDLI repository, we do not allow extended ATF to be used in the repository itself. Texts in Oracc's extended ATF will be converted to the archival core ATF format that we call Canonical ATF (C-ATF). Although C-ATF does not imitate the print versions of texts, C-ATF can be converted to a pretty-printed version using this webservice.

If you are typing texts to go directly into the CDLI repository you must follow the instructions in this document so that you create Canonical ATF (C-ATF) directly.

Oracc Documentation

Oracc documentation is generally written using extended ATF; when you are writing C-ATF you need to be careful to adjust the examples appropriately.

C-ATF Main Points

Examples in C-ATF

Example 1

&P100003 = AAS 015
#atf: lang sux
@tablet
@obverse
1. 1(disz) geme2 u4 1(disz)-sze3
2. ki dingir-ra-ta
3. da-da-ga
4. szu ba-ti
@reverse
1. mu ki-masz{ki} ba-hul

The various ATF features illustrated here are:

The &-line
Every text begins with an &-line giving the ID and the text's designation according to the CDLI catalog; if your text is not yet in the catalog, e-mail cdli@cdli.ucla.edu to get the ID and designation.
#atf: lang sux
You can specify the main language for the text; for Akkadian just write #atf: lang akk.
@tablet
You can specify an object type; this is normally @tablet, but others include @bulla and @envelope. If an object type which is used in the CDLI catalog is not understood by the ATF processor, you can use the exactly equivalent form @object OBJECT_TYPE, e.g., @object head.
@obverse, @reverse
You can specify the part of the object you are transliterating; the edges are given using: @left @right @top @bottom (but note that no physical surface of a tablet is to be included in C-ATF unless it, such as @left or in the case of occasional partial sums at the bottom of colums in Ur III administrative texts, assumes an explicit function in text format)
Lines of text
Lines of text are for the most part just like regular Assyriological practice. See Example 2 for how to do breakage.
Determinatives, phonetic complements and glosses

Determinatives are given in curly brackets.

Phonetic complements and glosses are marked with a + immediately after the first curly bracket; they are assumed to be in the same language as the rest of the word.

Rulings and Blank Spaces
Lines ruled on the tablet as paragraph separators, as well as empty space or space used for seal impressions, can be marked with $-lines ("dollar-lines").
Numbers
All numbers are qualified.

Example 2

&P348658 = SpTU 2, 055
#atf: lang akk
@tablet

@obverse
1.	t,up-pi _a-sza3_ ki-szub-ba#-[a ...]
2.	{i7}har-ri sza2 {d}muati? x [...]
3.	ša2 qe2-reb unu#[{ki}]
Damage and breakage

There are no half-brackets in ATF: signs which are damaged are flagged with the hash-sign (#) after the grapheme.

Signs which are completely broken away are placed in square brackets; square brackets may not occur inside a grapheme, only before or after it. The ellipsis (...) may be used to indicate that an undeterminable number of signs is missing.

Signs which cannot be identified are transliterated as x; when a number is missing the convention is to use n as in n(disz). Both within or after the parentheses further qualification of n as n(disz) is allowed.

Querying, Correction and Collation
The other flags are the query (?) which can be placed after a grapheme to indicate uncertainty of reading; the asterisk (*) which indicates a collated reading; and the exclamation mark which indicates correction. After a corrected sign, the actual sign on the tablet may optionally be given, using sign names in upper case: a! or ki!(DI).

Resources


Questions about this document may be directed to the Oracc Steering Committee (osc at oracc dot org).