-
Notifications
You must be signed in to change notification settings - Fork 5
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
parser does not raise Exception on missing "resources" #29
Comments
Hello Christian, Currently I am looking into this issue need your inputs for the below-mentioned clarifications: 1)When the Resource section is not available in the JSON file: As per my analysis in the existing source code, we are checking for Mandortory fields such as Resource, Spatial, contribution, etc. In the assert_1_3_metastring method: If mandatory fields are not present we are raising the exception with a specific message as shown in the below code snippet. 2)Assuming all the mandatory fields present in the JSON file, while parsing do I need to raise an exception if the content of the resource section is empty? or are there any mandatory values that should be present in the Resource section? |
@christian-rli could you help with above question? |
This is the description of the table name and column names (and types) in accordance with the datapacke specs |
According to our current JSON-schema spec, there are no mandatory fields in |
The field "resources" should be mandatory (This is also the specification for datapackages)
The text was updated successfully, but these errors were encountered: