Closed ktk closed 5 years ago
The issue is:
2018-05-14T00:00:00.000+02:00
)2018-05-13T22:00:00.000Z
)2018-05-13
)Solution is either explicitly parsing and displaying in the same TZ or not ever converting to UTC (which means: implicitly parsing and displaying in the same TZ, which defaults to the local one)
In the BLV pipeline I have date fields in the form:
14.05.2018
, we map it to RDF with the following mapping:This results in the following RDF output:
"2018-05-13"^^<http://www.w3.org/2001/XMLSchema#date>
So it is off by one day (in the past). I suspect this is some default timezone handling that goes wrong.