Jordi Rambla
Jordi Rambla
As we have many issues to address and this is "name change" is "cosmetic", I'll close the issue
I agree with the table description about how the responses are expected to be.
I don't think the alternatives are necessary, as with the correction above, the behavior would be the expected one. - A resultset is the equivalent of a collection. - The...
This is in the configuration endpoint. E.g. ``` "dataset": { "aCollectionOf": [ { "id": "genomicVariant", "name": "Genomic Variants" } ], "additionalSupportedSchemas": [], "defaultSchema": { "id": "ga4gh-beacon-dataset-v2.0.0", "name": "Default schema for...
(I'll be telegraphic, in order to be concise) About what is a `dataset `and what is a `cohort`: In the current model (v2.0) a dataset could only contain "genomicVariations" and...
The rationale behind the verbosity: - The design is meant for a network scenario, where requests are dispatched to several beacons and responses could come back at different paces. Indeed...
At the Dev Scout meeting finished a few minutes ago we agreed in two main principles regarding this issue: 1) Keep the properties mandatory, but... 2) Make them mandatory only...
I would suggest another approach : ``` - type: custom id: UNKNOWN_SEX label: unknown genotypic sex scope: subject.sex ``` as you are not actually doing any comparison here, just using...
My 2 cents: 1. We already have the `excluded `flag in phenotypicFeature schema, Its meaning is stated in PXF and "inherited" by Beacon. 2. We don't have a syntax for...