Michael Baudis

Results 55 issues of Michael Baudis

Warnings seem like a much needed item to understand responses where the server wants to indicate information about potential problems with the response which are not outright failures. Especially useful...

Dev scout

The email address [[email protected]](mailto:[email protected]) didn't exist. Suggestion: * one at ELIXIR? * or [email protected] w/ forwarding?

Dev scout

As per various discussions, using GET request seems a rather widely used concept with implementers (rapid UI integration w/o need of using specific frameworks; easier documentation, examples, testing etc.). In...

Dev scout

> The only ones that we agreed on adding were the collection ones if we prefer: > `biosamples?datasetIds=1,2,3` > to > ``` > dataset/1/biosamples > dataset/2/biosamples > dataset/3/biosamples > ```...

Dev scout

The `disease` class is still missing a number of parameters from Phenopackets v2 or represents them slightly different. We should: * rename `ageOfOnset` to `onset`, since it could be another...

Model related

"...entity" and "entryType" occasions should be normalized. This was agreed upon previously & just didn't make it into 2.0.0 as planned: https://github.com/ga4gh-beacon/beacon-framework-v2/pull/76 as issue in the unified repo, based on...

Dev scout

Schemas should have `$id` parameters. Example: `"$id": https://progenetix.org/services/schemas/BeaconServiceError/v2021-03-07`

Dev scout

When discussing variant queries or even as part of of UI implementations frequently "short form" annotations are being used instead of parameter=value pairs; but there is no recommended style or...

documentation
help wanted
question
Variants scout

This aligns the use of the "definitions" parameter to the "$defs" keyword as required from https://json-schema.org/draft/2020-12/schema as pointed out by @jrambla in https://github.com/ga4gh-beacon/beacon-v2/issues/153 Editing of the YAML files with conversion......

The OpenAPI `endpoints` files included a number of leftover or potentially misleading descriptions, e.g.: * "get a list of..." as description for responses, although responses depend on granularity and delivered...