1 files changed, 13 insertions, 3 deletions
diff --git a/32.md b/32.md
index bff3b80..0dc7f31 100644
--- a/32.md
+++ b/32.md
@@ -19,7 +19,7 @@ Label Namespace Tag
 An `L` tag can be any string, but publishers SHOULD ensure they are unambiguous by using a well-defined namespace
 (such as an ISO standard) or reverse domain name notation.
-`L` tags are REQUIRED in order to support searching by namespace rather than by a specific tag. The special `ugc`
+`L` tags are RECOMMENDED in order to support searching by namespace rather than by a specific tag. The special `ugc`
 ("user generated content") namespace MAY be used when the label content is provided by an end user.
 `L` tags starting with `#` indicate that the label target should be associated with the label's value.
@@ -28,7 +28,9 @@ This is a way of attaching standard nostr tags to events, pubkeys, relays, urls,
 Label Tag
 ----
-An `l` tag's value can be any string. `l` tags MUST include a `mark` matching an `L` tag value in the same event.
+An `l` tag's value can be any string. If using an `L` tag, `l` tags MUST include a mark matching an `L`
+tag value in the same event. If no `L` tag is included, a mark SHOULD still be included. If none is
+included, `ugc` is implied.
 Label Target
 ----
@@ -41,7 +43,7 @@ or topics respectively. As with NIP-01, a relay hint SHOULD be included when usi
 Content
 -------
-Labels should be short, meaningful strings. Longer discussions, such as for a review, or an
+Labels should be short, meaningful strings. Longer discussions, such as for an
 explanation of why something was labeled the way it was, should go in the event's `content` field.
 Self-Reporting
@@ -150,3 +152,11 @@ A good heuristic for whether a use case fits this NIP is whether labels would ev
 For example, many events might be labeled with a particular place, topic, or pubkey, but labels
 with specific values like "John Doe" or "3.18743" are not labels, they are values, and should
 be handled in some other way.
+Appendix: Known Ontologies
+-------------------------
+Below is a non-exhaustive list of ontologies currently in widespread use.
+- [social.ontolo.categories](https://ontolo.social/)

diff --git a/32.md b/32.md index bff3b80..0dc7f31 100644 --- a/32.md +++ b/32.md
@@ -19,7 +19,7 @@ Label Namespace Tag
19	An `L` tag can be any string, but publishers SHOULD ensure they are unambiguous by using a well-defined namespace	19	An `L` tag can be any string, but publishers SHOULD ensure they are unambiguous by using a well-defined namespace
20	(such as an ISO standard) or reverse domain name notation.	20	(such as an ISO standard) or reverse domain name notation.
21		21
22	`L` tags are REQUIRED in order to support searching by namespace rather than by a specific tag. The special `ugc`	22	`L` tags are RECOMMENDED in order to support searching by namespace rather than by a specific tag. The special `ugc`
23	("user generated content") namespace MAY be used when the label content is provided by an end user.	23	("user generated content") namespace MAY be used when the label content is provided by an end user.
24		24
25	`L` tags starting with `#` indicate that the label target should be associated with the label's value.	25	`L` tags starting with `#` indicate that the label target should be associated with the label's value.
@@ -28,7 +28,9 @@ This is a way of attaching standard nostr tags to events, pubkeys, relays, urls,
28	Label Tag	28	Label Tag
29	----	29	----
30		30
31	An `l` tag's value can be any string. `l` tags MUST include a `mark` matching an `L` tag value in the same event.	31	An `l` tag's value can be any string. If using an `L` tag, `l` tags MUST include a mark matching an `L`
		32	tag value in the same event. If no `L` tag is included, a mark SHOULD still be included. If none is
		33	included, `ugc` is implied.
32		34
33	Label Target	35	Label Target
34	----	36	----
@@ -41,7 +43,7 @@ or topics respectively. As with NIP-01, a relay hint SHOULD be included when usi
41	Content	43	Content
42	-------	44	-------
43		45
44	Labels should be short, meaningful strings. Longer discussions, such as for a review, or an	46	Labels should be short, meaningful strings. Longer discussions, such as for an
45	explanation of why something was labeled the way it was, should go in the event's `content` field.	47	explanation of why something was labeled the way it was, should go in the event's `content` field.
46		48
47	Self-Reporting	49	Self-Reporting
@@ -150,3 +152,11 @@ A good heuristic for whether a use case fits this NIP is whether labels would ev
150	For example, many events might be labeled with a particular place, topic, or pubkey, but labels	152	For example, many events might be labeled with a particular place, topic, or pubkey, but labels
151	with specific values like "John Doe" or "3.18743" are not labels, they are values, and should	153	with specific values like "John Doe" or "3.18743" are not labels, they are values, and should
152	be handled in some other way.	154	be handled in some other way.
		155
		156
		157	Appendix: Known Ontologies
		158	-------------------------
		159
		160	Below is a non-exhaustive list of ontologies currently in widespread use.
		161
		162	- [social.ontolo.categories](https://ontolo.social/)