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
Formalise schema #7
Comments
Some additional useful links from datasets/registry issue 201 referenced above
|
@iancoleman note that Table Schema has a pattern for adding units: frictionlessdata/specs#216. |
The JSON names are not in Pascal Case. If they were converted to PascalCase they would directly translate into classes better. Currently I get an automatic JSON conversion to a C# class that looks as follows. As you can see this is less than optimal from the var/method naming deserialization perspective.
|
Is it possible for the names to be in pascal case? This would make importing it more consistent and deserializing it directly to objects cleaner. |
I did some looking at conventions and the best I came up with (google JSON style guide) recommends camelCase. Would camelCase be ok or would you specifically prefer PascalCase? |
When the parser becomes a bit more mature it would be good to have a formal schema available
Something like http://json-schema.org/
I have a feeling there's still some bits and pieces that are inconsistent
eg I think percentage values are represented in two different ways
The text was updated successfully, but these errors were encountered: