-
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
Add restriction on Event linking it to a TimeInterval #950
Comments
Planned events may not have planned dates, so we can't say all events occur during some time interval. |
An Jamie: An event occurs during any number of time intervals (2-4pm today, 3-5pm today, 2023, the 21st century, etc.). DECISION:
|
This seems to be saying that
|
I like the idea of formal disjointness - that will help allay some confusion, perhaps. And yes, your rewording of the note is also good. |
I think you mean disjointness, not disjunction, which means OR / UNION. In any event, given the past history of |
Yes - corrected above. |
@rjyounes, do you agree to leave out the disjoint axiom, per above reasoning? If so, I think the PR can be approved and merged. |
Yes, fine. |
In the next major release (13.0.0) the property
isCharacterizedAs
will be gone as will the restriction onEvent
(isCharacterizedAs some Behavior
). This will leave the definition of Event with no formal axioms. I propose adding a subclass restriction along the lines of (occursDuring some TimeInterval
).This would likely mean introducing a new property.
The text was updated successfully, but these errors were encountered: