@vlorentz can we say that by using both CodeMeta and schema.org namespaces, we can use the roles in the metadata of a deposit?

The referencePublication property is available on the HAL preprod platform (waiting for deployment).
Also, IPOL is using the referencePublication property on the deposits to SWH.

https://hackmd.io/YIJXcf3YTDiwwYGD-yePrA

Here is the pad shared with the InvenioRDM team:
https://hackmd.io/YIJXcf3YTDiwwYGD-yePrA

We need to review this task with the current workflows.

In T2344#43031, @moranegg wrote:

Great news !!

Does this mean we need to be SWORD 3 compatible?

This is now published in CTAN (biblatex-software)

Here is the link to the open issue on the CodeMeta repository:
https://github.com/codemeta/codemeta/issues/240

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

they don't have to be single words. I'd say:

In T2329#43073, @moranegg wrote:

I've seen the new example, is this the right transformation?

I've seen the new example, is this the right transformation?

I just realized I didn't follow schema.org's roleName examples when writing this example. Could you copy-paste the new example from the pad, which uses "designer", "coder", and "documenter"?

If you agree with this proposal with @vlorentz's example, I can submit the issue tomorrow.

Great news !!

That's great news \o/ !

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

I do like the idea of adding a role to author, but the way schema.org is organized, is by adding properties with specific roles

I just discovered that there is a pending term maintaineron schema.org, thanks @vlorentz
for pointing this out.
https://schema.org/maintainer

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.

Taxon map:

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

Here is the first draft:
https://www.softwareheritage.org/?p=21219&preview=true

Chek with CodeMeta community that we are ready to communicate

Available here:
https://codemeta.github.io/codemeta-generator/

Thanks @anlambert ! That's great news !!

idutils 1.1.5 has been released and is now available on PyPI.

@rdicosmo , PR merged \o/ . SWH identifiers support will be available in the incoming idutils 1.1.5 release.

Pull request created: https://github.com/inveniosoftware/idutils/pull/54

I asked, and a patch will be welcome.

Opened this issue to inform Dirk Roorda:
https://github.com/annotation/text-fabric/issues/54

This is now done

review template with:

• @software for the software concept/project
• @softwareversion for a specific release
• @insoftware for a specific artifact in the software (e.g revision, directory, file)

review template with @software and @softwareversion entries

thanks @twitu for finding this location, if you see any other places dates are documented, feel free to comment here.

https://docs.softwareheritage.org/devel/apidoc/swh.model.html#module-swh.model.identifiers
This explains some of the fields associated with dates, timestamps and offset.

I too, two noticed the two glossaries. They have varying levels of explanations and merging them is one of the tasks I have considered for my GSoD application. I will be glad to assist in the process, in any way I can.

@zack: Good idea to have only one glossary.

I second the need of properly defining terms related to push archival.

Draft is done and was sent to Inria GT for feedback.