att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.3.6 Dates and Times]
Módulonamesdates — Names, Dates, People, and Places
Miembrosatt.datable [acquisition affiliation age application binding birth bloc change climate country creation custEvent date death district education event faith floruit geogFeat geogName idno langKnowledge langKnown licence location name nationality occupation offset orgName origDate origPlace origin persName placeName population precision provenance region relation residence resp seal settlement sex socecStatus stamp state terrain time title trait]
AtributosAtributos
when-customsupplies the value of a date or time in some custom standard form.
Estado Opcional
Tipo de datos 1–∞ apariciones de teidata.word separado por espacio en blanco

The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system

<p>Alhazen died in Cairo on the
<date when="1040-03-06"
  when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH
 </date>.</p>
<p>The current world will end at the
<date when="2012-12-21"
  when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p>
<p>The Battle of Meggidu
(<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p>
<p>Esidorus bixit in pace annos LXX plus minus sub
<date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date>
</p>

Not all custom date formulations will have Gregorian equivalents.

The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.

notBefore-customspecifies the earliest possible date for the event in some custom standard form.
Estado Opcional
Tipo de datos 1–∞ apariciones de teidata.word separado por espacio en blanco
notAfter-customspecifies the latest possible date for the event in some custom standard form.
Estado Opcional
Tipo de datos 1–∞ apariciones de teidata.word separado por espacio en blanco
from-customindicates the starting point of the period in some custom standard form.
Estado Opcional
Tipo de datos 1–∞ apariciones de teidata.word separado por espacio en blanco
<event xml:id="FIRE1"
 datingMethod="#julian" from-custom="1666-09-02"
 to-custom="1666-09-05">
 <head>The Great Fire of London</head>
 <p>The Great Fire of London burned through a large part
   of the city of London.</p>
</event>
to-customindicates the ending point of the period in some custom standard form.
Estado Opcional
Tipo de datos 1–∞ apariciones de teidata.word separado por espacio en blanco
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
Estado Opcional
Tipo de datos teidata.pointer
datingMethodsupplies a pointer to a calendar element or other means of interpreting the values of the custom dating attributes.
Estado Opcional
Tipo de datos teidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne
eſtate, and deſcription of that Citie, written in the yeare
<date when-custom="1598" calendar="#julian"
 datingMethod="#julian">1598</date>. by Iohn Stow
Citizen of London.

In this example, the calendar attribute points to a calendar element for the Julian calendar, specifying that the text content of the date element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.

<date when="1382-06-28"
 when-custom="6890-06-20" datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
</date>

In this example, a date is given in a Mediaeval text measured "from the creation of the world", which is normalised (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.