-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify TimeInterval
restrictions
#1112
Comments
Decision: use |
DECISION:
|
rjyounes
changed the title
Add
Modify Jun 27, 2024
TimeInterval
restrictionsTimeInterval
restrictions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #925, we settled on adding
actualStartDateTime
andactualEndDateTime
restrictions toTimeInterval
. @rjyounes has pointed out that the definitions of these predicates are phrased in the past tense, making them not a good fit for future time intervals. For this reason, we have kept the restrictions out of the 13.0 release.Assuming
dateTime
restrictions would be good to have onTimeInterval
, one option is to modify the definitions foractualStartDateTime
andactualEndDateTime
to include known datetimes in the future, even if we haven't reached them yet.The text was updated successfully, but these errors were encountered: