Decorative Arch, Resafa, Syria. Copyright, Daniel Schwartz.

Syriaca.org Documentation

Archive of Deprecated Encodings

This wiki documents previous TEI encoding practices adopted by Syriaca.org which were subsequently deprecated and (hopefully!) purged from the data. These encoding rules are archived here to assist with understanding or transforming old versions of the Syriaca.org data set.

Deprecated Encodings from the TEI Encoding Manual for The Syriac Gazetteer

revisionDesc/change/@target

The <change> element was previously allowed an optional @target attribute can point to the @xml:id of the particular entry modified. A fictional <revisionDesc> for Edessa might look as follows:

<revisionDesc>
   	<change when="2013-04-15" who="http://syriaca.org/editors.xml#ngibson"
		n="1.1" target="#ng">
ADDED: Pleiades coordinates</change>
   	<change when="2013-04-01"
		 who="http://syriaca.org/editors.xml#dmichelson" target="#dam">
FIXED: Ufra to Urfa</change>
   	<change when="2013-03-16" who="http://syriaca.org/editors.xml#tcarlson"
		 n="1.0">
ADDED: teiHeader/revisionDesc</change>
   	<change when="2013-03-15" who="http://syriaca.org/editors.xml#tcarlson">
		ADDED: teiHeader</change>
   	<change when="2013-03-01" who="http://syriaca.org/editors.xml#tcarlson"
		 n="0.1">
CREATED: place</change>
</revisionDesc>

In this example, later in the document the <place> element would contain the following elements with the @xml:id attributes pointed to here:

<place>
	<!-- … -->
	<placeName xml:id="dam" xml:lang="en" source="#bib78-1">Urfa</placeName>
	<!-- … -->
	<location xml:id="ng" type="gps"
		 source="http://pleiades.stoa.org/places/658457/dare-location">
   		<geo>37.14863 38.786696</geo>
   	 </location>
	<!-- … -->
</place>

A single change which affected multiple XML elements can include space-separated pointers to multiple @xml:id attributes. For example:

<change when="2013-03-16" who="http://syriaca.org/editors.xml#tcarlson" 
		target="#tac1 #tac2 #tac3">
	FIXED: typos in <gi>title</gi> entries within <gi>bibl</gi> elements
</change>

event/label and event/desc

Previously an event could optionally be labeled using a <label> or <desc> element, this was not used and is now deprecated in favor of <p>.

<event notBefore="0079" notAfter="0116">
	<desc xml:lang="en">Changed course to run between Kokhe and
	Ctesiphon rather than between Kokhe and Seleucia</desc>
</event>

On the other hand, the council of Chalcedon ran from Oct. 8 to Nov. 1, 451, so an <event> within the <place> for Chalcedon could read as follows:

<event from="0451-10-08" to="0451-11-01">
		<desc xml:lang="en">Site of Ecumenical Council</desc>
</event>

If the event took place before the common era, a negative sign should precede the four-digit year (e.g. “-0304” for 304 BCE). For example, according to GEDSH, in 304 BCE the Macedonian general turned Mesopotamian ruler Seleucus I Nicator renamed the city of Urhoy “Edessa” after a Macedonian city of that name. This event could be encoded:

<event when="-0304" source="#bib78-1">
	<desc xml:lang="en">Renamed Edessa by Seleucus I Nicator.</desc>
</event>

Example: For name attestations, the contents of the <event> element should simply be <label>Attestation of name {placeName} in {Author}, {title-of-work}</label>. For confession attestations, the contents of the <event> element could similarly be <label>Attestation of confession {name} in {Author}, {title-of-work}</label>. Alternately the <label> element could provide more precise indication of what exactly is attested, which we are taking as evidence for a religious community. For example, <label>Attestation of Chalcedonian author in Edessa according to the Chronicle of Edessa.</label> might be linked to the confession “Melkite.” While this content is redundant and not machine-readable, it will facilitate human proofreading.