Skip to content

fix(schemas): duplicate description key on V2 DetailedDefinition.examples#70

Merged
ronaldtse merged 1 commit into
mainfrom
fix/v2-localized-concept-duplicate-description
Jul 5, 2026
Merged

fix(schemas): duplicate description key on V2 DetailedDefinition.examples#70
ronaldtse merged 1 commit into
mainfrom
fix/v2-localized-concept-duplicate-description

Conversation

@ronaldtse

Copy link
Copy Markdown
Member

The V2 localized-concept.yaml schema has a duplicate description key on detailed_definition.examples. The new scoped-examples description (added in v3.1.0 for the VIM 1993 nesting feature) was committed on top of the existing sources description, which had drifted onto the wrong field.

Strict YAML parsers (e.g. the yaml package's default mode used by glossarist.org's bundle-schemas script) reject this as DUPLICATE_KEY, breaking the website's build.

This PR moves the bibliographic description to its intended home on sources (matching the V3 schema shape) and keeps the scoped-examples description on examples.

Discovered by glossarist.org CI while syncing to v3.1.0 (PR #59).

…ples

The VIM 1993 scoped-examples feature added a 'description' for the new
examples field on detailed_definition, but the original description
('Bibliographic references for this particular definition of the concept')
was left behind — producing two 'description' siblings under the same
mapping, which strict YAML parsers (e.g. js-yaml's default mode used by
glossarist.org's bundle-schemas script) reject as DUPLICATE_KEY.

Move the bibliographic description to its intended home on 'sources'
(matching the V3 schema shape) and keep the scoped-examples description
where it belongs.
@github-actions

github-actions Bot commented Jul 5, 2026

Copy link
Copy Markdown

Release reminder

This PR touches ontologies/ or schemas/. After merge, a new
tag should be cut per the semver policy.

Checklist:

  • Determine the semver bump (MAJOR / MINOR / PATCH)
  • Update RELEASE_NOTES.md with consumer-facing impact
  • Move [Unreleased] entries in CHANGELOG.md to the new version
  • Cut the tag after merge: git tag vX.Y.Z && git push origin vX.Y.Z

The tag push will trigger release.yml to create the GitHub Release.

If this PR is doc-only or CI-only within those paths and does NOT
warrant a release, dismiss this reminder.

@ronaldtse
ronaldtse merged commit ac33d5f into main Jul 5, 2026
10 checks passed
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.

1 participant