Lowering barriers to publishing biological data on the web
3 likes528 views
The document discusses the motivation and current state of publishing biological data on the web, emphasizing the need for web accessible and interoperable formats. It outlines proposals for reusable presentation components and frameworks that integrate bioinformatics libraries. It also highlights challenges in designing reusable components, ensuring multi-language support, and facilitating community engagement.
1 of 12
Download to read offline
More Related Content
What's hot (17)
Ad
Viewers also liked (20)
Ad
Similar to Lowering barriers to publishing biological data on the web (20)
More from Brad Chapman (6)
Lowering barriers to publishing biological data on the web
- 1. Lowering barriers to publishing biological data on the web Brad Chapman Department of Molecular Biology Massachusetts General Hospital Boston, MA USA chapmanb@50mail.com http://friendfeed.com/chapmanb 27 June 2009
- 2. Motivation
- 3. Motivation Web accessible Interoperable in standard formats Displays for browsing Analyses Scale
- 4. Current state: Reusable libraries Parse file formats Run programs Build analysis pipelines Communities Python examples Biopython pygr bx-python PyCogent
- 5. Current state: Database schemas Represent biological data Expand analyses beyond flat files Interoperate with standards BioSQL Chado
- 6. Current state: Web applications
- 8. Proposal Provide Reusable presentation components Quickly deployable frameworks Integrate Bioinformatics libraries Database schemas Web development frameworks
- 9. Proposal
- 11. Challenges: Design Reusable Components: avoid large framework Multi-language: javascript front end Accessible Automated data retrieval (REST) Standard formats (GFF, RDF) Available Creative Commons http://creativecommons.org/about/licenses Open Data Commons http://www.opendatacommons.org/licenses/
- 12. Challenges: Community questions How do we. . . provide plug-in components? leverage existing code? make reuse easier? communicate about these issues?