qaz@lemmy.world to Memes@lemmy.ml · 1 year agoStandards shouldn't be behind a paywalllemmy.worldimagemessage-square100fedilinkarrow-up1661arrow-down134file-text
arrow-up1627arrow-down1imageStandards shouldn't be behind a paywalllemmy.worldqaz@lemmy.world to Memes@lemmy.ml · 1 year agomessage-square100fedilinkfile-text
ISO 8601 is paywalled RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.
minus-squaretreadful@lemmy.ziplinkfedilinkEnglisharrow-up26·1 year agoISO 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.
minus-squareSirQuackTheDuck@lemmy.worldlinkfedilinkarrow-up8·1 year agoDoesn’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
minus-squareKilling_Spark@feddit.delinkfedilinkarrow-up1·11 months agoHmm I don’t get the T there tbh
minus-squareSirQuackTheDuck@lemmy.worldlinkfedilinkarrow-up1·11 months agoIt makes the difference between M meaning month or M meaning minute. Small differences.
minus-squareKilling_Spark@feddit.delinkfedilinkarrow-up1·11 months agoSo it’s redundant in P1DT4H? Or is it a mandatory separator between ymd and hms?
minus-squareSirQuackTheDuck@lemmy.worldlinkfedilinkarrow-up1·11 months agoIt’s mandatory, which also makes it nice and predictable.
minus-squareEnderMB@lemmy.worldlinkfedilinkarrow-up9arrow-down1·1 year agoThis 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.
minus-squarebaltakatei@sopuli.xyzlinkfedilinkarrow-up3·1 year agoWeek numbers are convenient for projects in which key delivery dates are often expressed in his many weeks out they are.
minus-squarepomodoro_longbreak@sh.itjust.workslinkfedilinkarrow-up2·11 months agowtf what is that gross
ISO 8601 also allows for some weird shit. Like
2023-W01-1which actually means2022-12-31. There’s a lot of cruft in that standard.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:
Hmm I don’t get the T there tbh
It makes the difference between M meaning month or M meaning minute. Small differences.
So it’s redundant in P1DT4H? Or is it a mandatory separator between ymd and hms?
It’s mandatory, which also makes it nice and predictable.
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.
Week numbers are convenient for projects in which key delivery dates are often expressed in his many weeks out they are.
wtf what is that gross