-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use BioLink dataset class in metadata #3
Comments
it's a good question to ask the biolink developers. don't they include property mappings in the biolink spec? |
Yes, for some attributes Unfortunately the mapping is not displayed in the documentation UI: https://biolink.github.io/biolink-model/docs/has_numeric_value.html So the best way to access them is the YAML |
can you request that the mappings are displayed in the documentatioN? |
Already mentioned in the past, I just created an issue: biolink/biolink-model#278 |
This has been solved with the new documentation UI: https://biolink.github.io/biolink-model/docs/Disease.html @micheldumontier Let me know if this is enough for the moment A clickable link would have been preferable, but the mappings are stored as CURIE in the YAML, so they would need to be resolved by a service |
Map the generated HCLS metadata to the BioLink model.
BioLink have classes equivalent to dataset, version, distribution:
https://biolink.github.io/biolink-model/docs/DataSet.html
Should we use BioLink property when we can? Or HCLS? Or the 2?
e.g. for label
bl:name
,bl:id
,bl:category
)The text was updated successfully, but these errors were encountered: