upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTerry Yiu <963907+tyiu@users.noreply.github.com>2024-08-08 01:04:25 -0400
committerTerry Yiu <963907+tyiu@users.noreply.github.com>2024-08-08 01:04:25 -0400
commitd36b24c82a07ad9769d5ff9aa2e01cfa65ca0614 (patch)
treece94e352ba26cf0597fa67eea71839a63b365d5a
parent8d451b3dc3ac5c0ccd7d6bdab4a7a5b7a420900d (diff)
Revise NIP-52 amendments so that they are backwards compatible
-rw-r--r--52.md12
1 files changed, 7 insertions, 5 deletions
diff --git a/52.md b/52.md
index fb85737..2b2f6db 100644
--- a/52.md
+++ b/52.md
@@ -187,9 +187,11 @@ This NIP is intentionally not defining who is authorized to attend a calendar ev
187 187
188This NIP is also intentionally not defining what happens if a calendar event changes after an RSVP is submitted. 188This NIP is also intentionally not defining what happens if a calendar event changes after an RSVP is submitted.
189 189
190The RSVP MUST tag the calendar event it is in response to with an `e` tag on the calendar event's id. 190The RSVP MUST have at least one of an `a` tag of the event coordinates to the calendar event, or `e` tag of the id of the specific calendar event revision.
191 191
192The RSVP MAY tag use an `a` tag to the calendar event's event coordinates to indicate that the RSVP response could hold trueregardless of any future revisions to the calendar event. If the `a` tag is omitted, the author of the RSVP is explicitly indicating that its response holds true for only that specific revision of the calendar event from the `e` tag. 192If an `e` tag is present, clients SHOULD interpret it as an indication that the RSVP is a response to that revision of the calendar event.
193
194If an `a` tag is present, clients SHOULD interpret it as an indication that the RSVP may hold true for all revisions of the calendar event.
193 195
194The RSVP MAY tag the author of the calendar event it is in response to using a `p` tag so that clients can easily query all RSVPs that pertain to the author. 196The RSVP MAY tag the author of the calendar event it is in response to using a `p` tag so that clients can easily query all RSVPs that pertain to the author.
195 197
@@ -200,12 +202,12 @@ The format uses a parameterized replaceable event kind `31925`.
200The `.content` of these events is optional and should be a free-form note that adds more context to this calendar event response. 202The `.content` of these events is optional and should be a free-form note that adds more context to this calendar event response.
201 203
202The list of tags are as follows: 204The list of tags are as follows:
203* `e` (required) event tag to kind `31922` or `31923` calendar event being responded to. 205* `e` (optional) event id of a kind `31922` or `31923` calendar event being responded to. This tag is required if `a` is omitted.
204* `a` (optional) reference tag to kind `31922` or `31923` calendar event being responded to. 206* `a` (optional) coordinates to a kind `31922` or `31923` calendar event being responded to. This tag is required if `e` is omitted.
205* `d` (required) universally unique identifier. Generated by the client creating the calendar event RSVP. 207* `d` (required) universally unique identifier. Generated by the client creating the calendar event RSVP.
206* `status` (required) `accepted`, `declined`, or `tentative`. Determines attendance status to the referenced calendar event. 208* `status` (required) `accepted`, `declined`, or `tentative`. Determines attendance status to the referenced calendar event.
207* `fb` (optional) `free` or `busy`. Determines if the user would be free or busy for the duration of the calendar event. This tag must be omitted or ignored if the `status` label is set to `declined`. 209* `fb` (optional) `free` or `busy`. Determines if the user would be free or busy for the duration of the calendar event. This tag must be omitted or ignored if the `status` label is set to `declined`.
208* `p` (optional) author of the calendar event being responded to. 210* `p` (optional) pubkey of the author of the calendar event being responded to.
209 211
210```json 212```json
211{ 213{