refactor: update backward arrow rule comment

This commit is contained in:
mirdono
2024-03-21 16:27:57 +01:00
parent 8755bbc432
commit 19f9d6f4e8
3 changed files with 15 additions and 28 deletions

View File

@@ -161,16 +161,11 @@ PREFIX ere: <http://data.lblod.info/vocabularies/erediensten/>
}. }.
# Backward arrow rule is like a function call. # Backward arrow rule is like a function call.
# Removes time info in the returned date # Removes the timezone indicator "Z" from incoming datetimes
# The user in DL selects a date via the UI. # To make sure all datetimes have the same convention we now save them as
# These dates are persisted as midnight dateTimes in UTC. # datetime without the timezone indicator
# Meaning that 1st of July is stored as # We use "T02:00:00" as time indicator to work around a virtuoso bug that
# "2022-06-30T22:00:00Z"^^xsd:dateTime # results in datetimes being converted to a date when using "T00:00:00"
# 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
{ {
?date :dateTimeFromDate ?dateTime ?date :dateTimeFromDate ?dateTime
} }

View File

@@ -148,15 +148,11 @@ PREFIX lblodlg: <http://data.lblod.info/vocabularies/leidinggevenden/>
# Backward arrow rule is like a function call. # Backward arrow rule is like a function call.
# Removes time info in the returned date # Removes the timezone indicator "Z" from incoming datetimes
# The user in DL selects a date via the UI. # To make sure all datetimes have the same convention we now save them as
# These dates are persisted as midnight dateTimes in UTC. # datetime without the timezone indicator
# Meaning that 1st of July is stored as # We use "T02:00:00" as time indicator to work around a virtuoso bug that
# "2022-06-30T22:00:00Z"^^xsd:dateTime # results in datetimes being converted to a date when using "T00:00:00"
# 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
{ {
?date :dateTimeFromDate ?dateTime ?date :dateTimeFromDate ?dateTime
} }

View File

@@ -144,15 +144,11 @@ PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
}. }.
# Backward arrow rule is like a function call. # Backward arrow rule is like a function call.
# Removes time info in the returned date # Removes the timezone indicator "Z" from incoming datetimes
# The user in DL selects a date via the UI. # To make sure all datetimes have the same convention we now save them as
# These dates are persisted as midnight dateTimes in UTC. # datetime without the timezone indicator
# Meaning that 1st of July is stored as # We use "T02:00:00" as time indicator to work around a virtuoso bug that
# "2022-06-30T22:00:00Z"^^xsd:dateTime # results in datetimes being converted to a date when using "T00:00:00"
# 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)
{ {
?date :dateTimeFromDate ?dateTime ?date :dateTimeFromDate ?dateTime
} }