Repository navigation
data dictionary - dcat-us:describedBy #220
Description
The data dictionary should be an extended JSON Schema file, using additionalProperties to capture non-standard JSON Schema elements.
Since there is no widely deployed standard for Data Dictionaries, we should create our own.
However, we should still hew closely to related standards like DDI to ensure wider adoption.
Activity
jqnatividad commentedon May 19, 2026
This will wait until
describegpthas been updated to save Data Dictionaries in jsonschema format.jqnatividad commentedon May 19, 2026
Deferring this work until qsv issue #2373 lands — i.e., until
qsv describegptproduces JSON Schema output natively.Rationale: building DP+'s data-dictionary-as-extended-JSON-Schema on top of
describegpt's current output shape would mean writing (and then throwing away) a conversion layer once qsv emits JSON Schema directly. The cleaner sequence is:describegptreturns JSON Schema withadditionalPropertiesfor non-standard fieldsjobs/stages/ai_suggestions.py— currently parses theDictionary/Description/TagsPascalCase envelope per fix(ai-suggestions): real-qsv schema + CLI flag corrections (PR #301/#302 follow-up) #303)dcat-us:describedByKeeping this issue open and unblocked-pending-upstream. Will revisit when qsv ships the schema output.