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.md21
1 files changed, 17 insertions, 4 deletions
diff --git a/32.md b/32.md
index 79f5937..92d18eb 100644
--- a/32.md
+++ b/32.md
@@ -6,10 +6,9 @@ Labeling
6 6
7`draft` `optional` 7`draft` `optional`
8 8
9A label is a `kind 1985` event that is used to label other entities. This supports a number of use cases, 9This NIP defines two new indexable tags to label events and a new event kind (`kind:1985`) to attach those labels to existing events. This supports several use cases, including distributed moderation, collection management, license assignment, and content classification.
10including distributed moderation, collection management, license assignment, and content classification.
11 10
12This NIP introduces two new tags: 11New Tags:
13 12
14- `L` denotes a label namespace 13- `L` denotes a label namespace
15- `l` denotes a label 14- `l` denotes a label
@@ -129,10 +128,24 @@ is labeling their note as being related to Milan, Italy using ISO 3166-2.
129} 128}
130``` 129```
131 130
131Author is labeling their note language as English using ISO-639-1.
132
133```json
134{
135 "kind": 1,
136 "tags": [
137 ["L", "ISO-639-1"],
138 ["l", "en", "ISO-639-1"]
139 ],
140 "content": "English text",
141 ...
142}
143```
144
132Other Notes 145Other Notes
133----------- 146-----------
134 147
135When using this NIP to bulk-label many targets at once, events may be deleted and a replacement 148When using this NIP to bulk-label many targets at once, events may be requested for deletion using [NIP-09](09.md) and a replacement
136may be published. We have opted not to use parameterizable/replaceable events for this due to the 149may be published. We have opted not to use parameterizable/replaceable events for this due to the
137complexity in coming up with a standard `d` tag. In order to avoid ambiguity when querying, 150complexity in coming up with a standard `d` tag. In order to avoid ambiguity when querying,
138publishers SHOULD limit labeling events to a single namespace. 151publishers SHOULD limit labeling events to a single namespace.