@goksel @jakebeal @cjmyers @Gonza10V - @Yehuda-Binik and I were having a discussion about this and we would like to hear your thoughts on the SBOL3 to SBOL2 conversion for a SubComponent.

In the SBOL3 documentation, it states that "SBOL 2 Component, Module, and FunctionalComponent objects map to SBOL 3 SubComponent objects." How would one convert an SBOL 3 component object into an SBOL 2 object? What specific set of rules would there be?

This is going to be the most complicated one, because the SBOL3 Component may need to be split into two SBOL2 objects, both a ModuleDefinition and a ComponentDefinition.

Basically, all hasModel and hasInteraction information needs to go into a ModuleDefinition and all hasSequence and hasConstraint information needs to go into a ComponentDefinition. The features go into one or both of these, depending on which models, interactions, and constraints they participate in. Basically, it's going to be quite messy.

Fortunately, there are very few actual nature SBOL2 documents out there with ModuleDefinition objects, so mostly we just have to worry about being able to round-trip and can have difficult to understand cases go to an exception if need be. I would recommend starting by working the examples in the IWBDA 2023 notebook. If we can handle all of those, we'll be in pretty good shape for normal SBOL3 to SBOL2 conversion.