Flexible, can handle a variety of things
Used differently by different groups
GBrowse integration needs work
Works well with GBrowse
Contains serialized Perl objects (is this necessary if you're storing subfeatures separately?)
Less flexible than Chado
Specialized for GFF3?
How widely used?
See page BioStore
for some links.
Simpler than Chado, more general than Bio::DB::SeqFeature::Store
How well does it work with GBrowse?
Roll our own
Yet Another Genomics Schema?!?!
Integrating something like an RDF triplestore with some relational tables should give scalability + flexibility at the expense of complexity
Going with a pure triplestore makes it easy to map to Semantic Mediawiki, but might not scale
- 21 Mar 2007
Copyright © 2008-2013 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback