Skip to content

Project

The current state of the project: what is implemented, what is known to be missing, and how a release is produced.

The conformance records below are engineering records rather than user documentation: they state what each oracle measures, which divergences are deliberate, and which rows are still open. Where the divergence census still keys its rows by a short row number, that number is a cross-reference within these records and means nothing outside this repository.

  • Spec compliance — faithful, approximate, or not implemented, rule by rule
  • Training examples — the OMG corpus, adjudicated per file
  • Pilot corpora gate — OpenSysML diagnostics on the three pinned OMG pilot corpora, ratcheted in CI
  • RDF corpus round-trip gate — the notation → Turtle → notation → Turtle verdict of every model under examples/, ratcheted per file in CI
  • PSSM migration gate — the SysML v1 migrator over the OMG PSSM test suite: the notation asserted to parse, the report's verdict totals ratcheted in CI
  • Pilot differential — OpenSysML diagnostics compared against the OMG pilot implementation, advisory
  • Spec-vs-pilot gap register — places where OpenSysML's behaviour rests on the pilot or on no clause, ranked by modeler impact, with the question each puts to the specification authors
  • Pilot execution referee — how far the pinned pilot's execution surface reaches, and which behavior rows it can adjudicate
  • PSSM referee — the OMG PSSM state-machine test suite, translated by rule into SysML v2 notation and run against the runtime as an advisory oracle, its bucket counts gated in CI; never evidence of SysML v2 conformance
  • fUML referee — the fUML reference implementation's activity tests as an advisory oracle for the action executor: how the pinned models, jar and expected-record are provisioned, the rules that translate each activity, the output-value oracle, and the adjudication of every row's bucket
  • Behavior semantic oracle — action and state-machine conformance cases whose expected outcomes are derived by hand from the Kernel Semantic and Systems Library text rather than recorded from the executor, and the three the executor fails
  • Pilot Xpect expectations — the pilot's own inline .xt assertions as a declared-intent oracle, advisory
  • Grammar coverage — which OMG grammar productions the project's inputs exercise, judged by whether an input for each exists, advisory
  • Validation-constraint census — which of the pilot's named validation constraints OpenSysML reports, each mapped to the pass and message that reports it, with a violating model as evidence; the figures and the name list are gated in CI
  • Adjudications — the divergences from the pinned pilot implementation we keep, the rows still open against it, and the reading behind each one
  • Protocol state machines — whether SysML v2 has a construct for UML's protocol state machine, which of its guarantees an exhibited state machine on a port or part already gives at run time, and the runtime follow-up that is left
  • Element-scoped tier gating — how a pass opts out of document-wide skipping and gates itself per subject, and what that measured
  • Declared errata overlay — how a defect in the published reference material is declared, cited and applied to what the oracles read a second time
  • Lossless library records — the record format and version-compatibility surface roadmap L3 needs, the measurements that chose it, and the rows it leaves open
  • Expansion regions — whether a multiplicity on a performed action usage fed by a flow is SysML v2's spelling of concurrent per-element performance, adjudicated against the specifications, the library, the corpora and the pilot, and closed: the iterative form is for, the parallel form is not SysML v2
  • Bitwise complement — whether the unary ~ has a meaning a runtime can give it, adjudicated against the specification, the Kernel Function Library, the corpora and the pinned pilot, and closed abstract-only: the runtime keeps its typed refusal and the checker warns on every use
  • Exception handlers — whether SysML v2 spells an exception handler or exception propagation, adjudicated against the specifications, the library, the corpora and the pilot, and closed as not a SysML v2 construct, with the idiom that covers the need — a result routed by decide, or a failure signal accepted beside the work and a terminate
  • Exact-rational evaluation — whether the evaluator should compute Real/Rational arithmetic exactly rather than in binary64, adjudicated against the pinned pilot and the specification text, and declined
  • HTML document backend — the design for rendering documents as semantic, styleable HTML straight from the document IR
  • View rendering forms — the view engine's writers over one rendering tree: why Graphviz DOT is offered next to Mermaid, what the DOT writer emits, and the surfaces that accept it
  • OOSEM library — the object-oriented systems engineering method as a bundled OpenSysML library: what it defines, what it reuses from the standard domain libraries, and the prior art it was checked against
  • MOSA library — the Modular Open Systems Approach as a bundled OpenSysML library: the statute's vocabulary, openness as metadata over the standard model, the interface control document and the warning-only checks
  • Performance: 0.9.1 against 0.9.0 — the release-gate measurement of the 0.9.1 line against the previous release: every benchmark on both revisions, whole-binary scaling, and each regression fixed or priced; the 0.8.0 against 0.7.0, 0.6 against 0.4.2 and 0.5 against 0.4.3 records precede it
  • Roadmap — the known gaps, in the order they should be picked up
  • Nightly snapshots — the prerelease built from develop every night: where it is, what it contains, and how to verify one
  • Releasing — the pre-tag gate, tagging, artifacts, Homebrew
  • macOS distribution — Gatekeeper and the signing decision
  • Bugs in the OMG materials — defects in the vendored specification libraries
  • Demo — a scripted walkthrough of the whole surface