idnits 2.17.1 draft-kunze-temper-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 225. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 7 longer pages, the longest (page 2) being 63 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 7 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (1 August 2007) is 6112 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'ISO8601' is defined on line 209, but no explicit reference was found in the text Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft: draft-kunze-temper-01.txt J. Kunze 3 TEMPER Date Format University of California 4 Expires 1 February 2008 C. Blair 5 University of Chicago 6 1 August 2007 8 Temporal Enumerated Ranges (TEMPER) 10 (http://www.ietf.org/internet-drafts/draft-kunze-temper-01.txt) 12 Status of this Document 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 Distribution of this document is unlimited. Please send comments to 36 jak at ucop dot edu. 38 Copyright (C) The IETF Trust (2007). All Rights Reserved. 40 Abstract 41 TEMPER (TEMPoral Enumerated Ranges) is a simple date and time syntax 42 for representing points, lists, and ranges of timestamps. The syntax 43 is designed to be trivial to parse, easy for humans to read, and 44 friendly to basic lexical sorting algorithms. Examples: 46 BCE1212 47 bce0551 48 1850~ 49 1952, 1958-1967, 1975 50 19990916_Z 51 19990916145903_z 52 20070401 54 1. TEMPER Points 56 A TEMPER point is a string of characters representing a single date 57 or a combination of a date and a time. Sometimes a point is called a 58 timestamp. Here are some examples of TEMPER points. 60 0384 The year 384. 61 1999 The year 1999. 62 19990916145903 3rd second past 2:59 PM, 16 September 1999. 63 19990916145903_z The same time, but in UTC time. 64 1999091614590312 12 seconds later, no specified time zone. 65 20041201 December 1st in the year 2004. 67 There are five different lengths of basic TEMPER points: 69 CCYY 4-digit year, with CC for 2-digit century 70 CCYYMMDD 8-digit year-month-day 71 CCYYMMDDhh 10-digit year-month-day-hour 72 CCYYMMDDhhmm 12-digit year-month-day-hour-minute 73 CCYYMMDDhhmmss 14-digit form with hour-minute-second 75 TEMPER points of 15 digits or more indicate fractions of seconds: 77 1999091614590312 No fractional seconds. 78 1999091614590312986 986 milliseconds later. 80 As a special case, to specify just a year and month without naming a 81 day in the month, give DD as 00: 83 CCYYMM00 8-digit year-month, but no day specified 85 For example, 87 20070500 The month of May in the year 2007. 89 A 6-digit form is reserved for a downgraded TEMPER idiom that 90 expresses a year-month-day with only a 2-digit year (i.e., the 91 2-digit century is missing): 93 YYMMDD 6-digit year-month-day (not recommended) 95 6-digit points are not recommended because they will not sort 96 correctly unless all the other dates (a) are 6-digit TEMPER points 97 and (b) have the same implicit century. 99 1.1. TEMPER Zones 101 The basic TEMPER point may optionally be followed by an '_' 102 (underscore) and a zone indicator of either 4 digits or 1-3 digits: 104 19990916145903_0000 Greenwich Mean Time (GMT). 105 19990916145903_GMT Greenwich Mean Time (GMT). 106 19990916145903_0100 One hour WEST of GMT. 107 19990916145903_2300 One hour east of GMT. 108 19990916145903_PST US Pacific Standard time. 109 19990916145903_edt US Eastern Daylight time. 110 19990916145903_EDT US Eastern Daylight time. 111 19990916145903_z UTC (Coordinated Universal Time). 113 In the absence of a zone indicator, TEMPER does not define a default. 115 1.2. Approximate and Uncertain Points 117 Any TEMPER point followed by a `~' (tilde) is interpreted as an 118 approximate point, indicating ambiguity or fuzziness in the point. 119 Because the tilde follows the TEMPER point, approximate and precise 120 dates will be placed together by normal sorting software. There is 121 currently no way in TEMPER to express the confidence level or the 122 extent of variation (plus or minus values). Examples: 124 1066~ Circa the year 1066. 125 20020800~ August 2002 or thereabouts. 126 19781201020000~ Around 2 AM on December 1st, 1978. 128 TEMPER reserves the '?' for expressing uncertain points; the details 129 of uncertain points are under construction. 131 1.3. Non-Gregorian Calendars 133 A TEMPER point may be preceded by the three letters "BCE" for "Before 134 Common Era" dates. These three ASCII letters express (with no case 135 sensitivity) "negative" dates, namely, dates that are chronologically 136 less than the year 0000. Examples: 138 BCE1212 Death of Rameses the Great. 139 bce0551 Birth of Confucius. 141 Note that BCE dates inherently sort in reverse order. But because 142 "BCE" appears first in TEMPER dates, naive sorting software (e.g., 143 Unix "sort" command with no arguments) first places all BCE dates 144 together as a group, after which the simple intervention of reversing 145 the order of the group achieves correct chronological order. 147 TEMPER reserves all 3-letter (alphabetic) prefixes for future use to 148 indicate Hebrew, Chinese, Islamic, and other calendars; these are 149 under construction. Although naive sorting will not work between 150 calendars, use of prefixes will cause sorting to work on groups of 151 dates that use the same calendar. The prefix "IBA" (from Tagalog) is 152 defined to mean "other unspecified", as in, 153 IBA 28 May, 2004 155 2. TEMPER Ranges and Lists 157 A TEMPER range is a start point and an end point separated by a 158 hyphen. 160 1996-2000 A range of four years. 161 2004- The year 2004 and later. 163 A missing start or end point indicates an open-ended range. In 164 general, a missing start point is strongly discouraged because it 165 disturbs sorting among records from other sources, e.g., shifting a 166 modern date range so that it appears near prehistoric dates; usually, 167 it works better at least to approximate the start point. 169 1860~-1872 Around 1860 and up to 1872. 171 A TEMPER list is one or more points and ranges separated by commas. 172 Every point in a list must have the same number of digits; e.g., a 173 14-digit point and a 4-digit range end point cannot occur in a valid 174 TEMPER list. Points and ranges in a list may occur in any order. 175 Here are some examples of lists. 177 1952, 1957, 1969 A list of three years. 178 1952, 1958-1967, 1985 A mixed list of dates and ranges. 180 3. Security considerations 182 The TEMPER syntax poses no direct risk to computers and networks. 183 Implementors should always exercise care when receiving data that may 184 be private or maliciously intended. These are normal risks to which 185 TEMPER is no more vulnerable than most other syntaxes. 187 4. Authors' Addresses 189 John A. Kunze 190 California Digital Library 191 University of California, Office of the President 192 415 20th St, 4th Floor 193 Oakland, CA 94612-3550, USA 195 Fax: +1 510-893-5212 196 EMail: jak@ucop.edu 198 Charles Blair 199 Digital Library Development Center 200 University of Chicago Library 201 1100 E. 57th St., JRL 220P 202 Chicago, IL 60637, USA 204 Fax: +1 773-702-6623 205 EMail: chas@uchicago.edu 207 5. Informative References 209 [ISO8601] ISO, "Data elements and interchange formats -- Information 210 interchange -- Representation of dates and times", 211 December 2004. 213 6. Copyright Notice 215 Copyright (C) The IETF Trust (2007). This document is subject to the 216 rights, licenses and restrictions contained in BCP 78, and except as 217 set forth therein, the authors retain all their rights. 219 This document and the information contained herein are provided on an 220 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 221 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 222 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 223 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 224 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 225 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 227 Expires 1 February 2008 228 Table of Contents 230 Status of this Document . . . . . . . . . . . . . . . . . . . . . . 1 231 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 232 1. TEMPER Points . . . . . . . . . . . . . . . . . . . . . . . . . 3 233 1.1. TEMPER Zones . . . . . . . . . . . . . . . . . . . . . . . . . 3 234 1.2. Approximate and Uncertain Points . . . . . . . . . . . . . . . 4 235 1.3. Non-Gregorian Calendars . . . . . . . . . . . . . . . . . . . 4 236 2. TEMPER Ranges and Lists . . . . . . . . . . . . . . . . . . . . 5 237 3. Security considerations . . . . . . . . . . . . . . . . . . . . 5 238 4. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 239 5. Informative References . . . . . . . . . . . . . . . . . . . . . 6 240 6. Copyright Notice . . . . . . . . . . . . . . . . . . . . . . . . 6