rename "parameterized replaceable event" to "tagged-replaceable event".

This commit is contained in:
fiatjaf
2024-05-08 17:19:03 -03:00
parent 8073c848a3
commit 3f5cd01239
16 changed files with 28 additions and 28 deletions

8
52.md
View File

@@ -6,7 +6,7 @@ Calendar Events
`draft` `optional`
This specification defines calendar events representing an occurrence at a specific moment or between moments. These calendar events are _parameterized replaceable_ and deletable per [NIP-09](09.md).
This specification defines calendar events representing an occurrence at a specific moment or between moments. These calendar events are _tagged-replaceable_ and deletable per [NIP-09](09.md).
Unlike the term `calendar event` specific to this NIP, the term `event` is used broadly in all the NIPs to describe any Nostr event. The distinction is being made here to discern between the two terms.
@@ -20,7 +20,7 @@ This kind of calendar event starts on a date and ends before a different date in
#### Format
The format uses a parameterized replaceable event kind `31922`.
The format uses a tagged-replaceable event kind `31922`.
The `.content` of these events should be a detailed description of the calendar event. It is required but can be an empty string.
@@ -79,7 +79,7 @@ This kind of calendar event spans between a start time and end time.
#### Format
The format uses a parameterized replaceable event kind `31923`.
The format uses a tagged-replaceable event kind `31923`.
The `.content` of these events should be a detailed description of the calendar event. It is required but can be an empty string.
@@ -180,7 +180,7 @@ This NIP is also intentionally not defining what happens if a calendar event cha
### Format
The format uses a parameterized replaceable event kind `31925`.
The format uses a tagged-replaceable event kind `31925`.
The `.content` of these events is optional and should be a free-form note that adds more context to this calendar event response.