Standards shouldn't be behind a paywall

3 years ago by qaz to c/memes

ISO 8601 is paywalled
RFC allows a space instead of a T (e.g. 2020-12-09 16:09:...) which is nicer to read.

load all comments

TeckFire 40 points 3 years ago

The difference:

2023-12-12T21:18Z is ISO 8601 format

2023-12-12 21:18 is RFC 3339 Format

A small change

save

path: 0 6006645, hotness: undefined, score: 40, children: 22

treadful 24 points 3 years ago

ISO 8601 also allows for some weird shit. Like 2023-W01-1 which actually means 2022-12-31. There's a lot of cruft in that standard.

save

path: 0 6006645 6008893, hotness: undefined, score: 24, children: 8

EnderMB 8 points 3 years ago

This is the killer for me. Most people promote ISO 8601 as a "definitive" date structure, when it actually supports a lot of different formats. What they actually want is usually RFC 3339.

save

path: 0 6006645 6008893 6011706, hotness: undefined, score: 8, children: 0

SirQuackTheDuck 8 points 3 years ago

Doesn't the ISO also includes time periods? Because if it does, those are amazing.

Without any explanation, you should be able to decypher these periods just by looking at them:

P1Y
P6M2D
P1DT4H
PT42M

save

path: 0 6006645 6008893 6011538, hotness: undefined, score: 8, children: 4

baltakatei 3 points 3 years ago

Week numbers are convenient for projects in which key delivery dates are often expressed in his many weeks out they are.

save

path: 0 6006645 6008893 6010355, hotness: undefined, score: 3, children: 0

pomodoro_longbreak 2 points 3 years ago

wtf what is that gross

save

path: 0 6006645 6008893 6022467, hotness: undefined, score: 2, children: 0

kogasa 14 points 3 years ago

That Z is doing a lot of work.

save

path: 0 6006645 6012952, hotness: undefined, score: 14, children: 8

TeckFire 10 points 3 years ago

Z indicates UTC. Alternatively,

2023-12.12T21:18-05 for time zone as central. The UTC time zone code at the end just tells you where the time is taken from. Usually Z is used since, well, it’s “universal,” but having a +13 or -06 or whatever else brings context, and allows computers to synchronize the string of text into a comparable time for event logs and such.

save

path: 0 6006645 6012952 6013224, hotness: undefined, score: 10, children: 7

hyperhopper 6 points 3 years ago

I definitely don't agree that the RFC is easier to read, the two numbers can appear to be one at a quick glance without a separator.

save

path: 0 6006645 6007215, hotness: undefined, score: 6, children: 2

elauso 16 points 3 years ago

But there is a separator between the numbers: the same one that also very reliably separates the words in this comment

save

path: 0 6006645 6007215 6009079, hotness: undefined, score: 16, children: 1

custard_swollower 3 points 3 years ago

Both are valid (if you'd add seconds) in both RFC 3339 and ISO 8601, but timezone support is the same here and there...

save

path: 0 6006645 6021087, hotness: undefined, score: 3, children: 0

Rules:

Rules: