Frictionless Standards (v2). Live Tracker

[roll]

It’s a live tracker of the Frictionless Standards (v2) work. All the new change proposals will be posted here on a weekly basis. The Data Package Working Group members will be notified of every update (please manage your issue subscription options if you want to unsubscribe from emails)

[pwalsh]

I'd be interested to join the working group

[roll]

@pwalsh
Amazing to see you joining! I added you to the WG team

[akariv]

@roll I'd also be happy to be part of the group. Thanks!

[roll]

@akariv
Amazing! Added you to the team

[nichtich]

I'd like to contribute to cleanup of Table Schema specification.

[roll]

Hi @nichtich,

Would you like to join the Working Group?

[roll]

Dear @frictionlessdata/data-package-working-group

Today's update is tiny as we didn't manage to start working on the specs issues in December but we will in January. So the only news is that Contribution Guide has been released - #857

[nichtich]

@roll wrote:

Would you like to join the Working Group?

Yet, please!

[johanricher]

I'd like to join the working group, please. 🙂

[martindurant]

The intake project is interesting in watching this and contributing, please include me.

[roll]

Dear @frictionlessdata/data-package-working-group,

Here is the first update of the new version of the standard work. Please take your time voting and reviewing the proposals as it's meant to be at the comfortable pace for everyone (cc @sapetti9).

Proposals

Please vote on the following pull requests by using a 👍 (yes), 👎 (no), or 👀 (neutral) reaction or a comment. Please suggest changes if you think that the pull request needs to be updated

• Query protocols extended #6
• Nicer theme #7
• Create Data Formats page and move over existing material #9
• first pass at documenting diff formats for data #10
• Add HTML microformats to Web-Oriented Data Formats #11
• Simple Data Format v0.1 - Discussion #12
• Simple data format: metadata file format? #13
• Grammar issues in CouchDB replication doc  #15
• s/teh/the/ #16
• Question: Differences between sdf schema and json-schema #17

Discussions

Please review, comment or participate in duscussions

• Proposed to close as wontfix - Hash should be an object? #379
• Proposed to close as wontfix - Allow any type for true/falseValues? #621
• Proposed to close as wontfix - If the folder name starts with a dot(.), the result of path pattern check is true negative #802
• Please review a new pattern - Add pattern - Table Schema: Relationship between Fields #859

Updates

Minor changes just for your information

• Fixed missed version property in the package profile - Version property missing in package.yml #631
• Fixed mixed keywords formatting - Mixed usage of MUST/SHOULD keywords with and without `` #534
• Created an ordered list of feature requests - Vote for your favorite feature request #863
• Fiscal Data Package as a domain-specific extension moved to its own project - https://github.com/frictionlessdata/datapackage-fiscal
• Fixed duration constraints - min/max constraint missing for Duration - where's the definitive list of constraints by type? #528
• Fixed geopoint wording - Geopoint coordinates: integer or floating-point #655
• Completed reviewing and triaging existent issues - Review and triage current backlog of specs issues #778

---

Here are linkable categories:

• https://github.com/frictionlessdata/specs/labels/Specifications (related to 2 or more specs)
• https://github.com/frictionlessdata/specs/labels/Data%20Package (related to Data Package spec)
• https://github.com/frictionlessdata/specs/labels/Data%20Resource (related to Data Resource spec)
• https://github.com/frictionlessdata/specs/labels/Table%20Dialect (related to Table Dialect spec)
• https://github.com/frictionlessdata/specs/labels/Table%20Schema (related to Table Schema spec)
• https://github.com/frictionlessdata/specs/labels/Metadata%20Profile (related to Metadata Profile spec)
• https://github.com/frictionlessdata/specs/labels/Extensions (extensions ideas/discussions)
• https://github.com/frictionlessdata/specs/labels/Patterns (patterns and best practices)
• https://github.com/frictionlessdata/specs/labels/Guides (the rest of the documentation)

PS.
Sorry for the long message, it was a first iteration I tried to cover as mush as possible "small changes" to free up the time for more important things in the future updates

[peterdesmet]

@roll, maybe it's just me, but for reviewing (future) proposals, I'd want to use an emoji to indicate neutral support (in addition to 👍 and 👎). Unfortunately GitHub only offers a limited option, maybe 👀 can be used to indicate "seen it, don't have a strong opinion"?

[roll]

@peterdesmet
No, it's not only you as it's the same at least for me 😄. I think 👀 is a great suggestion -- let's use it!

PS.
I updated the wording for proposals "Please vote on the following pull requests by using a 👍 (yes), 👎 (no), or 👀 (neutral) reaction or a comment. Please suggest changes if you think that the pull request needs to be updated" (also adding regarding proposing changes)

[roll]

Dear @frictionlessdata/data-package-working-group,

First of all, I want to thank all of you for participating in the discussions! It's really amazing to see so many great and insightful people dedicating their own time to the work on the standard. I think we're making great progress! Unfortunately, I'm away till the next week, so I'm going to join the discussion when I'm back, as well as preparing new proposals.

👏

[PietrH]

Could you add me to the list? I didn't get an invite to the community call and can't make it. I would love to be there next time!

[sapetti9]

Hi @PietrH I added your @inbo address to the mailing list, and will invite you to the calls from now on. I would also encourage you to join the community chat if you haven't yet.

[roll]

Dear @frictionlessdata/data-package-working-group,

Here is an update of the new version of the standard work. Please take your time voting and reviewing the proposals as it's meant to be at the comfortable pace for everyone.

Proposed

• Refine has moved #18
• Dataprotocols has moved #19
• Sort out hosting so we do not have /en/latest in all the urls #20
• [JTS] Primary Key / ID attribute support in JSON table schema #21
• Foreign Key attribute in JSON schema #23
• CSV Params standard #24

