Recommend qualified names for label namespaces

1 files changed, 6 insertions, 5 deletions

diff --git a/32.md b/32.md
index 161af53..858e637 100644
--- a/32.md
+++ b/32.md
@@ -28,14 +28,15 @@ or topics respectively. As with NIP-01, a relay hint SHOULD be included when usi
 Label Tag
 ----
 
-This NIP introduces a new tag `l` which denotes a label, and a new `L` tag which denotes a label namespace. A label MUST include a mark matching an `L` tag. `L` tags refer to a tag type within nostr, or a nomenclature external to nostr defined either formally or by convention. Some examples:
+This NIP introduces a new tag `l` which denotes a label, and a new `L` tag which denotes a label namespace. A label MUST include a mark matching an `L` tag. `L` tags refer to a tag type within nostr, or a nomenclature external to nostr defined either formally or by convention. Any string can be a namespace, but publishers SHOULD ensure they are unambiguous by using a well-defined ISO standard or reverse domain name notation. Some examples:
 
 - `["l", "footstr", "#t"]` - the publisher thinks the given entity should have the `footstr` topic applied.
 - `["l", "<pubkey>", "#p"]` - the publisher things the given entity should be tagged with with `<pubkey>`
 - `["l", "D005528", "MeSH"]` - ["Foot"](https://meshb.nlm.nih.gov/record/ui?ui=D005528) from NIH's Medical Subject Headings vocabulary
 - `["l", "3173435", "GeoNames"]` - [Milan, Italy](https://www.geonames.org/3173435/milan.html) using the GeoNames coding system
 - `["l", "IT-MI", "ISO-3166-2"]` - Milano, Italy using ISO 3166-2.
-- `["l", "relay", "review"]` - the publisher is leaving a review about a relay.
+- `["l", "VI-hum", "social.nos.ontology"]` - Violence toward a human being as defined by ontology.nos.social.
+- `["l", "review", "social.coracle.ontology"]` - the publisher is leaving a review about the target, as defined by ontology.coracle.social.
 
 `L` tags containing the label namespaces MUST be included in order to support searching by
 namespace rather than by a specific tag. The special `ugc` ("user generated content") namespace
@@ -58,7 +59,7 @@ Content
 -------
 
 Labels should be short, meaningful strings. Longer discussions, such as for a review, or an
-explanation of why something was labeled the way it was should go in the event's `content` field.
+explanation of why something was labeled the way it was, should go in the event's `content` field.
 
 Example events
 --------------
@@ -143,8 +144,8 @@ A plain review of a relay.
 {
   "kind": 1985,
   "tags": [
-    ["L", "review"],
-    ["l", "relay", "review", "{\"quality\": 0.1}"],
+    ["L", "social.coracle.ontology"],
+    ["l", "review", "social.coracle.ontology", "{\"quality\": 0.1}"],
     ["r", <relay_url>]
   ],
   "content": "This relay is full of mean people.",