Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release cycle of the specs #671

Closed
roll opened this issue May 4, 2020 · 1 comment
Closed

Release cycle of the specs #671

roll opened this issue May 4, 2020 · 1 comment
Assignees

Comments

@roll
Copy link
Member

roll commented May 4, 2020

The specs is the cornerstone for all the FD related software/data project. I think it's very important for any standard to define and publish as many governance details as possible. Probably the versioning is the most important at the current stage.

In my opinion, the versions of the specs should be very discrete (for example no v1.4.3) and well-emphasized in the docs. For example:

  • only v1 / v2 as in jsonschema - one release per a few years
  • something like ecmascript v2019 / v2020 - one release per year

I think it will not be possible to build a stable software eco-system on top of the specs if it changes too often.

References:

@rufuspollock
Copy link
Contributor

We're generally keeping the specs pretty stable so more like json schema approach. More details can be covered in frictionlessdata/frictionlessdata.io#524

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants