I've had a look of the schema and it does seem very reminiscent of
EMBL/Genbank files in the type of features it captures and the general way
they are laid out.
I think it is also possible to graft on hierarchical features onto this
schema in the manner Thomas indicated - use a separate table to
On Sun, Aug 05, 2001 at 03:41:54PM +1200, Mark Schreiber wrote:
> I'm personally a big fan of runtime exceptions but I think the argument
> was about making ChangeVetoExceptions a sub class of RuntimeException. I'm
> not sure if this is the same as what you are doing. What do you want to do
> with
Hi...
I've just added two new classes, NestedRuntimeException and
BioRuntimeException. As the names suggest, these are unchecked
exceptions, but they should be used with the same semantics
as their checked equivalents. Extra subclasses can be added
if necessary, but I'm hoping that use of them
David -
I would still encourage you to investigate with real code option (1). My
feeling is that the additional overhead of a heirarchy will be low. We
need a real example to show that. I would be sure that you have correctly
rejected (1) before starting on (2).
Otherwise we will end up with
We developed seperated module/classes in bioperl and biojava to dump
Sequence object with AGAVE format, which can be visualized with
GenomicViewer and SVG viewer, for more information, please see :
www.agavexml.org
Suggestions welcome,
Hanning Ni
___
Hanning -
thanks for the tools. Some comments -
(a) would you guys like to check this in directly with bioperl or do you
want to keep it a separate download?
(b) traditionally in the bioperl SeqIO system one is transforming a set of
sequences to a set of sequences. the agave write_seq is f
