ISO8601 to Timestamp is 1 hour ahead when on Daylight Saving Time, when using timezones.

When GMT (Z), the time conversion to timestamp is valid.
2022-05-10T14:34:58.360Z

However, the DST = 1 for any zone will convert with a 1-hour offset
2022-05-10T07:34:58.360-08:00

The two timestamps are supposed to be equal (7 hour difference to GMT due to DST, instead of timezone -08:00)

Installed this to a project to try it out but was frustrated to see it installs the GCentral menu package.

While this is a worthy cause this then gets sucked in to my project dependencies which I want to keep minimal. It also feels a little invasive to have packages install un-required dependencies.

According to section 4.3 (https://tools.ietf.org/html/rfc5322#section-4.3), there are a series of "obs-zone" fields that should be also supported. "obs-zone" referes to "Obsolete Zone Names" which are still used and preferably a library should try to support them for backward-compatibility reasons.

ABNF acceptable format is noted as:
"zone = (FWS ( "+" / "-" ) 4DIGIT) / obs-zone"

Currently, the library only supports "(FWS ( "+" / "-" ) 4DIGIT)"

Importantly, it should at the minimum recognize UT/GMT as +0000.
The other zones are North American specific and regarded as low priority, although probably easy to tackled if GMT notation is supported.

Quick Information

• OS: Windows 10 Pro, 22H2
• LabVIEW Version: 2023 Q3

What Happened?

Everything was working fine with LabVIEW 2020 Q1.
I tried to step up to LabVIEW 2023 Q3 on the same laptop and the same OS, unfortunately this package is not compatible with this new LabVIEW version.

Steps to reproduce

1. Use LabVIEW 2020.
2. Install Epoch Date & Time via VIPM. It works
3. Deinstall LabVIEW 2020 and install LabVIEW 2023 Q3
4. Install Epoch Date & Time via VIPM. There's a package information in red that mentions : "This package is not compatible with your operating system or any LabVIEW version installed on your computer."

Screenshots

Priority/Severity

As you want @francois-normandin ! Je ne suis pas assez bon pour detecter d'où vient le problème !
Peut-être les sources qui n'ont pas été sauvées dans cette version de LabVIEW ?

ISO8601 Format

Currently, the following subsets of the standard are implemented:

• UTC DateTime
• ISO Day
• ISO Week
• ISO WeekDay
• Ordinal Date
• Calendar Month

RFC3339 Format

Only the "string to timestamp" is implemented at the moment, as a non-strict ISO8601 validation.
Pending requests, the Timestamp to RFC3339 formatting could be added easily.

RFC5332 Format (Internet Email Date)

This is a less used formatting as it is only used in email headers.

GPS and UNIX Epochs Time

Unix and GPS Time computations are performed, including support for Leap Seconds. The library accounts for divergence of UTC and TAI (International Atomic Time) over time, to properly calculate GPS time.

#Epochs
A series of Epoch classes are abstracted in the palette and can be used for even more granularity or to build new methods that migrate from one epoch to another. The base Epoch class represents the local system time, unless it is overwritten. Current overrides include UTC, Unix and GPS.

GPS Epoch starts on Jan 6th, 1980
Unix Epoch starts on Jan 1st, 1970
UTC Epoch starts on Jan 1st, 1904
TAI epoch starts on Jan 1st, 1900 and is used to calculate leap second differential between GPS and UTC.
GPS is fixed to TAI, by definition, but with a 19 seconds offset.

Date Formatting Classes

By default, the Epoch Time to DateString uses the ISO8601 format. But a different date formatting can be created and injected to perform a user-defined formatting of whichever epoch time selected.

Current Date Formatters include: ISO8601 and RFC5322 formats

As per https://tools.ietf.org/html/rfc7231#section-7.1.1.1

RFC 850 format
ANSI C's asctime() format

Using the ISO DateTime string to form a path produces Not A Path errors because of invalid characters (":" for example).
It would be useful to have a pair of methods to produce a path-compatible date string and be able to extract it back to an ISO DateTime string.