From 992b045aa7b7610d1c492dab717eb183094fec39 Mon Sep 17 00:00:00 2001 From: Jonathan Staab Date: Wed, 14 Jun 2023 09:43:03 -0700 Subject: [PATCH] remove delimiter recommendation --- 32.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/32.md b/32.md index 45cadbe7..b1473859 100644 --- a/32.md +++ b/32.md @@ -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).