ga4gh / ga4gh/phenopacket-schema
Consider (breaking change) simplification or update of VRS.
- Dominant language
- Java
- Stars
- 101
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
- Low use of VRS among current users of Phenopackets (none are aware of)
- Preference for VCF-like and HGVS-like syntax.
- We are now using an outdated version of VRS to support a stable standard. Could we consider replacing this with a simpler version of the parts of VERSATILE we are using, along with a field to link to modern versions of VRS for those who need it?
Contributor guide
Research direction
Start by reviewing how VRS is currently used in the Phenopacket schema and compare those parts with the requested VERSATILE simplification. Clarify the proposed replacement fields, compatibility impact, and how links to modern VRS versions should work; done requires an agreed design before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100