From 19f9d6f4e84578fef308b0bdd0659d3a16b00a41 Mon Sep 17 00:00:00 2001 From: mirdono Date: Thu, 21 Mar 2024 16:27:57 +0100 Subject: [PATCH] refactor: update backward arrow rule comment --- config/reasoner/dl2op/main-info/mapping.n3 | 15 +++++---------- config/reasoner/dl2op/main/mapping.n3 | 14 +++++--------- config/reasoner/dl2op/private-info/mapping.n3 | 14 +++++--------- 3 files changed, 15 insertions(+), 28 deletions(-) diff --git a/config/reasoner/dl2op/main-info/mapping.n3 b/config/reasoner/dl2op/main-info/mapping.n3 index 6a4cdd1..326b028 100644 --- a/config/reasoner/dl2op/main-info/mapping.n3 +++ b/config/reasoner/dl2op/main-info/mapping.n3 @@ -161,16 +161,11 @@ PREFIX ere: }. # Backward arrow rule is like a function call. -# Removes time info in the returned date -# The user in DL selects a date via the UI. -# These dates are persisted as midnight dateTimes in UTC. -# Meaning that 1st of July is stored as -# "2022-06-30T22:00:00Z"^^xsd:dateTime -# and 1 December -# "2022-11-30T23:00:00Z"^^xsd:dateTime -# So, the following rule adds 2 hours to the datetime, and then takes the date part of the UTC date time -# to come to the date that the DL user selected (in CE(S)T) -# To make sure the date have the same convention we now save them as datetime without the timezone indicator +# Removes the timezone indicator "Z" from incoming datetimes +# To make sure all datetimes have the same convention we now save them as +# datetime without the timezone indicator +# We use "T02:00:00" as time indicator to work around a virtuoso bug that +# results in datetimes being converted to a date when using "T00:00:00" { ?date :dateTimeFromDate ?dateTime } diff --git a/config/reasoner/dl2op/main/mapping.n3 b/config/reasoner/dl2op/main/mapping.n3 index 268d389..a0fa3ba 100644 --- a/config/reasoner/dl2op/main/mapping.n3 +++ b/config/reasoner/dl2op/main/mapping.n3 @@ -148,15 +148,11 @@ PREFIX lblodlg: # Backward arrow rule is like a function call. -# Removes time info in the returned date -# The user in DL selects a date via the UI. -# These dates are persisted as midnight dateTimes in UTC. -# Meaning that 1st of July is stored as -# "2022-06-30T22:00:00Z"^^xsd:dateTime -# and 1 December -# "2022-11-30T23:00:00Z"^^xsd:dateTime -# So, the following rule adds 2 hours to the datetime, and then takes the date part of the UTC date time -# To make sure the date have the same convention we now save them as datetime without the timezone indicator +# Removes the timezone indicator "Z" from incoming datetimes +# To make sure all datetimes have the same convention we now save them as +# datetime without the timezone indicator +# We use "T02:00:00" as time indicator to work around a virtuoso bug that +# results in datetimes being converted to a date when using "T00:00:00" { ?date :dateTimeFromDate ?dateTime } diff --git a/config/reasoner/dl2op/private-info/mapping.n3 b/config/reasoner/dl2op/private-info/mapping.n3 index e230655..c410991 100644 --- a/config/reasoner/dl2op/private-info/mapping.n3 +++ b/config/reasoner/dl2op/private-info/mapping.n3 @@ -144,15 +144,11 @@ PREFIX xsd: }. # Backward arrow rule is like a function call. -# Removes time info in the returned date -# The user in DL selects a date via the UI. -# These dates are persisted as midnight dateTimes in UTC. -# Meaning that 1st of July is stored as -# "2022-06-30T22:00:00Z"^^xsd:dateTime -# and 1 December -# "2022-11-30T23:00:00Z"^^xsd:dateTime -# So, the following rule adds 2 hours to the datetime, and then takes the date part of the UTC date time -# to come to the date that the DL user selected (in CE(S)T) +# Removes the timezone indicator "Z" from incoming datetimes +# To make sure all datetimes have the same convention we now save them as +# datetime without the timezone indicator +# We use "T02:00:00" as time indicator to work around a virtuoso bug that +# results in datetimes being converted to a date when using "T00:00:00" { ?date :dateTimeFromDate ?dateTime }