It also say YYYY-mm-dd should be date and HH:MM:SS should be time and YYYY-mm-ddTHH:MM:SS should be datetime. But it also allow extremely cursed datetime, many prefer rfc3339
The standard specify a ton features and formats. Thing like day if week so 2015-W4-1 would be the first day of the fourth week of 2015.
But the you have can have periods like “P1Y2M10DT2H30M”, and you can specify start and end dates. So if you want to start an event that runs for 3 months, 20 days, and some time you could write it as “20220212T1133/P3M20DT7H15M”.
And then there’s more like giving the year as an exponent, so 2015 can be written as Y-2.015E3S4.
far_university1990@reddthat.com 12 hours ago
It also say YYYY-mm-dd should be date and HH:MM:SS should be time and YYYY-mm-ddTHH:MM:SS should be datetime. But it also allow extremely cursed datetime, many prefer rfc3339
piwakawakas@lemmy.nz 5 hours ago
I use that date format for saving work docs anyway. And use dd/mm/yyyy for anything else.
Although thinking about it, maybe I should just adopt the international standard for everything
trxxruraxvr@lemmy.world 11 hours ago
Like what?
HereIAm@lemmy.world 8 hours ago
The standard specify a ton features and formats. Thing like day if week so 2015-W4-1 would be the first day of the fourth week of 2015.
But the you have can have periods like “P1Y2M10DT2H30M”, and you can specify start and end dates. So if you want to start an event that runs for 3 months, 20 days, and some time you could write it as “20220212T1133/P3M20DT7H15M”.
And then there’s more like giving the year as an exponent, so 2015 can be written as Y-2.015E3S4.