Use BioLink dataset class in metadata

[vemonet]

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

• dct:title
• bl:name : ⚠️ no mappings to rdfs:label or dct:title in BioLink ontology
• set dct:title and bl:name (redundancy but we comply with the 2 models without the need for mappings and inference). It would only be for a few properties though (bl:name, bl:id, bl:category)

[micheldumontier]

it's a good question to ask the biolink developers. don't they include property mappings in the biolink spec?

[vemonet]

Yes, for some attributes e.g. https://github.com/biolink/biolink-model/blob/master/biolink-model.yaml#L1689 Search for mappings:

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

[micheldumontier]

can you request that the mappings are displayed in the documentatioN?

[vemonet]

Already mentioned in the past, I just created an issue: https://github.com/biolink/biolink-model/issues/278

[vemonet]

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