JSCalendar: A JSON Representation of Calendar Data
RFC 8984
Revision differences
Document history
Date | By | Action |
---|---|---|
2022-03-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2022-03-09
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2021-07-20
|
(System) | IANA registries were updated to include RFC8984 |
2021-07-16
|
(System) | Received changes through RFC Editor sync (created alias RFC 8984, changed title to 'JSCalendar: A JSON Representation of Calendar Data', changed abstract to 'This … Received changes through RFC Editor sync (created alias RFC 8984, changed title to 'JSCalendar: A JSON Representation of Calendar Data', changed abstract to 'This specification defines a data model and JSON representation of calendar data that can be used for storage and data exchange in a calendaring and scheduling environment. It aims to be an alternative and, over time, successor to the widely deployed iCalendar data format. It also aims to be unambiguous, extendable, and simple to process. In contrast to the jCal format, which is also based on JSON, JSCalendar is not a direct mapping from iCalendar but defines the data model independently and expands semantics where appropriate.', changed pages to 73, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-07-16, changed IESG state to RFC Published) |
2021-07-16
|
(System) | Removed all action holders (IESG state changed) |
2021-07-16
|
(System) | RFC published |