collective / collective/icalendar
RFC 9073 - Additional Components
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 413
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 45
Description
RFC 9073 specifies a few more components and values.
To claim compatibility, they must be added:
## Property Parameters
- [ ] [5.1. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-5.1)[Order](https://www.rfc-editor.org/rfc/rfc9073.html#name-order)
- [ ] [5.2. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-5.2)[Schema](https://www.rfc-editor.org/rfc/rfc9073.html#name-schema)
- [ ] [5.3. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-5.3)[Derived](https://www.rfc-editor.org/rfc/rfc9073.html#name-derived)
- [ ] This specification makes use of the "NAME" property, which is defined in [[RFC7986](https://www.rfc-editor.org/rfc/rfc9073.html#RFC7986)].
- [ ] [6.1. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-6.1)[Location Type](https://www.rfc-editor.org/rfc/rfc9073.html#name-location-type)
- [ ] [6.2. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-6.2)[Participant Type](https://www.rfc-editor.org/rfc/rfc9073.html#name-participant-type)
- [ ] [6.3. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-6.3)[Resource Type](https://www.rfc-editor.org/rfc/rfc9073.html#name-resource-type)
- [ ] [6.4. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-6.4)[Calendar Address](https://www.rfc-editor.org/rfc/rfc9073.html#name-calendar-address)
- [ ] [6.5. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-6.5)[Styled-Description](https://www.rfc-editor.org/rfc/rfc9073.html#name-styled-description)
- [ ] [6.6. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-6.6)[Structured-Data](https://www.rfc-editor.org/rfc/rfc9073.html#name-structured-data)
## Components
- [ ] [7.1. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-7.1)[Participant](https://www.rfc-editor.org/rfc/rfc9073.html#name-participant)
- [ ] [7.1.1. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-7.1.1)[Schedulable Participant](https://www.rfc-editor.org/rfc/rfc9073.html#name-schedulable-participant)
- [ ] [7.2. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-7.2)[Location](https://www.rfc-editor.org/rfc/rfc9073.html#name-location)
- [ ] [7.3. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-7.3)[Resource](https://www.rfc-editor.org/rfc/rfc9073.html#name-resource)
Support values:
- [ ] [11.2.1. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-11.2.1)[Participant Types](https://www.rfc-editor.org/rfc/rfc9073.html#name-participant-types)
- [ ] [11.2.2. ](https://www.rfc-editor.org/rfc/rfc9073.html#section-11.2.2)[Resource Types](https://www.rfc-editor.org/rfc/rfc9073.html#name-resource-types)
See also:
- https://github.com/collective/icalendar/issues/589
- https://www.rfc-editor.org/rfc/rfc9073.html
Contributor guide
Research direction
Start by reading the linked RFC 9073 sections and the related issue 589 to understand the required property parameters, components, and support values. The work is done when all checklist items are supported by the icalendar library and compatibility with the RFC is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100