Dmitry Repchevsky

I see no inconsistency here. The endpoint name shouldn't reflect neither entry type name, nor the path. In the analogue to the OpenAPI we have "operationId" which is the semantic...

Well, this shouldn't affect implementations at all, but ```json "endpointSets": { "Variants": { "entryType": "genomicVariant", "rootUrl": "https://beacons.bsc.es/beacon/v2.0.0/g_variants", }, ``` in this logic ```json "Individuals": { "endpoints": { "genomicVariant": { "returnedEntryType":...

Hm... u r right. That's my beacon that still uses "old" names... CRG has been updated: https://beacons.bsc.es/beacon/v2.0.0/map https://beacon-apis-demo.ega-archive.org/api/map

This is similar as the implementations actually do behind... but I oppose. Things are more complicated - the id may be in array (for instance) or backing implementation (e.g. OMOP)...

Hm... understand. For the information this even could be the schema element identifier in a form of Json Pointer. How to interpret is in a case of multiple scopes? Imagine...

Hi all, Just a naïve question. May the exclusion (negation) be included in filtering logic along with AND & OR?. I mean do we need this special case for negation?...

>In any case adding the excluded flag as an option seems straightforward (and is IMO clearer as the procedural similarity flag... I never understood the exact meaning of similarity for...

I implemented a possible [prototype](https://docs.google.com/presentation/d/1h4g_R2aSSfUdjWNzKopu8Cg1bh7q0LVzIMxOF_g4dj0/edit#slide=id.g2e75fd38f23_0_3) and still do not understand the difference between "excluded" and "negation". ```json "query": { "filters": [ { "id": "NCIT:C9335" } ], "filtersLogic": "NCIT:C9335 & !NCIT:C5213"...

The scopes are defined in the filters[] array. The "filtersLogic" only defines the logic. I use "ids" (or better should be "labels") in "filtersLogic" because we may reuse the same...

@mbaudis >filters[0].id should be NCIT:C9335, not double-prefixed fixed (typo). This is a question of interpretation and what actually be generated for execution. 1. For alphanumeric filters "! Weight > 25"...