nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Deprecate 'name' for 'title' on calendar events and add 'title' as a shared tag via NIP-24

Browse Source
This commit is contained in:
Terry Yiu 2023-12-08 09:59:44 -08:00
parent b8308a9a04
commit ec08d65665
No known key found for this signature in database
GPG Key ID: 108645AE8A19B71A
2 changed files with 13 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
24.md
View File

@ -39,3 +39,4 @@ tags
These tags may be present in multiple event kinds. Whenever a different meaning is not specified by some more specific NIP, they have the following meanings: These tags may be present in multiple event kinds. Whenever a different meaning is not specified by some more specific NIP, they have the following meanings:
- `r`: a web URL the event is referring to in some way - `r`: a web URL the event is referring to in some way
- `title`: title of the event

18
52.md
View File

@ -26,7 +26,7 @@ The `.content` of these events should be a detailed description of the calendar
The list of tags are as follows: The list of tags are as follows:
* `d` (required) universally unique identifier (UUID). Generated by the client creating the calendar event. * `d` (required) universally unique identifier (UUID). Generated by the client creating the calendar event.
* `name` (required) name of the calendar event * `title` (required) title of the calendar event
* `start` (required) inclusive start date in ISO 8601 format (YYYY-MM-DD). Must be less than `end`, if it exists. * `start` (required) inclusive start date in ISO 8601 format (YYYY-MM-DD). Must be less than `end`, if it exists.
* `end` (optional) exclusive end date in ISO 8601 format (YYYY-MM-DD). If omitted, the calendar event ends on the same date as `start`. * `end` (optional) exclusive end date in ISO 8601 format (YYYY-MM-DD). If omitted, the calendar event ends on the same date as `start`.
* `location` (optional, repeated) location of the calendar event. e.g. address, GPS coordinates, meeting room name, link to video call * `location` (optional, repeated) location of the calendar event. e.g. address, GPS coordinates, meeting room name, link to video call
@ -35,6 +35,9 @@ The list of tags are as follows:
* `t` (optional, repeated) hashtag to categorize calendar event * `t` (optional, repeated) hashtag to categorize calendar event
* `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc. * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
The following tags are deprecated:
* `name` name of the calendar event. Use only if `title` is not available.
```json ```json
{ {
"id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>, "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
@ -45,7 +48,7 @@ The list of tags are as follows:
"tags": [ "tags": [
["d", "<UUID>"], ["d", "<UUID>"],
["name", "<name of calendar event>"], ["title", "<title of calendar event>"],
// Dates // Dates
["start", "<YYYY-MM-DD>"], ["start", "<YYYY-MM-DD>"],
@ -82,7 +85,7 @@ The `.content` of these events should be a detailed description of the calendar
The list of tags are as follows: The list of tags are as follows:
* `d` (required) universally unique identifier (UUID). Generated by the client creating the calendar event. * `d` (required) universally unique identifier (UUID). Generated by the client creating the calendar event.
* `name` (required) name of the calendar event * `title` (required) title of the calendar event
* `start` (required) inclusive start Unix timestamp in seconds. Must be less than `end`, if it exists. * `start` (required) inclusive start Unix timestamp in seconds. Must be less than `end`, if it exists.
* `end` (optional) exclusive end Unix timestamp in seconds. If omitted, the calendar event ends instantaneously. * `end` (optional) exclusive end Unix timestamp in seconds. If omitted, the calendar event ends instantaneously.
* `start_tzid` (optional) time zone of the start timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica` * `start_tzid` (optional) time zone of the start timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica`
@ -93,6 +96,9 @@ The list of tags are as follows:
* `t` (optional, repeated) hashtag to categorize calendar event * `t` (optional, repeated) hashtag to categorize calendar event
* `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc. * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
The following tags are deprecated:
* `name` name of the calendar event. Use only if `title` is not available.
```json ```json
{ {
"id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>, "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
@ -103,7 +109,7 @@ The list of tags are as follows:
"tags": [ "tags": [
["d", "<UUID>"], ["d", "<UUID>"],
["name", "<name of calendar event>"], ["title", "<title of calendar event>"],
// Timestamps // Timestamps
["start", "<Unix timestamp in seconds>"], ["start", "<Unix timestamp in seconds>"],
@ -141,7 +147,7 @@ The `.content` of these events should be a detailed description of the calendar.
The format uses a custom replaceable list of kind `31924` with a list of tags as described below: The format uses a custom replaceable list of kind `31924` with a list of tags as described below:
* `d` (required) universally unique identifier. Generated by the client creating the calendar. * `d` (required) universally unique identifier. Generated by the client creating the calendar.
* `name` (required) calendar name * `title` (required) calendar title
* `a` (repeated) reference tag to kind `31922` or `31923` calendar event being responded to * `a` (repeated) reference tag to kind `31922` or `31923` calendar event being responded to
```json ```json
@ -153,7 +159,7 @@ The format uses a custom replaceable list of kind `31924` with a list of tags as
"content": "<description of calendar>", "content": "<description of calendar>",
"tags": [ "tags": [
["d", "<UUID>"], ["d", "<UUID>"],
["name", "<calendar name>"], ["title", "<calendar title>"],
["a", "<31922 or 31923>:<calendar event author pubkey>:<d-identifier of calendar event>", "<optional relay url>"], ["a", "<31922 or 31923>:<calendar event author pubkey>:<d-identifier of calendar event>", "<optional relay url>"],
["a", "<31922 or 31923>:<calendar event author pubkey>:<d-identifier of calendar event>", "<optional relay url>"] ["a", "<31922 or 31923>:<calendar event author pubkey>:<d-identifier of calendar event>", "<optional relay url>"]
] ]