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
Remove satellite-specific hardcoding: sysml_to_rdf.py has canonical state variable and parameter lists (lines 54-67) specific to the satellite model. The generic pipeline should derive these from @gds* metadata only.
Unit mapping table: The unit→TypeDef mapping (lines 34-51 in sysml_to_rdf.py) should be configurable, not hardcoded
Summary
Port the working SysML v2 → GDS pipeline from
unity-GDS-experimentsintogds-coreas the foundation for thegds-sysmlpackage (#188).What exists in unity-GDS-experiments
sysml_parser.pysysml_to_rdf.pyspec_builder.pysysml_validator.pysimple_satellite.sysmltest_rdf_roundtrip.pytest_spec_builder.pyTotal: 194 tests passing, pipeline produces a GDSSpec with 7 blocks, 20 state variables, 14 parameters.
What needs to change during port
gds_lifecycle.sysml_parser→gds_sysml.parser.regexsysml_to_rdf.pywith SPARQL CONSTRUCT queries (Research spike: OSLC SysML v2 → GDS ontology SPARQL CONSTRUCT mapping #189) — or keep as initial implementation and refactor latersysml_to_rdf.pyhas canonical state variable and parameter lists (lines 54-67) specific to the satellite model. The generic pipeline should derive these from @gds* metadata only.sysml_to_rdf.py) should be configurable, not hardcodedsimple_satellite.sysmlas a test fixture, add at least one non-satellite modelAcceptance Criteria
simple_satellite.sysmlproduces identical GDSSpec (29/29 + 6/6 checks)gds-sysmlin workspaceDependencies