In T2369#43635, @moranegg wrote:

The choice for IPOL is between:
[1] https://www.ipol.im/pub/art/2018/236/ -> link to metadata record containing article, code and demo
[2] https://www.ipol.im/pub/art/2018/236/mlheIPOL.tgz -> direct link to tar.gz
[3] https://doi.org/10.5201/ipol.2018.236 -> which is a PID recognized in the academic ecosystem

In T2369#43616, @zack wrote:

If we go for the DOI, shouldn't we converge on it also for other similarly archives, for the sake of uniformity? HAL comes to mind, of course.
(To be clear: I'm not proposing to uniform past deposits, but to change this for the future.)

The origin
For IPOL, we could use indifferently the DOI: https://doi.org/10.5201/ipol.2018.236 or the URL: https://www.ipol.im/pub/art/2018/236/, as it is trivial to convert the one into the other.

Our proposal to extend the CodeMeta vocabulary is based on the following nine roles identified in https://hal.archives-ouvertes.fr/hal-02135891v2/document :

Just checked with our contacts at Zenodo, it's now in production!

Oh, sorry for the noise...

This is now done in the few commits leading to https://forge.softwareheritage.org/rDMODaccca603c42ad68252532222ca6467a19691524e

• Further clarifications in the PID extension

• Clarify ambiguities in PID extensions

Ok, great!

It looks like the patch only fixes the issue for the gitlab.com origin, while the issue is present in all origins that are instances of GitLab, like https://gitlab.inria.fr/solverstack/maphys/maphys/

@zack thanks for spotting the missing pieces... now fixed in the description, we're ready to go! :-)
Would you take care of extending the definition in https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html ?

Update the proposal with visit instead of snp

About the anchor point: no objection to having also shapshot as a possible anchor in the schema.

As part of the discussion about the revamped UX, we have simplified the proposal for describing paths in the Merkle DAG. When the anchor denotes a revision (and most often when it's a release), it's trivial to find in the DAG the root directory of the source code, and we only need the file path to identify the content we are interested in. When it's a snapshot, there is a default root directory to point to.

Encoding the roles into existing property of CodeMeta or schema.org is a possibility.
The other, that I prefer, is to associate a "role" property to authors/contributors: indeed, an author/contributor may have multiple roles, just like multiple affiliations.

Here is a sample request provided by the ScanR developers to get all the metadata entries that can be found about software in ScanR

Chek with CodeMeta community that we are ready to communicate

What about try to resolve the origin url as it is, and in case of failure
retry without trailing slash?

I asked, and a patch will be welcome.