From 0bcaf418804b905c4a2db7561b2c480af7de0d25 Mon Sep 17 00:00:00 2001 From: franzap <_@franzap.com> Date: Mon, 9 Oct 2023 16:40:42 -0300 Subject: [PATCH 1/2] Include definitions for a tags --- 10.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/10.md b/10.md index 9c79b4a27f..6d06a29fdc 100644 --- a/10.md +++ b/10.md @@ -37,8 +37,8 @@ They are citings from this event. `root-id` and `reply-id` are as above. >This scheme is deprecated because it creates ambiguities that are difficult, or impossible to resolve when an event references another but is not a reply. -## Marked "e" tags (PREFERRED) -`["e", , , ]` +## Marked "e" and "a" tags (PREFERRED) +`["e", , , ]` (or `["a", , , ]` for replaceable events) Where: @@ -48,7 +48,7 @@ Where: Those marked with `"reply"` denote the id of the reply event being responded to. Those marked with `"root"` denote the root id of the reply thread being responded to. For top level replies (those replying directly to the root event), only the `"root"` marker should be used. Those marked with `"mention"` denote a quoted or reposted event id. -A direct reply to the root of a thread should have a single marked "e" tag of type "root". +A direct reply to the root of a thread should have a single marked `"e"` tag (or `"a"` tag if it is a replaceable event) of type `"root"`. >This scheme is preferred because it allows events to mention others without confusing them with `` or ``. From 20b11187ade5a277ef077902dae3ef65899defb4 Mon Sep 17 00:00:00 2001 From: franzap <_@franzap.com> Date: Mon, 9 Oct 2023 16:42:00 -0300 Subject: [PATCH 2/2] Update subtitle --- 10.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/10.md b/10.md index 6d06a29fdc..abb8573dad 100644 --- a/10.md +++ b/10.md @@ -2,13 +2,13 @@ NIP-10 ====== -On "e" and "p" tags in Text Events (kind 1). +On "e", "a" and "p" tags in Text Events (kind 1). -------------------------------------------- `draft` `optional` `author:unclebobmartin` ## Abstract -This NIP describes how to use "e" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event. +This NIP describes how to use "e", "a" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event. ## Positional "e" tags (DEPRECATED) >This scheme is in common use; but should be considered deprecated.