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

Unstranded position #11

Open
JervenBolleman opened this issue Dec 1, 2013 · 2 comments
Open

Unstranded position #11

JervenBolleman opened this issue Dec 1, 2013 · 2 comments
Milestone

Comments

@JervenBolleman
Copy link
Collaborator

As FALDO does not describe the concepts of sequences its hard to infer or detect
that a sequence can not be stranded.

We could add a UnstrandedPosition which is disjoint with a StrandedPosition

@KimJBaran
Copy link
Contributor

I think we discussed such an encoding that was in use in BioInterchange. As far as I remember, the consensus was that it would be better to just use a "Position" (i.e., not expressing strandedness at all), because that information could be added later.

If the sequence is inherently unstranded, then I think that "Position" would be sufficient for the encoding too. Otherwise, users might opt to use "UnstrandedPosition" when they do not know the strand, and then later, this would create a contradiction when strand information is added for the position.

@JervenBolleman
Copy link
Collaborator Author

I remember, the discussion came up when talking about restrictions. We have Stranded for UnknownStrandedness
but we don't have a concept of can not be stranded at all. NeverStranded or ImpossibleToBeStranded could be options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants