SEP | 057 |
---|---|
Title | Best practices modifications on SBOL specification |
Authors | Gonzalo Vidal ([email protected]), Jake Beal ([email protected]) |
Editor | Gonzalo Vidal |
Type | Procedure |
Status | Draft |
Created | 08-Feb-2023 |
Last modified | 13-Feb-2023 |
Add the attribute to create new SBOL ontology terms to SBOL best-practices
- 1. Rationale
- 2. Specification
- 3. Example or Use Case
- 4. Backwards Compatibility
- 5. Discussion
- 6. Competing SEPs
- Copyright
With the creation of SBOL-Examples we have noticed that best practices may require new onlogy terms to be implemented. For this reason we propose to give the capability of adding new SBOL ontology terms to best practices in a child namespace.
Append at the end of section 5.2, first paragraph:
The SBOL child namespace,
http://sbols.org/v3/bp#TERM
is used to indicate entities or properties from best practices that are outside of this specification. Terms in this child namespace MUST NOT match terms in the SBOL namespace.
The best practice BP011 proposes the new term http://sbols.org/v3#assemblyPlan
that under this SEP will be implemented as http://sbols.org/v3/bp#assemblyPlan
There are no compatibility issues with previous SEPs
In the discussion has been proposed the creation of a child namespace for best preactices terms.
The form of the child namespace has been proposed to be http://sbols.org/v3/bp#TERM, avoding conflicts between BPs, then there MUST NOT be a matching http://sbols.org/v3#TERM.
There are no competing SEPs
To the extent possible under law,
SBOL developers
has waived all copyright and related or neighboring rights to
SEP 002.
This work is published from:
United States.