Package apollo.datamodel

Interface Summary
AnnotatedFeatureI  
ApolloDataI DataLoader returns an ApolloDataI which can be queried whether its holding a CurationSet or CompositeDataHolder, which can then be retrieved.
AssemblyFeatureI  
CodingPropertiesI  
Comparable  
EvidenceConstants  
ExonI  
FeaturePairI  
FeatureSetI  
RangeI  
SeqFeatureI  
SequenceI  
StrandedFeatureSetI  
TranslationI im thinking maybe there should be a separate interface for translation methods (yes i know there is - its called a feature set) and seqfeatureI would have this - not be implemented in a subclass (or if it is not have that be noticaeable at the api/interface level) in other words a HASA not a ISA! i think that would be cleaner
 

Class Summary
AbstractSequence  
AnnotatedFeature One thought Im having is that annotation stuff would be a HASA instead of a ISA for SeqFeatureI.
AssemblyFeature A class to represent SeqFeatures which have been mapped to a static golden path- the usual start/end is assumed to be in chromosome coords, but the assembly start/end specific to this subclass are in coords relative to the feature.
Chromosome  
ChromosomeBand  
Comment  
CompositeDataHolder Holds multiple curation sets for synteny.
CurationSet I am the central holder of renderable data - results, annotations etc.
DbXref  
Evidence  
EvidenceFinder  
EvidenceSet  
Exon  
FeaturePair  
FeatureSet I think SeqFeature should implement all the functions of FeatureSet, so its polymorphic, so when you have a SeqFeatureI you dont have to care whether its a SeqFeature or a FeatureSet, so you dont have to keep downcasting to descend the datamodel (or do any other feature set functionality) As now you go through the Vector of SeqFeatures, cast to SeqFeature, then ask instanceof FeatureSetI and cast to FeatureSetI, which is potentially confusing.
GenomicRange  
Identifier  
Karyotype  
Link  
LinkSet Set of links for synteny view
Protein  
Range  
Score  
SeqFeature A class to represent a basic sequence feature, such as a result span.
Sequence Update this to take to use Range - used to ignore Range and use residueOffset, which was redundat with using Range.
SequenceEdit seq edits are really seq features (very tiny ones) arent they so subclass seq feature? do we still need seq edit? or seq edit has a seq feature? chado models indels as features which makes sense so why not apollo? needs to be annotated feat for chado transaction transformer sake - to be consistent with other annots
SpeciesComparison  
StrandedFeatureSet It may well be that any FeatureSet for which the strand is not explicitly set to either 1 or -1 (in other words the strand is 0) should be treated as a mixed set of features that may be on either strand
Synonym In Apollo, synonyms used to be strings, but in the ChadoXML data, synonyms have other fields (pub_id, is_current), so this new datamodel allows us to capture those fields (and any others that may come up) as properties.
SyntenyRegion  
Transcript