But we might want to discuss with them either (a) making their schema less strict, so it can take anything that could be parsed as a date ('format': 'any': https://github.com/okfn/json-table-schema-py/blob/master/jtskit/_types.py#L280), or (b) having them update all published sources for correct date format. Seeing as (b) is likely not possible, (a) seems like a good solution :).
I've discussed this at length with the people at Cabinet Office in UK Govt. While some resolution may appear, it is not relevant to this codebase, so closing.
Many errors found in cabinet office data are simple date format errors.
The HMT schema specifies
DD/MM/YYYY
, and we implement that here: https://github.com/okfn/goodtables/blob/master/examples/hmt/spend-publishing-schema.json#L20But much of the data has
DD/MM/YY
format.Is is technically, and practically, incorrect.
But we might want to discuss with them either (a) making their schema less strict, so it can take anything that could be parsed as a date (
'format': 'any'
: https://github.com/okfn/json-table-schema-py/blob/master/jtskit/_types.py#L280), or (b) having them update all published sources for correct date format. Seeing as (b) is likely not possible, (a) seems like a good solution :).