Skip to content

Commit

Permalink
Specify docs with undefined terms MUST include related context.
Browse files Browse the repository at this point in the history
  • Loading branch information
msporny committed Jul 20, 2024
1 parent db6124b commit 257bd98
Showing 1 changed file with 9 additions and 4 deletions.
13 changes: 9 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3216,10 +3216,15 @@ <h4>Semantic Interoperability</h4>
</p>

<p>
Developers SHOULD NOT use the <a data-cite="JSON-LD11/#default-vocabulary">`@vocab`</a> feature in production as it can lead to
JSON term clashes, resulting in semantic ambiguities with other applications. Instead,
to achieve proper interoperability, developers SHOULD define all terms used by their
applications, as described earlier in Section [[[#extensibility]]].
A [=conforming document=] SHOULD NOT use the
<a data-cite="JSON-LD11/#default-vocabulary">`@vocab`</a> feature in production
as it can lead to JSON term clashes, resulting in semantic ambiguities with
other applications. Instead, to achieve proper interoperability, a [=conforming
document=] SHOULD use JSON-LD Contexts that define all terms used by their
applications, as described earlier in Section [[[#extensibility]]]. If a
[=conforming document=] does not use JSON-LD Contexts that define all terms
used, it MUST include the `https://www.w3.org/ns/credentials/undefined-terms/v2`
as the last value in the `@context` property.
</p>
</section>
</section>
Expand Down

0 comments on commit 257bd98

Please sign in to comment.