anchor.diff:   * `instant.nanosecond` - the _nanosecond_ component as an integer (0-999999999)
    * `instant.timezone` - the _timezone_ as a string, either as a timezone name or as an offset from UTC in the format `±HHMM`, depending on how the timezone was specified.
    * `instant.offset` - the _timezone_ offset as a string, in the format `±HHMM`
  - * `instant.epoch` - the number of milliseconds between `1970-01-01T00:00:00+0000` and the instant, positive for instants after and negative for instants before.
  + * `instant.offsetMinutes` - the _timezone_ offset in minutes
  + * `instant.offsetSeconds` - the _timezone_ offset in seconds
  + * `instant.epochMillis` - the number of milliseconds between `1970-01-01T00:00:00+0000` and the instant, positive for instants after and negative for instants before.
  + * `instant.epochSeconds` - the number of seconds between `1970-01-01T00:00:00+0000` and the instant, positive for instants after and negative for instants before.
  +   For the nanosecond part of the epoch offset, the regular `nanosecond` component (`instant.nanosecond`) can be used.
   
   
   ==== Available components per instant type
  
positive.code:     "-08:00"
  
  
  ==== The default timezone and the session timezone
  
  For operations that require a timezone (creation of _Time_ or _DateTime_, or ordering by temporal instants of mixed types), where no timezone is given a default timezone is used.
  The default timezone is retrieved through first inspecting the session for a timezone.
  If a timezone is specified as a session variable, this timezone is used.
  If no timezone is specified in the session, the default timezone configured for the database is used.
  If the default timezone has not been configured for the database, UTC is assumed.
  
  
  === Creating temporal values
  
negative.code: 
  Since time is always stored in UTC, temporal instants can be trivially ordered without taking time zone into account.
  
  The standard way of specifying a time zone according to ISO 8601 is by specifying the offset from UTC in hours and minutes.
  In addition to this format, Cypher also supports specifying a named time zone, or specifying both the offset and the time zone name (in this case requiring that they match).
  
  Cypher's support for named time zones is based on the https://www.iana.org/time-zones[IANA timezone database].
  When entering a time using a named time zone, the offset from UTC is computed from the rules in the timezone database in order to create a time instant in UTC and in order to verify that the named timezone represents an actual existing timezone.
  The named timezone is then simply stored with the instant and only used when the time is presented.
  This means that if the rules for the timezone change in the timezone database in between when the time was created and when the time is presented, for example if the daylight savings time rules for that area changes, the presented time could differ from the originally entered time in the local timezone, although the absolute time in UTC will remain the same.
  