Evaluate the Generation of Go Types from Metaschema

[brandtkeller]

A recommended approach to mature implementations of OSCAL ingestion is through the generation of types from OSCAL's metaschema: seen here

gocomply/metaschema is one such implementation that has done this historically - although it looks unmaintained and out of date.

Would like to evaluate understanding the gocomply implementation and possibly contributing to bringing it up to date. Otherwise looking to write new logic that could be folded into this project to support golang oscal support in a maintained fashion.

[brandtkeller]

Review https://github.com/Credentive-Sec/metaschema-python/tree/main

Intent: Possible collaboration on the generation front to have a separate project own the code-generation while go-oscal positions itself as the exported library. Greater adoption on a multi-language code generator may mean for project resiliency and ability to adapt to changes in OSCAL in the long-term.