Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minor rewording re application of type-scoped contexts #445

Open
VladimirAlexiev opened this issue Nov 10, 2024 · 0 comments
Open

minor rewording re application of type-scoped contexts #445

VladimirAlexiev opened this issue Nov 10, 2024 · 0 comments
Labels
Editorial Used by the errata management ErratumRaised Used by the errata management

Comments

@VladimirAlexiev
Copy link

VladimirAlexiev commented Nov 10, 2024

In Scoped Contexts, the description of Type-Scoped Contexts has two notes (right after this note):

When expanding, each value of @type is considered (in code point order) where that value is also a term in the active context having its own type-scoped context. If so, that the scoped context is applied to the active context.

The values of @type are unordered, so if multiple types are listed, the order that type-scoped contexts are applied is based on code point ordering

I suggest to merge these two notes and make it more explicit that later contexts override earlier contexts;
and add a last sentence to say explicitly that @type must be present in the JSON-LD instance for type-scoped contexts to work:

When expanding, each value of @type is considered. If the value is also a term in the active context having its own type-scoped context, the scoped context is applied to the active context. If multiple @type types are present they are applied in code point order (since the values of @type are unordered), and terms defined in later scoped contexts take precedence. If no @type is present then no type-scoped contexts are applied.

@gkellogg gkellogg added ErratumRaised Used by the errata management Editorial Used by the errata management labels Nov 11, 2024
@gkellogg gkellogg moved this to Errata in JSON-LD Management Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial Used by the errata management ErratumRaised Used by the errata management
Projects
Status: Errata
Development

No branches or pull requests

2 participants