Add repo structure to facilitate tracking examples and required schemas, instances & manifests, re-projected data, and scripts to create above.
Aa an OSDU demo developer, I would like a structure within this repo that facilitates tracking and creation of:
- example loading service manifests for OSDU type instances, reference data instances, master data instances, and WP/WPC instances
- type instances and associated schemas required for the demo
- master data types
- reference data types
- file types
- WP types
- WPC types
- instances and loading service manifests of above types
- master data instances
- reference data instances
- WP / WPC / File instances
- Re-projected file data
- aligned with WPC and File instance boundaries
- aligned with file types in Demo Script
Ideally I would like the structure of this repo and its associated READMEs to be a self-documenting example of the OSDU data preparation process.