Add example to NIP-32 to support tagging multiple entities with multiple labels

32.md

@@ -55,8 +55,26 @@ A report that an event contains nudity.
 {
   "kind": 1985,
   "tags": [
-    ["e", <id>]
+    ["e", <id>],
-    ["l", "nudity"],
+    ["l", "nudity"]
+  ],
+  "content": "",
+  ...
+}
+```
+
+A single event can apply multiple labels to multiple targets to support mass-tagging.
+
+```json
+{
+  "kind": 1985,
+  "tags": [
+    ["e", <id>],
+    ["p", <id>],
+    ["t", "chickens"],
+    ["l", "permaculture"],
+    ["l", "permies"],
+    ["l", "farming"]
   ],
   "content": "",
   ...
@@ -71,7 +89,7 @@ A suggestion that multiple pubkeys be associated with the `permies` topic.
   "tags": [
     ["l", "#t/permies"],
     ["p", <pubkey1>],
-    ["p", <pubkey2>],
+    ["p", <pubkey2>]
   ],
   "content": "",
   ...
@@ -89,7 +107,7 @@ that's the case.
     ["l", "#t/bitcoin"],
     ["r", <relay_url>],
     ["quality", 0.7],
-    ["confidence", 0.2],
+    ["confidence", 0.2]
   ],
   "content": "I think this relay is mostly just bitcoiners.",
   ...
@@ -104,7 +122,7 @@ A plain review of a relay.
   "tags": [
     ["l", "review"],
     ["r", <relay_url>],
-    ["quality", 0.1],
+    ["quality", 0.1]
   ],
   "content": "This relay is full of mean people.",
   ...
@@ -121,7 +139,7 @@ this spec provides for overlaying structured metadata on top of nostr.
   "tags": [
     ["l", "lightning/channel"],
     ["p", <pubkey1>],
-    ["p", <pubkey2>],
+    ["p", <pubkey2>]
   ],
   "content": "<channel_id>",
   ...