Wrong values of xsd:dateTime

[mereolog]

https://www.w3.org/TR/xmlschema-2/#dateTime spec, in particular section 3.2.7.2, second bullet, requires that "fractional second string, if present, must not end in '0'".

Still there is quite a lot of strings that are declared as xsd:dateTime that do not satisfy this condition - see below.

All of them can be fixed by a script if required.

2012-06-06T15:50:00.000^^xsd:dateTime
2012-06-06T15:51:00.000^^xsd:dateTime
2012-06-06T15:52:00.000^^xsd:dateTime
2012-06-06T15:53:00.000^^xsd:dateTime
2012-06-06T15:54:00.000^^xsd:dateTime
2012-06-06T15:55:00.000^^xsd:dateTime
2012-06-26T13:54:00.000^^xsd:dateTime
2012-06-27T11:47:00.000^^xsd:dateTime
2012-10-19T18:57:00.000^^xsd:dateTime
2012-11-28T20:59:00.000^^xsd:dateTime
2012-12-11T21:45:00.000^^xsd:dateTime
2013-03-01T16:35:00.000^^xsd:dateTime
2013-08-14T02:34:00.000^^xsd:dateTime
2013-12-10T03:07:00.000^^xsd:dateTime
2014-01-07T03:04:00.000^^xsd:dateTime
2014-03-28T01:39:00.000^^xsd:dateTime
2015-08-31T16:16:00.000^^xsd:dateTime
2016-05-05T01:54:00.000^^xsd:dateTime
2017-12-29T15:32:00.000^^xsd:dateTime
2020-12-23T00:19:00.000^^xsd:dateTime
2021-01-07T23:26:00.000^^xsd:dateTime
2021-02-09T07:33:00.000^^xsd:dateTime
2021-03-09T13:03:09.110^^xsd:dateTime
2021-04-26T14:19:00.000^^xsd:dateTime
2021-04-27T13:02:00.000^^xsd:dateTime
2021-05-17T15:24:00.000^^xsd:dateTime
2021-05-27T19:56:00.000^^xsd:dateTime
2021-05-27T21:33:00.000^^xsd:dateTime
2021-06-07T16:35:00.470^^xsd:dateTime
2021-06-09T15:32:00.000^^xsd:dateTime
2021-06-17T15:33:00.000^^xsd:dateTime
2021-06-28T12:47:00.000^^xsd:dateTime
2021-07-20T17:18:41.850^^xsd:dateTime
2021-08-12T15:32:00.000^^xsd:dateTime
2021-08-19T21:31:00.000^^xsd:dateTime
2021-08-24T20:52:00.000^^xsd:dateTime
2021-09-01T15:31:00.000^^xsd:dateTime
2021-09-06T15:31:00.000^^xsd:dateTime
2021-09-15T15:32:00.000^^xsd:dateTime
2021-09-23T00:46:00.000^^xsd:dateTime
2021-09-23T02:31:00.000^^xsd:dateTime
2021-09-28T21:32:00.000^^xsd:dateTime
2021-09-29T21:32:00.000^^xsd:dateTime
2021-10-22T15:33:00.000^^xsd:dateTime
2021-11-15T15:32:00.000^^xsd:dateTime
2021-11-16T15:33:00.000^^xsd:dateTime
2021-11-17T23:23:00.000^^xsd:dateTime
2021-11-29T23:17:00.000^^xsd:dateTime
2021-11-30T23:23:00.000^^xsd:dateTime
2021-12-22T19:31:00.000^^xsd:dateTime
2022-01-07T23:27:00.000^^xsd:dateTime
2022-01-07T23:30:00.000^^xsd:dateTime
2022-02-09T07:38:00.000^^xsd:dateTime
2022-04-27T13:06:00.000^^xsd:dateTime
2022-04-27T13:14:00.000^^xsd:dateTime
2022-05-10T21:00:00.000^^xsd:dateTime
2022-05-17T15:31:00.000^^xsd:dateTime
2022-05-27T20:19:00.000^^xsd:dateTime
2022-06-28T12:51:00.000^^xsd:dateTime
2022-06-28T20:23:33.650^^xsd:dateTime
2022-08-02T07:54:00.000^^xsd:dateTime
2022-08-03T23:22:00.000^^xsd:dateTime
2022-08-05T19:16:00.000^^xsd:dateTime
2022-08-09T17:42:00.000^^xsd:dateTime
2022-08-26T18:01:00.000^^xsd:dateTime
2022-08-27T20:07:00.000^^xsd:dateTime
2022-09-02T16:53:00.000^^xsd:dateTime
2022-09-09T12:59:00.000^^xsd:dateTime
2022-10-11T00:31:00.000^^xsd:dateTime
2022-10-24T00:30:00.000^^xsd:dateTime
2022-11-02T18:50:00.000^^xsd:dateTime
2022-11-17T18:01:00.000^^xsd:dateTime
2022-11-29T17:57:00.000^^xsd:dateTime
2022-11-30T20:13:00.000^^xsd:dateTime

[ElisaKendall]

@merelog - while that may be true, the values are from external entries, for example from the GLIEF LEI data, and those were the values at the time we grabbed them. One option would be to update the the examples to reflect the latest content but there is no guarantee that this would correct the trailing "0".

[mereolog]

The problem with these values is that some reasoners, e.g., Hermit, think that an ontology that contains such malformed values is consistent. Also the change I propose is semantically irrelevant.