Browse files

Minor tweaks to SEP 018 and SEP 019.

  • Loading branch information...
nroehner committed Nov 13, 2017
1 parent 4582dd3 commit c951f5d6b5a63c6441a9c1de89ba834c67280655
Showing with 2 additions and 4 deletions.
  1. +1 −1
  2. +1 −3
@@ -81,7 +81,7 @@ This proposal has been discussed extensively at HARMONY 2017 and on the Github i
Relation to Other SEPs <a name="relation"></a>
This proposal relates to SEP 14, 16, and 17, all of which deal with how experimental data should be linked to SBOL.
This proposal relates to SEP 019, which deals with how experimental data should be linked to SBOL as part of encoding the provenance for design-build-test-learn cycles in synthetic biology.
References <a name="references"></a>
@@ -12,7 +12,7 @@ SEP | <leave empty>
**Replaces** | SEP 014, SEP 016, SEP 017, SEP 018
**Status** | Draft
**Created** | 10-Nov-2017
**Last modified** | 10-Nov-2017
**Last modified** | 13-Nov-2017
@@ -171,8 +171,6 @@ In addition to specifying a procedural workflow, this specification also allows
[Example 4](#example4) illustrates how the `Implementation` class is used to differentiate a conceptual design from a realized design. In the left hand example, the `Implementation` links via PROV-O to the `ComponentDefinition` that represents the original design, while its `componentDefinition` property links to the `ComponentDefinition` which describes the structure of the actual physical implementation. The right hand example demonstrates a case where the `Implementation` matches its design specification.
[Example 5](#example5) illustrates how a "Test" may be represented as a `Collection` of `Attachments`. In this example, a quality control "Test" links a gel photo in PNG format and sequencing data in the AB1 format.
Relation to Other SEPs <a name='competing_seps'></a>

0 comments on commit c951f5d

Please sign in to comment.