upleb.uk

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

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhodlbod <jstaab@protonmail.com>2024-08-12 08:40:57 -0700
committerGitHub <noreply@github.com>2024-08-12 08:40:57 -0700
commitf8e108e61dedd50b2d0e6100a719852a7631a149 (patch)
treec168380596d501b05b0d3425ee7ababd4f8ef438
parented15e318f452830dddb17193881f8e2f1c19aa38 (diff)
parentec1f0fcadaa7b62cc17633cc5a86686e85ebe7a6 (diff)
Merge pull request #1414 from tyiu/nip52-rsvp-e-and-p-tags
Amend NIP-52 to include e and p tags to calendar event RSVPs
-rw-r--r--52.md12
1 files changed, 10 insertions, 2 deletions
diff --git a/52.md b/52.md
index 97873ef..bedf613 100644
--- a/52.md
+++ b/52.md
@@ -187,6 +187,10 @@ 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 have an `a` tag of the event coordinates to the calendar event, and optionally an `e` tag of the id of the specific calendar event revision. If 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, and MAY interpret it to not necessarily apply to other revisions of the calendar event.
191
192The 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.
193
190### Format 194### Format
191 195
192The format uses a parameterized replaceable event kind `31925`. 196The format uses a parameterized replaceable event kind `31925`.
@@ -194,10 +198,12 @@ The format uses a parameterized replaceable event kind `31925`.
194The `.content` of these events is optional and should be a free-form note that adds more context to this calendar event response. 198The `.content` of these events is optional and should be a free-form note that adds more context to this calendar event response.
195 199
196The list of tags are as follows: 200The list of tags are as follows:
197* `a` (required) reference tag to kind `31922` or `31923` calendar event being responded to. 201* `a` (required) coordinates to a kind `31922` or `31923` calendar event being responded to.
202* `e` (optional) event id of a kind `31922` or `31923` calendar event being responded to.
198* `d` (required) universally unique identifier. Generated by the client creating the calendar event RSVP. 203* `d` (required) universally unique identifier. Generated by the client creating the calendar event RSVP.
199* `status` (required) `accepted`, `declined`, or `tentative`. Determines attendance status to the referenced calendar event. 204* `status` (required) `accepted`, `declined`, or `tentative`. Determines attendance status to the referenced calendar event.
200* `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`. 205* `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`.
206* `p` (optional) pubkey of the author of the calendar event being responded to.
201 207
202```json 208```json
203{ 209{
@@ -207,10 +213,12 @@ The list of tags are as follows:
207 "kind": 31925, 213 "kind": 31925,
208 "content": "<note>", 214 "content": "<note>",
209 "tags": [ 215 "tags": [
210 ["a", "<31922 or 31923>:<calendar event author pubkey>:<d-identifier of calendar event>", "<optional relay url>"], 216 ["e", "<kind 31922 or 31923 event id", "<optional recommended relay URL>"]
217 ["a", "<31922 or 31923>:<calendar event author pubkey>:<d-identifier of calendar event>", "<optional recommended relay URL>"],
211 ["d", "<UUID>"], 218 ["d", "<UUID>"],
212 ["status", "<accepted/declined/tentative>"], 219 ["status", "<accepted/declined/tentative>"],
213 ["fb", "<free/busy>"], 220 ["fb", "<free/busy>"],
221 ["p", "<hex pubkey of kind 31922 or 31923 event>", "<optional recommended relay URL>"]
214 ] 222 ]
215} 223}
216``` 224```