Conversation
Add machine-readable license `name` fields using Open Definition IDs per Data Package v2 spec. Fixes barley.json where description was in `name`. Spec: https://datapackage.org/standard/data-package/#licenses Licenses: https://licenses.opendefinition.org/licenses/groups/ckan.json
Add strptime format patterns to date/datetime fields for cross-framework validation compatibility. The spec's `format: "any"` is not implemented by frictionless-ts. Spec: https://datapackage.org/standard/table-schema/#date Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- cars.json: Miles_per_Gallon as `number` (has decimals, not integer) - flare.json: full schema with optional fields for tree structure - monarchs.json: commonwealth as explicit `boolean` type Spec: https://datapackage.org/standard/table-schema/#field Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Link to the actual Python script that generates this synthetic dataset. Spec: https://datapackage.org/standard/data-package/#sources Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- flare.json: document tree structure (root/branch/leaf node fields) - movies.json: document known data quality issues for teaching use - flights-airport.csv: consolidate duplicate source entries Spec: https://datapackage.org/standard/data-resource/#description Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…scriptions - Add missing schema for flare-dependencies.json with source/target fields - Clarify that source/target represent directed import dependencies - Update descriptions to explicitly reference the Flare visualization library Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Using 'uvx' can verify against a newer version of ruff than what is locked in 'uv.lock', causing formatting discrepancies with CI. Switching to 'uv run' ensures the locked version is used.
Updated datapackage.json and datapackage.md via 'npm run build'.
Update `_data/datapackage_additions.toml` to explicitly mark key fields as required in the schema definitions: - `flare.json`: `id` and `name` are now required. - `flare-dependencies.json`: `source` and `target` are now required. This establishes a strict data contract in the generated `datapackage.json`, improving documentation and allowing downstream tools to validate the integrity of these hierarchical datasets. See: https://datapackage.org/standard/table-schema/#field-constraints
dsmedia
changed the title
dsmedia
changed the title
domoritz
approved these changes
Feb 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
namefield) to all resource licenses for machine-readable complianceflare.jsonandflare-dependencies.jsonwith required field constraints%Y/%m/%d %H:%M) for validation compatibility with date fields (e.g. in validating with frictionless-ts)Miles_per_Gallonas number)uvx→uv runfor lockfile-consistent tool versionsNote: Some issues with Frictionless Data v2 validation tooling (Python and/or TypeScript) will need to be resolved before validation can be incorporated into this repo's CI.