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
I've come across an issue in our topological representation that I think needs clarification: how should we interpret topology type (circular vs. linear) with regards to a SubComponent?
More specifically, given a Component C with a SubComponent that is an instanceOfComponent S:
Is the topology of a C constrained by the topology of S?
Is the topology of S as a feature of C the same as the topology of S?
My proposed answers:
Is the topology of a C constrained by the topology of S?**
I believe the answer to this question NO. Consider the following examples:
Circular plasmid C is created by ligation of linear fragments S1, S2, ..., Sn
Linear construct C is created by cleaving circular plasmids S1 and S2 and joining them by ligation of the 3' end of S1 to the 5' end of S2.
These examples show that it is reasonable to build a circular Component from SubComponent objects that are instanceOf linear Component objects and vice versa. This also implies that any mixture of SubComponent topologies should be able to produce either topology.
Is the topology of S as a feature of C the same as the topology of S?
SubComponent does not have a type field, so we cannot explicitly designate a topology for a SubComponent. I continue to believe this choice is correct, since it means one make nonsensical type changes things like declaring that a piece of DNA is protein in context.
This means that the effective topology of a SubComponent as a feature has to be inferred. Accordingly, I would propose the following rule for interpretation of the topology of a SubComponent, covering the common cases in which a circular SubComponent is either used intact or is incorporated as a linear segment of a larger (possibly circular) construct.
If a SubComponent has a hasLocation property other than EntireSequence or is the subject or object of a Constraint whose restriction has value precedes, strictlyPrecedes, meets, overlaps, finishes, or starts, then its topology MUST be interpreted as being linear.
Otherwise, the SubComponent MUST be interpreted as having the same topology as its instanceOfComponent.
The only case this interpretation does not cover is that of a Component whose topology is changed without being combined with any other component. This case SHOULD be handled by "wrapping" the Component in a Component or LocalSubComponent that changes its topology to explicitly represent a modification of circularity.
Examples:
Plasmid C is built by insertion of linear fragment S1 into circular plasmid S2, as represented by two SubComponent elements with appropriate locations on C's sequence. In this case, S2 is circular and C is circular but the S2 portion of C is linear.
Cell strain C is created by transformation of cell strain S1 with circular plasmid S2. The relationship is indicated by a Constraint with restriction value contains, subject S1, and object S2. Since this is not a linearizing constraint, S2 is still interpreted as being circular.
Examples 1 and 2 combined in a single Component: cell strain C is created by transformation of cell strain S1 with a plasmid created by insertion of linear fragment S2 into circular plasmid S3. In this case, in order to represent the transformation, we need a LocalSubComponent L, representing the plasmid combining S2 and S3, to be the object of the containsConstraint whose subject is S1. Since L has a type field, it can be explicitly marked circular, S2 and S3 are each included in L via a containsConstraint. The relationship of S2 and S3 is indicated via two meetsConstraint objects, and S2 and S3 are then correctly interpreted as linear portions of L.
Cell strain C is created by transformation of cell strain S1 with a circularized version of linear viral genome S2. Again we include a LocalSubComponent L, this time representing the circularized version of S2 with its circular type. A contains constrain is used to include S2 in L. S2 is still interpreted as linear, since this is the topology of the Component, but it is a linear portion of a circular construct (which happens to not contain anything else besides S2).
The text was updated successfully, but these errors were encountered:
I've come across an issue in our topological representation that I think needs clarification: how should we interpret topology type (circular vs. linear) with regards to a
SubComponent
?More specifically, given a
Component
C with aSubComponent
that is aninstanceOf
Component
S:My proposed answers:
Is the topology of a C constrained by the topology of S?**
I believe the answer to this question NO. Consider the following examples:
These examples show that it is reasonable to build a circular
Component
fromSubComponent
objects that areinstanceOf
linearComponent
objects and vice versa. This also implies that any mixture ofSubComponent
topologies should be able to produce either topology.Is the topology of S as a feature of C the same as the topology of S?
SubComponent
does not have atype
field, so we cannot explicitly designate a topology for aSubComponent
. I continue to believe this choice is correct, since it means one make nonsensical type changes things like declaring that a piece of DNA is protein in context.This means that the effective topology of a
SubComponent
as a feature has to be inferred. Accordingly, I would propose the following rule for interpretation of the topology of aSubComponent
, covering the common cases in which a circularSubComponent
is either used intact or is incorporated as a linear segment of a larger (possibly circular) construct.SubComponent
has ahasLocation
property other thanEntireSequence
or is thesubject
orobject
of aConstraint
whoserestriction
has valueprecedes
,strictlyPrecedes
,meets
,overlaps
,finishes
, orstarts
, then its topology MUST be interpreted as being linear.SubComponent
MUST be interpreted as having the same topology as itsinstanceOf
Component
.The only case this interpretation does not cover is that of a
Component
whose topology is changed without being combined with any other component. This case SHOULD be handled by "wrapping" theComponent
in aComponent
orLocalSubComponent
that changes its topology to explicitly represent a modification of circularity.Examples:
SubComponent
elements with appropriate locations on C's sequence. In this case, S2 is circular and C is circular but the S2 portion of C is linear.Constraint
withrestriction
valuecontains
,subject
S1, andobject
S2. Since this is not a linearizing constraint, S2 is still interpreted as being circular.Component
: cell strain C is created by transformation of cell strain S1 with a plasmid created by insertion of linear fragment S2 into circular plasmid S3. In this case, in order to represent the transformation, we need aLocalSubComponent
L, representing the plasmid combining S2 and S3, to be theobject
of thecontains
Constraint
whose subject is S1. Since L has atype
field, it can be explicitly markedcircular
, S2 and S3 are each included in L via acontains
Constraint
. The relationship of S2 and S3 is indicated via twomeets
Constraint
objects, and S2 and S3 are then correctly interpreted as linear portions of L.LocalSubComponent
L, this time representing the circularized version of S2 with itscircular
type. Acontains
constrain is used to include S2 in L. S2 is still interpreted as linear, since this is the topology of theComponent
, but it is a linear portion of a circular construct (which happens to not contain anything else besides S2).The text was updated successfully, but these errors were encountered: