From 057d097e741453895164590d1c56fe87703c2c97 Mon Sep 17 00:00:00 2001 From: Jonathan Staab Date: Thu, 25 May 2023 10:22:35 -0700 Subject: [PATCH] Add an example for self-tagging, clarify # labels --- 32.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/32.md b/32.md index 858e637..dd2f50c 100644 --- a/32.md +++ b/32.md @@ -30,8 +30,10 @@ 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. 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: +Namespaces starting with `#` indicate that the label target should be associated with the label's value. This is a way of attaching standard nostr tags to events, pubkeys, relays, urls, etc. + - `["l", "footstr", "#t"]` - the publisher thinks the given entity should have the `footstr` topic applied. -- `["l", "", "#p"]` - the publisher things the given entity should be tagged with with `` +- `["l", "", "#p"]` - the publisher thinks the given entity is related to `` - `["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. @@ -170,3 +172,17 @@ this spec provides for overlaying structured metadata on top of nostr. ... } ``` + +Publishers can self-label by adding `l` tags to their own non-1985 events. + +```json +{ + "kind": 1, + "tags": [ + ["L", "social.nos.ontology"], + ["l", "IL-frd", "social.nos.ontology"] + ], + "content": "Send me 100 sats and I'll send you 200 back", + ... +} +```