-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop a mechanism for practices documents #16
Comments
|
We are going to use SEP 055 as a test case for this workflow. |
Now @PrashantVaidyanathan is doing the SBOL Examples, but I'm happy to help |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Things like SynBioDex/SBOL-specification#9 actually belong in separate "practices" documents that recommend how to use SBOL to represent common use cases.
Similarly, some of the material in the best practices section really belong in separate documents (e.g., representation of media, multi-cellular systems)
We do not currently have a means of actually maintaining such documents however. Should they be in this repository or in other repositories? Do they need to be blessed by SEPs? Do they get published by JIB?
These issues need to be worked out as a process SEP.
The text was updated successfully, but these errors were encountered: