This repository has been archived by the owner on Oct 28, 2024. It is now read-only.
Promote "Metadata in Table Schema" recipe to the specs. #63
Conversation
This file contains 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
Bumps [csv-parse](https://github.com/wdavidw/node-csv-parse) from 1.3.3 to 4.6.5. - [Release notes](https://github.com/wdavidw/node-csv-parse/releases) - [Changelog](https://github.com/adaltas/node-csv-parse/blob/master/CHANGELOG.md) - [Commits](adaltas/node-csv-parse@v1.3.3...v4.6.5) Signed-off-by: dependabot[bot] <[email protected]>
Add uniqueNulls property to unique constraints pattern - refs #593.
Security outline.
allow FK references to different data packages (fix #653)
Remove pattern constraint from number/integer/yearmonth schemes
[yml][s]: CI build and deploy specs #412.
…abular-data-resource/#csv-dialect), Dialect should bei either a JSON object or a file reference.
… JSON schema definition for `dialect` to allow object and string not just object. Data Resource JSON schema definition for `dialect` seems to contradict specification
…pears at the start - refs #254. Merge pull request #662 from chrispomeroyhale/registery/commentChar.
Merge pull request #668 from AntoineAugusti/patch-1
…le markdown - as per plan in frictionlessdata/frictionlessdata.io#413.
Also move specs folders up from specs to base directory and standardize frontmatter.
… default vuepress green color to #1A98FF
… copied from the old FD website).
|
Hmm, git is all out of wack it seems. The repository has moved and the access rights have changed. Let's wait until the v2 dust has settled. Still to do on this PR:
|
|
Thanks for your patience @pierrecamilleri 😄 |
* Added the announcement * Update content/docs/index.mdx Co-authored-by: Peter Desmet <[email protected]> * Update content/docs/index.mdx Co-authored-by: Peter Desmet <[email protected]> * Added a release blog post * Fixed linting --------- Co-authored-by: Peter Desmet <[email protected]>
* Added seo descriptions * Added back-to-top * Removed react * Removed unused comments
|
@@pierrecamilleri |
…data-package/resource (#960) * Fix anchor to $schema * Fix incorrect links in CHANGELOG * Use active tense and correct error * Explain what happened to `tabular-data-resource` * Indicate that Tabular Data Package was removed * Clarify that $schema allows extension and versioning Note: it did not replace profile in table-schema and table-dialect. That property was not present in v1 * Update header cf `field.missingValues`
This reverts commit cc10899.
This reverts commit 8cfb654.
6 tasks
|
I rebased this PR on the datapackage repo (see link right above). Only conflict I had was the moved changelog, hope nothing else has broken. I also moved the checklist in the pull request description. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Context and related issue :
fix #899
Details
I tried to be as clear as possible in the constraints associated to the different metadata.
I chose to make a specific section for these properties, as they specifically refer to the schema and not to the data the schema describes, contrary to the other top schema properties. One may argue that the "$schema" property can also be seen as metadata, and could be moved into this section. What do you think ?
I see two points worth mentioning, as they differ from what was in the recipe :
versionfield and impose semantic versioning (with or without "v" prefix)nameproperty, and disallows the underscore "_" character. This is aiming at a more URL-friendly name. The current implementation of frictionless allows this character, but as the property was to my knowledge not in the specs, I don't think this can be considered a breaking change.I'm happy to listen to any requests for modifications.