About chronoreferencing the MBM monasteries' data (v. 2.0)

T. Matthew Ciolek

Document created: 12 Dec 2012; Last updated: 21 Dec 2012

Corrections & addenda to this document were kindly provided by:

  • Ms Gita Gunatilleke, Librarianship and Technology Reviews, Wellington, New Zealand / Colombo, Sri Lanka.

0. Previous MBM's chronoreferencing schemes

  • This document replaces an earlier scheme, which has been in use from late Sep 2012 to early Dec 2012. In the superseded scheme five chronological periods of 20 year duration each were distinguished and tagged for each century.
  • That system was working well for monastic institutions with relatively short history. However, it also has been generating fifty or more tags in case of monasteries that have been in existence before and after the 200 AD and 1200 AD reference dates. The sheer volume of the chrono-tags for such monasteries was often such that it exceed the wikidot's limits for the number characters than can be legitimately stored in the bottom tag line of a data page.

1. Objectives of the MBM's chronoreferencing

  • The MBM project aims to annotate with chrono-tags all catalogued by it Buddhist monasteries that have been known to operate at any time during the 1,000 years long period between 200 AD and 1200 AD.
  • These chrono-tags tags need to be short, unambiguous and informative.
  • The chrono-tags shall refer not to a specific date, or to the overall period/duration/stretch of time between the Start and End date, but - instead- to a consecutive series of approx. 33 years-long sequences of time during which a given monstery was known/assumed (on the basis of the available data) to operate.
  • The approximately 33-years intervals provide rough and reasonably useful anchors in time. The interval is sufficiently general so that the MBM project is not burdened by an oversupply of chronological tags. For example, an attempt to mark all five periods of twenty years' duration within each century would generate for the MBM project no less than 50 tags. Morever, each of these tags may have two distinct variants (i.e. Confirmed vs. Probable period - see the paragraph below that deals with the question of suffixes). Thus, a notation system that flags only three periods of 33 years each (in fact, 33, 34 and 33 years long), for each of the ten centuries (= a maximum of 3x10x2 tags or 60) seems to be a reasonable compromise between indifference, precision and prolixity.
  • These chronoreferencing tags annotate all data pages. Pages with any chronological data found to be missing are suitably tagged.
  • The chrono-tags enable a researcher to ask the MBM wiki to display a list of all monasteries that have been known to be contemporary with one another, i.e. known to operate during the same 33 years-long period, say between 333 and 366 AD, or 1100 and 1132 AD.

2. The preferred format for the MBM chrono-tags

  • Possibility 1 - an Extra Long format HCDY-HCDY = Hundreds-of-centuries, Century, Decade, Year, Hyphen, Hundreds-of-centuries, Century, Decade, Year - eg. 0800-0832 (= a 33 years long period from 800 AD till 832 AD).
  • Possibility 2 - a Long format HCDY-DY - eg. 0800-32 (= a 33 years long period from 800 AD till 832 AD).
  • Possibility 3 - a Short format HCDY - eg. 0800 or 0867 (= tags with implied a 33 years long period from 800 AD till 832 AD, or from 867 AD till 899 AD, respectively).
  • Upon consideration, the author of the scheme - T. Matthew Ciolek - believes that the long format (i.e. the Possibiity 2) for chrono-tags is preferred for use by the MBM project. It is shorter than the extra long scheme, and more explicit than the short scheme. The value of its informativeness-at-a-quick-glance outweights the cost of its length (7 chars vs. 4).
  • All these chrono-tags need to be additionally enhanced with one of the following suffixes:

3. Suffixes for individual chrono-tags

"c" for Confirmed use of a given monastery (= a specific year within the 33 year period is known), e.g. code = 0232-66c
"p" for Probable use of the monastery in question (= the dating is uncertain/approximate only), e.g. code = 0267-99p

Sudden and gradual periods:

  • Sudden late dates (say, in the case of destruction of a given monastic institution) are indicated with a single 33 years-long period and marked "c"
  • Gradual (fuzzy) late dates (say, in the case of abandonment of a given monastic institution), are indicated with two 33 years-long periods, all marked "p". Example: the Anuradhapura monasteries in Sri Lanka were gradually abandoned from 1070 A.D. onwards when for strategic reasons the capital (together with its civilian population and monks) has shifted from Anuradhapura to Polonnaruva - Kulatunga (1999:3-4). Thus the relevant tags here would be "1067-99p 1100-32p".

