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
We have been considering the question of higher-level interactions in SBOL Visual, such as aTc repressing the repression of a TetR CDS on pTet. (See discussion on: SynBioDex/SBOL-visual#73).
The key question that we are hung up on right now is whether something can simultaneously be both an occurring entity and a participant role (e.g., both Inhibition (SBO:0000169) and Inhibited (SBO:0000642). I have come to believe this may be reasonable.
If we allow this, we will definitely be making a choice that is incompatible with the current SBOL data model, which does not support higher-level interactions at present. That might, however, instead be indicating a thing that we'd want to change in the data model, and indeed I've recently seen an example where it might make sense, in which an operator is regulating a genetic production relationship. This was indicated by giving a role to the operator, but it might be more elegantly represented by the operator controlling the interaction.
If we allowed this in SBOL3, the change would be to allow a Participant to be either a Feature or an Interaction. What do people think of this possibility?
The text was updated successfully, but these errors were encountered:
We have been considering the question of higher-level interactions in SBOL Visual, such as aTc repressing the repression of a TetR CDS on pTet. (See discussion on: SynBioDex/SBOL-visual#73).
The key question that we are hung up on right now is whether something can simultaneously be both an occurring entity and a participant role (e.g., both Inhibition (SBO:0000169) and Inhibited (SBO:0000642). I have come to believe this may be reasonable.
If we allow this, we will definitely be making a choice that is incompatible with the current SBOL data model, which does not support higher-level interactions at present. That might, however, instead be indicating a thing that we'd want to change in the data model, and indeed I've recently seen an example where it might make sense, in which an operator is regulating a genetic production relationship. This was indicated by giving a role to the operator, but it might be more elegantly represented by the operator controlling the interaction.
If we allowed this in SBOL3, the change would be to allow a Participant to be either a Feature or an Interaction. What do people think of this possibility?
The text was updated successfully, but these errors were encountered: