Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Pages: 25. Chapters: CalConnect, CalDAV, Comparison of CalDAV and CardDAV implementations, Darwin Calendar Server, DAViCal, Epoch (reference date), GroupDAV, ICalendar, ISO week date, Julian day, Lilian date, Rata Die, SabreDAV, Unix time, Web Calendar Access Protocol. Excerpt: Unix time, or POSIX time, is a system for describing instances in time, defined as the number of seconds that have elapsed since midnight Coordinated Universal Time (UTC), 1 January 1970, not counting leap seconds. It is used widely in Unix-like and many other operating systems and file formats. It is neither a linear representation of time nor a true representation of UTC. Unix time may be checked on some Unix systems by typing date +%s on the command line. Two layers of encoding make up Unix time. These can usefully be separated. The first layer encodes a point in time as a scalar real number, and the second encodes that number as a sequence of bits or in another form. As is standard with UTC, this article labels days using the Gregorian calendar, and counts times within each day in hours, minutes, and seconds. Some of the examples also show International Atomic Time (TAI), another time scheme, which uses the same seconds and is displayed in the same format as UTC, but in which every day is exactly 86 400 s long, gradually losing synchronization with the Earth's rotation at a rate of roughly one second per year. Unix time is a single signed integer number which increments every second, without requiring the calculations to determine year, month, day of month, hour and minute required for intelligibility to humans. Modern Unix time is based on UTC, which counts time using SI seconds, and breaks up the span of time into days almost always 86 400 s long, but due to leap seconds occasionally 86 401 s this keeps the days synchronized with the rotation of the Earth...