From 9e7c7e4c91d238dba7a33e8295bc67593a5b2be5 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Mon, 15 Jul 2024 10:28:59 -0400 Subject: [PATCH] Fine tune guidance on `@vocab` usage. Co-authored-by: Gabe <7622243+decentralgabe@users.noreply.github.com> --- index.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index d1d799280..2bd154ff0 100644 --- a/index.html +++ b/index.html @@ -4445,8 +4445,9 @@

JSON-LD

While this specification cautions against the use of `@vocab`, there are legitimate uses of the feature, such as to ease experimentation, development, and localized deployment. If an application developer wants to use `@vocab` in -production — even though strongly advised against — they are urged to understand that -any use of `@vocab` will disable reporting of "undefined term" errors, and +production, which is advised against to reduce term collisions and leverage the benefits +of semantic interoperability, they are urged to understand that any use of `@vocab` will +disable reporting of "undefined term" errors, and later use(s) will override any previous `@vocab` declaration(s). Different values of `@vocab` can change the semantics of the information contained in the document, so it is important to understand whether and how these changes will affect the