You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
oml has more modeling capabilities for modeling concepts, s.a., mission objective to component mapping, metrology (including measurements for mass budget analysis), interfaces & junctions, as well as file-based model exchange & querying capabilities, allowing for use with our current templating toolchain for generating textual and/or graphical documents. The oml-tutorial & firesat-example can also serve as a reference implementation for SeaLion's architecture modeling purposes.
The text was updated successfully, but these errors were encountered:
primarily want to adopt ontology vocabularies from oml patterns as to be able to model interfaces and junctions, but vocabularies should be expressed in YAML using linkml schemas, as current architecture is already expressed in YAML. Current approach under consideration is to write a version of the m30ml metamodel using linkml-owl schemas, as to be able to map to OWL/RDF, then use SPARQL queries from OML patterns (s.a., from pattern 8) to extract contents of the model
oml has more modeling capabilities for modeling concepts, s.a., mission objective to component mapping, metrology (including measurements for mass budget analysis), interfaces & junctions, as well as file-based model exchange & querying capabilities, allowing for use with our current templating toolchain for generating textual and/or graphical documents. The oml-tutorial & firesat-example can also serve as a reference implementation for SeaLion's architecture modeling purposes.
The text was updated successfully, but these errors were encountered: