search

marco-bolo / dataset-catalogue

The index for MBO datasets
Creative Commons Zero v1.0 Universal
0 stars 0 forks source link

Metadata for software - codeMeta for early 2025 #32

Open kmexter opened 4 weeks ago

kmexter commented 4 weeks ago

As software is being produced in MBO (e.g. WP5) we will need to create a CodeMeta.jsonld template for them to fill in so they can be described in a m2m way. Required early 2025

dblear commented 2 days ago

@pbuttigieg to confirm if OIH holds software metadata and if there's example metadata in CodeMeta.jsonld ? If not where should it sit?

dblear commented 2 days ago

Will do a GA2025 session on this

pbuttigieg commented 2 days ago

@dblear yes - ODIS can relay software metadata .

https://github.com/iodepo/odis-in/tree/master/dataGraphs/thematics/software/graphs

pbuttigieg commented 2 days ago

what's "CodeMeta" ?

kmexter commented 2 days ago

https://codemeta.github.io/

pbuttigieg commented 2 days ago

I don't get what CodeMeta does that schema.org doesn't

https://raw.githubusercontent.com/codemeta/codemeta/master/codemeta.jsonld

it just looks like a partial implementation of schema.org

is there an example that shows its added value ?

kmexter commented 1 day ago

Sorry, was in meetings The thing CodeMeta provides are examples and templates (which one can modify) and that is useful to show people. I actually made one for some code we wrote for a project: https://github.com/arms-mbon/code_release_001/blob/main/codemeta.json. Am not sure I used it exactly as intended since I describe several codes in there, but so it is. So since OIH has some templates you provide above, and we have templates from CodeMeta, we could compare-mix-match-select and made some templates for MBO developers to use?

pbuttigieg commented 1 day ago

The thing CodeMeta provides are examples and templates (which one can modify) and that is useful to show people. I actually made one for some code we wrote for a project: https://github.com/arms-mbon/code_release_001/blob/main/codemeta.json. Am not sure I used it exactly as intended since I describe several codes in there, but so it is.

So it's a new context. This breaks semantic interoperability. It looks fine, but it's an n+1 standard situation.

So since OIH has some templates you provide above, and we have templates from CodeMeta, we could compare-mix-match-select and made some templates for MBO developers to use?

ODIS just uses schema.org, providing some illustrations on how.

I think schema:SourceCode does everything we need, and I still can't see any value in adding CodeMeta contexts

adding it will make it less interoperable

kmexter commented 1 day ago

I disgree - righth now there are no descriptions of the software developed under MBO, as no-one has been told to do so. So how can ensuring that a description, in RDF, exists, make it less interoperable?