xsd:dateTime sometimes displays slightly incorrectly
Hey Vincent,
I know this is going to sound a bit weird.
I have this statement:
sosa:resultTime "2022-11-19T13:10:34.999477+00:00"^^xsd:dateTime
but it's rendered in Penny (running in the UK using GMT locally) as:
19/11/2022, 13:27:13
If it was something I could understand such as timezones, characters being transposed or a million other things I'd try to explain it. However, it's about 17 minutes wrong. I've tried with many different times, sometimes it works perfectly and other times it's just plain wrong. I was looking at it at 13:11 and it said 13:27 which meant my time was in the future. Now, when I look at it after the unexpected time it's still showing 13:27. So it's not some sort of "always add 17 minutes to the current time".
I've created you a test file so you can see it too:
https://storage.inrupt.com/957bd805-d991-45e1-8538-17b59d808012/pywws/penny_unexpected_time.ttl
Here's a screenshot so you know I'm not messing with you:
I am of course totally fine with you not fixing this. I just wanted to show you in case it made a lightbulb go off that made you want to dive in.
Thanks.
PS: Keep up the good work.
