Persistently identify semantic represenations of benchmarks and tool configurations

[doigl]

A semantic representation of benchmarks shall - among other aspects - specify in a machine readable way all input parameters and post-processing metrics. A representation of a tool configuration could adress a simulation code in a specific version with its dependencies and configurations.

This information should be placed in a knowledge graph for machine readability. To also offer some human readable information, we could provide landing pages basing on markdown/github pages

For identification, a prefix for persistent identifiers of the different benchmark scenarios should be used. My suggestion: a https://w3id.org/ in the namespace from nfdi4ing like w3id.org/nfdi4ing/benchmarks.

This would allow to support Content-Negotiation to redirect text/html requests to the human readable landing page and text/turtle requests to the rdf representation of the benchmark.