phenopacket-format
phenopacket-format copied to clipboard
phenopackets
The json-schema has many repetitive sections. This is not in itself wrong, but it can be confusing and/or intimidating to people trying to introspect the format directly from the jsons...
Many of the examples in this repo are out of date. The [ref implementation test resources](https://github.com/phenopackets/phenopacket-reference-implementation/tree/master/src/test/resources) is currently the best place for these. We should either auto-sync these (possible confusing)...
Why are the DOBs or age not asserted within the "admin profile"? from @cmungall : Every assertion about an entity is partitioned into a module, and can have full provenance/audit...
variant
It would be better to put the variant and the genotye into separate elements - type: OPA1 value: "homozygous c.1601T>G" - value: c.1601T>G - genotype: homozygous Also, c.1601T>G is not...
There are schemes such as HGVS that unambiguously map a genomic variation to a string. It is suggested we use this in #10. However, in relation to #22, if we...
This repo defines an exchange format(s), it is API-neutral. However, it would be useful to have a reference API, and to document strategies for incorporating pxf into existing APIs. A...
This of course complements high level documentation, examples, etc Dependent on #31 There are various options for JSON-Schema This is for language-binding independent docs. See also https://github.com/phenopackets/phenopacket-java/issues/4
