Closed ptsefton closed 7 years ago
:+1:
I would prefer a version
property, instead of datapackage_version
, because it could also be used for other objects such as schema
. I suggested that in #384.
I'm doing a PR that will add the following to all descriptors (Data Package, Data Resource, Table Schema):
"spec": {
"profile": "",
"version": ""
}
The spec version property was specifically removed in https://github.com/frictionlessdata/specs/issues/140. I'm dubious about adding to the spec as per discussion there. It is the kind of thing to add when we do our first major version (because then you maybe need it).
@pwalsh what you are proposing involves two changes (the adding of version and the change of profile to a different location). Can you open an issue for this if you are proposing doing it so we can discuss 😄
I would like to see us add a version
property immediately, applicable to v1. For a discussion on how I would like to see this added, see https://github.com/frictionlessdata/specs/issues/444
FIXED / DUPLICATE. I'm closing this as fixed as the answer (atm) is clear - there isn't one. Meanwhile #444 introduces a proposal for how to have this going forward with sensible defaults.
In the spec here https://specs.frictionlessdata.io/data-package/ there is no mention of a version property in the JSON although the document is versioned.
On this page: http://frictionlessdata.io/guides/data-package/ there is an example which contains this:
"datapackage_version": "1.0-beta",
This seems like a useful thing to have both for identifying datapackages and processing them reliably, is it meant to be part of the spec?