ISO-8601 date format reference not publicly available

Re:ISO-8601 date format reference not publicly available by taylodl on Tuesday March 09, 2021 @02:41PM (#26403076)

> period definition format

You mean the milliseconds? You're correct that YMMV with regards to libraries, but a lot of them handle milliseconds as well.

[ Parent | on HN ]

Re:ISO-8601 date format reference not publicly available by Macha on Tuesday March 09, 2021 @03:02PM (#26403392)

No, I mean stuff like

2007-03-01T13:00:00Z/P1M

For something that occurs on the first of each month.

[ Parent | on HN ]

Re:ISO-8601 date format reference not publicly available by taylodl on Tuesday March 09, 2021 @03:09PM (#26403481)

Oh - combining a date/timestamp and a duration, such as xsd:duration (http://www.datypic.com/sc/xsd/t-xsd_duration.html). I've never seen them combined into a single string, though there have been times when that would have been really useful!

[ Parent | on HN ]

Re:ISO-8601 date format reference not publicly available by em500 on Tuesday March 09, 2021 @03:24PM (#26403673)

It looks like xsd:duration uses duration notation from ISO8601. The rules for combining them or designating recurring intervals are in ISO8601 section 4.4-4.5 [1]. Unfortunately, awareness and library support for ISO8601 interval notation are very sparse and most people/orgs just roll their own.

[1] https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0038_i...

[ Parent | on HN ]

Re:ISO-8601 date format reference not publicly available by phendrenad2 on Tuesday March 09, 2021 @07:37PM (#26406395)

Yeah I didn't know that ISO had recurring events in the spec. I guess most library authors don't either, and as GP said, they think the RFC covers it.

[ Parent | on HN ]