We would need to add schemas to our API design in an intuitive way
Questions
Do we need Table Schema? Can we just have people define their data schema/dictionary with JSON Schema given extreemly broad constraints (the schema defines a simple array of objects)?
There were a lot of false starts for this in DKAN 1, but we want to get this right in DKAN2. Schemas for Datasets provide value in several areas:
Implementation details
Based on conversations so far, a rough spec might look like:
Questions