Avatar
unclebobmartin
2ef93f01cd2493e04235a6b87b10d3c4a74e2a7eb7c3caf168268f6af73314b5
Uncle Bob, Software Craftsman. http://cleancoder.com http://cleancoders.com

Is there a procedure to get a document like this into the document chain?

Does this capture the intent?

# On 'e' and 'p' tags in Text Events (kind 1).

## Definitions:

* A reply chain is the list of events from the root event to a specific reply.

* A reply thread is the tree of events consisting of all replies beginning at the root.

## The 'e' tag

Used in a text event contains a list of event ids.

* No 'e' tag:

This event is not a reply to, nor a referent to any other event.

* ["e",id]:

The id of the event to which this event is a reply.

* ["e",root-id,reply-id]

'root-id' is the id of the event at the root of the reply chain. 'reply-id' is the id of the article to which this event is a reply.

* ["e",root-id, mention-id,...,reply-id]

There may be any number of 'mention-ids'. These are the ids of events which may, or may not be in the reply chain. They are citings from this event. 'root-id' and 'reply-id' are as above.

## The 'p' tag

Used in a text event contains a list of pubkeys used to record who is involved in a reply thread.

When replying to a text event E with 'p' tags P, the replying event's 'p' tags should contain P as well as the pubkey of the of the event being replied to.

Example: Given a text event authored by a1 with p tags [p1, p2, p3] then the p tags of the reply should be [a1, p1, p2, p3] in no particular order.

And should that p tag contain a list of all the authors up to the root?

>There should be at least two refs when replying to a non-root note: first is

>root, second is immediate reply, and anything inbetween are mentioned notes.

>It's informal atm but works well.

OK. So the structure of the e tag is different from NIP-01 which says that the e tag contains only one event id.

You are suggesting that the e tag has n event ids, [root-id, mention1-id, mention2-id, ..., reply-id]

Where root-id refers to an event that has no e tag, and reply-id refers to the event being replied to, which must be

in the chain of replies below the root.

Do I have this right?

>I'm guessing the point of the quotes is that the notes your client will create

>will be email sized ?

Yes. I'm thinking it'll be like newsgroups where we editted the quoted material with answers to questions.