Introduce the ability to generate LabOP files for a Lab Compiler protocol - #14
Merged
Merged
Conversation
marpaia
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every compilation now includes
protocol.labop.ttl, generated directly from the captured protocol plan.lab.labop.export()also exports a protocol or its captured snapshot independently. The compiler continues to accept onlyProtocol; this PR adds no input wrappers or dispatch types.Depends on #13 (SBOL Provenance). This PR targets
marpaia/sbol-provenanceto keep its diff focused; merge #13 first, then retarget this PR tomaster.The exporter covers the current operation vocabulary, preserves SBOL design references, and produces deterministic RDF. It bundles only the three upstream primitives it uses, with pinned source checksums and attribution. Operations without an upstream equivalent use documented extension terms. Export runs offline; a separate validation script checks the output against the full pinned upstream schemas.
This is prospective protocol export. It does not model execution records or claim general executable compatibility with every LabOP consumer.
Review size against
marpaia/sbol-provenance: 1,398 changed lines (1,396 additions, 2 deletions), including tests, documentation, and bundled RDF resources.Local validation: 170 tests passed with robot SDKs, Ruff and mypy passed, cloning/transformation/export examples ran, and fresh wheel/source-distribution installations passed the install checks. Strict distribution metadata checks passed. Assembly, transformation, and plating exports each validated against the full pinned upstream schemas with zero errors and zero warnings. Remote CI is separate from these local results.