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

Consider switching canonical data sheets to SSSOM TSV format #66

Open
cthoyt opened this issue Oct 12, 2021 · 0 comments
Open

Consider switching canonical data sheets to SSSOM TSV format #66

cthoyt opened this issue Oct 12, 2021 · 0 comments

Comments

@cthoyt
Copy link
Member

cthoyt commented Oct 12, 2021

There are a few benefits:

  1. The SSSOM format uses CURIEs exclusively, so there won't be any confusion about identifier style ambiguity
  2. We can use SSSOM tooling instead of implementing it ourselves or alternatively contribute our tooling back to the SSSOM community
  3. There would be fewer artifacts that need to get built, and the messaging in Biomappings could be a bit more straightforwards

A few drawbacks:

  1. Requires more programming churn
  2. Have to assess how downstream dependencies consume Biomappings

Note: we're still allowed to choose our own prefix map with our SSSOM files, so we don't necessarily have to consider conflicts in nomenclature with the OBO community, but it would probably be a good idea to consider.

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

1 participant