search

elixir-europe / human-data-maturity-model

Code for the ELIXIR Human Data Maturity Model website.
https://elixir-europe.github.io/human-data-maturity-model/
0 stars 2 forks source link

3.2.1 Interoperable metadata for discovery #17

Open MKonopkoELIXIR opened 1 year ago

MKonopkoELIXIR commented 1 year ago

What should the metadata structure be interoperable with in regards to 1+MG? Does 1+MG have a metadata framework in place? Should this indicator be re-written?

MKonopkoELIXIR commented 1 year ago

Contacted Michael Baudis for potential connection to Beacon

MKonopkoELIXIR commented 1 year ago

Per Michael Baudis: Beacon provides just the exchange framework (think formatting of URLs in www) and model (think required document structure - for a letter you need an address and sender and some content, w/ optional opening, topic ...). That's what Beacon defines; and some used formats (e.g. address, date .... have to have a certain format). But your topic is more about the content & the language; e.g. which parameters are needed (partially defined in Beacon, too), but mostly about the dictionaries (e.g. ontologies, standards). Here Beacon sits on the fence; some things are recommended, but overall we try to be agnostic.

So Beacon should be (one of the) protocol's to be considered for representing resource (metadata) content; the format of the metadata is then rather defined in e.g. the cohort specification, which itself refers to recommended ontologies ... for its values.