diff options
| author | Jonathan Staab <shtaab@gmail.com> | 2023-06-14 09:43:03 -0700 |
|---|---|---|
| committer | Jonathan Staab <shtaab@gmail.com> | 2023-06-14 09:43:03 -0700 |
| commit | 992b045aa7b7610d1c492dab717eb183094fec39 (patch) | |
| tree | e99a8ff158734fcee8cb6d74b27bc200fdca89de /32.md | |
| parent | bef3e6c941c80114c1a040d42317c8fef4a74e7d (diff) | |
remove delimiter recommendation
Diffstat (limited to '32.md')
| -rw-r--r-- | 32.md | 9 |
1 files changed, 5 insertions, 4 deletions
| @@ -182,7 +182,8 @@ namespace clashes, but for the sake of interoperability all namespaces should be | |||
| 182 | considered open for public use, and not proprietary. In other words, if there is a | 182 | considered open for public use, and not proprietary. In other words, if there is a |
| 183 | namespace that fits your use case, use it even if it points to someone else's domain name. | 183 | namespace that fits your use case, use it even if it points to someone else's domain name. |
| 184 | 184 | ||
| 185 | Vocabularies MAY choose to include the namespace in the label, delimited by a `:` character. | 185 | Vocabularies MAY choose to fully qualify all labels within a namespace (for example, |
| 186 | This may be preferred when defining more formal vocabularies that should not be confused with | 186 | `["l", "com.example.vocabulary:my-label"]`. This may be preferred when defining more |
| 187 | another namespace when querying without an `L` tag. For these vocabularies, all labels | 187 | formal vocabularies that should not be confused with another namespace when querying |
| 188 | SHOULD include the namespace (rather than mixing qualified and unqualified labels). | 188 | without an `L` tag. For these vocabularies, all labels SHOULD include the namespace |
| 189 | (rather than mixing qualified and unqualified labels). | ||