Approximate periods:

  • When the data refer to the entire century (e.g. "a place X was established in 5th century AD") - use the key chrono-tag at the mid point of such a century, e.g. "0433-66" and add the "p" suffix. Thus, "0433-66p".
  • References are given to the early part of century (e.g. "the place X was established in early 7th century AD") - start the key chrono-tag at the 00s point, e.g. use the code, say "0600-32" and add the "p" suffix. Thus, the complete code will read "0600-32p".
  • References are given to the late part of century (e.g. (e.g. "the place X was established in late 7th century AD") - start the key chrono-tag at the 67s point, e.g. use the code, say "0667-99" and add the "p" suffix. Thus, the complete code will read "0667-99p".
  • Finally, for all such early, intermediate and late dates, use the key tagged period itself, together with one preceding period and one following period, both marked "p". In other words, for the "century" dates, use 3 tags, all marked "p". For any other preceding and subsequent periods (if applicable) use tags that are marked "c".

Very early OR very late periods:

  • Do not add any c/p suffixes to the chrono-tags marking periods that are earlier than 200 AD or later than 1200 AD. Thus, the appropriate tags are <=0200 & 1200=>, respectively.

4. The suggested MBM chrono-tags

  • The recommended duodecadal codes used to annotate the chronological dimension of events are:

Earlier time periods
Use the unsuffixed tag:
<=0200

3rd century AD/CE
for the years 0200 AD/CE till 0232 AD/CE use the tag 0200-32c
for the years 0233 AD/CE till 0266 AD/CE use the tag 0233-66c
for the years 0267 AD/CE till 0299 AD/CE use the tag 0267-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0200-32c 0233-66c 0267-99c

4th century AD/CE
for the years 0300 AD/CE till 0332 AD/CE use the tag 0300-32c
for the years 0333 AD/CE till 0366 AD/CE use the tag 0333-66c
for the years 0367 AD/CE till 0399 AD/CE use the tag 0367-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0300-32c 0333-66c 0367-99c

5th century AD/CE
for the years 0400 AD/CE till 0432 AD/CE use the tag 0400-32c
for the years 0433 AD/CE till 0466 AD/CE use the tag 0433-66c
for the years 0467 AD/CE till 0499 AD/CE use the tag 0467-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0400-32c 0433-66c 0467-99c

6th century AD/CE
for the years 0500 AD/CE till 0532 AD/CE use the tag 0500-32c
for the years 0533 AD/CE till 0566 AD/CE use the tag 0533-66c
for the years 0567 AD/CE till 0599 AD/CE use the tag 0567-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0500-32c 0533-66c 0567-99c

7th century AD/CE
for the years 0600 AD/CE till 0632 AD/CE use the tag 0600-32c
for the years 0633 AD/CE till 0666 AD/CE use the tag 0633-66c
for the years 0667 AD/CE till 0699 AD/CE use the tag 0667-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0600-32c 0633-66c 0667-99c

8th century AD/CE
for the years 0700 AD/CE till 0732 AD/CE use the tag 0700-32c
for the years 0733 AD/CE till 0766 AD/CE use the tag 0733-66c
for the years 0767 AD/CE till 0799 AD/CE use the tag 0767-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0700-32c 0733-66c 0767-99c

9th century AD/CE
for the years 0800 AD/CE till 0832 AD/CE use the tag 0800-32c
for the years 0833 AD/CE till 0866 AD/CE use the tag 0833-66c
for the years 0867 AD/CE till 0899 AD/CE use the tag 0867-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0800-32c 0833-66c 0867-99c

10th century AD/CE
for the years 0900 AD/CE till 0932 AD/CE use the tag 0900-32c
for the years 0933 AD/CE till 0966 AD/CE use the tag 0933-66c
for the years 0967 AD/CE till 0999 AD/CE use the tag 0967-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 0900-32c 0933-66c 0967-99c

11th century AD/CE
for the years 1000 AD/CE till 1032 AD/CE use the tag 1000-32c
for the years 1033 AD/CE till 1066 AD/CE use the tag 1033-66c
for the years 1067 AD/CE till 1099 AD/CE use the tag 1067-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 1000-32c 1033-66c 1067-99c

12th century AD/CE
for the years 1100 AD/CE till 1132 AD/CE use the tag 1100-32c
for the years 1133 AD/CE till 1166 AD/CE use the tag 1133-66c
for the years 1167 AD/CE till 1199 AD/CE use the tag 1167-99c
"C" tags for the century with confirmed existence of a given monastery. Replace the suffix "c" with "p" to indicate probable dates.

Range: 1100-32c 1133-66c 1167-99c

Later time periods
Use the unsuffixed tag:
1200=>

  • Therefore, the complete list of tri-decadal chrono-tags for the millennium long period between 200 AD and 1200 AD is as follows:

0200-32c 0233-66c 0267-99c 0300-32c 0333-66c 0367-99c 0400-32c 0433-66c 0467-99c 0500-32c 0533-66c 0567-99c 0600-32c 0633-66c 0667-99c 0700-32c 0733-66c 0767-99c 0800-32c 0833-66c 0867-99c 0900-32c 0933-66c 0967-99c 1000-32c 1033-66c 1067-99c 1100-32c 1133-66c 1167-99c

5. Types of dates

  • A page with data about monastery may have information about one of the following dates:
  • EARLY date - a date, which - in the light of available information - is as close as possible to the time a given monastery has been established.
  • INTERMEDIATE date - self-explanatory.
  • LATE date - a date, which - in the light of available information - is as close as possible to the time a given monastery has ceased to exist. Such a terminal event can be linked to a disaster (e.g. accidental fire, earthquake) or abandonment (sudden or gradual) or, most commonly, deliberate destruction by enemy troops or pillagers.

6. Practicalities of the allocation of chrono-tags to the monastic data pages

  • 1. Invoke a tag "untimed" to identify pages which still require the MBM editor's attention and chrono-tagging
  • 2. For each "untimed" page with data on a monastery determine the monastery's chronological parameters and then follow the instructions given in the Table below:
SCENARIO Situation Data page tagging Bottom line tagging
0. No time-pegs no dates are given no chrono-tags, nor suffixes to be allocated use the bottom tag: "undated"
1a. One time-peg only an "early" date is given (1) mark the "early date" 33 yrs period with the relevant chrono-tag and add "c" or "p" suffix, as appropriate; (2) mark the next 33 years with the relevant chrono-tag, apply the "p" suffix. use the bottom tag: "dated-e" (= dated using early date);
1b. One time-peg only an "intermediate" date is given (1) mark the "intermediate date" 33 yrs period with the relevant chrono-tag and add "c" or "p" suffix, as appropriate; (2) mark the previous 33 years with the relevant chrono-tags, apply the "p" suffix; (3) mark the next 33 years with the relevant chrono-tag, apply the "p" suffix) use the bottom tag: "dated-x" (= dated using an intermediate date)
1c. One time-peg only a "late" date is given (1) mark the "late date" 33 yrs period with the relevant chrono-tag and add "c" or "p" suffix, as appropriate; (2) mark the previous 33 years with the relevant chrono-tag, apply the "p" suffix use the bottom tag: "dated-l" (= dated using the late date)
2a. Two time-pegs both the "early" & "late" dates are given (1) mark the early and late dates with "c" or "p" suffixes, as appropriate; (2) mark the balance of the period between and including the "early" and "late" dates with the relevant chrono-tags, apply "c" suffixes use the bottom tag: "dated-el" (= dated using early & late dates)
2b. Two time-pegs only the "early" & "intermediate" dates are given (1) mark the early and intermediate dates with "c" or "p" suffixes, as appropriate; (2) mark the balance of period between these two dates with the relevant chrono-tags, apply "c" or "p" suffixes, as appropriate; (3) mark the next 33 years following the "intermediate" date with the relevant chrono-tag and apply the "p" suffix use the bottom tag: "dated-ex" (= dated using early and intermediate dates)
2c. Two time-pegs only the "intermediate" & "late" dates are given (1) mark the intermediate and late dates with "c" or "p" suffixes, as appropriate; (2) mark the balance of the period between the "intermediate" and "late" dates with the relevant chrono-tags & apply "c" suffixes; (2) mark the 33 years preceding the "intermediate" date with the relevant chrono-tag & apply the "p" suffix use the bottom tag: "dated-xl" (= dated using the intermediate and late dates)
2d. Two time-pegs Two "intermediate" dates are given (1) mark the first intermediate date with "c" or "p" suffixes, as appropriate; (2) mark the 33 years preceding the first "intermediate" date with the relevant chrono-tag & apply the "p" suffix; (3) mark the second intermediate date with "c" or "p" suffixes, as appropriate; (4) mark the 33 years following the end "intermediate" date with the relevant chrono-tag & apply the "p" suffix use the bottom tag: "dated-xx" (= dated using the two intermediate dates)
3. Three time-pegs the "early", "intermediate" & "late" dates are given (1) mark the early and late dates with "c" or "p" suffixes, as appropriate; (2) mark the balance of the period between and including the "early" and "late" dates with the relevant chrono-tags, apply "c" suffixes use the bottom tag: "dated-el" (= dated using early and late dates)
  • 3. All chrono-tags need to observe the following format:

