It's a small pain point but the format allowed in cs:updated is an xsd:dateTime when it should probably have been an xsd:date. One shouldn't have to look up xsd:dateTime and type in a bunch of zeroes and colons in the right order to make CSL validate. For a field that really, really does not need timestamp precision.
Simple solution: allow either. Then people can update with 2020-05-19, much more human friendly.
It's a small pain point but the format allowed in
cs:updated
is an xsd:dateTime when it should probably have been an xsd:date. One shouldn't have to look up xsd:dateTime and type in a bunch of zeroes and colons in the right order to make CSL validate. For a field that really, really does not need timestamp precision.Simple solution: allow either. Then people can update with
2020-05-19
, much more human friendly.