nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05: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
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.
This may be preferred when defining more formal vocabularies that should not be confused with
another namespace when querying without an `L` tag. For these vocabularies, all labels
SHOULD include the namespace (rather than mixing qualified and unqualified labels).
Vocabularies MAY choose to fully qualify all labels within a namespace (for example,
`["l", "com.example.vocabulary:my-label"]`. This may be preferred when defining more
formal vocabularies that should not be confused with another namespace when querying
without an `L` tag. For these vocabularies, all labels SHOULD include the namespace
(rather than mixing qualified and unqualified labels).