You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our data package examples we should ensure compliance with the specs at https://specs.frictionlessdata.io/data-package. For instance, "name": "objectsTable" is not valid because "name" cannot contain uppercase characters, so the value might be changed to "objects_table". Validity can be checked with:
ValidationError: u'objectsTable' does not match u'^([a-z0-9._-])+$'
Failed validating u'pattern' in schema[u'properties'][u'resources'][u'items'][u'properties'][u'name']:
{u'description': u"An identifier for this package. Lower case characters with '.', '_' and '-' are allowed.",
u'pattern': u'^([a-z0-9._-])+$',
u'title': u'Name',
u'type': u'string'}
On instance[u'resources'][0][u'name']:
u'objectsTable'
Ensuring that generated data packages will be compliant is trickier, because we'd need to perform the same checks that datapackage does on configuration files etc. Rather, it should be the user's responsibility to check that any setting that will end up in a restricted data package field is compliant with the corresponding specs.
The text was updated successfully, but these errors were encountered:
@danfowler thanks! Another thing I'm wondering about is whether there is a way to know which version of the specs a given version of the Python API is implementing (and if older specs are still available).
In our data package examples we should ensure compliance with the specs at https://specs.frictionlessdata.io/data-package. For instance,
"name": "objectsTable"
is not valid because "name" cannot contain uppercase characters, so the value might be changed to "objects_table". Validity can be checked with:And here's the error for the above case:
Ensuring that generated data packages will be compliant is trickier, because we'd need to perform the same checks that
datapackage
does on configuration files etc. Rather, it should be the user's responsibility to check that any setting that will end up in a restricted data package field is compliant with the corresponding specs.The text was updated successfully, but these errors were encountered: