isoparse function from python-dateutil The python-dateutil package has dateutil.parser.isoparse to parse not only RFC 3339 datetime strings like the one in the question, but also other ISO 8601 date and time strings that don’t comply with RFC 3339 (such as ones with no UTC offset, or ones that represent only a date). >>> import dateutil.parser … Read more
If you want to get the seconds since epoch, you can use python-dateutil to convert it to a datetime object and then convert it so seconds using the strftime method. Like so: >>> import dateutil.parser as dp >>> t=”1984-06-02T19:05:00.000Z” >>> parsed_t = dp.parse(t) >>> t_in_seconds = parsed_t.timestamp() >>> t_in_seconds ‘455051100’ So you were halfway there … Read more
If you use Java 7+, this pattern should work (X is for the ISO 8601 time zone): SimpleDateFormat fmt = new SimpleDateFormat(“yyyy-MM-dd’T’HH:mm:ssX”);
You could theoretically get an ISO8601 Duration that looks like the following: P1Y4M3W2DT10H31M3.452S I wrote the following regular expression to parse this into groups: (-)?P(?:([.,\d]+)Y)?(?:([.,\d]+)M)?(?:([.,\d]+)W)?(?:([.,\d]+)D)?T(?:([.,\d]+)H)?(?:([.,\d]+)M)?(?:([.,\d]+)S)? It’s not pretty, and someone better versed in regular expressions might be able to write a better one. The groups boil down into the following: Sign Years Months Weeks Days … Read more
ISO 8601 does have a standard for representing date ranges. To represent the start and end date using this format you would write: 2013-01-01/2013-06-31 Note how the forward slash is used as the interval designator to separate the start and end dates. See this Wikipedia page for more information.
PowerShell’s Get-Date supports standard .NET time formats. The o round-trip format complies with ISO 8601. Like so, Get-Date -Format “o” 2017-08-15T12:10:34.4443084+03:00
If you want to parse all valid formats of offsets (Z, ±hh:mm, ±hhmm and ±hh), one alternative is to use a java.time.format.DateTimeFormatterBuilder with optional patterns (unfortunatelly, it seems that there’s no single pattern letter to match them all): DateTimeFormatter formatter = new DateTimeFormatterBuilder() // date/time .append(DateTimeFormatter.ISO_LOCAL_DATE_TIME) // offset (hh:mm – “+00:00” when it’s zero) .optionalStart().appendOffset(“+HH:MM”, … Read more
tl;dr Always use ISO 8601 format: 2019-11-14T00:55:31.820Z Avoid the legacy format of RFC 1123 & 822: Thu, 14 Nov 2019 00:55:16 GMT UTC & GMT are time-keeping, not formats UTC and GMT are not formats. UTC and GMT are two slightly different ways of tracking time. This is a complicated topic, so see the Wikipedia … Read more