Merge 050d2e43bd into 223bbdc152

21.md

@@ -19,6 +19,17 @@ The identifiers that come after are expected to be the same as those defined in
 - `nostr:note1fntxtkcy9pjwucqwa9mddn7v03wwwsu9j330jj350nvhpky2tuaspk6nqc`
 - `nostr:nevent1qqstna2yrezu5wghjvswqqculvvwxsrcvu7uc0f78gan4xqhvz49d9spr3mhxue69uhkummnw3ez6un9d3shjtn4de6x2argwghx6egpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5nxnepm`
 
+### Typed Schemes
+
+Nostr apps SHOULD register for the specific event types they support, enabling operating systems to suggest only applications that can handle those event types and allowing the OS to have a different default application for each type.
+
+The typed scheme is `nostr+<event type number>:` followed by a `note`, `nevent` or an `naddr` [NIP-19](19.md) identifier.
+
+#### Examples
+
+- `nostr+1:note1fntxtkcy9pjwucqwa9mddn7v03wwwsu9j330jj350nvhpky2tuaspk6nqc`
+- `nostr+1:nevent1qqstna2yrezu5wghjvswqqculvvwxsrcvu7uc0f78gan4xqhvz49d9spr3mhxue69uhkummnw3ez6un9d3shjtn4de6x2argwghx6egpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5nxnepm`
+
 ### Linking HTML pages to Nostr entities
 
 `<link>` tags with `rel="alternate"` can be used to associate webpages to Nostr events, in cases where the same content is served via the two mediums (for example, a web server that exposes Markdown articles both as HTML pages and as `kind:30023' events served under itself as a relay or through some other relay). For example: