Stian Soiland-Reyes

Two approaches has emerged: - https://github.com/workflowhub-eu/workflowhub-graph/ is a pipeline that builds a knowledge graph of every RO-Crate in WorkflowHub, see documentation in https://doi.org/10.5281/zenodo.16992674 with some example visualisations - https://github.com/crs4/provenance-storage uploads...

Maybe @dgarijo is able to suggest some directions here?

There is also https://www.researchobject.org/workflow-run-crate/profiles/provenance_run_crate/#tool-runtime-environment in Provenance Run Crate but linking to a Conda environment

I agree this is not quite consistent. While JSON-LD supports and in many cases encourage the use of prefixes to use CURIEs, as @multimeric point out, in the RO-Crate spec...

btw as the expanded properties http://www.w3.org/1999/02/22-rdf-syntax-ns#Property do not give a human-readable representation, the RO-Crate 1.2 base profile has defined these https://www.researchobject.org/ro-crate/specification/1.2/ro-crate-preview.html#http%3A//www.w3.org/1999/02/22-rdf-syntax-ns%23Property but I notice that `rdfs:comment`, `rdfs:subPropertyOf` and `rdfs:subClassOf` are...

There is still inconsistency with the URL in https://schema.org/schemaVersion refers to https://schema.org/docs/releases.html#v10.0 which works (at least for humans) and links further to http://htmlpreview.github.io/?https://github.com/schemaorg/schemaorg/blob/main/data/releases/10.0/schema-all.html which says > This release, full core...

There is also https://github.com/schemaorg/schemaorg/releases/tag/v12.0-release etc. in GitHub, but these release pages do not currently contain any assets or documentation beyond a git tree snapshot. It would be OK if a...

To not rock the boat too much in sense of distribution/redirects/permalinks I suggest just that the schema.org downloads (not just NQ) self-declares their own version as such: ``` a schema:CreativeWork;...

Rebumping this as #2805 was closed, and now ALL older releases have disappeared, e.g. https://schema.org/version/12.0/ We have published contexts using: ``` }, "schemaVersion": { "@id": "http://schema.org/version/10.0/" }, ``` and ```...

@marc-portier can have a look