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

Non-IRI extension identifier and reference keywords? #1309

Closed
handrews opened this issue Sep 22, 2022 · 1 comment
Closed

Non-IRI extension identifier and reference keywords? #1309

handrews opened this issue Sep 22, 2022 · 1 comment
Labels

Comments

@handrews
Copy link
Contributor

I've filed issue #1304 and #1305 regarding IRI usage and extension keywords.

As discussed in #1140, we are likely to move $dynamic* to using non-IRI identifiers. This is an architectural change from needing to maintain a mapping of IRIs to schemas (or resolve them on demand) to needing to maintain (or resolve on demand) a mapping of an arbitrary keyword+value. For $dynamic*, this involves dynamic scope associations and lookups, but we could conceive of lexical identifier/lookup behavior as well.

This is not about whether we should allow or forbid dynamic behavior. This is about whether we should support assigning identifiers and looking them up in general for extension keywords. If we do think that this is worth supporting, we can further discuss dynamic vs static/lexical behaviors. But there's no need if we can't come up with use cases that make this worth supporting at all.

@handrews
Copy link
Contributor Author

Closing in favor of the referencing discussion, can be re-filed if needed once that resolves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant