update to parameterized tags

[ArmanTheParman]

Tried to improve the explanation of parameterized tags

[ArmanTheParman]

You are probably right, but a little redundancy in strategic places can help readability - your call.

It's only a suggestion, I won't be hurt if my edits are not accepted 👍

On Tue, 18 June 2024, 5:55 pm Asai Toshiya, @.***> wrote:

@.**** commented on this pull request.

In 01.md https://github.com/nostr-protocol/nips/pull/1311#discussion_r1644004643:

@@ -77,11 +77,12 @@ This NIP defines 3 standard tags that can be used across all event kinds with th

• The e tag, used to refer to an event: ["e", <32-bytes lowercase hex of the id of another event>, <recommended relay URL, optional>]
• The p tag, used to refer to another user: ["p", <32-bytes lowercase hex of a pubkey>, <recommended relay URL, optional>] -- The a tag, used to refer to a (maybe parameterized) replaceable event
• • for a parameterized replaceable event: ["a", <kind integer>:<32-bytes lowercase hex of a pubkey>:<d tag value>, <recommended relay URL, optional>]
• • for a non-parameterized replaceable event: ["a", <kind integer>:<32-bytes lowercase hex of a pubkey>:, <recommended relay URL, optional>] +- The a tag, used to refer to a replaceable event.

• • The second element (tag value) contains a minimum of 2 identifiers - the kind and the pubkey. If a third is optionally added (the arbitrary "d tag value"), the event becomes "parameterized".

Seems like a redundant explanation to me.

— Reply to this email directly, view it on GitHub https://github.com/nostr-protocol/nips/pull/1311#pullrequestreview-2124781689, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASQCCX3NMCVTKGANHJHHZOTZH7RWZAVCNFSM6AAAAABJPGH7POVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCMRUG44DCNRYHE . You are receiving this because you authored the thread.Message ID: @.***>