Skip to content

Use unaltered prefixed terms with term definitions - #623

Open
niklasl wants to merge 1 commit into
developfrom
feature/valid-context-term-definitions
Open

Use unaltered prefixed terms with term definitions#623
niklasl wants to merge 1 commit into
developfrom
feature/valid-context-term-definitions

Conversation

@niklasl

@niklasl niklasl commented Sep 3, 2026

Copy link
Copy Markdown
Member

Specifically define some bibdb: and ls: prefixed names as always being used with language containers.

Some notes:

  • JSON-LD 1.1 prohibits defining prefixed names where the expanded IRI differs between term (key) and actual @id (see step 14.2.4.2 of https://w3c.github.io/json-ld-api/#create-term-definition).
  • Previously, "virtual" prefixed terms with our convention for language containers where defined (by adding a ByLang to the local name).
  • Our convention still works for @vocab-resolved names, since there is no rule against that ("all bets are off" for regular keys), but prefixed names (presumably) signal a specific meaning).
  • If need be, we could define other compact terms without prefixes (or at worst define owl:sameAs IRIs and map to names actually containing the ByLang convention; that could be more confusing though).

Specifically define some `bibdb:` and `ls:` prefixed names as always
being used with language containers.

Some notes:

- JSON-LD 1.1 prohibits defining prefixed names where the expanded IRI
  differs between term (key) and actual `@id` (see step 14.2.4.2 of
  https://w3c.github.io/json-ld-api/#create-term-definition).
- Previously, "virtual" prefixed terms with our convention for language
  containers where defined (by adding a `ByLang` to the local name).
- Our convention still works for `@vocab`-resolved names, since there is
  no rule against that ("all bets are off" for regular keys), but
  prefixed names (presumably) signal a specific meaning).
- If need be, we could define other compact terms without prefixes (or
  at worst define `owl:sameAs` IRIs and map to names actually containing
  the `ByLang` convention; that could be more confusing though).

@kwahlin kwahlin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Let's merge together with libris/lxlviewer#1681 when we've verified that nothing else breaks.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants