Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion during the development of the SmartAPI ontology lookup proxy #1

Open
jonquet opened this issue Feb 7, 2018 · 1 comment

Comments

@jonquet
Copy link

jonquet commented Feb 7, 2018

(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.

@jonquet
Copy link
Author

jonquet commented Feb 7, 2018

Point 2 is discussed more in issue #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant