Permalink
Browse files

Fix typos in SEP 20

  • Loading branch information...
udp committed Dec 6, 2017
1 parent 502f7eb commit ebbe2c93f635829a973856f38df5cb3486257cec
Showing with 2 additions and 2 deletions.
  1. +2 −2 sep_020.md
View
@@ -231,15 +231,15 @@ This proposal does not affect backwards compatibility.
### 5.1 Key differences to SEP 19 <a name='differences'></a>
SEP 19 relies heavily on prov-O providence ontology terms which are freely mixed with SBOL terms. SEP 20 instead tries to establish a clear separation of concerns: SBOL terms are used to describe the core information of **What** we are looking at. Prov-O terms are used to add an optional layer of information about **How** something was created. In practice, this means the proper SBOL terms `model`, `design`, `attachment` are used to link Experimental Results, `Implementation`, `Component/ModuleDefinition`, and `Model` (the "What").
SEP 19 relies heavily on prov-O provenance ontology terms which are freely mixed with SBOL terms. SEP 20 instead tries to establish a clear separation of concerns: SBOL terms are used to describe the core information of **What** we are looking at. Prov-O terms are used to add an optional layer of information about **How** something was created. In practice, this means the proper SBOL terms `model`, `design`, `attachment` are used to link Experimental Results, `Implementation`, `Component/ModuleDefinition`, and `Model` (the "What").
Key differences are:
* No (redundant) `wasDerivedFrom` links between `Implementation` and `ComponentDefinition`
* Instead, SEP 20 defines a direct and mandatory field `design`
* All use of providence ontology terms and constructs is optional
* All use of provenance ontology terms and constructs is optional
* Massive reduction of prov-O overhead and reference redundancy

0 comments on commit ebbe2c9

Please sign in to comment.