diff --git a/framework/json/responses/sections/beaconFilteringTermsResults.json b/framework/json/responses/sections/beaconFilteringTermsResults.json index e7a0ab74a..f283dfaf7 100644 --- a/framework/json/responses/sections/beaconFilteringTermsResults.json +++ b/framework/json/responses/sections/beaconFilteringTermsResults.json @@ -21,12 +21,14 @@ ], "type": "string" }, - "type": { - "description": "Either \"custom\", \"alphanumeric\" or ontology/terminology full name. TODO: An ontology ... with a registered prefix does not need a full name so one may better use CURIE to indicate that the resource can be retrieved from the id. This also will allow to provide an enum here.", - "examples": [ - "Human Phenotype Ontology", - "alphanumeric" + "type":{ + "description": "Either \"custom\", \"alphanumeric\" or \"ontology\" .", + "enum": [ + "custom", + "alphanumeric", + "ontology" ], + "example": "alphanumeric", "type": "string" } }, diff --git a/framework/src/responses/sections/beaconFilteringTermsResults.yaml b/framework/src/responses/sections/beaconFilteringTermsResults.yaml index 4c3bd96c3..319e8c231 100644 --- a/framework/src/responses/sections/beaconFilteringTermsResults.yaml +++ b/framework/src/responses/sections/beaconFilteringTermsResults.yaml @@ -23,13 +23,12 @@ definitions: type: type: string description: >- - Either "custom", "alphanumeric" or ontology/terminology full name. - TODO: An ontology ... with a registered prefix does not need a full name - so one may better use CURIE to indicate that the resource can be retrieved - from the id. This also will allow to provide an enum here. - examples: - - "Human Phenotype Ontology" + Either "custom", "alphanumeric" or "ontology" . + enum: + - custom - alphanumeric + - ontology + example: alphanumeric id: description: >- The field id in the case of numeric or alphanumeric fields, or