-
Notifications
You must be signed in to change notification settings - Fork 821
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
3 properties should use DateTime instead of Date #996
Comments
Thanks, this seems fair. Another option would be to say that either "Date" or "DateTime" are appropriate values. |
|
I like your option the best; that would best allow events that are "all day" or at specific times. |
bump Any objections to adding DateTime and leaving Date there too? @scor @mfhepp @rvguha @chaals @shankarnat @vholland @tmarshbing |
@danbri ok |
👍 |
Implemented + queued for review in upcoming release: http://webschemas.org/docs/releases.html#g996 |
3 properties ( startDate endDate and commentTime ) have as their range a Date and yet expect a ISO8601 values that include the time (indicated in their comment). The model restricts an Event to have startDate or endDate without time which isn't the intention. Change their property range from Date to DateTime.
Alternatively, change startDate to startTime, endDate to endTime.
The text was updated successfully, but these errors were encountered: