v3 dataset planning

[rsdoiel]

It'd be nice to do another major release with these properties.

• YAML input/output support for storing object or retrieving objects in our dataset collections
• libdataset should be implemented as a WASM module for integration with other languages in addition to shared C libraries
• Simplify the sql storage module, cleanup interfaces
• Allow dataset collections to include TypeScript and WASM modules for a crates like experience of collection as website

[rsdoiel]

Revised thinking for v3

• adopt a read/write model for interaction in the cli and in the web service
  • decide if I need to still support REST?
• simplify codebase focusing on core verbs (e.g. read, write, remove, purge, keys and query)
• attachments need to be organized on disk using OCFL and OR-crates approaches, they need to have similar but unique verbs for working with attachments (maybe attach, retrieve, detach, prune and list)
• automatic versioning on metadata objects and attachments
• make code easy to port to other languages
  • avoid the need for libdataset or wasm targets
• load and dump should have the ability to respect version histories for JSON documents
• attachments will not be supported by load and dump since using OCFL and OR-crates directory structure should allow for other tools to curate the attachements if needed outside of dataset.