1 files changed, 5 insertions, 8 deletions
diff --git a/Proposal-Subject-Discussion.md b/14.md
index cf9ee19..0b37e8a 100644
--- a/Proposal-Subject-Discussion.md
+++ b/14.md
@@ -1,22 +1,19 @@
-NIP-??
+NIP-14
 ======
-I am implementing this as a trial in more-speech.  
 Subject tag in Text events.
 ---------------------------
 `draft` `optional` `author:unclebobmartin`
-This NIP defines the use of the Subject tag in text (kind: 1) events.
+This NIP defines the use of the "subject" tag in text (kind: 1) events.  
+(implemented in more-speech)
-Subject
-------
 `["subject": <string>]`
 Browsers often display threaded lists of messages.  The contents of the subject tag can be used in such lists, instead of the more ad hoc approach of using the first few words of the message.  This is very similar to the way email browsers display lists of incoming emails by subject rather than by contents.
-When replying to a message with a subject, clients should replicate the subject tag.
+When replying to a message with a subject, clients SHOULD replicate the subject tag.  Clients MAY adorn the subject to denote
+that it is a reply.  e.g. by prepending "Re:".  
 Subjects should generally be shorter than 80 chars.  Long subjects will likely be trimmed by clients.

diff --git a/Proposal-Subject-Discussion.md b/14.md index cf9ee19..0b37e8a 100644 --- a/Proposal-Subject-Discussion.md +++ b/14.md
@@ -1,22 +1,19 @@
1	NIP-??	1	NIP-14
2	======	2	======
3		3
4	I am implementing this as a trial in more-speech.
5
6	Subject tag in Text events.	4	Subject tag in Text events.
7	---------------------------	5	---------------------------
8		6
9	`draft` `optional` `author:unclebobmartin`	7	`draft` `optional` `author:unclebobmartin`
10		8
11	This NIP defines the use of the Subject tag in text (kind: 1) events.	9	This NIP defines the use of the "subject" tag in text (kind: 1) events.
12		10	(implemented in more-speech)
13	Subject
14	-------
15		11
16	`["subject": <string>]`	12	`["subject": <string>]`
17		13
18	Browsers often display threaded lists of messages. The contents of the subject tag can be used in such lists, instead of the more ad hoc approach of using the first few words of the message. This is very similar to the way email browsers display lists of incoming emails by subject rather than by contents.	14	Browsers often display threaded lists of messages. The contents of the subject tag can be used in such lists, instead of the more ad hoc approach of using the first few words of the message. This is very similar to the way email browsers display lists of incoming emails by subject rather than by contents.
19		15
20	When replying to a message with a subject, clients should replicate the subject tag.	16	When replying to a message with a subject, clients SHOULD replicate the subject tag. Clients MAY adorn the subject to denote
		17	that it is a reply. e.g. by prepending "Re:".
21		18
22	Subjects should generally be shorter than 80 chars. Long subjects will likely be trimmed by clients.	19	Subjects should generally be shorter than 80 chars. Long subjects will likely be trimmed by clients.