upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

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