nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-19 22:35:50 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

remove delimiter recommendation

Browse Source
This commit is contained in:
Jonathan Staab 2023-06-14 09:43:03 -07:00
parent bef3e6c941
commit 992b045aa7
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
32.md
View File

@ -182,7 +182,8 @@ namespace clashes, but for the sake of interoperability all namespaces should be
considered open for public use, and not proprietary. In other words, if there is a considered open for public use, and not proprietary. In other words, if there is a
namespace that fits your use case, use it even if it points to someone else's domain name. namespace that fits your use case, use it even if it points to someone else's domain name.
Vocabularies MAY choose to include the namespace in the label, delimited by a `:` character. Vocabularies MAY choose to fully qualify all labels within a namespace (for example,
This may be preferred when defining more formal vocabularies that should not be confused with `["l", "com.example.vocabulary:my-label"]`. This may be preferred when defining more
another namespace when querying without an `L` tag. For these vocabularies, all labels formal vocabularies that should not be confused with another namespace when querying
SHOULD include the namespace (rather than mixing qualified and unqualified labels). without an `L` tag. For these vocabularies, all labels SHOULD include the namespace
(rather than mixing qualified and unqualified labels).