Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Reconsider use of ISO 8601 in OpenActive standards #305

Closed
thill-odi opened this issue May 26, 2022 · 2 comments
Closed

Reconsider use of ISO 8601 in OpenActive standards #305

thill-odi opened this issue May 26, 2022 · 2 comments
Assignees
@thill-odi
Labels
discussion General discussion question, not yet a formal proposal

Comments

@thill-odi
Copy link
Contributor

thill-odi commented May 26, 2022 •
edited
Loading

At various points in the Opportunity specification the use of ISO 8601 data/time formats is required. However, despite very widespread implementation, ISO 8601 is not an open standard and is in fact paywalled by the ISO.

Consider shifting to RFC 3339 instead. A nice summary of the differences between RFC 3339 and ISO 8601, and in particular the more restricted scope of RFC 3339, can be found here. The question of whether these restrictions affect plausible OpenActive use-cases will need to be considered.
@thill-odi thill-odi added the discussion General discussion question, not yet a formal proposal label May 26, 2022
@thill-odi thill-odi self-assigned this May 26, 2022
@thill-odi
Copy link
Contributor Author

Currently planned as an agenda item for the W3C call of 22 June 2022

@thill-odi
Copy link
Contributor Author

See #304

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thill-odi thill-odi

Labels
discussion General discussion question, not yet a formal proposal
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thill-odi