Skip to content
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

Writing SBOL3 IO #52

Closed
TimothyStiles opened this issue Oct 23, 2020 · 1 comment
Closed

Writing SBOL3 IO #52

TimothyStiles opened this issue Oct 23, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@TimothyStiles
Copy link
Collaborator

TimothyStiles commented Oct 23, 2020

Is your feature request related to a problem? Please describe.

People keep asking for SBOL3 IO so I thought there should be an issue for it.

Describe the solution you'd like

The SBOL3 parser should implement four functions `ReadSBOL, ParseSBO, BuildSBOL, WriteSBOL.

  • ReadSBOL pretty much just does file io and passes a file string to ParseSBOL.

  • ParseSBOL picks apart the sbol file string and appropriately fills an AnnotatedSequence instance with it.

  • BuildSBOL takes an AnnotatedSequence object and uses it to build a string that can be passed to WriteSBOL.

  • WriteSBOL writes an SBOL string to file.

Each function should be tested. The easiest way is to read, and parse an SBOL into a Sequence then build a string with it and write it out then compare the input with the output. If they're the same then you've done it!

@TimothyStiles TimothyStiles added enhancement New feature or request ucb-students labels Oct 23, 2020
@Koeng101
Copy link
Contributor

Koeng101 commented Nov 4, 2020

SBOL3 is probably where it is worth going to. SBOL2 will be going away at some point, might as well focus on the future!

@TimothyStiles TimothyStiles changed the title Writing SBOL2 IO Writing SBOL3 IO Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants