v2.5.0 planning

[rsdoiel]

This issue tracks the ideas I want to capture before starting the v2.5 release series.

[rsdoiel]

I want a working data model system for v2.5.0. This will improve the use of dataset web service's JSON API by ensuring JSON object validation before creating or updating objects. It would remove the requirement of writing middle ware for validation when building project on datasetd.

Two ideas I'm mulling over

1. Use something like GitHub Issue YAML template syntax for describing what the object should confirm two
   a. use this to auto-generate simple web forms as well as validate
   b. downside is I'd need to document/teach how to write GHIYTS
2. Use a WASM file with known function names to handle validation (essentially creating a validation plugin situation)
   a. this would allow the validation to be written in any language that can be compiled to WASM
   b. Other than documenting the what is required from the WASM module it shifts the object specification outside dataset
   c. It avoids requiring an object oriented approach to data validation (interface of the WASM module would define functions only)
   d. down side is this creates a plugin architecture which then blurs the separation of concerns in the web application
   e. down side is that modeling data now requires knowledge of a WASM target langauge and how all that appendage