<p><em>Note: I will use SBOL3 in my descriptions; the answer can be equivalently translated to SBOL2</em></p>
<p>At present, SBOL doesn't have any explicit recommendations for how to represent these types of timing parameters. This is because there is not yet a clear scientific consensus on whether or not such parameters are a good way to represent genetic circuits.</p>
<p>That said, one of the advantages of using SBOL is that its extensible RDF-based model allows additional information like this to be added into a model. Two good ways of doing so are:</p>
<ol>
<li>If the parameters are simple and can stand alone as measurements, then they can be added to designs as a <code>Measure</code> object with appropriate units and type. For example, if you have biological devices with a 90 minute propagation delay, then on the <code>Component</code> representing the device you can add a <code>Measure</code> with numerical value 90, units of <code>om:minute</code>.  You'd likely want two types, one of <code>SBO:0000225 (Delay)</code>, and a custom type for your own notion of propagation delay, since I don't think that's included in any ontology yet.</li>
<li>If the parameters are more complex and/or inter-related, e.g., a full data-sheet, then you'd likely want to instead create one or more extension classes that are used to represent the information. A library that makes this easy is <a href="https://github.com/SynBioDex/sbol_factory" rel="nofollow noreferrer">sbol_factory</a>, though one can do it with any of the SBOL libraries.</li>
</ol>
<p>This becomes more complicated if you want to talk about behavior in different environmental contexts, but the basic principles are still the same.</p>
<p>Finally, as for SBOL visual: again, there's no explicit representation, but the model is extensible, and this information can be added as any sort of text or custom glyph as long as it doesn't conflict with ones already in the standard.</p>

CC BY-SA 4.0
2021-04-16T13:54:57.303Z
2021-04-16T13:54:57.303Z
jakebeal
<p>Like the propagation delay and threshold value parameters in electronic circuits, does SBOL format support any such parameters/glyph to represent the <strong>propagation delay</strong> (time to trigger the output protein once the input is provided) and <strong>threshold value</strong> (minimum input concentration required to trigger the model's output) of genetic models?</p>
<p>If currently not supported, can these parameters be incorporated in the SBOL visual representation which would give reader an idea (just by looking at the schematic diagram) about the timing behavior of a model?</p>

<sbol>
Does SBOL support timing and threshold value parameters?
# Does SBOL support timing and threshold value parameters?

(Asked by: username_0 on 2021-04-06)

Like the propagation delay and threshold value parameters in electronic circuits, does SBOL format support any such parameters/glyph to represent the **propagation delay** (time to trigger the output protein once the input is provided) and **threshold value** (minimum input concentration required to trigger the model's output) of genetic models?

If currently not supported, can these parameters be incorporated in the SBOL visual representation which would give reader an idea (just by looking at the schematic diagram) about the timing behavior of a model?

**Tags:** sbol

---

## 1 answers

### Answer by username_1 on 2021-04-16. Score: 3 | Accepted answer

*Note: I will use SBOL3 in my descriptions; the answer can be equivalently translated to SBOL2*

At present, SBOL doesn't have any explicit recommendations for how to represent these types of timing parameters. This is because there is not yet a clear scientific consensus on whether or not such parameters are a good way to represent genetic circuits.

That said, one of the advantages of using SBOL is that its extensible RDF-based model allows additional information like this to be added into a model. Two good ways of doing so are:

1. If the parameters are simple and can stand alone as measurements, then they can be added to designs as a `Measure` object with appropriate units and type. For example, if you have biological devices with a 90 minute propagation delay, then on the `Component` representing the device you can add a `Measure` with numerical value 90, units of `om:minute`. You'd likely want two types, one of `SBO:0000225 (Delay)`, and a custom type for your own notion of propagation delay, since I don't think that's included in any ontology yet.
2. If the parameters are more complex and/or inter-related, e.g., a full data-sheet, then you'd likely want to instead create one or more extension classes that are used to represent the information. A library that makes this easy is [sbol\_factory](https://github.com/SynBioDex/sbol_factory), though one can do it with any of the SBOL libraries.

This becomes more complicated if you want to talk about behavior in different environmental contexts, but the basic principles are still the same.

Finally, as for SBOL visual: again, there's no explicit representation, but the model is extensible, and this information can be added as any sort of text or custom glyph as long as it doesn't conflict with ones already in the standard.


---

