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
(just copy paste the relavant points raised in email on Feb 1st - with enumerated points we can refer to in the tracker)
1- We often use Json-LD Playground to check the validity of the JSON generated. I am not fully aware of the specification, but in BioPortal we use @context to specify the properties
2- For the property includedInDataCatalog in the /ontologies call, indeed it needs to link back to the object defined in your own API then something like :
"includedInDataCatalog": [
"http://176.31.200.199/repositories/ols,
http://176.31.200.199/repositories/bioportal,
],
Also I used an array here as an ontology will be present sometimes in several repositories. Then of course the question of identifying the duplicates raises.
6- You need to complete the API with a call to isolate a concept only: /concepts/{URI-ID} for this you might need to use URL encoding of the concept URI.
7- For your /concepts call, you will need to implement some kind of iterator for ontologies that have a huge amount of concept or the API call will break/time out.
The text was updated successfully, but these errors were encountered:
(just copy paste the relavant points raised in email on Feb 1st - with enumerated points we can refer to in the tracker)
1- We often use Json-LD Playground to check the validity of the JSON generated. I am not fully aware of the specification, but in BioPortal we use @context to specify the properties
2- For the property includedInDataCatalog in the /ontologies call, indeed it needs to link back to the object defined in your own API then something like :
"includedInDataCatalog": [
"http://176.31.200.199/repositories/ols,
http://176.31.200.199/repositories/bioportal,
],
Also I used an array here as an ontology will be present sometimes in several repositories. Then of course the question of identifying the duplicates raises.
6- You need to complete the API with a call to isolate a concept only: /concepts/{URI-ID} for this you might need to use URL encoding of the concept URI.
7- For your /concepts call, you will need to implement some kind of iterator for ontologies that have a huge amount of concept or the API call will break/time out.
The text was updated successfully, but these errors were encountered: