Bugfix: Fix incorrect wording regarding negative times and add some clarification...

The time specification is mistakenly using the word "after" when it should be the word "before" for the example "2022:-5".

I decided that I needed to better clarify what I meant by default and not make it sound so strict.
Add additional language to better communicate that when the year is not specified, it is not specified.
There is no required interpretation and a default is simply a recommendation.

I am going to start trying to establish a habit of using UTC for my timestamps.
My local time zone, the date of the specification is still the 15 of December, 2023.
However, to stick with UTC for records purpose I need to the start doing this now.
There may be occasional inconsistencies for a while until I establish the habit of using UTC.

diff --git a/specifications/time.txt b/specifications/time.txt
index 402e25b1b3f162a2191232c912eeb19530d96eb9..f0aaa591b3e1bbacc1b339edb1c4ac7157a5c744 100644 (file)
--- a/specifications/time.txt
+++ b/specifications/time.txt
@@ -1,7 +1,7 @@
 # fss-0002 iki-0000
 #
 # license open-standard-license-1.0
-# version 2023/07/14
+# version 2023/12/16
 #
 # This file (assumed to be named time.txt) can be more easily read using the following iki_read commands:
 #   iki_read time.txt +Q -r UTC UTC -w -WW character "'" "'" code '"' '"'
@@ -25,17 +25,20 @@ Time Specification:
   The systems should expect 64-bit and larger bits would have to become common before something larger than 64-bit is the expected or assumed default.
   Negative signs can be allowed but they must not prevent the full use of the 64-bit.
   The implementation of how this is done is left to the implementer except that the signs are immediately to the left of the digit.
-  For example code:"2022:-5" would be 5 units after the start of the year 2022.
+  For example code:"2022:-5" would be 5 units before the start of the year 2022.
   Because the negative is allowed, so must the positive character (such as code:"2022:+5").
   A positive value is the default interpretation when no sign is valid.
 
   The unit of time called bold:"Time" is counted increments of a nanosecond, or 10^-9 seconds.
   A unit of bold:"Time" is, therefore, equivalent to a nanosecond.
-  The default year for bold:"Time" is the current year.
+  When the year is not specified, then the behavior of the year is not defined.
+  The year can be inferred, directly designated through some other means, understood, asserted, or simply unknown or otherwise unspecified.
+  The general recommendation is that the default year for bold:"Time" is the current year.
 
   The unit of time called bold:"EpochTime" is counted increments of a second, or 10^-9 seconds.
   A unit of bold:"EpochTime" is, therefore, equivalent to a second.
-  The default year for bold:"EpochTime" is the bold:"UNIX Epoch", sometimes called bold:"Unix time".
+  The behavior when the year is not specified is the same as described for the bold:"Time".
+  The general recommendation is that the default year for bold:"EpochTime" is the bold:"UNIX Epoch", sometimes called bold:"Unix time".
 
   The unit bold:"Time" has two technical forms and one common form, with the year and without the year.