Difference between revisions of "Project Plan for NeXML and RDF API in BioRuby"

From Phyloinformatics
Jump to: navigation, search
(Week 2)
Line 5: Line 5:
 
** Taxa block( <code>otus</code> ) and
 
** Taxa block( <code>otus</code> ) and
 
** Sets( <code>class</code> )
 
** Sets( <code>class</code> )
* Parse <code>otu</code>, <code>otus</code> and <code>class</code> return objects of the corresponding class.
+
* Parse <code>otu</code>, <code>otus</code> and <code>class</code> and return objects of the corresponding class.
 
== Week 2 ==
 
== Week 2 ==
 
* Design classes to encapsulate:
 
* Design classes to encapsulate:
 
** Trees( <code>trees</code> )
 
** Trees( <code>trees</code> )
 
** Tree( <code>tree</code> ), Network( <code>network</code> ), Node( <code>node</code> ) and Edge( <code>edge</code> )
 
** Tree( <code>tree</code> ), Network( <code>network</code> ), Node( <code>node</code> ) and Edge( <code>edge</code> )
 
+
* Parse <code>trees</code>, <code>tree</code>, <code>node</code>, <code>edge</code> and return objects of the corresponding class.
 
== Week 3 ==
 
== Week 3 ==
 +
* Design classes to encapsulate:
 +
** Character block( <code>characters</code> )
 
== Week 4 ==
 
== Week 4 ==
 
== Week 5 ==
 
== Week 5 ==
Line 21: Line 23:
 
== Week 11 ==
 
== Week 11 ==
 
== Week 12 ==
 
== Week 12 ==
 
  
  

Revision as of 00:12, 26 May 2010

Week 1

Development of the NeXML parser.

  • Design classes to encapsulate:
    • Taxa( otu )
    • Taxa block( otus ) and
    • Sets( class )
  • Parse otu, otus and class and return objects of the corresponding class.

Week 2

  • Design classes to encapsulate:
    • Trees( trees )
    • Tree( tree ), Network( network ), Node( node ) and Edge( edge )
  • Parse trees, tree, node, edge and return objects of the corresponding class.

Week 3

  • Design classes to encapsulate:
    • Character block( characters )

Week 4

Week 5

Week 6

Week 7

Week 8

Week 9

Week 10

Week 11

Week 12

A discussion on API can be found here - NeXML and RDF API for BioRuby