qaz to [email protected] • 10 months agoStandards shouldn't be behind a paywalllemmy.worldimagemessage-square102fedilinkarrow-up1663arrow-down134file-textcross-posted to: [email protected]
arrow-up1629arrow-down1imageStandards shouldn't be behind a paywalllemmy.worldqaz to [email protected] • 10 months agomessage-square102fedilinkfile-textcross-posted to: [email protected]
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-square@[email protected]linkfedilinkEnglish4•10 months 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 IdlenesslinkfedilinkEnglish3•10 months agoDevelopment wise, It’d be better if it’s required not allowed. Best case scenario, it’s just another redundant if statement.
minus-square@[email protected]linkfedilinkEnglish2•10 months 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/