Version 2 (modified by RutgerVos, 14 years ago)

--

Project description for Rutger Vos's visit to DBCLS, 24 January - 24 February 2011.

NeXML I/O as a BioRuby plugin

During the 2010 Google Summer of Code, student Anurag Priyam developed some classes for reading and writing NeXML ( http://www.nexml.org). However, these classes were built as part of the "core" BioRuby architecture. Best practices dictate that new code is instead released as a biogem plugin. To this end, I am refactoring Anurag's code. Steps taken so far:

  • Tools needed for biogem development and deployment:
    • Update RubyGems?, i.e. sudo gem update --system
    • Install bio-gem, i.e. sudo gem install bio-gem
    • Install bio-gem dependency jeweler, i.e. sudo gem install jeweler
    • Install bio-gem dependency bundler, i.e. sudo gem install bundler
  • Tools needed for git(hub):
    • Install git
    • Fork yeban/bioruby on github
    • git clone git@github.com:rvosa/bioruby.git
    • git branch bioruby-nexml
    • git checkout bioruby-nexml
  • Make biogem compliant folder layout
    • biogem nexml
    • Merge bioruby-nexml classes, unit tests and test files in biogem folder structure

NeXML/RDF as a BioRuby plugin

Elements in NeXML documents can be annotated using RDFa. This means that every element (and the objects in which it can be de-serialized) can be the subject in an RDF triple. For example, TreeBASE uses this extensively to add metadata about submissions to its repository to the NeXML it produces (e.g. author names, NCBI taxonomy record identifiers, etc.). In order to fully implement NeXML functionality, the BioRuby objects that are generated when reading a NeXML file should therefore be able to be annotated with predicates (with namespaces) and with objects (also, perhaps, with namespaces). To make this possible, Anurag started some work on this, but this needs to be extended and released as a biogem (bio-rdf?)

BioHackathon? meeting reports

  • finish abstract for BioHack?09 meeting report
  • help finish BioHack?10 meeting report for special issue of Journal of Biomedical Semantics