Difference between revisions of "PhyloSoC:BioPerl integration of the NeXML exchange standard and Bio::Phylo toolkit/nexml module design"

From Phyloinformatics
Jump to: navigation, search
m (Nexml Item Module Design (work in progress))
m (Overview)
Line 3: Line 3:
 
==== Overview ====
 
==== Overview ====
  
Currently, parsing a nexml file into Bioperl makes use of the *IO modules (AlignIO, SeqIO, and TreeIO) to load nexml represented data into Bioperl objects.  These modules will handle each data type separately, but the ultimate goal is to make this easier on the user and allow the full parsing of a nexml document into a bioperl object that can contain each data type and maintain the relationships between them.  To accomplish this, a Bio::Nexml module will be created that will act as a representation of an entire Nexml document and will hold seq, aln, and tree objects.  Creating a new class will provide a way to maintain relationships between the data and will also make it more clear to the user that this represents an entire nexml document.  It will be a simple container that lets the majority of the work be done by the object classes it contains making use of the modules/methods previously written during this project.
+
Currently, parsing a nexml file into Bioperl makes use of the *IO modules (AlignIO, SeqIO, and TreeIO) to load nexml represented data into Bioperl objects.  These modules will handle each data type separately, but the ultimate goal is to make this easier on the user and allow the full parsing of a nexml document into a bioperl object that can contain each data type and maintain the relationships between them.  To accomplish this, a Bio::Nexml module will be created that will act as a representation of an entire Nexml document and will hold seq, aln, and tree objects.  Creating a new class will provide a way to maintain relationships between the data and will also make it more clear to the user that this represents an entire nexml document.  It will be a simple container that lets the majority of the work be done by the object classes it contains making use of the modules/methods previously written during this project.
  
creating a new Bio::Nexml class will make it more clear to the user that this represents an entire nexml document and was there
 
  
 
Something like
 
Something like
  
 
$nexml_doc = Bio::NeXML->new(-file=>'a_nexml_file.xml');
 
$nexml_doc = Bio::NeXML->new(-file=>'a_nexml_file.xml');
 
  
 
==== Data Relationships to Maintain ====
 
==== Data Relationships to Maintain ====

Revision as of 07:58, 15 June 2009

Nexml Item Module Design (work in progress)

Overview

Currently, parsing a nexml file into Bioperl makes use of the *IO modules (AlignIO, SeqIO, and TreeIO) to load nexml represented data into Bioperl objects. These modules will handle each data type separately, but the ultimate goal is to make this easier on the user and allow the full parsing of a nexml document into a bioperl object that can contain each data type and maintain the relationships between them. To accomplish this, a Bio::Nexml module will be created that will act as a representation of an entire Nexml document and will hold seq, aln, and tree objects. Creating a new class will provide a way to maintain relationships between the data and will also make it more clear to the user that this represents an entire nexml document. It will be a simple container that lets the majority of the work be done by the object classes it contains making use of the modules/methods previously written during this project.


Something like

$nexml_doc = Bio::NeXML->new(-file=>'a_nexml_file.xml');

Data Relationships to Maintain

  • Sequences <=> Nodes
  • Alignments <=> Trees
  • Taxa <=> Trees
  • Taxa <=> Alignments
  • Taxon <=> Node