Develop a mechanism for practices documents

[jakebeal]

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.

[jakebeal]

Known issues that need this: #7, #6, #8, #9

[cjmyers]

1. For a potential best practice example, open a discussion topic on the sbol-editors repository.
2. If an issue exists on this topic, link to it to see the past discussion, but have all future discussion on the discussion thread.
3. When a solution is being formulated, create a markdown description following the SEP format. Where appropriate, there should be fully formulated SBOL example(s).
4. When the solution appears to have achieved consensus (determined by the SBOL editors), then a link to this solution is added to the FAQ on the SBOL standard website.
5. Note that not all discussion topics need to ever be promoted to best practices linked on the FAQ.

[cjmyers]

We are going to use SEP 055 as a test case for this workflow.

[Gonza10V]

Now @PrashantVaidyanathan is doing the SBOL Examples, but I'm happy to help