diff options
Diffstat (limited to '52.md')
| -rw-r--r-- | 52.md | 9 |
1 files changed, 9 insertions, 0 deletions
| @@ -25,6 +25,7 @@ These tags are common to both types of calendar events: | |||
| 25 | * `p` (optional, repeated) 32-bytes hex pubkey of a participant, optional recommended relay URL, and participant's role in the meeting | 25 | * `p` (optional, repeated) 32-bytes hex pubkey of a participant, optional recommended relay URL, and participant's role in the meeting |
| 26 | * `t` (optional, repeated) hashtag to categorize calendar event | 26 | * `t` (optional, repeated) hashtag to categorize calendar event |
| 27 | * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc. | 27 | * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc. |
| 28 | * `a` (repeated) reference tag to kind `31924` calendar event requesting to be included in Calendar | ||
| 28 | 29 | ||
| 29 | The following tags are deprecated: | 30 | The following tags are deprecated: |
| 30 | 31 | ||
| @@ -32,6 +33,12 @@ The following tags are deprecated: | |||
| 32 | 33 | ||
| 33 | Calendar events are _not_ required to be part of a [calendar](#calendar). | 34 | Calendar events are _not_ required to be part of a [calendar](#calendar). |
| 34 | 35 | ||
| 36 | ## Collaborative Calendar Event Requests | ||
| 37 | |||
| 38 | Calendar events can include an `a` tag referencing a calendar (kind 31924) to request addition to that calendar. When a calendar event includes such a reference, clients should interpret this as a request to add the event to the referenced calendar by referencing it with an `a` tag. | ||
| 39 | |||
| 40 | This enables collaborative calendar management where multiple users can contribute events to calendars they do not own, subject to the calendar owner's approval. | ||
| 41 | |||
| 35 | ### Date-Based Calendar Event | 42 | ### Date-Based Calendar Event |
| 36 | 43 | ||
| 37 | This kind of calendar event starts on a date and ends before a different date in the future. Its use is appropriate for all-day or multi-day events where time and time zone hold no significance. e.g., anniversary, public holidays, vacation days. | 44 | This kind of calendar event starts on a date and ends before a different date in the future. Its use is appropriate for all-day or multi-day events where time and time zone hold no significance. e.g., anniversary, public holidays, vacation days. |
| @@ -125,6 +132,8 @@ Aside from the common tags, this also takes the following tags: | |||
| 125 | 132 | ||
| 126 | A calendar is a collection of calendar events, represented as a custom _addressable list_ event using kind `31924`. A user can have multiple calendars. One may create a calendar to segment calendar events for specific purposes. e.g., personal, work, travel, meetups, and conferences. | 133 | A calendar is a collection of calendar events, represented as a custom _addressable list_ event using kind `31924`. A user can have multiple calendars. One may create a calendar to segment calendar events for specific purposes. e.g., personal, work, travel, meetups, and conferences. |
| 127 | 134 | ||
| 135 | Calendars can accept event requests from other users. When calendar events reference a calendar via an `a` tag, this represents a request for inclusion. | ||
| 136 | |||
| 128 | The `.content` of these events should be a detailed description of the calendar. It is required but can be an empty string. | 137 | The `.content` of these events should be a detailed description of the calendar. It is required but can be an empty string. |
| 129 | 138 | ||
| 130 | * `d` (required) universally unique identifier. Generated by the client creating the calendar. | 139 | * `d` (required) universally unique identifier. Generated by the client creating the calendar. |