[BDG-FORMATS-29] Re-organize the Feature schema

This is attempting to re-organize the Feature schema, along the
discussions that we (Timothy, Uri, Matt, Frank) have had in email and on
the phone.  The main requirements are:
- less file-format dependence in the field choice ('qValue'-like fields
  could be relegated to the 'attributes' field)
- fewer fields to improve the memory footprint
No, I mean, what if the same accession is used in multiple databases? Does
this ever happen?
On Sep 15, 2014 12:39 PM, "Timothy Danford" <notifications@github.com>
wrote:

> In src/main/resources/avro/bdg.avdl:
>
> > -  union { null, double } signalValue = null;
> > -  union { null, double } pValue = null;
> > -  union { null, double } qValue = null;
> > -  union { null, long } peak = null;
> > +
> > +  /**
> > +   The value associated with this feature (if double)
> > +   */
> > +  union { null, double } value = null;
> > +
> > +  /**
> > +   Cross-references into other databases.
> > +
> > +   Key is database name and value is the accession.
> > +   */
> > +  map<string> dbxrefs = null;
>
> Well, and ID->DB (as opposed to DB->ID) mapping would handle "multiple
> acc's in one DB," right? I'm agnostic either way.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/bigdatagenomics/bdg-formats/pull/30/files#r17563834>.
>