Accepted

• Add HTML microformats to Web-Oriented Data Formats #11
• Nicer theme #7
• Grammar issues in CouchDB replication doc  #15
• first pass at documenting diff formats for data #10

Rejected

• Simple Data Format v0.1 - Discussion #12
• s/teh/the/ #16

Closed

• Hash should be an object? #379

[roll]

Dear @frictionlessdata/data-package-working-group,

Here is an update of the new version of the standard work. Please take your time voting and reviewing the proposals as it's meant to be at the comfortable pace for everyone.

Proposed

• teh -> the #27
• Added data transmission info #28
• Support Categorical Variables in JSON Schema #29
• Clarify DataPackage File Info Section #30
• Hosted Set of Examples #31
• Files should have a required name (or id) attribute #32
• Interactive guide to datapackage.json #33
• Add additional detail of potential fields describing data files in Data Package spec #34

Rejected

• [JTS] Primary Key / ID attribute support in JSON table schema #21

---

If you have some time, please take a look at some pull requests that are still both not accepted and not rejected (link with oldest PRs first). Note, that currently we need 7 votes yes to accept the change otherwise we will have to close a PR before the release. Next week, I'm going to work on the requested changes as well to update the PRs that are supported in-principle but require some implementation updates

[roll]

Dear @frictionlessdata/data-package,

Based on the first month's work experience, we added an additional tier to the Working Group structure -- the advisory group. Obviously, participating in the weekly-votings is time-consuming, and it will be great to have the ability to have more great people in the working group but without asking them to actively vote. As the decision-making system is based on the quorum concept we really need to have only active members in the voting category so let's discuss an exact mechanism of how people can change their WG tier on this week community call 🚀

Currently, the structure is as below (note that @nichtich's and @ezwelty's invite to the voting group is pending), making it 9 voting group members and 6 votes for a quorum (updated). Please let me know if you'd like to change your tier on GitHub or on the community call! As mentioned before the veto group is reserved for core Data Package implementation representatives. Also, we already added the first version of the governance document to the website which is now are ready for comments - https://datapackage.org/standard/governance/

[ezwelty]

@roll I'd be interested in being part of the working group (with the power to vote, I suppose?). I've already gone rogue and voted sporadically on some of the proposed issues.

Note that the link to the working group members (in the original post of this thread, and at https://datapackage.org/standard/governance/) is broken:
https://github.com/orgs/frictionlessdata/teams/data-package-working-group/members?query=

[roll]

@ezwelty
Amazing! It will be great to have you! I've sent the invite and fixed the link

[nichtich]

@roll could you also please resend my invite? I seem to have missed it.

[roll]

Dear @frictionlessdata/data-package,

Thanks for a productive week towards Data Package (v2) and a great community call! Here is a traditional weekly update:

Active votings

You can track a live version using this link

• Sort out hosting so we do not have /en/latest in all the urls #20
• Added data transmission info #28
• Refine has moved #18
• Add additional detail of potential fields describing data files in Data Package spec #34
• Fix spelling in data-packages.rst #38
• Simple data format: metadata file format? #13
• Support Categorical Variables in JSON Schema #29
• DP - field "hash" in resource information is unclear. #41
• Table schema for geojson feature properties #39
• Data package standard is not versioned #40

Drafts for discussion

• I18N and Metadata Translations for Data Package #42
• Question: Differences between sdf schema and json-schema #17

Accepted

• Query protocols extended #6
• CSV Params standard #24
• Dataprotocols has moved #19
• Foreign Key attribute in JSON schema #23
• Clarify DataPackage File Info Section #30
• teh -> the #27

Rejected

• Create Data Formats page and move over existing material #9
• Hosted Set of Examples #31
• Discussion of Catalogs re Data Packages #37

Closed

• New property requiredResources #823

[roll]

Dear @frictionlessdata/data-package,

Thanks for the finished Data Package (v2) draft release!

Accepted

• Fix spelling in data-packages.rst #38
• Added data transmission info #28
• Support Categorical Variables in JSON Schema #29
• Table schema for geojson feature properties #39
• Simple data format: metadata file format? #13
• Refine has moved #18
• DP - field "hash" in resource information is unclear. #41

Rejected

• Add additional detail of potential fields describing data files in Data Package spec #34

[roll]

Dear @frictionlessdata/data-package,

Here is a weekly update for the Data Package (v2) work. We now have proposals for almost all the outstanding issues; please take a look at them. On this month's community call, we will have time to discuss everything we need regarding the last chunk of possible changes.

Proposals

• datapackages - title element - SHOULD or MAY #48
• I18N and Metadata Translations for Data Package #42
• Data Packages name descriptor #49
• Documentation - datapackages - optional fields #50
• Simple data format docs - label #51
• datapackage JSON illustrative example: make name a valid name #52

[roll]

Dear @frictionlessdata/data-package,

Here is an end-of-April update of the Data Package (v2) work.

Proposals

The last bits of changes we're discussing for v2:

• Data Packages name descriptor #49
• datapackages - title element - SHOULD or MAY #48 (Add specification of invariance of name field #62)
• String Encoding #57 (please vote for this one. It's small and seems to be more like a fix)

Accepted

• Documentation - datapackages - optional fields #50
• I18N and Metadata Translations for Data Package #42
• datapackage JSON illustrative example: make name a valid name #52
• Simple data format docs - label #51

Software

A new CKAN extension - https://github.com/frictionlessdata/ckanext-datapackage - focuses only on one thing (Data API) and hopefully does it well (similarly to ckanext-dcat).

[roll]

Thanks, everyone! The Data Package (v2) is going to be released today! We will post the update in the announcement issue #854 to notify all the contributors.