Toshiaki Katayama
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- title: 'Application of genome graph for standard representation of structural variations in RDF' title_short: 'Structural variations in RDF' tags: - structural variations, genome graph, knowledge graph authors: - name: Toshiaki Katayama orcid: 0000-0003-2391-0384 affiliation: 1 - name: Takatomo Fujisawa affiliation: 2 - name: Yuki Moriya affiliation: 1 - name: Shuichi Kawashima affiliation: 1 - name: Mayumi Kamada affiliation: 3 affiliations: - name: Database Center for Life Science, Research Organization of Information and Systems, Kashiwa, Chiba, Japan index: 1 - name: National Institute of Genetics, Mishima, Shizuoka, Japan index: 2 - name: Department of Biomedical Data Intelligence, Graduate School of Medicine, Kyoto University, Kyoto, Japan index: 3 date: 12 November 2021 bibliography: paper.bib event: Spain2021 biohackathon_name: "ELIXIR BioHackathon 2021" biohackathon_url: "https://biohackathon-europe.org/" biohackathon_location: "Barcelona, Spain, 2021 (remote)" group: Application of genome graph for standard representation of structural variations in RDF # URL to project git repo --- should contain paper.md git_url: https://github.com/elixir-europe/bioHackathon-projects-2021/tree/main/projects/31 # This is the short authors description that is used at the # bottom of the generated paper. authors_short: Toshiaki Katayama & Takatomo Fujisawa \emph{et al.} --- # ELIXIR BH21 SV-RDF Authors * Toshiaki Katayama * Takatomo Fujisawa * Yuki Moriya * Shuichi Kawashima * Mayumi Kamada ## Introduction Representation of structural variations (SVs) is one of the urgent issues for data sharing. Some databases already use the VCF format for this purpose. However, the way to serialize SVs is not standardized and the format will not be applicable for more complex SVs detected in the future. Meanwhile, the 'vg' tool that constructs and manipulates genome graphs has the capability to serialize any variations into the Resource Description Framework (RDF). In this proposal, we plan to apply the generic 'vg' RDF model for representing existing SVs to be standardized and extended for future complex SVs. As we have been developing knowledge graphs in RDF covering a diverse range of life sciences and biomedical datasets, the interpretation of SVs can be seamlessly realized. ## Methods https://docs.google.com/document/d/1tG9Zv0wzwvZVYGqiOaqsmli1u3U8x14NSboUApEwVyg/edit#heading=h.r3tromt0fbkg 課題整理 * 保存されている両端のノード * ref/alt の入れ替えた場合の対称性 * rdf:value に配列が必要? * FALDO Region はなぜ向きを持たないのか * 代わりに begin, end それぞれに Fwd/Rev Position を持たせている * なぜか。富山BHを思い出しつつ、たぶん position に fwd か rev かそれ以外を書く必要のあるユースケースがあって、region に向きをもたせる場合と begin/end のポジションにもたせる場合で SPARQL が変わるのはイヤとか? * いずれにしても begin/end の向きをみれば region の向きは推論できる * SV の階層性 * caller ごとに複数の結果が出ていて、それをマージして variant region をサブミッションにしている場合あり ### VCF to (GFA to) RDF * https://github.com/dbcls/visc/wiki/VISC-SPARQLthon107 * https://github.com/dbcls/visc/wiki/VISC-SPARQLthon109 ## Results SVはサブミッターのアノテーション、主張(ファクトではない) 目的:サブミッションをうけつけたい、ゲノムグラフでそれができればキレイ、無理なら? 現実:各SV callerが作った機械的な結果も、マニュアルキュレーションされた結果も、両方格納する必要あり(整合性が取れなかったとしても) なので、オントロジーファースト、ゲノムグラフファーストはリアリティがない 理論屋さんはOKでもDB屋さんとしては困る VCFの breakend 記法で書かれているような、切れたもう一方の端がどこに繋がっているか分からないものがありえる? → gnomAD SV の CTX/BND には CHM2 も書いてあるのでOKだが、とくにBNDでCHM2がないものはある? path は step のリストで、step は向きを含めた node、、nodeはリファレンス上のpositionを持つ ### Plan A Starting from a genome grpah which already contains SVs to be annotated. * Pros * easy to obtain nodes before and after the node that are required to define paths (usually ommitted in the VCF thus needs to be complemented) * Cons * representation can be complicated when simple variants are located on the SV nodes. A node can have SNPs after the dupulication e.g., in case of CNV or dDUP-iDEL. ### Plan B Adding new submissions of SVs to the genome graph. * Pros * practically more feasible as new submissions will usually report new SVs * Cons * nodes in a genome graph needs to be edited (break into two or more nodes etc.) ### Application to gnomAD SVs ### Application for de novo SVs ### GVO (ver. AshinoCore) ## Discussion ゲノムグラフで表現できるSVはOK 世の中のVCFやサブミッションにはゲノムグラフにできないものもあるんじゃ? (ファジーポジション) ### Can GFA represent any types of SVs? Theoritically yes (really?) * practically, each node can have SNVs inside... etc. * see limitations below Minimal requirements: ### SPARQL query of SNV/MNVs and SVs How many types? What's are the biological mechanisms to cause SVs? ### Interoperability of submissions Same SV = Same RDF limitations: * left shift (left alignment) * split node * node1 -> node1a, node1b (then delete node1?) * fuzzy position (dbVar, gnomAD VCF) * might not be represented in genome graph? * inter chromosomal / translocation * might be OK if genome graph contains all chromosomes * diploids? / trisomy? / cancer? #### TogoVar, MGeND, JVar TODOs ## Acknowledgements * Jerven Bolleman * Simon Heumos * Dmitry Repchevsky ## References

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully