March Checklist for v0 Release

[mbrush]

Work to compete before we can package a v0 VA-Spec release.

1. Statements: Essentially done, with exception of small issue with Computational Functional Impact Statement model (pre-testing with BRCA Exchange data revealed an overlooked requirement from initial analysis)

• [x] Address new requirement related to the Computational Functional Impact Statement model (See #21)
• [x] Address potential new requirement for the Relative Location model - provided by the Beacon v2 schema (See #18)
• [x] Issue of whether we can leave Variant Pathogenicity descriptor blank (See #22)

2. Domain Entities: Essentially done (see gdoc, models), with exception of final touches on Sequence Feature model

• [x] Complete domain entity model for Sequence Features (See #19)

3. Value Sets: See #56

• [x] Review where we want to provide recommended value sets, define terms for each
• [x] Decide how/where we should encode these value sets.

4. Data Types: See #57

• [ ] General review of proposal for data types (in particular 'identifier' and 'coding' may require additional consideration)
• [ ] Review/compare the data types below to those defined and used in the VRS specification (to be sure they are aligned as best possible)

5. Extension Mechanisms: See #54, #55

• [ ] Define specifics of modeling to support addition of ad hoc, custom attributes to any VA class

6. Record/System-Level Metadata: See #49

• [ ] Decide if and how to support this type of information in the v0 release. See proposal in linked ticket.

7. Evidence and Provenance Model: This is the one remaining big ticket item to complete. We have assembled detailed requirements that we will review, and then propose a SEPIO-based set of models to cover the core VA types to be released in the v0 Spec. Includes finalizing Contribution modeling.

[andrewyatz]

I think #61 should get linked into here now