The "chrono-tag with the suffix - editor/name date" (dd Mmm YYYY)
for instance:

  • MBM chrono-tag: 0933-66p - tmciolek 27 Oct 2012
  • 4. See, for example, tags given to Jokhang monastery, (in) Lhasa, Xizang, CN. Note that the site is known to be established circa 650 AD, and it was still in use in 2012:

Date-early

  • MBM chrono-tag 0633-66c - tmciolek 12 Dec 2012

0633-66c 0667-99c 0700-32c 0733-66c 0767-99c 0800-32c 0833-66c 0867-99c 0900-32c 0933-66c 0967-99c 1000-32c 1033-66c 1067-99c 1100-32c 1133-66c 1167-99c 1200=> dated-el
Date-late

  • MBM chrono-tag 1200=> - tmciolek 26 Oct 2012

7. Practicalities of the allocation of chrono-tags to the bottom tag line of monastic data pages

  • 1. In late Sep 2012 all data pages were tagged with a keyword "untimed". This was to mark the pages as documents ready for inspection and chrono-tagging.
  • 2. Following the determination of each monastery's temporal boundaries the "untimed" tag for a given monastery's page is changed as indicated in the "Bottom line tagging" column of the table above.

end of page

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-NonCommercial-NoDerivs 3.0 License