refactor metamodel (m30ml & DOF schema) to build off LinkML

[capsulecorplab]

m30ml & DOF schema used for the sealion-mission-architecture should build off LinkML, as to be able to leverage LinkML's schema validator tools. DOF schema should also be extended as to including model elements (s.a., interfaces and junctions) for use in modeling and generating assembly instructions and/or architecture documentation.

Desired outcomes

• YAML schemas defining architecture modeling elements (i.e., stakeholder needs, user stories, data structure) that can be used for validating architecture model
• YAML schemas defining system model (components, interfaces, junctions, functions, and assembly steps) that can be used for validating system model
• Jinja2 templates for defining views from architecture and system model for generating documentation - s.a., spec docs (stakeholder needs, user stories, data structures, components, and their relationships), bill of materials (BOM's), purchase orders (PO's), assembly instructions, and/or N2-chart or interface-control documents (ICD's)

[capsulecorplab]

As per Jan 4 systems meeting, Turtle (TTL) models built from LinkML-OWL following pizza tutorial appear to primarily contain graph data about model vocabulary, not descriptions. i.e., can run a query for what TomatoTopping is a subclass of, but not which pizzas have TomatoTopping. Approach moving forward will be to define LinkML schemas in DOF-CubeSat (as an extension of m30ml to include architecture model elements) and use LinkML toolchain for schema validation as a precursor to building a unified model, then pipe unified model into templates for rendering views, such as architecture document, bill of materials, purchase orders, N2-chart / interface-control doc (ICD), and/or assembly instructions.