I write a lot, a lot of personal journals in a plain text. They contain a lot of dates and times, many of them should be ideally tracked automatically (like, if I've written "15:00 tomorrow" some software ought to alarm at that time), so they should be written in a consistent manner. So far I've used ISO 8601 date and time format (e.g. 2020-09-05
or 11:30
) and a bunch of natural extensions (e.g. tomorrow
, last Sun
).
And folks, it's verbose or often ambiguous to other plain text! For example I tend to schedule things in a multiple of hours so :00
is not necessary, but a single number 15
would be less recognizable as hours. Many systems will helpfully try to recognize at 15
or 3pm
, but how would you know that at 15
is not a part of at 15 km/h
or similar? Also my journals are in Korean anyway, and such workarounds tend to not work well crosslingually. How about the intervals like 15:00 thru 18:30
? ISO 8601 interval 15:00/18:30
would be particularly problematic because a