|
|
Although a great improvement over the Metonic calendar, the Julian calendar was still not quite in synchronization with the seasons. The Venerable Bede, an English scholar who lived from 673-735, noted that the vernal equinox had slipped three days earlier than the traditional March 21. The Julian calendar remained in use, however, until replaced by the Gregorian calendar in the late sixteenth century. Although the Roman abbot Dionysius Exiguus proposed that the years be numbered from the birth of Christ in about 524 (Boyer 1968, p. 272), Bede was the first to actually date events from the birth of Christ. This system gives rise to the familiar classification of dates as BC or AD (also sometimes denoted BCE and CE). Interestingly enough, probably because the concept for zero was not widely used in Europe at the time, this method of dating omits the year zero, so that the year 1 BC is followed immediately by the year 1 AD. In any case, whoever zeroed the calendar made an error, since the Bible says Jesus was alive in Herod's time, but Roman records showed that Herod died in what turns out to be 4 BC. The German astronomer Christoph Clavius (1537-1612) was the motivating force behind the needed revision of the Julian calendar. The reform brought the calendar back in synchronization with the seasons (which now occurred 11 days earlier that their traditional dates), and altered the rules under which leap years occurred. By the new rules, the years that were divisible by 400 were leap years, while other century years were not. These modifications were sufficient to match almost precisely the length of the tropical year. The reform was first adopted by Pope Gregory XIII, who decreed that the day after October 4, 1582 would be October 15, 1582. This decree was followed by the Catholic countries of France, Spain, Portugal, and Italy. Various Catholic German countries (Germany was not yet unified), Belgium, the Netherlands, and Switzerland followed suit within a year or two, and Hungary followed in 1587. Because of the Pope's decree, the reform of the Julian calendar came to be known as the Gregorian calendar. The rest of Europe did not follow suit for more than a century. The Protestant German countries adopted the Gregorian reform in 1700. By this time, the calendar trailed the seasons by twelve days. England finally followed suit in 1752, declaring that Wednesday, September 2, 1752 was immediately followed by Thursday, September 14, 1752 as shown in the below calendar. The English calendar was also used in America. English Calendar:
Sweden followed England's lead in 1753. Russia, however, did not follow suit until 1918, when January 31, 1918 was immediately followed by February 14th. In fact, Russia is not on the Gregorian calendar, but on a more accurate one of their own devising. The Russian calendar is designed to more closely approximate the true length of the tropical year, thus has one additional rule for when a year is a leap year. It will remain in synchronization with the Gregorian calendar for thousands more years, by which time one or both will have probably fallen into disuse. Similarly, Iranian calendar is also a more accurate version of the Gregorian calendar (Ross). The names of the days of the week were derived from gods, "planets," and--in some languages--metals. These name were later carried over to almost all modern European languages, though the names may sound different. In English, Wednesday is derived from a form of the Norse god Odin and Thursday from the Norse God Thor. During the French Revolution, the French invented and put into use a new French revolutionary calendar. The Revolutionary calendar was established in October 1793, but Year I was made effective on September 22, 1792 (the autumnal equinox). The Revolutionary calendar had 12 months of 30 days, plus 5 or 6 leap days (with a rule for leap years). The French Revolutionary calendar was abolished when Napoleon re-instituted the Gregorian calendar on December 31, 1805. The Julian calendar still remains in some use, since it is the basis of the system of the Julian date, devised by Clavius' contemporary Julian Scaliger (1540-1609). (In addition, some religious sects still calculate holidays based on the Julian calendar.) The name for this system, incidentally, was from Julius Scaliger, not Julius Caesar. In it, Scaliger defined Day One was as a day when three cycles converged on it. The first cycle was the 28 year period over which the Julian calendar repeats. (After 28 years, all the dates fall on the same days of the week, so you need only buy 28 calendars. Note that since the Gregorian calendar was adopted the calendar now takes 400 years to repeat.) The second was the 19 year Metonic cycle, over which phases of the moon almost land on the same dates of the year. The third cycle was the 15 year ancient Roman tax cycle. Scaliger picked January 1, 4713 BC on the Julian calendar as Day One (Seidelmann 1992, p. 55). I don't know the significance for picking this date as opposed to any other "triple convergence" date. After Julian date One, subsequent Julian dates are sequential. Therefore, midnight before January 1, 1982 is Julian Date 2,444,970.5. The modified Julian date system, defined as the Julian date minus 2,400,000.5, is also occasionally used by astronomers, but not so frequently in recent years. The Julian and Gregorian calendars differ by 13 days in the 20th and 21st Centuries. They would have been in synchronization during the 3rd Century. The following table gives the dates corresponding to January 1, 1989 in the Gregorian calendar for various other calendar systems (Astronomical Almanac).
*begins at sunset AD,
Aztec
Calendar,
Babylonian Calendar,
BC,
BCE,
Besselian
Epoch,
Chinese
Calendar, CE,
Egyptian Calendar,
French Revolutionary Calendar,
Gregorian Calendar,
Hebrew
Calendar,
Hindu
Calendar,
Iranian
Calendar,
Islamic
Calendar,
Julian
Calendar,
Julian Date,
Julian Epoch,
Mayan
Calendar,
Roman
Calendar, Time
References
Japanese EraFrom ancient times in Asia, it was the practice to count years according to the reign of an emperor. This custom of reckoning years by eras was adopted in Japan in seventh century. From that time until the nineteenth century, the reigning emperor decided when one era ended and another began. Under the current system, adopted following the ascension of Emperor Meiji in 1868, the era begins on the day an emperor ascends the throne and continues until his death. Thus Meiji era began in 1868 and lasted until 1912. Showa began in 1926 when Emperor Hirohito ascended and lasted until 1989. At present, the era is Heisei. Meiji : 1868/ 9/ 8 - 1912/ 7/30 Taisho : 1912/ 7/30 - 1926/12/25 Showa : 1926/12/25 - 1989/ 1/ 7 Heisei : 1989/ 1/ 7 - Actually, any date of the year during which era has changed, could be referred in either era. For example, 1989/1/5 could be referred as Heisei 1st 1/5 as well. Era changes at 12:00 noon so eras do not overlap in terms of hours although it does in terms of day.
A New Calendrical System Angivelse av datoen 1. januar 2000 i ulike kalendere:
The Burroughsian Calendar: This is the dream calendar of William S. Burroughs. It began on 23 Terre Haute, 1 which corresponds to Julian Day Number - 2,440,579The Poundian Calendar: This is based directly on the Gregorian calendar, merely changing the starting day and year. Designed by Ezra Pound, 1 Hephaistos, 1 psU (post scriptum Ulysses) was the day after Joyce finished writing Ulysses, thus marking the end of the Christian Era. This was also the day after Pound's 36th birthday, and corresponds to Julian Day Number - 2,422,995The Thelemic Calendar: Designed by Aleister Crowley when he received or conceived The Book of the Law and inaugurated the New Aeon of Horus, Anno 0 (Fool) : 0 (Fool) began on Julian Day Number - 2,416,560The 'Pataphysical Calendar: Designed by Alfred Jarry, Sunday, 1 Absolu, 1 EP (Ere Pataphysique or ‘Pataphysical Era) marks his birth, corresponding to Julian Day Number - 2,405,410The Bahá'í Calendar: Bahá Day of Bahá Month of Alif Year, 1 BE (Bahá'í Era) marks the first day of the year that the Bab started his ministry, corresponding to Julian Day Number - 2,394,647The French Revolutionary Calendar: Introduced in France on Tridi, 3 Brumaire, An 2, marking the beginning of the first French Republic on the Autumnal Equinox as Primidi, 1 Vendemiaire, An 1 corresponding to Julian Day Number - 2,375,840The Zodiac Calendar: I as yet have found no starting year to the cycle, if it were numbered at all.The Wiccan Calendar: I as yet have found no starting year to the cycle, if it were numbered at all.The Druidic Calendar: I as yet have found no starting year to the cycle, if it were numbered at all.The Hopi Calendar: I as yet have found no starting year to the cycle, if it were numbered at all.The Zoroastrian Calendar: Begun with the coronation of the last Zoroastrian Sasanian King, Yazdegird II, 1 Y (Yazdegird) corresponds to Julian Day Number - 1,951722The Islamic Calendar: Begun with the flight of the prophet (Hijri), 1 Muharram, 1 AH (Anno Hegirae) corresponds to Julian Day Number - 1,948,437The Jalaali Calendar: 1 farvardin, 1 corresponds to Julian Day Number - 1,948,323The Indonesian Calendar: Decreed by Sultan Agung Hanyokrokosumo in 1585, year 1 corresonds to Julian Day Number - 1,750,000This is the same year that the Hindu (civil) calendar begins on, but I don't know if it's a coincidence, because I don't know as yet what event(s) this correlates to, historical or astronomical. The Gregorian Calendar: Proposed by Aloysius Lilius, a Naples physician, and decreed by Pope Gregory XIII in February, 1582 AD in a papal bull, this merely modified the use of leap-years in the Julian calendar, with a different starting year that had been established in 523 AD (see below). To realign the Vernal Equinox with 21 March, as it had been in 325 AD the year of the First Council of Nicaea, 10 days were dropped from October, 1582 AD. 1 January, 1 AD (Anno Domino or Year of the Lord) follows shortly after the supposed date of the birth of Jesus Christ, corresponding to Julian Day Number - 1,721,424The date of Christ's birth was assumed to be 25 December, 1 BC (Before Christ) as established by Dionysius Exigus, a monk from Scythia, around 523 AD. How he calculated this is unknown, and it was disputed early on. Christ was born during the reign of King Herod, who died in 4 BC, and it is suggested the birth is actually around 7 BC. The Babylonian Calendar: Year 1 corresponds to Julian Day Number - 1,448,007The Julian Calendar: Designed by mathematician and astronomer Sosigenes, and enacted by Julius Caesar in 709 AUC to reform the old and confusing Roman calendar. 1 Januarius, 1 AUC (Ab Urbe Condita or Since the founding of Rome) corresponds to Julian Day Number - 1,446,427The Erisian Calendar: This is based directly on the Gregorian calendar, merely changing the starting year. Designed by Malclypse the Younger, Sweetmorn, 1 Chaos, 1 YOLD (Year Of Our Lady Of Discord) marks the year of the Original Snub, as explained in The Principia Discordia, corresponding to Julian Day Number - 1,289,004The Chinese Calendar: The start of this calendar was a very rare day indeed! Shortly after dawn, the sun and new moon both aligned with the conjunction (within a few degrees of each other) of Mercury, Venus, Mars, Jupiter and Saturn in the constellation of Pegasus. This date began jia-zi 1 (Year of the Mouse) and corresponds to Julian Day Number - 1,007,826The Tibetan Calendar: The calendar begins with the enlightening day of Buddha, which had a complete moon eclipse. Different Tibetan schools vary on this date, so I will use the oldest of the four I have and refer to it as Fire Rabbit 1. The other start dates appear in this system as Wood Horse 1108, Fire Bird 1591 and Water Dragon 2006. Fire Rabbit 1 corresponds to Julian Day Number - 942,097 The Balinese Calendar: I as yet have found no starting year to the cycles.The Hindu Calendar: Established by The Calendar Reform Committee in 1879 SE, 1 Chaitra, 1 SE (Sata Era) in the civil calendar, corresponds to Julian Day Number - 1,750,037This is the same year that the Indonesian calendar begins on, but I don't know if it's a coincidence, because I don't know as yet what event(s) this correlates to, historical or astronomical. Of the other Eras, the oldest of the starting dates is 1 KY (Kali Yuga or Iron Age), corresponding to Julian Day Number - 588,813 The Aztec Calendar: I haven't done much with this one yet, since it's so much like the Mayan, and that one has so much. Once I have the Mayan organized, then it will probably be easier to sort this one out as well.The Mayan Calendar: The beginning of the last Great Cycle corresponds to Julian Day Number - 584,298The Hebrew Calendar: According to Jewish teachings, 1 Tishrei, 1 AM (Anno Mundane, or Year Of The World) follows the creation of the universe by God, corresponding to Julian Day Number - 347,998The Illuminati Calendar: This is based directly on the Gregorian calendar, merely changing the starting year. Designed by Robert Anton Wilson in 5969-5971 AL for the Illuminatus trilogy (co-written with Bob Shea), 1 Verwirrung, 1 AL (Anno Lumina) marks the birth of ancient Chinese Chaoist (pre-Taoist) Hung Mung, corresponding to Julian Day Number - 260,460The Egyptian Calendar: The cycle began when the sun and Sirius rose in the same place, which may have been one of three possibilities. Referring to the older as year 1, the second would appear in this system as year 1141 and the third as 1468. Year 1 corresponds to Julian Day Number - 172,609 I've been informed that this year 1 was debunked by Richard Parker in the 6190's, and that the currently accepted starting date is the 1141, but whenever I have multiple sources I refer to the oldest in my calculations, and reference others relative to it.The Julian Day Number: Developed by the French scholar Joseph Scaliger, this is simply the number of solar days elapsed since noon GMT on the first day of the cycle. The cycle began on a day in the Julian calendar when the Indiction, Golden Number, and Solar Number were all 1, corresponding to Julian Day Number - 0
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| easily readable and writeable by software (no 'JAN', 'FEB', ... table necessary) | |
| easily comparable and sortable with a trivial string comparison | |
| language independent | |
| can not be confused with other popular date notations | |
| consistency with the common 24h time notation system, where the larger units (hours) are also written in front of the smaller ones (minutes and seconds) | |
| strings containing a date followed by a time are also easily comparable and sortable (e.g. write "1995-02-04 22:45:00") | |
| the notation is short and has constant length, which makes both keyboard data entry and table layout easier | |
| identical to the Chinese date notation, so the largest cultural group (>25%) on this planet is already familiar with it :-) | |
| date notations with the order "year, month, day" are in addition already widely used e.g. in Japan, Korea, Hungary, Sweden, Finland, Denmark, and a few other countries and people in the U.S. are already used to at least the "month, day" order | |
| a 4-digit year representation avoids overflow problems after 2099-12-31 |
As dates will look a little bit strange anyway starting with 2000-01-01 (e.g. like 1/1/0), it has been suggested that the year 2000 is an excellent opportunity to change to the standard date notation.
ISO 8601 is only specifying numeric notations and does not cover dates and times where words are used in the representation. It is not intended as a replacement for language-dependent worded date notations such as "24. Dezember 2001" (German) or "February 4, 1995" (US English). ISO 8601 should however be used to replace notations such as "2/4/95" and "9.30 p.m.".
Apart from the recommended primary standard notation YYYY-MM-DD, ISO 8601 also specifies a number of alternative formats for use in applications with special requirements. All of these alternatives can easily and automatically be distinguished from each other:
The hyphens can be omitted if compactness of the representation is more important than human readability, for example as in
19950204
For situations where information about the century is really not required, a 2-digit year representation is available:
95-02-04 or 950204
If only the month or even only the year is of interest:
1995-02 or 1995
In commercial and industrial applications (delivery times, production plans, etc.), especially in Europe, it is often required to refer to a week of a year. Week 01 of a year is per definition the first week that has the Thursday in this year, which is equivalent to the week that contains the fourth day of January. In other words, the first week of a new year is the week that has the majority of its days in the new year. Week 01 might also contain days from the previous year and the week before week 01 of a year is the last week (52 or 53) of the previous year even if it contains days from the new year. A week starts with Monday (day 1) and ends with Sunday (day 7). For example, the first week of the year 1997 lasts from 1996-12-30 to 1997-01-05 and can be written in standard notation as
1997-W01 or 1997W01
The week notation can also be extended by a number indicating the day of the week. For example, the day 1996-12-31, which is the Tuesday (day 2) of the first week of 1997, can also be written as
1997-W01-2 or 1997W012
for applications like industrial planning where many things like shift rotations are organized per week and knowing the week number and the day of the week is more handy than knowing the day of the month.
An abbreviated version of the year and week number like
95W05
is sometimes useful as a compact code printed on a product that indicates when it has been manufactured.
The ISO standard avoids explicitly stating the possible range of week numbers, but this can easily be deduced from the definition:
Theorem: Possible ISO week numbers are in the range 01 to 53. A year always has a week 52. (There is one historic exception: the year in which the Gregorian calendar was introduced had less than 365 days and less than 52 weeks.)
Proof: Per definition, the first week of a year is W01 and consequently days before week W01 belong to the previous year and so there is no week with lower numbers. Considering the highest possible week number, the worst case is a leap year like 1976 that starts with a Thursday, because this keeps the highest possible number of days of W01 in the previous year, i.e. 3 days. In this case, the Sunday of W52 of the worst case year is day number 4+51*7=361 and 361-366=5 days of W53 belong still to this year, which guarantees that in the worst case year day 4 (Thursday) of W53 is not yet in the next year, so a week number 53 is possible. For example, the 53 weeks of the worst case year 1976 started with 1975-12-29 = 1976-W01-1 and ended with 1977-01-02 = 1976-W53-7. On the other hand, considering the lowest number of the last week of a year, the worst case is a non-leap year like 1999 that starts with a Friday, which ensures that the first three days of the year belong to the last week of the previous year. In this case, the Sunday of week 52 would be day number 3+52*7=367, i.e. only the last 367-365=2 days of the W52 reach into the next year and consequently, even a worst case year like 1999 has a week W52 including the days 1999-12-27 to 2000-01-02. q.e.d.
[The new 1999 version of the C programming language
standard (ISO 9899) added in the strftime() function means to
generate the ISO 8601 week notation. The author of this text developed a
further proposal for a
modernised clock and calendar API for C, which provides full proper
treatment of leap seconds and timezones and fixes numerous other problems in
the current C timing library functions. It also serves as a model for those
who want to design clock library functions for other programming languages.]
Both day and year are useful units of structuring time, because the position of the sun on the sky, which influences our lives, is described by them. However the 12 months of a year are of some obscure mystic origin and have no real purpose today except that people are used to having them (they do not even describe the current position of the moon). In some applications, a date notation is preferred that uses only the year and the day of the year between 001 and 365 (366 in leap years). The standard notation for this variant representing the day 1995-02-04 (that is day 035 of the year 1995) is
1995-035 or 1995035
Leap years are years with an additional day YYYY-02-29, where the year number is a multiple of four with the following exception: If a year is a multiple of 100, then it is only a leap year if it is also a multiple of 400. For example, 1900 was not a leap year, but 2000 is one.
The international standard notation for the time of day is
hh:mm:ss
where hh is the number of complete hours that have passed since midnight (00-24), mm is the number of complete minutes that have passed since the start of the hour (00-59), and ss is the number of complete seconds since the start of the minute (00-60). If the hour value is 24, then the minute and second values must be zero. [The value 60 for ss might sometimes be needed during an inserted leap second in an atomic time scale like Coordinated Universal Time (UTC). A single leap second 23:59:60 is inserted into the UTC time scale every few years as announced by the International Earth Rotation Service in Paris to keep UTC from wandering away more than 0.9 s from the less constant astronomical time scale UT1 that is defined by the actual rotation of the earth.]
An example time is
23:59:59
which represents the time one second before midnight.
As with the date notation, the separating colons can also be omitted as in
235959
and the precision can be reduced by omitting the seconds or both the seconds and minutes as in
23:59, 2359, or 23
It is also possible to add fractions of a second after a decimal dot or comma, for instance the time 5.8 ms before midnight can be written as
23:59:59.9942 or 235959.9942
As every day both starts and ends with midnight, the two notations 00:00 and 24:00 are available to distinguish the two midnights that can be associated with one date. This means that the following two notations refer to exactly the same point in time:
1995-02-04 24:00 = 1995-02-05 00:00
In case an unambiguous representation of time is required, 00:00 is usually the preferred notation for midnight and not 24:00. Digital clocks display 00:00 and not 24:00.
ISO 8601 does not specify, whether its notations specify a point in time or a time period. This means for example that ISO 8601 does not define whether 09:00 refers to the exact end of the ninth hour of the day or the period from 09:00 to 09:01 or anything else. The users of the standard must somehow agree on the exact interpretation of the time notation if this should be of any concern.
If a date and a time are displayed on the same line, then always write the date in front of the time. If a date and a time value are stored together in a single data field, then ISO 8601 suggests that they should be separated by a latin capital letter T, as in 19951231T235959.
A remark for readers from the U.S.:
The 24h time notation specified here has already been the de-facto standard all over the world in written language for decades. The only exception are some English speaking countries, where still notations with hours between 1 and 12 and additions like "a.m." and "p.m." are in wide use. The common 24h international standard notation starts to get widely used now even in England. Most other languages don't even have abbreviations like "a.m." and "p.m." and the 12h notation is certainly hardly ever used on Continental Europe to write or display a time. Even in the U.S., the military and computer programmers have been using the 24h notation for a long time.
The old English 12h notation has many disadvantages like:
| It is longer than the normal 24h notation. | |
| It takes somewhat more time for humans to compare two times in 12h notation. | |
| It is not clear, how 00:00, 12:00 and 24:00 are represented. Even encyclopedias and style manuals contain contradicting descriptions and a common quick fix seems to be to avoid "12:00 a.m./p.m." altogether and write "noon", "midnight", or "12:01 a.m./p.m." instead, although the word "midnight" still does not distinguish between 00:00 and 24:00. | |
| It makes people often believe that the next day starts at the overflow from "12:59 a.m." to "1:00 a.m.", which is a common problem not only when people try to program the timer of VCRs shortly after midnight. | |
| It is not easily comparable with a string compare operation. | |
| It is not immediately clear for the unaware, whether the time between "12:00 a.m./p.m." and "1:00 a.m./p.m." starts at 00:00 or at 12:00, i.e. the English 12h notation is more difficult to understand. |
Please consider the 12h time to be a relic from the dark ages when Roman numerals were used, the number zero had not yet been invented and analog clocks were the only known form of displaying a time. Please avoid using it today, especially in technical applications! Even in the U.S., the widely respected Chicago Manual of Style now recommends using the international standard time notation in publications.
A remark for readers from German speaking countries:
In May 1996, the German standard DIN 5008, which specifies typographical rules for German texts written on typewriters, has been updated. The old German numeric date notations DD.MM.YYYY and DD.MM.YY have been replaced by the ISO date notations YYYY-MM-DD and YY-MM-DD. Similarly, the old German time notations hh.mm and hh.mm.ss have been replaced by the ISO notations hh:mm and hh:mm:ss. Those new notations are now also mentioned in the latest edition of the Duden. The German alphanumeric date notation continues to be for example "3. August 1994" or "3. Aug. 1994". The corresponding Austrian standard has already used the ISO 8601 date and time notations before.
ISO 8601 has been adopted as European Standard EN 28601 and is therefore now a valid standard in all EU countries and all conflicting national standards have been changed accordingly.
Without any further additions, a date and time as written above is assumed to be in some local time zone. In order to indicate that a time is measured in Universal Time (UTC), you can append a capital letter Z to a time as in
23:59:59Z or 2359Z
[The Z stands for the "zero meridian", which goes through Greenwich in London, and it is also commonly used in radio communication where it is pronounced "Zulu" (the word for Z in the international radio alphabet). Universal Time (sometimes also called "Zulu Time") was called Greenwich Mean Time (GMT) before 1972, however this term should no longer be used. Since the introduction of an international atomic time scale, almost all existing civil time zones are now related to UTC, which is slightly different from the old and now unused GMT.]
The strings
+hh:mm, +hhmm, or +hh
can be added to the time to indicate that the used local time zone is hh hours and mm minutes ahead of UTC. For time zones west of the zero meridian, which are behind UTC, the notation
-hh:mm, -hhmm, or -hh
is used instead. For example, Central European Time (CET) is +0100 and U.S./Canadian Eastern Standard Time (EST) is -0500. The following strings all indicate the same point of time:
12:00Z = 13:00+01:00 = 0700-0500
There exists no international standard that specifies abbreviations for civil time zones like CET, EST, etc. and sometimes the same abbreviation is even used for two very different time zones. In addition, politicians enjoy modifying the rules for civil time zones, especially for daylight saving times, every few years, so the only really reliable way of describing a local time zone is to specify numerically the difference of local time to UTC. Better use directly UTC as your only time zone where this is possible and then you do not have to worry about time zones and daylight saving time changes at all.