You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the specification, only FilterTermsResponse is required, however when you check FilterTermsResourceResponse, id is required, breaking the chain of requirements in the specification.
FilterTermsResourceResponse:type: arraydescription: |Description of an ontology resource defined externally to this beacon implementation, such as MeSH or EFO, based on the phenopackets resource object (https://phenopacket-schema.readthedocs.io/en/latest/resource.html)items:type: objectrequired:- idproperties:id:type: stringdescription: |Preferably OBO ID representing the resource; alternatively a URI pointing towards the definitions may be used if not in OBO.
Also, the use of "resource" tagname in order to the name the CURIE syntax for the terms used, could led to confusion, they are not resources, only vocabulary and terminology, i would recommend to change the name to something like "vocabulary" or "terminology"
Bests!
The text was updated successfully, but these errors were encountered:
Based on the specification, only FilterTermsResponse is required, however when you check FilterTermsResourceResponse,
id
is required, breaking the chain of requirements in the specification.Also, the use of "resource" tagname in order to the name the CURIE syntax for the terms used, could led to confusion, they are not resources, only vocabulary and terminology, i would recommend to change the name to something like "vocabulary" or "terminology"
Bests!
The text was updated successfully, but these errors were encountered: