You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jerven will use spodgi to output a complete triple store graph genome. We'll then have component_segmentation and schematize add to that triple store and use it as the only data source. It's not performant for gigabase genomes, but totally sufficient for COVID and simpler to develop RDF logic against a pure TTL.
Here we need to load data via SPARQL query based on pantograph ontologies graph-genome/graph-genome.github.io#15.
The text was updated successfully, but these errors were encountered:
I think it is better to implement the SPARQL queries for our Pantograph RDF in a separate repository:
Schematize should focus on visualization
Form the code in a way suitable for Schematize
Automatic testing, specifically of federated queries
Lot's of query examples
Installable via npm
Documentation not only of queries but how to set up your own Triple-Store, etc.
We can advertise it as an independent tool to other browser developers (e.g. JBrowse2) so they can play around with the data. Explore new visualization concepts. And reference us and especially your concept @josiahseaman.
Jerven will use spodgi to output a complete triple store graph genome. We'll then have component_segmentation and schematize add to that triple store and use it as the only data source. It's not performant for gigabase genomes, but totally sufficient for COVID and simpler to develop RDF logic against a pure TTL.
Here we need to load data via SPARQL query based on pantograph ontologies graph-genome/graph-genome.github.io#15.
The text was updated successfully, but these errors were encountered: