qaz@lemmy.world to Memes@lemmy.ml · 1 year agoStandards shouldn't be behind a paywalllemmy.worldimagemessage-square102fedilinkarrow-up1664arrow-down134file-textcross-posted to: iso8601@lemmy.sdf.org
arrow-up1630arrow-down1imageStandards shouldn't be behind a paywalllemmy.worldqaz@lemmy.world to Memes@lemmy.ml · 1 year agomessage-square102fedilinkfile-textcross-posted to: iso8601@lemmy.sdf.org
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-squareCallumWells@lemmy.mllinkfedilinkEnglisharrow-up4·1 year agoallows, not requires. It basically means you can use space instead of T when showing it to end users and any technical person can just use T
minus-squarePraise Idleness@sh.itjust.workslinkfedilinkEnglisharrow-up3·1 year agoDevelopment wise, It’d be better if it’s required not allowed. Best case scenario, it’s just another redundant if statement.
minus-squareCallumWells@lemmy.mllinkfedilinkEnglisharrow-up2·1 year agoThe amount of things allowed by ISO 8601 is even more than what’s allowed by RFC 3339, if you take the time to look at https://ijmacd.github.io/rfc3339-iso8601/
allows, not requires. It basically means you can use space instead of T when showing it to end users and any technical person can just use T
Development wise, It’d be better if it’s required not allowed. Best case scenario, it’s just another redundant if statement.
The amount of things allowed by ISO 8601 is even more than what’s allowed by RFC 3339, if you take the time to look at https://ijmacd.github.io/rfc3339-iso8601/